Customer Portal Software vs Building Bespoke: How to Decide

If you’re evaluating customer portal software, you’ll find no shortage of options. Clinked, Huddle, Salesforce Experience Cloud, SharePoint, HubSpot’s client portal, and dozens of others all offer some version of the same proposition: a secure, branded space where your customers can log in, find information, and manage their interactions with your business.

For a lot of organisations, one of those products is exactly the right answer. For others, it’s a compromise that looks affordable at the outset and becomes expensive later — in licence fees, workarounds, and the cost of processes that don’t quite fit.

This article covers the decision honestly. When does off-the-shelf software make sense? When does building bespoke make sense? And what does the decision actually look like when a real business works through it?

What is a customer portal?

A customer portal is a secure, authenticated digital space where your customers log in to interact with your business: to access their account information, submit requests, track orders or cases, download documents, manage warranties, or complete any other task that would otherwise require a phone call or email.

The defining characteristic is that the portal is specific to each customer. Unlike a public website or a knowledge base, a portal serves personalised content — your data, your orders, your history — and typically connects to the systems that hold that data: your ERP, CRM, warranty database, or back-office platform.

That integration requirement is where the off-the-shelf vs bespoke question usually starts to matter.

What off-the-shelf customer portal software does well

The strongest case for off-the-shelf software is speed and simplicity. If your portal needs are relatively standard — document sharing, support ticket submission, knowledge base access, basic account management — a well-chosen product can be live in weeks, not months, at a fraction of the cost of a custom build.

Off-the-shelf products also come with ongoing development built into the subscription: security patches, new features, compliance updates, and mobile apps are handled by the vendor. For a small team without dedicated development resource, that managed-service model has genuine value.

It works well when:

• Your portal needs are generic — document access, ticket submission, account lookup

• You don’t need deep integration with proprietary back-office systems

• Speed to launch matters more than exact fit

• You have limited internal development capability for ongoing maintenance

• Your customer base is relatively homogeneous — one type of user, one workflow

Where off-the-shelf software runs out of road

The limitations of off-the-shelf portal software tend to fall into three categories: integration depth, workflow specificity, and user experience control.

Integration depth

Most portal products connect to popular platforms via standard connectors — Salesforce, HubSpot, Zendesk, Google Workspace. If your data lives in a proprietary ERP, a bespoke back-office system, or a specialist industry platform, those connectors don’t exist. You’re either building a custom integration on top of the product — which often costs as much as a bespoke build — or accepting that the portal and your systems won’t talk properly, which defeats much of the purpose.

Workflow specificity

Off-the-shelf software is built for general use cases. If your customer workflow is specific — a multi-step product registration process, a warranty claim that triggers an automated service reminder, a trade installer completing a job record on a mobile device in a location without signal — you’re bending the software to fit a process it wasn’t designed for. That usually means manual steps to bridge the gaps, which reduces the efficiency the portal was supposed to create.

User experience control

Most portal products allow branding customisation up to a point: colours, logos, domain. The underlying structure, navigation, and interaction patterns are fixed. For a business where the portal is a significant customer touchpoint — something that 1,000 trade installers use daily as part of their job — the constraints of a product’s UX template can become a real limitation.

What bespoke customer portal development makes possible

A bespoke portal is built to your exact specification: your data model, your workflow, your integration requirements, your user experience. There are no constraints imposed by what a third-party product does or doesn’t support.

That means:

• Integration with any back-office system, however proprietary, because the integration is engineered specifically for it

• Workflows built around how your business and your customers actually operate, rather than adapted to fit a generic model

• A user experience designed for your specific user type — which matters significantly when the portal is used daily by people doing a job, not just occasionally by customers checking an order

• Ownership of the platform — no recurring licence fees, no dependency on a vendor’s pricing decisions or product roadmap

• The ability to extend and adapt over time without being constrained by what the product permits

The trade-off is upfront investment and build time. A bespoke portal costs more to start with and takes longer to get to launch. That’s a genuine consideration, and the right answer depends on the specifics.

