The phone is the status update
"Where's my order" and "where's my case up to" fill your team's day when the answer already exists in a system, just not one the customer can see.
✦ Customer portals
A customer portal gives your clients a place to check status, raise requests, view documents and pay invoices without phoning your office. Off-the-shelf client portal software covers standard cases well. We build the portals that need to reflect a specific B2B process, integrate with systems a generic tool can't reach, or carry your own workflow rather than the vendor's.
✦ Where it hurts
"Where's my order" and "where's my case up to" fill your team's day when the answer already exists in a system, just not one the customer can see.
Contracts, invoices, reports and certificates emailed one at a time, with no single place a client can find them again.
Generic client portal software assumes a simple ticket-and-reply model, and your actual workflow - approvals, multi-stage jobs, account hierarchies - doesn't map onto it.
B2B customers need several of their own people to see different things, with permissions that generic tools don't model well.
The information customers want lives in your CRM, ERP or job system, and a bolt-on portal can't reach it without real integration.
A portal that looks and feels like a third-party tool undermines the relationship you've built rather than reinforcing it.
✦ The honest bit
If your customers mainly need to raise a support ticket, check a simple order status or view a handful of standard documents, a package such as Zendesk, HubSpot's client portal or your existing helpdesk's self-service module will do the job well and far more cheaply than a bespoke build.
The same applies if you have a small number of customer types and the workflow is genuinely generic - ticket in, response out, document attached. That is what off-the-shelf tools are built for, and buying is the right call.
Bespoke earns its cost when the portal has to reflect a specific B2B process: multi-stage approvals across an account hierarchy, live data pulled from your own ERP or job-management system, account-specific pricing or documents, or a workflow that is part of what makes your service distinct.
We'll be direct about this on a scoping call. If a configured off-the-shelf tool covers 80% of what you need and the remaining 20% isn't worth the cost of a custom build, that's what we'll recommend.
✦ What we build
Built as a genuine extension of your core systems, not a separate silo customers have to trust alongside them.
✦ Decision
| Situation | Likely right answer |
|---|---|
| Simple support tickets and standard document sharing | Off-the-shelf client portal software |
| One customer type, one generic workflow | Off-the-shelf, well configured |
| Multi-stage approvals across an account hierarchy | Bespoke |
| Live data from your own ERP, CRM or job system | Bespoke |
| The portal experience is part of your competitive position | Bespoke |
✦ Path
The real questions your team answers by phone or email, ranked by volume and cost.
If an off-the-shelf tool covers it, we say so before any design work starts.
Roles, permissions and hierarchy modelled on how your customers' organisations actually work.
The portal reads and writes to your existing CRM, ERP or job platform rather than duplicating data.
Real usage before a full rollout, so the workflow is proven rather than assumed.
✦ Questions we get asked
Buy off-the-shelf if your needs are close to standard ticketing and document sharing. Build bespoke when the portal needs to reflect a specific B2B process or pull live data from your own systems.
A CRM is for your team to manage relationships and pipeline. A customer portal is the external-facing view your customers use themselves, usually reading from the same underlying data as your CRM or ERP.
Yes, that's usually the main reason to build bespoke rather than buy. We connect the portal to your CRM, ERP, job system or accounts package so customers see real, current data.
We model your customers' own account hierarchies - head office, branch, individual contact - with role-based permissions, which is the area generic portal tools handle least well.
A first version covering your highest-volume customer requests is typically a matter of months, released to a pilot group before a full rollout across your customer base.
A well-designed portal should need very little. We design around the requests customers already make by phone or email, so the portal replaces a familiar interaction rather than introducing a new one.
✦ Related
Bring us the questions your team answers by phone every day. We'll tell you honestly whether off-the-shelf covers it or whether a bespoke portal earns its cost.
No pitch deck · We map your process · You own the software