How long will your app take to build?
WeBuildStack is a remote-first software development company in Bengaluru, India, that builds web and mobile applications and the cloud behind them. This project scoper turns five answers about a web or mobile application into a timeline, team size and effort range, before a written, fixed quote from a tech lead in Bengaluru, India.
Five questions, two minutes. You get a timeline, a team size and an effort range. Then a written, fixed quote within 48 hours, deployment included.
- 1 Written quote in 48 hoursOne 30-minute call, then a fixed scope and figure in writing.
- 2 Kickoff within a weekNamed tech lead, shared board, discovery workshop in week one.
- 3 Demo every FridayWorking software weekly, deployed free to your cloud account.
What the scoper is actually doing
The same arithmetic a tech lead does on the first call, written down so you can check it. It produces effort, a team and a timeline. The price comes with the written quote, after we have seen your requirements.
- 1
Platforms set the base
Each platform you tick carries a base amount of engineering effort: a web app is the largest, then iOS, Android and an admin panel. If you pick both iOS and Android we assume one React Native or Flutter codebase, so the second platform adds less than half of its own base rather than doubling the work.
- 2
Screens scale it
Size is a multiplier on that base. A small product of five to ten screens is a little over half the effort of a medium one; a large product of twenty-five screens or more is close to double. Screens are the best single predictor we have found, because every screen needs design, state, an API and tests.
- 3
Features add fixed blocks
Each feature adds its own block of effort on top, and the blocks are not equal: login and roles is the smallest, real-time chat and AI features are the largest, payments and dashboards sit in between. When a feature has to work on more than one platform, its block grows a little, because it is built once and tested everywhere.
- 4
Design and starting point adjust the total
A standard UI kit trims the total; premium design with motion raises it by about a quarter. Extending an existing codebase is cheaper than starting fresh because the foundations exist, while a rebuild or migration costs a little more than new work: the old system has to be understood, mapped and switched over without losing data.
- 5
QA and project management are always in
We add a fifth on top of the engineering effort for testing, release management and the tech lead's time. It is not optional and it is not a line you can remove to get a lower number; it is the part that makes the Friday demos work.
- 6
Effort decides the team, the team decides the weeks
Total effort picks the team size in steps: two engineers for a small build, three or four for most products, six for the largest, always with a tech lead reviewing. Weeks are effort divided by what that team realistically delivers in a week, never shorter than three. The range you see allows for the unknowns that only show up once we read your requirements; the written quote closes it.
- 7
Anything over six weeks is split
If the full scope lands beyond six weeks, we do not stretch the first release. The core flow ships as a six-week MVP, deployed and usable, and the remaining features follow in sprints with a demo every Friday.
It is a ballpark based on the effort we see across our projects, typically within ±25% for well-understood scope. A written quote after a scoping call is binding.
The same feature can take a day or a month depending on integrations, edge cases and design polish. The range narrows as soon as we see your requirements.
Third-party fees: cloud usage, app-store accounts, SMS, email and payment-gateway charges are billed by those providers directly to your accounts. Deployment itself is included.