One fixed price, agreed before we start.
Every build is scoped in a short paid discovery and then priced as a number that does not move unless the scope does. These are the floors, so you know before the call whether we are the right size.
Starting points.
Floors, not quotes. Discovery ends in a one page brief and the actual number. Most builds land within a third of the floor once the scope is written down.
| From | What it covers | |
|---|---|---|
| Discovery | from $1,500 | One to two weeks. Ends in a one page brief and a fixed price. Credited to the build if you go ahead. |
| 3D website | from $4,000 | A scroll-driven film hero or a three.js scene, real copy, schema, analytics, launched in one to two weeks. |
| AI automation | from $6,000 | The first workflow live against real data by week three, with the human checkpoints decided before code. |
| Integrations and modernization | from $8,000 | One connection or one seam at a time, with rollback at every step and no big bang cut over. |
| Custom software and SaaS | from $15,000 | Tenancy, roles, billing and the data model decided once. Weekly releases to staging from the third week. |
| Retainer | from $3,000 a month | For teams that keep shipping after launch. A fixed number of engineering days a month, rolled over within the quarter. |
| Advisory | from $1,200 a week | An engineer in the room for a decision that needs one. Architecture reviews, vendor selection, hiring. |
| Workshop | from $2,500 a day | One to three days with your own team when they are going to build it. You leave with the plan and the first slice working. |
Discovery is credited to the build if you go ahead. Every project price includes a month of support after launch and the code, in your own accounts.
How a fixed price is reached.
Discovery first, one to two weeks, paid. We map the workflow as it really runs, including the workarounds nobody wrote down, and we read the code if there is code. It ends in a one page brief that says what is being built, what is not, and what it costs.
Then the number is fixed. It does not move unless the scope does, and a scope change is priced in writing before it is built. There is no hourly rate to run over and no percentage of anything.
You see working software from the third week, on a staging address you can log into, not a slide about it. Weekly releases after that, until the Monday your team is using it.
Week one and two
Discovery. The brief and the fixed price.
Week three
The first working slice on staging.
Launch
Migration, training, and a month of support in the price.
What every build includes.
The discovery brief
One page. What is being built, what is not, and the number. Yours whether or not you go ahead.
Weekly staging releases
From the third week. You log in, you click, you tell us what is wrong while it is cheap to fix.
A month of support
After launch, in the price. Most clients keep a small retainer after that; nobody is required to.
The code, in your accounts
Repository, hosting, domains and keys are yours from day one. A handover you cannot execute is not ownership.
If you run a practice, the pricing is different.
The content system for healthcare is the one thing with a public monthly price: $600 a month for one provider, priced by volume, plus a one-time $1,000 studio session that happens once and never again.
It has its own page because it is a product, not a build. The numbers there are the numbers; nothing is quoted.
Questions people ask first
Bring the problem. Twenty minutes is enough to know whether it is worth building, and roughly what it costs.
Or write a few sentences on the contact page. A reply from a person within one working day.