Skip to capability content
What I build

Offered capability

Customer portals

DefinitionCustomer self-service around accounts, orders, subscriptions, documents and requests.

Buyer outcomeOne place for customers to act, approve and understand what happens next.

The recognisable problem

Customers are chasing updates across email, files and calls because the tools they can see do not reflect the service happening behind them.

Illustrative capability · not client work

One request, without the chasing.

A fictional specialist service business has the information, messages and approvals it needs, but they arrive through different channels. Bring them into one service timeline.

Specialist service · Request 184Manual timeline · motion reduced

Waiting on customer

Missing informationIdentity document and site photographs are still needed before the assessment can begin.

01 · Owned plan

Map the states, rules and systems before the build begins.

The resulting scope is yours to keep, including if someone else builds it.

02 · Delivery

Keep the person who shaped the plan close to the implementation.

If I build it, the discovery context follows into the software instead of being handed off.

Delivered work · Knobby

A real portal for a different customer relationship.

Knobby is separate from the fictional service scenario above. Its delivered member portal brings subscription management and a growing collection into one experience.

Delivered Knobby portal screens
Delivered subscription portal and collection experience.
1,300+

customers signed into the portal in the first week.

Knobby supplied the brief and interface designs.

I developed the portal and connected the member experience to the subscription systems behind it.

Delivered as Solutions Architect at Supernormal Systems.

The work began during my time at Supernormal Systems and continues through Bryte Labs.

Explore the Knobby project

A practical first step

Start with the business problem, then work out what belongs in the build.