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.

Software development

Your features ship in days, not months.

One feature at a time, at a price agreed before it is built. You can stop after any of them.

Your project, today Refunds and cancellations
You agreed it14 September
Pricefixed that day, in writing
Built15–18 September
├A refund inside 30 days is accepted works
├A refund after 30 days is refused works
├The customer is told why works
└Nobody is refunded twice works
Right nowrunning in your private environment
Waiting onyou, to put it in front of customers

What you are buying

A price and a date you can plan the rest of your business around.

Every feature is priced and defined before anyone starts building it. You are not billed by the hour, so nobody profits from the project taking longer, and there is no invoice you have to take on trust.

Then it takes days. Not because people work harder, but because your features are built in parallel by machines instead of queuing behind one team of developers — and because you are not waiting weeks for anyone to check that work by hand.

If something goes wrong

Three moments where a software project normally goes off the rails

You asked for one thing and got another

Before anything is built, you approve a plain-language description of what the feature will do. It spells out what counts as working, in terms you can test yourself.

If what arrives does not match it, fixing that is our cost, not yours.

It reaches your customers broken

Every finished feature first runs in a private environment that is yours to use exactly as a customer would, for as long as you want.

Nothing reaches your real users until you say it does.

You change your mind halfway

Normal, and planned for. A change is quoted before it is made, so you decide with the number in front of you.

What you never get is an argument about whether it was already included. The document you approved settles that in one reading.

While it is being built

You can check on your project at 2am without asking anyone

Everything being built for you sits in a dashboard you have access to: what is agreed, what is in progress, what is waiting on you, and every question we have had to raise. There is nothing about your project that we can see and you cannot.

An engineer works alongside you on every one of those documents. You describe the problem; we write the version precise enough to build from; you approve it or send it back.

In English or in Spanish, your choice — the documents you approve, the dashboard and the meetings. You are never approving something written in a language you have to work in rather than think in.

Fit

This works for you if

You are building something new, you are the one who decides what it should do, and you would rather pay a fixed price per feature than fund an open-ended team. You do not need to be technical.

This does not work for you if

You have an existing system you want maintained or extended. Everything here depends on the product being written down before it is built, and an inherited codebase never is, so you would be paying for a guarantee you would not actually receive.

Getting started

Try it on one feature

Pick the smallest thing your product needs. We write the definition, you approve it, and you see it running in your own environment before committing to anything larger.

If you want the mechanics first: how we work, and the full set of rules your project would be run by.