Fixed price. Locked scope. One builder.
Most software projects do not fail for technical reasons. They fail because nobody wrote down precisely what was being bought, the price moved once work was underway, and the results were never really measured. Everything below exists to take those three failures off the table before you spend anything.
Four rules we do not break.
These are not marketing lines. Each one is a decision that costs us something, which is the only reason it is worth telling you about.
Agree in writing before you pay
We map the process and write down exactly what the tool will do, what it connects to, and what is deliberately left out. You approve that plan first. The investment and the delivery day are fixed at that moment, and the plan is free whether or not you go ahead.
One fixed investment, no meter running
You are never billed by the hour and there are no change orders. If the work turns out to be too big for one build, we say so and quote it plainly rather than letting the number drift while you are already committed.
You own everything at the end
The code, the database, the accounts and the hosting are handed to you. Walking away from us never costs you your tool, which means we have to keep earning the next project instead of holding the last one hostage.
We only claim what is measured
No invented results, no borrowed logos, no numbers nobody checked. Where we show proof we say exactly what it is and who measured it, including when the honest answer is that we measured it ourselves.
What actually happens, and when.
A three week build only works because the thinking happens before the clock starts. Here is the whole sequence, including the parts that happen before you have paid anything and after the tool is live.
The free plan
We meet and you walk us through the process as it really runs, including the workarounds. We write down the tool, the connections, the exclusions, the fixed price and the delivery date.
What the plan contains
The users, the data, the rules, the systems it must talk to, the awkward cases, and an explicit list of what is not part of this build. That last list prevents most disputes before they exist.
You approve, and only then
Nothing is built and no money moves until you have read and approved the plan. Half the rate books your dates. If we conclude a build is the wrong move for you, we say so, and you keep the plan.
If the work does not fit
Usually it can be split so the first build stands on its own and the rest is quoted separately. Occasionally the right answer is that you need a different kind of firm, and we will tell you that.
The build
Evan builds the screens, rules, data and connections. You see progress as it lands rather than waiting in silence, which is how wrong assumptions get caught on day three instead of day nine.
What gets built beyond the screens
Empty states, bad input, permissions, failed connections and the awkward cases your team meets in month two. These are inside the rate.
Your review, then launch
You test the full process described in the plan against real work. We fix what is wrong, launch, and hand over the code, database, hosting, accounts, a walkthrough video and plain written notes.
What the review is not
It is the moment to catch what does not match the plan, not the moment to add a second project. New ideas are welcome and get their own quote.
The support window
Anything broken in the agreed tool is fixed at no cost for a full month after launch. After that you own a working tool outright and owe us nothing at all.
What happens later
Some clients come back for a second build once the first has proved itself. That is quoted in writing, at the same published price. There is no retainer and no ongoing fee.
What happens if we are late.
If we miss the delivery date, the final payment waits and we keep working at no added cost until the tool described in the plan is in your hands. That is the whole penalty, and it falls on us, because we are the ones who chose the date.
This covers the work in the approved plan. It does not cover features added later, and it depends on you giving us access, files, feedback and approvals within one business day, since a short build cannot absorb a week of waiting. We also cannot control outages at another company whose system we are connecting to.
Bring us the process. We will tell you plainly if it fits.
Evan Atha reads every request himself, usually the same business day, and the written plan costs nothing either way.