Customer Portal Cost Guide: How Much Does a Customer Portal Cost?

If you have started looking into customer portal costs, you have probably encountered a wide range of figures. Some vendors quote £500 per month. Others quote £80,000 upfront. Neither figure is wrong — but they describe very different products.

The truth is that a customer portal is not a single product. It is a category that spans plug-and-play ISV add-ons, low-code platform builds, and fully custom web applications. The cost varies by a factor of ten or more depending on which route you take, what features you need, and which ERP system sits behind it.

This guide breaks down the three tiers of customer portal cost, what you actually get at each level, and the factors that push the price up or down. No fluff. No hidden fees. Real numbers you can take to a budget meeting.

The Three Tiers of Customer Portal Cost

Customer portals broadly fall into three pricing tiers. Each serves a different type of business and a different set of requirements.

Tier 1: ISV Add-On (£15,000–£50,000 per year in licensing)

ISV add-ons are commercial off-the-shelf portal products sold by ERP partners. If you run Dynamics 365 Business Central or Sage 200, your ERP partner probably offers one. Examples include Simova and similar add-on modules.

How pricing works: You pay an annual license fee based on the number of users or the volume of transactions. Setup and configuration cost extra. The portal is hosted by the ISV on multi-tenant infrastructure.

What you get:

• Pre-built, standardised portal features — order tracking, invoice viewing, statement download
• Limited customisation — brand colours and logo, sometimes layout
• Read-only access to a fixed set of ERP objects
• Multi-tenant hosting — your portal shares infrastructure with other customers
• Vendor-managed updates (but also vendor-dictated update schedules)

Who it suits: Businesses with straightforward, standardised portal needs. If every customer gets the same experience and you do not need custom workflows, this is the easiest option to procure.

The downsides: Annual licensing costs add up quickly. Over five years, a £30,000-per-year add-on costs £150,000 — plus setup fees. You do not own the code. You cannot extend the portal beyond what the vendor has built. And if you change ERP systems, the add-on is useless.

Tier 2: Power Pages (£2,000–£12,000 per year + Power Platform licensing)

Microsoft Power Pages is a low-code portal builder within the Power Platform ecosystem. It connects to Dataverse and, through Power Automate and connectors, can surface data from ERP systems like Business Central.

How pricing works: Power Pages pricing is based on authenticated users per month. A typical mid-market deployment with 100–500 customer users costs roughly £2,000 to £12,000 per year in Power Pages licensing. On top of that, you need Power Apps per-user or per-app licenses, Power Automate consumption, and Dataverse storage.

What you get:

• Low-code portal builder with templates and drag-and-drop components
• Authentication via Microsoft Entra ID or built-in provider
• Integration with Dataverse and, through connectors, with ERP systems
• Content management capabilities built in
• Microsoft-hosted infrastructure

Who it suits: Organisations already invested in the Microsoft ecosystem. If you use Power Apps internally and have Power Platform expertise in house, Power Pages can be a cost-effective route for a basic portal.

The downsides: Power Pages is constrained by Dataverse. Data must flow from your ERP into Dataverse before the portal can display it — adding latency, cost, and a sync failure point. Write-back (letting customers place orders or update details through the portal) is technically possible but complex to implement reliably. Performance degrades at scale. And you are locked into Microsoft’s portal roadmap — if they deprecate a feature or change pricing, you have no recourse.

Tier 3: Custom-Built Portal (£20,000–£80,000 fixed price)

A custom-built portal is a web application developed specifically for your business. Built with a modern tech stack (typically React, Next.js, TypeScript), it connects directly to your ERP system’s REST API in real time.

How pricing works: Fixed-price build based on a defined scope. No per-user licensing. No annual license fees. You pay once for the build and then a monthly fee for hosting and maintenance.

What you get:

• Full control over features and functionality — nothing is off-limits
• Your own branding, UX, and workflows, designed around how your customers actually behave
• Real-time read and write access to your ERP data via its native API
• You own the intellectual property and the source code
• Dedicated hosting on your choice of cloud (AWS, Azure, or GCP)

Who it suits: Businesses that need more than a standardised portal. If you need write-back (customers placing orders, submitting returns, updating account details), complex business logic, or a bespoke user experience, custom is the only option that delivers.

The downsides: Higher upfront cost. Longer delivery timeline (typically 6–12 weeks versus 2–4 weeks for an ISV add-on). You need to manage the relationship with a development partner rather than just procuring a license.

Comparison Table: 10 Factors Across the Three Tiers

The headline takeaway: ISV add-ons look cheap upfront but become expensive over five years. Power Pages looks cheap on paper but the hidden costs (Dataverse sync, licensing complexity, limitations) add up. Custom-built sits in the middle on total cost but gives you ownership and flexibility that neither of the others can match.

What Affects the Cost of a Customer Portal

Regardless of which tier you choose, several factors will push the cost up or down.

Feature Set

The biggest cost driver is what your portal actually does. A read-only portal showing order status and invoices is at the bottom of the price range. A portal that lets customers place orders, manage their account details, submit returns, view delivery schedules, and communicate with your team is at the top. Each additional feature adds design, development, testing, and integration effort.

ERP Platform

