Why there's no single number
A single-role internal tool with one database table costs a fraction of a multi-role client portal with billing integration — both are "web applications" in name only. Cost tracks scope, not the category label.
What actually drives cost up
- Number of distinct user roles and permission boundaries
- Data complexity — how many entities, how they relate to each other
- Number and complexity of third-party integrations
- Whether AI features are read-only (cheaper) or take actions (more testing required)
- Whether the product needs to scale to meaningful concurrent usage from day one
Rough shape, not a quote
A narrowly-scoped internal tool or MVP with one role and simple data is the cheapest end. A client portal with multiple roles and CRM/billing integration sits in the middle. A multi-role platform with complex workflows and heavy integration sits at the top — these are directional, not quotes, since the same category can vary 3-5x based on the factors above.
How to get a real number
Through a Product Scope conversation once the actual workflow and data model are understood — not a generic "packages" page, since the honest range depends entirely on the specifics above.
Questions
Is this cheaper or more expensive than a website?+
Almost always more, since it involves persistent data, authentication and often integrations — a website is a content product, not comparable scope.
Does this include ongoing hosting and maintenance?+
Hosting and maintenance are typically scoped and priced separately, agreed upfront rather than assumed.
Can I start smaller and expand later?+
Yes — an MVP-first approach (see SaaS MVP Development) is often the more honest path than committing to full scope before validating it.