Web Portal Development Cost in 2026: Customer, Partner and Employee Portals

The short answer

A portal is a logged-in web application where a specific group of people (customers, partners, employees, patients, suppliers) sees their own data and gets things done without calling you. That last part is what you pay for. The login screen is cheap. Showing each user the right orders, invoices, tickets and documents from three back-office systems, and letting them act on that data safely, is where the hours go.

If what you are building is less a portal into existing systems and more a product of its own, our guide to web application development cost is the better fit. For an internal sales system with a customer-facing side, see custom CRM development cost.

Cost by portal type

"Portal" covers very different projects. The audience decides the permission model, the integrations and the compliance load, so it decides most of the budget before anyone draws a screen.

Partner portals surprise buyers most often. The screens look like a customer portal, but the data model has an extra layer: a partner is a company, its people have different rights, and prices or discounts differ by tier. That layer alone is often 15–25% of the build.

What each portal module costs

Every portal quote is a sum of modules. The ranges below include design, development and testing for each piece, built by an offshore or nearshore team.

Integrations are the line that moves budgets most. A portal is usually a window into systems you already run, and the window is only as good as the data behind it. One "read-only view of orders from our ERP" can mean a clean REST API and three days of work, or a nightly CSV export and three weeks of reconciliation logic. We cover that range in API integration cost.

Where the money goes

A portal has four layers, and buyers tend to budget only for the one they can see. This is how they usually split in a mid-size customer portal of about $150k.

For a phase-by-phase and role-by-role view across all software types, see our software development cost breakdown.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Size your portal

Pick the portal type, the number of user roles and integrations, and the modules you need. The calculator estimates hours, build cost by team location, a rough timeline, and a three-year total next to a per-user platform license for comparison.

Two quick checks. A customer portal with 3 roles, 3 integrations, payments and documents lands at about 1,850 hours, or roughly $110k with a Central/Eastern European team. Move the same scope to a US agency and it is about $275k. Then slide the active users to 10,000 with a $3 license: three years of licenses alone reach about $1.1M, which is why high-volume customer portals so often end up custom.

Platform portal or custom build

Before pricing a custom portal, check what the systems you already pay for can do. Most CRMs, ERPs and help desks sell a portal add-on, and for some projects it is the right answer.

The license side, at 2026 list prices:

• Salesforce Experience Cloud: Customer Community licenses are listed at around $2 per login or $5 per member per month, and Customer Community Plus (more data access, reports) at around $6 per login or $15 per member. Partner licenses cost more. Volume discounts can be steep, so treat list prices as a ceiling.
• Microsoft Power Pages: $200 per 100 authenticated users per site per month at the entry tier, dropping to $75 per 100 at 10,000 users and $50 per 100 at 100,000. Anonymous visitors are billed separately. Capacity applies per site, so two portals mean two license pools.
• Help desk and ERP portals: many ticketing tools and ERPs include a basic customer portal in higher plans. Cheap and fast, but limited to the data that system holds.

How the choice usually plays out in the projects we look at:

• Platform wins when users are few (hundreds, not thousands), the data lives mostly in that one platform, and the portal can look like the vendor's template. You launch in weeks and pay a configuration partner instead of a build team.
• Custom wins when monthly active users run into the thousands, the portal pulls data from several systems, the experience is part of your product or brand, or per-user pricing punishes growth. It also wins when you want the option to switch CRM or ERP later without rebuilding the portal.
• The hybrid is common. Keep Salesforce, Dynamics or NetSuite as the system of record and build a custom portal that reads and writes through their APIs. You pay platform licenses for internal staff only. Our enterprise app development cost guide covers the identity and compliance side of that setup.

How team location changes the price

For the same mid-size portal of about 2,200 hours, region moves the price more than any feature decision. These are typical 2026 vendor rates for a blended team (engineers, QA, design, PM).

Rates are not the only difference. Latin America gives US teams the most time-zone overlap, which is why it is called nearshore. Central and Eastern Europe, where Gilzor works from Poland and Cyprus, is offshore for the US: Warsaw is six hours ahead of New York, which leaves two to four shared hours with the East Coast on shifted schedules and very little with the West Coast. Portals suit that setup well, because the work runs on written specs, clickable designs and weekly demos rather than constant live calls. For a US baseline: according to the US Bureau of Labor Statistics, the median annual wage for software developers was $135,980 in May 2025, before benefits, recruiting and management overhead. Our nearshore software development rates guide compares regions across stacks.

Which build approach fits your portal?

