What does a customer portal cost?
A customer portal isn't a brochure site: people log in, see their data, and complete tasks. Price follows mainly from roles, data integrations, and how many workflows must run in version 1.
Updated 2026-08-02 · 8 min read
Short answer
A focused first version of a customer portal or dashboard often sits in the mid-range of custom web apps: more than a marketing page, less than a full SaaS with billing. Exact cost depends on screens, permissions, and data sources.
Don't ask 'what does a portal cost?' Ask 'what three things must the customer be able to do in week one?'
Concrete starting prices for dashboards and portals are on the pricing page.
What is a customer portal here?
A logged-in environment where customers or partners see status, fetch documents, submit tickets, track orders, or manage data. Often with an admin side for your team.
That needs authentication, a data model, and reliable integrations. Those three drive budget more than colors or animations.
What determines the price?
- Number of user roles (customer, partner, admin, internal)
- Number of core flows in v1 (view, upload, approve, order…)
- Sources: own database, ERP, CRM, email, file storage
- Realtime or notifications versus periodic sync
- Design: template/sober or full brand UI
- Security requirements: SSO, 2FA, audit logging
- Migration from spreadsheets or an old portal
Indicative ranges
Simple portal: login, one dashboard, limited documents or status. Scope stays narrow.
Mid-sized: multiple screens, roles, notifications, and one or two serious integrations.
Heavy: SSO, complex permission matrices, many sources, and workflows critical to operations. Plan in phases.
Ranges are direction. A quote follows after mapping data and must-have flows.
Common pitfalls
- Moving everything from the old intranet in one go
- Defining roles too late ('who may do what?' stays vague)
- Underestimating integrations: 'we already have an API' isn't a plan
- No owner for content/data quality on your side
An approach that keeps budget manageable
1. Jobs to be done
Three to five tasks customers must really be able to do. Everything else is backlog.
2. Data map
Where does the truth live? What do we sync, what do we show read-only?
3. Ship a slice
First one role and one flow live, then expand. You learn before you build everything.
When I can help
Looking for a Next.js customer portal or dashboard and a realistic estimate? I sharpen scope and integrations first, then a proposal without fluff.