Build vs Buy a Customer Portal: An Honest Decision Framework for Mid-Market B2B

If your customers, members or partners keep emailing your team for updates, documents and status, you have probably reached the same conclusion as most mid-market operators: you need a portal. The harder question is whether to buy one off the shelf or build your own. Get it wrong in either direction and you pay for it for years, either in licence fees for software that never quite fits, or in a bespoke project that runs long and over budget.

This post gives you an honest framework for the decision. It is the keystone of our wider work on customer portals for mid-market B2B, and it deliberately avoids the usual vendor answer of "build, obviously, talk to us". Sometimes buying is the right call. Here is how to tell the difference.

The one rule that settles most of it: buy the commodity, build the differentiator

Almost every build-versus-buy decision comes down to a single principle. Buy the commodity. Build the differentiator.

A commodity is something hundreds of businesses need in roughly the same shape: email, payroll, accounting, helpdesk ticketing. You should never build these. A vendor has already solved the problem better than you will, and they spread the cost across thousands of customers. Buying is cheaper, faster and lower risk.

A differentiator is something specific to how your business runs. The way a customer moves through your onboarding. The exact documents a member needs to see and sign. The status your partners chase you for. The data sitting in your CRM and finance system that would answer their question if they could just see it. This is where a generic product fights you, and where a custom build pays for itself.

So the real question is not "is a portal a commodity or a differentiator?" It is "which parts of my portal are commodity, and which parts are the thing customers actually came for?"

When buying off the shelf is the right call

Off-the-shelf is the correct decision more often than custom-software vendors like to admit. Buy when:

• Your need is standard. You want a login, a place to download invoices and a knowledge base. A vendor built for exactly that case will serve it well and cheaply.
• A product exists for your exact vertical and workflow. If a SaaS portal is purpose-built for your kind of membership body or your compliance regime, and it matches how you already work, that is a strong signal to buy.
• The portal does not touch your differentiated process. If what customers see is generic information that does not depend on your unique data or rules, there is nothing to differentiate.

When these are true, buying is not a compromise. It is the disciplined choice. Do not build a worse version of something you can rent.

The hidden costs of buying that the demo never shows

The trap is assuming "buy" means "cheap and done". The licence fee is the visible cost. The expensive costs surface later:

• Per-seat fees, forever. Off-the-shelf portals usually charge per user per month. That is fine at fifty users and painful at five hundred. As you grow, the tool you bought cheaply becomes a line item you cannot switch off, and your success makes it more expensive.
• Integration limits. Most products integrate with a fixed list of systems in fixed ways. If your stack is not on the list, you are stuck. Proper, two-way integration between a portal and your core systems is the difference between a portal that informs customers and one that just looks the part.
• It cannot show live CRM data. This is the big one. A bought portal typically cannot surface a customer's real, current record from your CRM: their live order status, their open items, their actual next step. So customers still email to ask, and your team still answers manually. The portal exists but the chasing does not stop.
• It bends your process to its shape. The product has opinions about how onboarding, approvals and notifications should work. If they do not match yours, you change your process to suit the software. Over time the tool dictates how your business operates, which is exactly backwards.
• Data ownership and lock-in. Your customer interactions accumulate inside someone else's platform. Exporting cleanly when you outgrow it is rarely as simple as the sales call suggested.

None of this means "never buy". It means price the whole cost, not just the sticker, and be honest about whether the product can ever do the differentiated job you actually need.

When to build

Build when the portal touches the parts of your business that make you who you are. Specifically:

• The portal is the experience your specific journey requires. Customers expect it to behave the way your business behaves, not the way a generic template behaves.
• It needs to show live data from your systems. If the whole point is letting customers self-serve their real status, documents and records, the portal has to read and write to your stack with your CRM as the single source of truth.
• Your rules, fields, permissions and notifications are specific. Who sees what, when, and what triggers an alert is particular to you, and a product's fixed options do not cover it.
• Per-seat economics break at your scale. When you are heading towards hundreds of users, a one-off build plus hosting often beats an ever-climbing subscription.

If two or more of these are true, you are looking at a differentiator, and renting a commodity will not deliver it.

Custom does not mean a 12-month bespoke project

