Client case study · Technology sales · Identity withheld

A twin beside
every role.

One digital twin for every person, designed around the way the organisation already works. Agents prepare. People decide.

Industry
Technology sales and solutions
System
Purposive Twin Agents
Operating model
Human-controlled agent organisation
Autonomy
L2, draft and recommend
41
Role-based twins
10
Teams mapped
205
KPIs connected to owners
L2
Draft-only autonomy ceiling

Organisation-mapping figures supplied in the case-study brief. The client identity is withheld.

Your best people should drive growth,
not chase coordination.

01

Routine work crowds out selling

CRM updates, meeting preparation, pipeline reports and follow-ups pull account teams away from customers.

02

Hand-offs disappear into inboxes

Work moves across marketing, sales, pre-sales and product without one shared view of what is waiting.

03

Decisions wait on leaders

Questions reach the right person late, with too little context and no consistent way to track turnaround.

04

Goals lack an operating layer

KPIs exist, but ownership, dependencies, routines and evidence are difficult to see in one place.

A parallel agent organisation,
built around the human one.

The system mirrors roles and responsibilities. It does not replace them. A control layer sits between every agent proposal and every real-world action.

Human organisation

41 people across 10 teams

People retain ownership of customer relationships, decisions and final actions.

Control layer

Named approvals and policy gates

Every proposal is checked, routed and held for the right person before anything moves.

Agent organisation

One twin beside every role

Each twin works from its role card, KPIs, routines and authorised organisational context.

From scorecard to working twin
01

KPI sheet

Start with the scorecard the organisation already uses.

02

Role card

Define what each person owns and how success is reviewed.

03

Hand-off map

Name what moves between roles, who sends it and who receives it.

04

Success streams

Group work around shared goals, owners and contributors.

05

Agent playbooks

Turn recurring work into reviewable daily and weekly routines.

Less chasing.
More coordinated action.

Active role
Pipeline twin

A gap becomes visible

The twin finds stalled deals and a partner registration that needs attention.

Handoff evidence

A prioritised issue, not another dashboard alert.

Illustrative workflow using sample account activity. It demonstrates how work moves through the agent organisation, not a reported client result.

Agents propose.
People remain accountable.

The system is intentionally capped at L2 autonomy. It can draft, recommend and route. A person approves the decision and owns what happens next.

L0
Available
L1
Available
L2
Ceiling
L3+
Blocked

Draft first

Twins prepare work. People decide whether it moves.

Named owner

Every twin belongs to a role with a person accountable for its actions.

Two keys for higher risk

Customer-facing and sensitive work can require a second approval.

Grounded context

Twins work only from authorised organisational data and state what is missing.

Central stop control

Agent routines can be paused while people review the system.

Measured against
the organisation's own KPIs.

These are the measures built into the operating model. They describe how value is evaluated, not unverified performance gains.

Decision turnaround

How long priority decisions wait before a named owner resolves them.

Pipeline hygiene

Open opportunities with a current owner, next step and date.

Customer follow-through

Drafts reviewed and customer actions completed within the agreed rhythm.

Hand-offs on time

Cross-team work delivered when the receiving role needs it.

Time returned

Routine work no longer completed manually, validated by the people doing the job.

Approval quality

Approval rates, rejection reasons and policy flags used to improve the playbooks.

From first map to scaled system
01

Assess

Map roles, KPIs and the highest-friction hand-offs.

02

Design

Agree the first agent pod, policies and approval model.

03

Build

Connect context and turn routines into governed playbooks.

04

Deploy

Start with a small pod at draft-only autonomy.

05

Success

Measure against the baseline, then scale what earns its place.

Make AI earn its place in every role.

Start with one team, one scorecard and one set of hand-offs. Build the first pod around work people can review and value they can measure.

Continue exploring
Return to all case studies
→