An app cost calculator that shows its arithmetic.

No, and it never becomes one. It is an indicative band: a starting package from our published 2026 bands, plus the features you ticked priced at real engineer-weeks × our published rates. What it cannot see is your data model, your legacy systems, the quality of the APIs you need to integrate with or the reliability bar you need on day one — and those are exactly what move a real number. The fixed price comes out of a paid discovery sprint, in writing, and the sprint is credited in full against the build.

One place: our published 2026 rate card. The starting packages are the typical all-in bands for a first production release. Every feature block is priced as engineer-weeks × the monthly rate of the role that actually does the work, divided by four — because a working month with us is 160 hours, which is four 40-hour weeks. The component computes each figure live from the rate card rather than storing it, so nothing can drift, and the derivation for every block is written out in the source.

The package band pays for the foundation — architecture, the design system, CI/CD, QA, a delivery lead and the release — plus the scope its own description names. Those building blocks are pre-ticked and marked 'in the package', so nothing is charged twice. Only what you add beyond them moves the number, and each addition appears as its own line with the engineer-weeks and the role behind it.

Because a single number before discovery would be false precision. The spread between the low and the high end is the honest width of what is still unknown — how clean the integrations are, how much of the edge-case behaviour surfaces once real users arrive, how strict the compliance evidence has to be. Where scope is genuinely fixed we do publish exact prices: support plans, DevOps retainers and setup packages all carry a precise figure.

This estimator works in US dollars. Swiss and EU clients are quoted in Swiss francs or euros from the same 2026 rate card — your contact issues that edition with the proposal, so the figure you sign is in your own currency. We publish one currency here rather than a converted one, because a rate we fixed months ago would quietly drift from the market.

No. The estimator runs entirely in your browser: nothing you tick is saved, transmitted or attached to analytics, and no email address is required to see the result. The project brief leaves the page only when you copy it and choose to send it to us.

Send it and we come back with a high-level estimate — the first workshop and that estimate are free, usually within three working days. If it looks like a fit we propose a paid discovery sprint: workflows mapped, integrations named, the v1 cut-line drawn, an architecture and a costed roadmap you keep whatever you decide next. The fixed quote is written from that document, the sprint cost is credited in full against the build, and 100% of the code and IP transfers to you if we build.