The reason teams default to buying is fear of the build: the bespoke project that takes a year, blows its budget and ships late. That fear is reasonable, because plenty of custom software is delivered exactly that way. But it is not the only way to build.

A SpotDev customer portal is fixed-price from £15,000 and launched in 30 days from contract signing. That is possible because we do not start from a blank page. We build on established portal foundations, reusable journey patterns and an in-house engineering team that works on this operational software all day. You pick proven journeys, typically three, and we adapt them to your brand, systems, data, fields, permissions, notifications and integrations. It is productised scope on a genuinely custom build, not a generic template you log into. We have built portals for clients including Superior, Wolsey Hall Oxford, Icon Solutions and L&DI.

The 30-day timeline depends on a fixed scope, fast access to the systems we need to connect, and prompt feedback from your side. There is working software within about two weeks, and it is ready for real users by day 30. We back it with a written guarantee: miss the agreed launch date and we refund the first payment in full, and you keep everything built. No clauses. Open-ended product development, complex legacy rebuilds, bespoke mobile-app functionality and data-cleansing projects sit outside the fixed price, which is how the date stays firm.

So the honest version of "build" for a mid-market B2B (£3m to £50m revenue, 30 to 500 employees) is not a 12-month gamble. It is a fixed-price, fixed-date project that lands in a month. That changes the maths of the whole decision. For the detail, see our guides on custom customer portal cost in the UK and how long it takes to build a customer portal.

The decision checklist

Run your situation through these and count your answers.

1. Does the portal need to show each customer their live, real data from your CRM or core systems? Yes leans build.
2. Are your journeys, rules, permissions or notifications specific to how you operate? Yes leans build.
3. Will you have hundreds of users, where per-seat fees compound against you? Yes leans build.
4. Is the need genuinely standard (login, downloads, knowledge base) with no differentiated logic? Yes leans buy.
5. Does a product exist for your exact vertical and workflow that matches how you already work? Yes leans buy.

If you land mostly on "buy", buy with confidence and do not over-engineer. If you land mostly on "build", the next decision is what to build and what it should cost, not whether to fear the timeline.

Frequently asked questions

What is the simplest way to decide between building and buying a customer portal?

Buy the commodity, build the differentiator. If the portal only needs to do standard things hundreds of businesses need in the same shape (login, document downloads, a knowledge base), buy it. If it has to reflect your specific journey, show live data from your CRM, or follow rules and permissions unique to you, build it. Most decisions resolve once you separate the commodity parts from the parts customers actually came for.

Why can't an off-the-shelf portal just show my customers their live CRM data?

Most bought portals integrate with a fixed list of systems in fixed ways and were not designed to surface each customer's real, current record from your CRM. So customers still email to ask for status and your team still answers manually. The portal exists but the chasing does not stop. Showing live, per-customer data with your CRM as the single source of truth usually requires a custom build with proper two-way integration.

Doesn't building a custom portal take a year and cost a fortune?

It can, if it is delivered as an open-ended bespoke project. It does not have to be. A SpotDev customer portal is fixed-price from £15,000 and launched in 30 days from contract signing, because it is built on established portal foundations and reusable journey patterns rather than from a blank page. You pick proven journeys, typically three, adapted to your brand, systems, data and rules. There is working software within about two weeks.

What are the hidden costs of buying an off-the-shelf customer portal?

The licence fee is the visible cost. The expensive ones surface later: per-seat fees that climb as you grow, integration limits when your stack is not on the vendor's list, an inability to show live CRM data, having to bend your own process to fit the software's opinions, and data lock-in that makes leaving harder than the sales call implied. Price the whole cost over several years, not just the sticker.

When is buying off the shelf genuinely the right choice?

Buy when your need is standard, when a product exists for your exact vertical and workflow that matches how you already work, and when the portal does not touch your differentiated process or require live data from your systems. If you only need a login, downloads and a knowledge base at modest user volumes, a purpose-built product will serve it well and cheaply. In that case, buying is the disciplined choice, not a compromise.

When you are ready to scope a build, our customer portal service is fixed-price from £15,000 and live in 30 days, integrated with your systems and built around your journeys. To pressure-test the wider decision first, the pillar guide on customer portals for mid-market B2B covers the full landscape.