Pricing
Three tiers. Every line visible.
Lean, standard and premium — itemized line by line, with a blended total rather than a rate card. You choose how much of the build to buy, and you can see exactly what each tier carries.
| Line item | Lean | Standard | Premium |
|---|---|---|---|
| Core scope, as specified | ●included | ●included | ●included |
| Test coverage 80%+ | ●included | ●included | ●included |
| Security review | ●included | ●included | ●included |
| Admin console | —not in this tier | ●included | ●included |
| Reporting dashboard | —not in this tier | ●included | ●included |
| Second language | —not in this tier | —not in this tier | ●included |
QA and security sit in every tier. They are never what a smaller tier removes.
We never print certainty the specification does not have.
Where the scope is firm, the price is fixed. Where it is not, the quote says so in writing — before you sign, not after.
The second list
What the price excludes, in writing
Every quote ships with a second list headed Not in this release — the adjacent features that usually ride along unspoken. Each carries a backlog price, so adding one later is a number rather than a negotiation.
The quote is defined by both lists.
In this release priced
- Booking flow
- Card payments
- Admin console
Not in this release backlog
- Second language
- SSO / SAML
- Push notifications
Changes
What changes a price after you have it
A broken assumption
Every estimate rests on written assumptions — English only, under ten thousand users, you provide the content. If one turns out to be wrong, that is a pre-agreed trigger to re-quote, not an argument.
A change you ask for
Priced as a delta before you approve it — never discovered in an invoice.
Change request
Add single sign-on
There is no rate card and no per-role rate to decode — every line shows a blended total.
Defined by both lists
Describe your project. See what comes back.
No signature, no call. A business email unlocks the full quote.