Method

How we read a client portal

A Utilitycorner review is a sequence of sittings, not a login you receive. The five steps below are the same whether we are in Ipoh or on your floor.

Notebook and papers on a desk during a written review

Access, not a dump

We need a named contact, a read-only view of the portal’s event records, and a list of the screens that matter. We do not take a copy of client files. If your analytics sit in more than one place, we agree which source is the source of record before day three.

Name every event in the client’s language

Invoice_viewed means nothing until someone in billing points at the page. We sit with the owner of each main screen — orders, tickets, documents, statements — and write the human name next to the event name.

Sample sessions, then pair them with tickets

We pull a sample of sessions from the last quarter, not a single busy Monday. Then we match stubborn paths with the support queue: password resets, “where is my invoice”, “the catalogue shows last month’s price”.

Walk the first fortnight

For new accounts we reconstruct invite, first login, first useful action. In Malaysia that often means the invite sits in a shared inbox while the real instruction went out on WhatsApp.

Debrief in the room

The last sitting is with the people who can change a screen or a process. We bring a short brief, not a slide opera: which paths stall, which modules go unused, which habits live outside the portal, and what we would examine next if you asked us back.

The method is older than most portal vendors. You give a specialist a limited view of a working system, they name what they see in the language of the people who use it, and they bring a brief back to the room. We apply that to B2B client portal apps because those apps already record a trail — invites, logins, invoice views, ticket starts, downloads — that few firms have time to sit with.

We refuse two things that often get attached to this kind of work. We will not take a copy of your clients’ documents home. We will not deliver a hundred-page pack that nobody reads. The written brief for a usage review is short enough to be argued with in a two-hour sitting.

If you want the sequence applied to invoices, onboarding, or a quiet module, start with the engagements and then write to us.

Ask us to walk this method on your portal