Six questions on the factors that decide platform vs custom, and how big the first release should be.

The costs that don't show up in the first quote

A build estimate covers building. These items arrive later, and we see them catch buyers out in most portal conversations.

• Maintenance: 15–20% of the build cost per year. Security patches, framework upgrades, browser changes, bug fixes and the steady trickle of small requests once real users arrive. Our software maintenance cost guide breaks it down.
• Hosting and identity. Cloud hosting, backups, a CDN, plus an identity provider that often bills per monthly active user, with enterprise SSO features on higher plans. For a portal with a few thousand users, $500–2,500 a month across hosting and services is typical.
• Integration upkeep. When your ERP is upgraded or a vendor changes its API, the portal shows stale or wrong data. Budget a few days per integration per year, more for older systems.
• Security testing. A portal exposes internal data to the internet by design. Plan an independent penetration test before launch and once a year, plus fixes. Customers' security questionnaires will ask for it.
• Compliance. Patient portals bring HIPAA safeguards, business associate agreements with every vendor that touches health data, and audit logs. Payment features bring PCI DSS scope, which you mostly avoid by using hosted payment fields so card data never touches your servers.
• Accessibility. WCAG 2.1 AA is the standard US regulators and plaintiffs' lawyers point to. The Department of Justice requires it for state and local government sites and apps under ADA Title II; an interim rule in April 2026 moved the first deadline to April 2027. Private companies face demand letters and lawsuits under Title III. Designing for it from the start costs a fraction of retrofitting.
• Content and onboarding. Knowledge base articles, help text, invite emails, and the effort of moving existing customers onto the portal. Adoption does not happen by itself.

Overruns are common enough to plan for. The Standish Group's CHAOS research has for years rated only around three in ten software projects as fully successful (on time, on budget, with the planned scope). A 2012 McKinsey and University of Oxford study of large IT projects found they ran on average 45% over budget and delivered 56% less value than predicted. Portals that integrate many back-office systems carry exactly that kind of risk.

What we see in portal estimates and first calls

• "Customers should do everything themselves" is not a scope. In a survey of almost 5,800 customers that Gartner published in 2024, it found only 14% of service issues are fully resolved in self-service, and only 36% of issues customers call very simple. The portals that pay back are built around the five or six requests that fill your support inbox, not around every possible action.
• The data is not where people think it is. In discovery, "the order status is in the ERP" often turns into "partly the ERP, partly a spreadsheet the warehouse updates." Finding that in week two costs little. Finding it in month five resets the timeline.
• Permissions get specified last and cost the most. Who at a client company can see invoices? Can a regional partner see another region's deals? Write the permission matrix before design starts.
• The admin side gets forgotten. Your support team needs to see what a user sees, reset access and fix data. Without an admin back office, every support request becomes a developer ticket.
• Testing every role is real work. Five roles across twenty screens is a hundred combinations. Our own metric is that only 5% of tasks sent to QA come back to developers, and that comes from testing each task with each role as it is built, not in a bug-hunt at the end.

How to reduce the cost without breaking the portal

1. Start from support data. Rank the requests users make most often and build those first. A short business analysis phase that ends with a task list, a permission matrix and a data map makes every later estimate accurate.
2. Launch read-only, then add actions. Showing orders, invoices and documents is far cheaper than letting users change them. Many portals cut support load with a read-only first release, then add self-service workflows. Our MVP development cost guide covers how to size that release.
3. Buy identity, payments and e-signature. Use a proven identity provider, hosted payment fields and an e-signature service. Monthly fees are small next to the weeks of work and the security risk of building them.
4. Put one integration layer in the middle. Connect each back-office system once to a small integration service, not directly from every screen. It costs a little more up front and much less every time a system changes.
5. Use a component library. Portals are forms, tables and dashboards. A solid design system and component library cuts front-end time without making the portal look generic.
6. Defer the mobile app. A responsive web portal covers most use cases. Add a native app only when usage data shows people need push notifications, offline access or the camera.
7. Keep QA in every sprint. A portal bug can show one customer another customer's data. Cutting QA is the most expensive saving you can make.

FAQ

Where Gilzor fits

We build customer, partner and employee portals and the integration layers behind them. A typical engagement starts with discovery to fix the task list, permissions and data sources, then a phased build with our web development team, QA in every sprint and, where users need it, a mobile app. If you already have an in-house team, our engineers can join it through development support.

Send us your user types, the systems the portal must read from and what your support team spends its time on. We will size the first release, estimate the full build and tell you honestly when a platform portal is the cheaper route.