Skip to content

/ Role Central

The operating systemfor getting client work done.

Projects, requests, tasks, approvals, discussions, support and ongoing client work — a delivery team and its clients working from one calm place, from capture through commercial close.

One workspace per organisation. Customer-visible content stays customer-visible; internal work stays internal.

/ 02See it, then read it

The operational inbox — where client work lands.

Every request lands as a real record: customer, service, SLA and commercial classification are attached before anyone starts triaging. What follows on this page is why that matters.

Placeholder surface · will be replaced with real Role Central UI

[01]

Requests lost in inboxes

Client requests disappear into email and chat. Role Central captures every one with a customer, service, SLA and commercial class before triage begins.

RequestsSLA
ClassificationService

How Role Central captures them →

[02]

Retainers run blind

Retainer work is hard to control until it's too late. Time logs, allowance draw-down and per-period reporting share the same records — no month-end reconstruction.

AllowanceTime
Draw-downReports

Retainers, in detail →

[03]

Launch breaks history

Projects launch and handover breaks the customer's history. Handover, ongoing support and retained capacity live in the same workspace as the project that produced them.

HandoverSupport
ContinuityHistory

Delivery → support continuity →

/ 05Connected

One piece of work.One connected history.

Role Central is not a bundle of independent modules. The domains reference each other by design, so a piece of work carries its full context from the moment it lands to the moment it closes.

/ Ready when you are

Bring your delivery teamand your clients into one place.

Role Central is in active pilot with a small number of teams. If you’d like to see it in your workflow, sign in or get in touch.