Not accepting new projects. The spec is what drives development, and our engineers are at capacity writing them. Write to us anyway and we will tell you when that changes.
Accepting new projects. We have engineer capacity for spec work and can start a first feature spec with you.
Contact
The smallest useful engagement is a single feature spec. We draft it, you approve it, and you watch the whole cycle run once — spec, approved tests, automated gates, showroom — with no obligation beyond that one feature.
What to send
Writing the spec is our job, not yours. What helps most in a first message is the problem in your own words, who the system is for, and any constraint that is already fixed — a deadline, a platform, an integration you cannot change.
You get back a draft feature spec. You read it, we correct it together, and you approve it or you do not. Nothing gets built before that.
Approval. Specs are drafted on our side, but no feature advances without your formal, recorded approval of the version it is built from. A fortnightly meeting is the working rhythm; we adjust the cadence to the project.
Our engineers are at capacity on spec work. Agents do the building; people write and approve the specifications, and that is the part we cannot run more of in parallel. We will tell you where you sit in the queue rather than start something we cannot staff.
Inherited codebases. The method assumes every existing behaviour is specified, which a pre-existing system does not satisfy, so you would be paying for a guarantee you would not actually get. New projects only.