The cost varies significantly depending on which ERP system sits behind the portal. Systems with mature, well-documented REST APIs (like Dynamics 365 Business Central) are cheaper to integrate with than older systems with limited or proprietary APIs (like Sage 200 or older on-premise ERPs). If your ERP requires custom API development or middleware, expect costs to increase by £5,000–£20,000.

Write-Back (Read vs Read-Write)

Read-only portals are significantly cheaper than portals that write data back to your ERP. Write-back requires idempotency handling, validation logic, error handling, and transaction management. It also introduces risk: if your portal writes bad data into your ERP, you have a real problem. A write-back portal can cost 40–60% more than a read-only portal of equivalent scope.

Number of Customer Users

For ISV add-ons and Power Pages, user count is a direct cost driver because licensing is per-user. For custom-built portals, user count affects hosting and support costs but not the build cost. A custom portal serving 100 customers costs roughly the same to build as one serving 1,000 customers.

Branding and Design

Basic branding (logo, colours, font) is cheap. A fully designed user experience with customer journey mapping, user research, and usability testing adds £5,000–£15,000 to the build cost. For customer-facing portals, this investment almost always pays for itself in adoption rates.

Integration Depth

Does your portal need to show data from multiple systems? A portal that pulls order data from your ERP but delivery tracking from a logistics system and invoice PDFs from a document store is more expensive to build and maintain than one that reads everything from a single source.

Ongoing Costs: What Happens After Launch

The build cost is only half the picture. Every portal has ongoing costs that need to be budgeted for.

Hosting: £100–£500 per month for a custom-built portal on cloud infrastructure. ISV add-ons include hosting in the license fee. Power Pages hosting is bundled into the Power Pages license.

Maintenance: Expect £300–£1,000 per month for security patching, dependency updates, and platform monitoring. For ISV add-ons, maintenance is included. For custom portals, this covers keeping your application secure and compatible with evolving browser and API versions.

ERP API changes: When your ERP vendor updates its API (which happens 2–4 times per year for cloud ERPs), your portal needs to stay compatible. Minor changes are typically covered by maintenance. Major version updates may require additional development work.

Feature evolution: Your portal will never be finished on launch day. Customers will request new features. Your business will evolve. Budget 15–25% of the original build cost per year for ongoing feature development in years two and beyond.

ROI: How Quickly Does a Customer Portal Pay for Itself?

The return on investment for a customer portal comes from several sources. Here is how the math works for a typical mid-market manufacturer or distributor.

Reduced sales team workload: Salespeople spend 2–4 minutes per call answering order-status queries. In a business handling 50 such calls per day, that is 100–200 minutes of sales time daily. At even a modest blended rate, a portal that eliminates these calls saves £15,000–£30,000 per year. Most portals eliminate 60–80% of order-status calls.

Fewer invoice queries: Accounts receivable teams field invoice and statement queries daily. A portal with invoice visibility eliminates the majority of these. For a team of two handling AR, that is 20–40% of their time freed up — worth £10,000–£20,000 per year.

Faster payment: Customers with direct access to invoices and statements pay faster. Businesses that have implemented customer portals report average payment time reductions of 5–12 days. For a business with £5m in annual receivables, that improvement unlocks £70,000–£165,000 in working capital.

Customer retention: A portal is a sticky feature. Customers who use your portal are less likely to move to a competitor. Quantifying this is harder, but for competitive markets, a portal can be the difference between retaining and losing a £200,000-per-year account.

Payback period: Most well-designed customer portals pay for themselves in 12–18 months through operational savings alone. When you factor in working capital improvements and retention benefits, the payback period shrinks to 6–12 months.

FAQ: Customer Portal Cost Questions

1. What is the cheapest way to build a customer portal?

Power Pages is the cheapest entry point from a licensing perspective, starting around £2,000 per year. However, the total cost of ownership depends on your requirements. If you need write-back, complex workflows, or high performance, a custom-built portal often works out cheaper than trying to make Power Pages do things it was not designed for.

2. Why do some portals cost £500/month and others £50,000?

The £500/month option is almost certainly a shared, standardised ISV add-on with limited features and no customisation. The £50,000 option is a custom-built portal designed specifically for your business. They are fundamentally different products serving different needs. Comparing them on price alone misses the point.

3. Do I need to pay per customer user?

With ISV add-ons and Power Pages, yes — licensing is typically per authenticated user per month. With a custom-built portal, no — you pay a fixed build cost and then a hosting fee regardless of how many customers use it. This makes custom portals significantly more cost-effective at scale.

4. How long does a customer portal take to build?

ISV add-ons can go live in 2–4 weeks. Power Pages portals typically take 4–8 weeks. Custom-built portals take 6–12 weeks depending on scope. The timeline difference reflects the difference in flexibility and capability.

5. Can I move my portal to a different provider later?

If you own the code (custom-built), yes — you can take it to any hosting provider or development team. If you use an ISV add-on or Power Pages, no — you are locked into that vendor. Rebuilding on a different platform means starting from scratch.

6. What ongoing costs should I budget for after the build?

For a custom-built portal, budget £6,000–£18,000 per year for hosting, maintenance, and security. Add 15–25% of the original build cost per year for feature evolution. For ISV add-ons, the annual license fee covers most ongoing costs, but feature additions may incur separate charges.

---