What will it cost to build?
Pick what you are building and what it needs to do. You get the scope in hours, a realistic timeline, the team it takes, and a budget range - before you talk to anyone.
Questions people ask
- How accurate is this estimate?
- It is a range, and the range is wide on purpose. Before anyone has seen your requirements, a single number would be a guess dressed up as a promise. The hours come from how we have actually scoped comparable projects - our largest recent platform came in at 3,086 hours over 31 weeks with a team of five to six, and the model is calibrated against work like that.
- What is not included?
- Ongoing support, infrastructure costs and third-party licences. Design, development, QA and release are included.
- Why does compressing the timeline cost more?
- Because the work does not shrink - it just runs in parallel. More people at once means more coordination, more overlap and more rework, and that shows up as hours rather than as a discount on weeks.
- What makes the number move most?
- Unclear requirements, by a wide margin. A week of discovery upfront typically halves the range. After that: integrating into systems you already run, and any compliance regime that adds review cycles which are not development time at all.
- Do I have to talk to sales to get the breakdown?
- No. Leave an email and the full module-by-module breakdown arrives by email. If you want a scoped estimate after that, reply to it.