What a system gives backNo price here

How many hours a week does your team spend on work a system could carry?

Count it from three numbers you already know: how many clients, cases or accounts are live, how often each one is handled, and the minutes each handling spends finding where it was left. The page turns them into hours a week, then shows what a system would give back at your own rate. Nothing you type is sent anywhere.

TodayYour own week, in three numbers
countthe ones being worked, not the ones on the books
per cyclecalls, emails, updates, hand-offs: every time someone picks it up
minutesbefore the work starts: reading back, opening tabs, asking a colleague
weeks
With a systemThe one that fits, and how much it takes on

It captures each request, routes it, follows it through and keeps one record, so nobody has to go looking.

50%

Nothing you type is sent anywhere. Nothing to sign up for.

Back to your team, every week12 hoursAbout 1.5 working days a week that today go to reading what came in, chasing what is waiting, and finding where each one was left. Research averages for three people on your team: put yours in the boxes.Worth $43,608 a year at the average rate

1 day2 days3 days4 days5 daystodaywith an operations systemback
stays with your team carried by the system
Today, a week
24 h
Today, a year
1,104 h
Back, a year
552 h
Today, a year at the average rate
$87,216
Back, a year at the average rate
$43,608

A year here is 46 working weeks, holidays and slack taken out.

What this estimate leaves out
  • The system’s price. It is given after the mapping call, fixed and in writing.
  • The weeks before the system runs, and the time your team gives the mapping.
  • Work that needs judgement. It stays with your team, and the share you set should leave it there.
  • Anything these three numbers do not count, in either direction: errors caught earlier, replies sent sooner, the hours a new process takes to settle.
The price

Why there is no price on this page.

What a system costs depends on what it has to carry, which is exactly what these three numbers cannot tell anyone. A price given before the work is mapped is a guess, and the buyer pays for the guess either way.

So the order is the other way round. The mapping call sets the scope, the Consult maps the work and sets the baseline, and the price comes after it: one figure, fixed, in writing. The numbers you typed here are the right thing to bring to that call.

The count

What the three numbers measure.

Not the work itself: the minutes before it, spent finding where each client, case or account was left. That is the part a system carries best, because it is the same every time, and the part nobody staffs for, because it hides inside every handling.

The share is yours to set. Leave the work that needs judgement with your team, and set the share to what is left. The mapping call is where that estimate gets tested against how your company actually runs.

Map what this would give back.

Bring the numbers you just typed. The first conversation is with the people who would build it, and the price comes after the Consult, fixed and in writing.

Map what this would give back