How Much Does It Cost to Build a Customer Portal

Most buyers asking what a customer portal costs are really asking two separate questions: what the application does, and which parts of it genuinely need to be custom. The honest answer sits in a wide band. A functional B2B portal MVP lands around $40,000. An enterprise portal with SSO, SCIM, deep ERP ties, and a real permissions model can clear $400,000 before the first bug report. The reason the range is so wide is that the word "portal" covers everything from a glorified document locker to a tenant-aware operational cockpit.

The pricing exercise worth doing is not tier shopping. It is module decomposition: pricing the specific capabilities you actually need, at the architectural depth you actually need them. Below is how senior engineers scope this work when a buyer asks for a defensible number.

The business case usually survives the sticker. Harvard Business Review research puts a single live support interaction above $7 for B2C and above $13 for B2B, with self-service running at pennies. Mature self-service programs report 25% to 40% reductions in live-agent contact volume. A portal that deflects even a thousand tickets a month pays for itself quickly, which is why so many budgets survive engineering review once the modules are itemized.

What a Customer Portal Actually Is

A B2B customer portal is a tenant-aware web application where a company's customers log in, see data about their own account, and complete self-service tasks against the vendor's backend. It is not a help center. It is not a marketing site with a login. The architecture that distinguishes a real portal is multi-tenancy, role-based access control, and bidirectional integration with the systems of record where customer data actually lives.

That architectural reality is why portal costs behave differently from marketing site costs. A static site scales with pages. A portal scales with roles, tenants, integrations, and the audit expectations of enterprise buyers. Adding a new customer segment to a brochure site is a navigation change. Adding one to a portal can mean new RBAC policies, new integration contracts, and a new round of security review.

Demand is pushing in the same direction. Roughly 95% of businesses report increased self-service demand, and about 63% of companies running portals see meaningful reductions in support workload. On the revenue side, B2B companies implementing eCommerce portals see an average 25% revenue lift and 45% faster procurement cycles. The portal is doing operational work the sales team used to do by email.

The Modules That Actually Drive Hours

Scoping by feature list gives bad estimates. Scoping by module gives defensible ones, because each module has a known architectural shape and a known integration surface. Seven modules account for most of the budget on a typical B2B portal.

Authentication and SSO

Email and password with MFA is a weekend of work when you buy it from Clerk, Auth0, or Supabase, and a month when you build it. Enterprise SSO is the real line item. SAML and OIDC against customers' identity providers (Okta, Entra ID, Ping) is where custom builds get expensive. Teams building admin dashboards and SSO plumbing from scratch typically spend 200 to 400 engineering hours on work that identity vendors have already solved. Budget $8,000 to $25,000 for a managed SSO integration with WorkOS or similar, or three times that if you insist on building SAML yourself.

Role-Based Access Control

RBAC is the module that separates toy portals from real ones. Three fixed roles (admin, member, viewer) is a week of work. Hierarchical roles with per-resource permissions, delegated administration, and an audit trail of policy changes is a quarter. Teams running Cerbos or Oso as a sidecar save weeks compared to hand-rolling a policy engine, which matters when the sales team is promising custom roles to every enterprise prospect.

Billing and Payments

Stripe Billing against a usage meter plus a self-serve plan change flow is $10,000 to $20,000 of integration work. Dunning, prorations, multi-currency, tax handling via Stripe Tax or Avalara, and reconciliation against an ERP ledger pushes that past $50,000. The hours live in the reconciliation code, not the checkout page.

Document Exchange

Signed URLs against S3 with virus scanning and audit logging is the baseline. Add e-signature via DocuSign or Dropbox Sign, versioning, retention policies for SOC 2 or HIPAA, and a reviewer workflow, and this module alone runs $15,000 to $40,000. Regulated verticals (healthcare, finance, legal) tend to live at the top of that range.

Ticketing and Case Management

