Contact
Talk to an engineer
Not a sales queue. Tell us what you are building and someone who has delivered this kind of product will read it, challenge the assumptions worth challenging, and reply with something you can plan against.
What happens next
An engineer reads it
Your answers go to someone who has delivered this kind of product, not to a form filler.
We push back in writing
You get the parts of your estimate we would challenge, and the reasoning for each one.
A call, only if it helps
If it is useful to both of us, we talk. If it is not, you keep the analysis anyway.
About the cost calculator
Five questions, each one a screen of real options rather than a field to fill in. It takes about a minute and the calculation runs in your browser.
What it asks about
- Where it runs — one platform or several
- Who it serves, and the obligations that brings
- What kind of product it is
- How much of it exists on day one
- How many people will use it
- Features, integrations and third-party services
- Design depth, backend shape and security posture
- Compliance regimes, never inferred
What comes back
- An itemised US cost range with a stated confidence band
- Engineering hours by discipline
- A delivery timeline and the team shape it assumes
- The architecture tier the traffic demands
- The same build priced at four different scopes
- Cloud and vendor running costs, kept separate from the build
- Annual maintenance, kept separate again
- Every assumption behind the number, listed
You can also start from something that already exists: pick a product in the library of 128 app cost guides and the calculator opens with that product’s shape already selected, so you are editing a real scope rather than building one from an empty list.