Web App Scope Estimator
Early app scope is driven more by roles, workflows, integrations and trust boundaries than by screen count alone. This score supports discovery; it is not a quote.
Need an independent review of your growth model?
Review your digital marketing unit economics with our senior growth specialists in a direct diagnostic session.
📧 Email me this Web App Scope Estimator forecast — get a summary with your inputs and an actionable roadmap.
Why screen count is a poor guide
People often describe an app by its screens. But effort in a web app comes mostly from who uses it, what they need to get done, what it connects to and where mistakes would be costly. A portal with ten screens and four user roles, each with different permissions, can take far more work than a twenty-screen app with one type of user.
This estimator gives an early scope score from those factors. Use it to decide how much discovery, prototyping and risk review your first release needs before you ask for estimates.
The four inputs
Distinct user roles. Different types of user with different permissions or views: customer, staff, manager, admin, partner. Every role multiplies the screens, rules and tests needed.
Core workflows. The main jobs the app must support from start to finish, such as "submit an order", "approve a leave request" or "generate an invoice". Count end-to-end processes, not individual screens.
External integrations. Other systems the app must exchange data with: payment gateways, CRM, accounting, SMS or WhatsApp, maps, identity providers. See CRM integration for one common case.
High-risk custom areas. Parts where errors have serious consequences or where nothing off-the-shelf exists: payments and refunds, medical or financial data, complex pricing rules, real-time features, data migration from an old system.
How the score is calculated
The score adds weighted points: 2 per user role, 3 per core workflow, 5 per integration and 8 per high-risk custom area. High-risk areas carry the most weight because they need the most design, testing and review. The weights are a planning convention, not a measured effort.
Reading your result
A higher score suggests more discovery and prototyping before development, and a stronger case for a smaller first release. High-risk areas deserve early technical proof-of-concept work, because surprises there cost the most. The score isn't a fee or a timeline. Our guide to app development cost factors explains what else affects price, and our web application development page explains how we run discovery.
Frequently asked questions
Is this an estimate of cost or time?
No. It's a planning score to help decide how much discovery and risk review you need.
How do I count workflows?
List the main tasks users complete from start to finish. Variations of the same task usually count once.
What if I'm not sure about integrations yet?
Run conservative and full-scope versions. The difference shows how much integrations matter for your project.
Is my data stored?
The calculator runs in your browser. Details are only sent if you choose to email yourself the result.