Most portals should not build ticketing. They should embed Zendesk, Intercom, or HubSpot and theme it. Buyers who insist on native ticketing because "it needs to feel like one product" should expect to spend $20,000 to $60,000 recreating what the SaaS vendors already sell, and to maintain it forever. The embed route is usually two weeks of work and a monthly fee.

Notifications

Transactional email through Postmark or SES, in-app notifications backed by a Postgres table, and digest batching is $8,000 to $15,000. SMS, push, Slack, and webhooks for enterprise customers who want portal events in their own systems pushes that to $25,000 or more. Notification preferences per user per channel is the quiet complexity.

ERP and CRM Integrations

This is where estimates go wrong. Each integration with Salesforce, NetSuite, SAP, Dynamics, or HubSpot is its own project, with its own authentication model, rate limits, and data contract. A clean REST sync against a well-documented SaaS API is $5,000 to $15,000 per endpoint. A bidirectional sync with a legacy on-prem ERP, requiring a middleware layer and reconciliation jobs, can run $40,000 to $100,000 on its own. Our breakdown of API development and integration services walks through the patterns that keep this bounded.

What Changes Between an MVP and an Enterprise Build

The modules are the same. The depth is not. An MVP ships three fixed roles, email auth with Google OAuth, Stripe for billing, S3 for documents, embedded ticketing, email-only notifications, and one CRM integration. Two to three senior engineers can land that in 12 to 16 weeks at $40,000 to $120,000 depending on design polish and integration count.

An enterprise build adds SAML and OIDC SSO, SCIM provisioning for user lifecycle, hierarchical RBAC with custom roles, audit logging with a searchable viewer, multi-tenant data isolation enforced at the database layer, API keys and webhooks for customer-side automation, white-label theming, and typically three to six integrations with ERP, CRM, data warehouse, and support systems. That is a 6-to-9-month build with four to six engineers, landing between $200,000 and $400,000 before compliance work.

Compliance is the escalator. SOC 2 Type II readiness adds roughly $30,000 to $60,000 in engineering and audit prep. HIPAA and PCI add more. If your portal exposes anything a regulator cares about, scope the compliance work as its own module from day one. For a reference on how recurring infrastructure costs behave over the first twelve months, our writeup on production RAG system costs covers the same budgeting mechanics applied to AI features some portals now add.

Where the Rate Card Moves the Number

The same scope priced against different teams produces wildly different numbers. 2026 senior rates average $37 per hour in Eastern Europe, $66 in Western Europe, $28 in Asia, $50 in Latin America, and $31 in Africa. US senior engineers in major metros bill $150 to $250. A $200,000 portal from a US firm might quote at $80,000 from an Asian shop on paper. The honest question is whether the delivered software is the same.

Rate is one input. The others are architecture decisions made correctly the first time, integration contracts negotiated with the customer's IT before code is written, and a product owner who can say no to scope. Buyers evaluating offshore quotes should price in the rework and the coordination overhead honestly. For how team shape affects the number, our writeup on dedicated team cost covers the staffing math in detail.

What a Defensible Estimate Looks Like

Ask any vendor for a flat number and the quote will be either padded or unreliable. Ask for a module-by-module breakdown with assumptions named, and the conversation changes. A defensible estimate names which auth provider, which RBAC pattern, which billing engine, which integration endpoints, and which compliance target. It separates one-time build from year-one run cost. It calls out the two or three modules where scope will likely grow and prices the contingency explicitly.

Before signing anything, pin down which integrations are launch-blocking versus phase-two, whether SSO is launch-day or post-GA, and who owns the data contract with each system of record. Our checklist on what to include in a software development RFP is a reasonable starting point for the questions worth asking.

A Working Answer

Price a B2B customer portal by its modules, not its tier. An MVP that solves one real problem for one customer segment can ship for $40,000 to $120,000. A production portal with enterprise auth, real RBAC, and two or three serious integrations lands between $150,000 and $300,000. An enterprise platform with SSO, SCIM, audit logging, compliance posture, and deep ERP ties runs $300,000 to $400,000 and often more. The number that matters is not the headline. It is the one you can defend module by module when the CFO asks why.