The person who scopes your build writes it, reviews it, and picks up when it breaks. Nothing is handed down to whoever is free.
Auditable, documented and handed over so your team can run it without us. The expensive thinking happens before the first release.
Retrieval and agent workflows that cite where an answer came from, so your team can check it rather than trust it.
Your code, your keys, your data, self hostable where that matters. No lock in and no licence you have to keep paying to read.
I run the studio and I hold a full time engineering role. Neither one is a hobby.
Since 2025
I decide what we take and what we turn down, set the architecture, review the code, and sit in the client calls myself. A few projects at a time, deliberately, so every one has a senior on it.
Islamabad, on site
Production code every week. Retrieval over Postgres databases holding millions of records, agent workflows on LangChain and n8n, Next.js front ends, AWS underneath. When it breaks at two in the morning it is my phone.
proposeAI, DevFlow AI, ColorDrop
Devyst ships its own software alongside the client work, two of them open source. They are how we test an opinion before charging someone else for it.
AI SaaS product · 2025
A proposal engine for freelancers. A job post goes in and a pitch written for that specific client comes out.
The decision
Self service or not at all
Agentic AI system · 2025
An engineering workspace that replaces the daily standup and answers questions about a codebase with citations to the file and line.
The decision
Give away the thing we could have charged for
Custom SaaS, under NDA · 2025
A usage based billing engine for enterprise contracts, where every contract carries its own tiers, overage rules and terms.
The decision
Contract terms are configuration, not code
I would rather ship a smaller system that holds than a bigger one that demos well.
Almost all of the cost of software arrives after launch: a schema you can no longer change, a query that slows every month, an integration nobody owns. None of it shows up in a demo, because a demo runs on clean data with one user and somebody watching.
So I spend the expensive time early, on the parts nobody asks to see. It makes the first release slower and every release after it faster, and that trade has never once gone against me.
A small bench, on purpose. Every project has someone senior on it and nothing goes to whoever is free.
We say no often. A studio that needs the next contract cannot afford to turn down bad work.
Configuration over code for anything a client will want to change.
Email reaches me fastest and I reply inside a day. If it is a fit I will say so, and if it is not I will tell you that too.
