Customer portals,
one coherent surface.
Self-serve portals engineered as products, identity, personalisation, self-service, billing and support unified behind a single front door your customers actually enjoy using.
A customer portal is the front door of your business relationship. When it's engineered as a product, with the same discipline your app has, it deflects tickets, opens revenue, and builds trust. When it's not, it becomes a wiki with a login screen.
Identity
SSO, delegated administration and role-based access designed from day one, because a portal without proper identity is a permissions bug waiting to happen.
We integrate with the identity your customers already have, corporate SSO, social, or portal-native, with SCIM provisioning and delegated admin for team leads. Every action is auditable; every role is enforceable.
Impersonation, staff access, break-glass, designed against your support model rather than added after the first incident. That's usually where portals leak most quietly.
The portal your customer never has to email support about is the portal that pays for itself.
Self-service
Ticket deflection, account management, documents, orders and billing, engineered around the questions your customers actually ask.
We audit real support tickets and structure the portal around the top 20 reasons customers reach out. Answers are one click away, not four. Common actions are self-serve, not form-and-wait.
AI-powered search and assistants get pulled in where they change the outcome, grounded in your documented answers, not on the open web.
Personalisation
The portal a large customer sees is not the portal a small one sees, and neither is a template.
Content, quick actions, dashboards and notifications shaped per segment, product tier and role. Feature flags and entitlements are engineered so personalisation is testable, versioned and auditable.
Enterprise customers get the enterprise surface with proper administration. Small customers get the fast, frictionless one. Same platform, no forks.
Operate
Adoption, deflection and satisfaction monitored as ongoing engineering, not as a launch metric that fades after quarter one.
Analytics tie every portal surface to the outcome it was designed to move. Improvement backlog stays live; the surfaces that stop earning their weight are retired, not tolerated.
The portal that ages gracefully is the one operated as a product. That's the operating model we design in from the beginning.
Toolkit
Framework, platform and vendor selection is driven by the shape of the work and the team who'll own it, not by whichever ecosystem is loudest this year. The list below is representative, not prescriptive.
- Front-end
- Next.js · React · TypeScript · Tailwind
- Identity
- Auth0 · Okta · Entra ID · Clerk · SCIM
- Search & content
- Algolia · Elasticsearch · Contentful · Sanity
- Analytics
- Amplitude · Segment · PostHog
- Platform
- AWS · Azure · Vercel · Datadog
Selected work
What clients ask us first
01How much of the portal should be self-service versus assisted?
As much as the data allows without pushing complexity onto the customer. We map the top-volume reasons for contact and design self-service against them; the residual gets an assisted path with context pre-loaded. The goal is not to eliminate support, it's to make each contact higher-value.
02How do you handle enterprise administration (SSO, roles, audit)?
SSO with SAML/OIDC, SCIM provisioning, delegated admin, role-based access and audit logging engineered from day one. Enterprise customers rarely evaluate portals on features first, they evaluate on how safely they can hand them to their own users.
03Where does AI fit?
In search, drafting and triage, grounded in your documented answers and account data, with clear escalation to a human. We don't ship AI experiences that hallucinate against a customer's own contract.
04How do you handle a heavy backend of legacy systems?
The portal is a coherent front, the backend is honest about its state. We integrate through APIs where they exist, wrap systems where they don't, and use the portal itself as the forcing function for gradual backend modernisation. Nothing rides on a single big-bang integration.
Let's discuss your customer portal.
Share a brief overview of the customers you're serving and the pain points they hit today, we'll arrange an introductory conversation with the relevant practice leadership.