Tina is the test case. The portal logs everything she does inside it — emails replied to, quotes drafted, suppliers chased, accounts checked. It watches the rhythm, learns the patterns, and works out where each thread would route if she weren't there. By the end of week three, every recurring behaviour has a destination: the system handles it, Pia handles it, or it comes to you.
Week 2 of 3 · 156 observations · 11 distinct behaviours classified
Hafele query triage
~24 queries / week
Tina checks Hafele’s shared inbox 3-4 times daily. Of the queries logged so far: 14/week are spec or colour confirmations she looks up from past jobs (mechanical), 6/week are pricing decisions that need your sign-off, 4/week are escalations to suppliers.
Routes toSystemChelseaPia
Observed for 14 days. High confidence on the split.
THX quote drafting
8 quotes in the last fortnight
Tina builds THX quotes from a saved template and supplier roster. Every quote followed the same 4-step pattern, with margin held to 22% on stock and 35% on bespoke. None required strategic input.
Routes toSystem
THX is fully absorbable by the system. No human gate needed.
Westfield Health renewal cadence
Annual cycle, matched against last 3 renewals
Fixed cadence: nudge at 30 days before renewal, formal quote at 14 days, escalate at 7. The portal can run the sequence and only surface the renewal close itself to you.
Routes toSystemChelsea
Pattern matched. System runs the chase; you make the call.
Friday recap email to Chelsea
Every Friday, 3 weeks running
Tina writes you a weekly summary on her accounts: jobs in flight, money in and out, anything bubbling up. The portal already has the underlying data — the recap can be generated automatically and dropped into your Monday morning briefing.
Routes toSystem
Format learned. Lands directly in Morning briefing.
Supplier price-change pass-through
11 events in 3 weeks across her accounts
Supplier raises a price, Tina recalculates the client-facing number and forwards. She uses a flat 15% markup on stock, 25% on bespoke. Mechanical, but the client-facing send is worth a human eye.
Routes toSystemPia
System drafts; Pia approves before it reaches the client.
On-the-road client visits
Roughly monthly per account
Hafele in Wolverhampton, City Electrical in Sheffield. The portal logs each visit — date, topics raised, actions committed. Trip planning stays with you; follow-through tracking moves to Pia.
Routes toChelseaPia
Two visits observed. Cadence will firm up by week 6.
By end of week 3 — preliminary routing
System
58%
mechanical, no human gate
Chelsea
24%
strategic, needs your call
Pia
18%
routine, needs a human eye but not yours
When you're ready, Tina's role can be retired with no functional gap. Every behaviour the portal has observed has a documented destination — the system handles most of it, Pia covers the review-worthy routine, and the strategic edges come to you with all the context attached.