Client work
Every client, exactly where you left it.
You move between clients all day. DevSpec keeps each one whole. The decisions, the reasons, what was agreed and why, and coding agents that arrive already knowing.
Exports either download, or say what went wrong
Stay quiet while it is still retrying. Once it has given up, say so. The March call to never interrupt someone over a retry was right for a blip and wrong for a real failure.
Webhook signatures verify out of band
Inline verification blocked the worker pool under load. The constraint was latency, not security.
New people read the record first
Do not recap a settled decision in the room. Point at the memory. The next agent arrives already knowing.
What was decided on this client, and why. Waiting for you when you come back.
The Switch
Changing clients costs you an hour you never bill
Every switch starts the same way. You open the repository and try to remember what you decided, why you decided it, and what you promised would be ready. None of it is lost. It is in commits, in threads, in someone's notes, in a call nobody recorded. But it has to be reassembled before you can start, and you do that several times a day across every client on your books. Past a certain number of clients, the reassembling is the job.
You had twenty minutes between two calls. Fifteen of them went on working out where you left off.
The Multiplier
You already know this problem. You have it once per client.
Every coding agent has to be told how the codebase works. So you write the rule files, you paste in the architecture, you explain the convention somebody settled on months ago. A team working on its own product pays that cost once, against one codebase, and can keep the file roughly current because there is only one of it.
You pay it per client. Six clients is six architectures, six sets of conventions, six sets of decisions taken by six different groups of people, and an agent that knows none of it until you say it again. The cost of explaining a codebase does not fall as you take on more clients. It multiplies.
DevSpec holds that context per project and gives it to the agents you already run. What was decided, what it was decided instead of, and what everyone agreed to build. Your agent opens a client project knowing the things you would otherwise have retyped.
A rule file rots on one product. Across a book of clients it was never going to be current in the first place.
The Record
When they ask why it works that way
Months in, somebody asks why the export behaves the way it does, or whether they ever asked for the thing that is now missing. Usually the answer lives in a thread nobody can find, or in the memory of whoever happened to be on the call.
In DevSpec the answer is in the room, dated and attributed, sitting next to the work it produced. Not a defence you have to assemble. A record that was already there.
The same record that answers your client is the one your agents read before they write anything.
The Shape of It
How it works when the work is for someone else
Four things worth knowing before you put a client engagement in here.
Is this for you?
You build software for other people. Every client is a different codebase, a different set of decisions, and a different set of people who have to sign things off. Nothing about that fits a tool built for one team working on one product.
One organisation. One project per client.
Your company is the organisation. Each engagement is a project inside it, with its own repositories, its own decisions and its own record. Spend is broken down per project, so you can see what each client actually costs you.
Your client sees what you decide they see.
Bring named people from a client into one project as guests, so they can specify and sign off on their own work. Or keep it to your own team and share what you choose. Projects stay separate: a guest on one client project cannot see another.
A product owner who can answer a question in the room beats a product owner who answers it three days later by email.
The record shows who directed the work.
Agents do the building. The decisions, the acceptance criteria and the sign offs carry the name of the person who made them. When you show a client what happened on their project, it shows your people making the calls.
Put one client in and see.
Start with a single engagement. Connect the repository, hold one session about what you are building, and come back to it tomorrow to see what changed.
Start your projectStart with $15of usage, on us · nothing charged until you buy