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 itYour answers go to someone who has delivered this kind of product, not to a form-filler.
- We push back in writingYou get the parts of your estimate we would challenge, and the reasoning for each one.
- A call, only if it helpsIf it is useful to both of us, we talk. If it is not, you keep the analysis anyway.
About the app cost calculator
Sixteen questions, each one a card you click rather than a field you fill.
What it asks about
- App category and revenue model
- Registered and active users
- API traffic and peak concurrency
- Media and storage volume
- Platforms and features
- Backend and cloud infrastructure
- Third-party integrations
- Design depth, security and compliance
- Team shape and timeline
What comes back
- An itemised US cost range, broken down by workstream
- A delivery timeline
- A recommended team
- A suggested architecture
- Separate figures for cloud infrastructure and annual maintenance — the two lines most estimates leave out entirely
You can also start from something that already exists: pick a product in the app cost library and the wizard preloads the features that kind of app almost always ships with, so you are editing a real scope instead of building one from an empty list.