Case study: Grant UK G1 — a portal built for 1,000+ trade installers

Grant UK is an award-winning heating systems manufacturer that has been designing and making products since 1970. With over 1,000 accredited G1 installers across the UK, they needed a portal that could handle the full product registration lifecycle — from initial registration through to warranty tracking, service reminders, and maintenance scheduling.

Off-the-shelf portal software wasn’t considered seriously, for a straightforward reason: the core requirement was deep, real-time integration with Grant’s proprietary back-office systems. Standard portal connectors don’t exist for bespoke ERP environments. Building a custom integration on top of a third-party portal would have introduced a maintenance overhead and a dependency on the product vendor that Grant didn’t want.

16i built the G1 portal from the ground up on a .NET stack. The key features were determined by how installers actually work:

• A summary dashboard showing each installer’s own customers, recent registrations, and upcoming service due dates — personalised by installer account

• A step-by-step product registration workflow integrated live with Grant’s back-office, so data entered by an installer flows directly into Grant’s systems without manual re-entry

• Full warranty and registration history, with filtering so installers can quickly find a specific customer or product and confirm warranty status before a maintenance visit

• Automated service reminders on login — removing the need for installers to manage their own follow-up calendar

• A companion iOS and Android app, developed alongside the portal, that allows installers to submit registrations on the move — including in rural locations without a data connection, using barcode scanning to pull in product serial numbers

The portal replaced a process that had required manual data entry in multiple systems. The integration means Grant’s back-office records are updated in real time as installers complete registrations, with no duplication and no data integrity risk.

The decision framework: six questions to ask before you choose

These are the questions that determine whether off-the-shelf or bespoke is the right answer for your project. Work through them honestly before committing to either path.

• Question

  Off-the-shelf if…

  Bespoke if…

  How complex is your
  back-office integration?

  Standard platforms
  (Salesforce, HubSpot, Zendesk)

  Proprietary ERP, bespoke back-office,
  or specialist industry systems

  How specific is your
  customer workflow?

  Generic — document access,
  ticket submission, account lookup

  Multi-step, industry-specific,
  or tightly coupled to your operations

  How many users, and how
  often do they use it?

  Occasional use, mixed
  user types

  High-frequency, daily use by a defined
  user group (e.g. trade partners)

  How important is the
  user experience?

  Functional is sufficient

  The portal is a primary customer
  touchpoint; UX affects outcomes

  What is your three-year
  cost horizon?

  Low upfront is the priority

  Licence fees + workaround cost will
  exceed bespoke build cost over time

  Do you need offline or
  mobile capability?

  Browser-based access is sufficient

  Field workers, rural locations,
  or native app required

What does a bespoke customer portal cost?

The honest answer is: it depends on scope. A portal with a defined user group, a single integration, and a clear workflow is a different undertaking from a multi-integration platform serving several distinct user types.

As a rough guide:

• Portal type

  Typical range

  Single integration, defined user group,
  focused workflow

  From £25,000 — 8 to 14 weeks

  Multiple integrations, varied user types,
  complex workflow

  From £60,000 — 16 to 24 weeks

  Enterprise platform with multiple
  environments and phases

  Scoped individually after discovery

These figures assume a professional .NET development team with proper discovery, UX design, build, QA, and deployment. They do not include ongoing hosting and support, which should be factored into the three-year cost comparison with any off-the-shelf subscription.

At 16i, we scope portal projects during a discovery phase rather than quoting upfront. The discovery conversation is how we establish what the portal actually needs to do, which is the only honest basis for a realistic figure.

Working with 16i on a bespoke portal

16i is a B Corp-certified bespoke software development agency based in Cheltenham. We build customer portals, trade platforms, and business applications in .NET — engineered around your specific workflows and integrated with your back-office systems rather than constrained by what a third-party product permits.

If you’re evaluating a portal project — whether that’s a first-time build, a migration from an off-the-shelf product that’s run out of road, or an extension of an existing platform — we’d welcome a conversation about what’s involved.

Get in touch at hello@16i.co.uk or call +44(0)1242 654 000.