BH Technology Book a consultation

ROI for AI · A five-part guide

Where should AI work first in your business?

Start with the work where better information, decisions or handoffs could matter most.

This guide shows how to choose that work and the right leader, check what actually improved, prepare the next team as capacity grows, and reassess from evidence.

Start with Capacity

  1. WorkWhat matters most?
  2. LeaderWho leads it?
  3. Next moveWhat changed?
Choose the work. Equip the lead. Check, then reassess.

Step 1 · Capacity

One person can move faster. A department can free more hours.

Start with the work that matters, then equip the right person or group to do more of it.

Illustrative values, each for its own example’s batch of work with review and upkeep included. Hours and percentage are separate measures. Orange labels show what each setup takes.

One person · typical setup example

What could improve when one person gets practical AI support?

This example focuses on repeated work, while judgment stays with the person responsible. Here is one standard sales proposal, before and after.

See what changes
Moves
Searching, organizing and first drafts go to an assistant.
Stays
You decide prices, scope, customer fit and what gets sent.
Repeats
A schedule finds the work. A review keeps improving it.
One person, their own desk and their usual work.
Hypothetical workflow · the same standard sales proposal

Before: you do every step by hand

  1. You Find information

    Search emails, notes, pricing, scope documents and customer history.

  2. You Prepare the proposal

    Build the scope, confirm prices, write the explanation and format the document.

  3. You Review and send

    Check accuracy, adjust judgment calls, approve the final version and send it.

  4. You Next proposal

    Starts the same way, from the beginning.

After: the routine prepares, you decide, and approved steps get finished

  1. Recurring schedule Find the work

    A scheduled routine lists new requests, missing information, follow-ups and proposals needing attention.

  2. Assistance Prepare a ready-to-check pack

    It organizes what is relevant and drafts the scope, explanation, checklist and questions.

  3. Human check Decide what is correct

    You confirm prices, scope, customer fit, risks and wording, then approve.

  4. Execution Complete permitted steps

    After approval, a connected workflow may file it, update a record or start the next task. This needs that setup and permission.

  5. Recurring review Improve the routine

    Review errors, missed information and unnecessary steps. Update the routine so the next proposal starts better.

Back to the first step: the next scheduled run uses the improved routine.
10 hours saved and +50% productivity: how the same work gives bothWorked example, with review and upkeep included
Hours for the same batch of workScale: 0 to 30 hours
  • Today30 h
  • With the routine20 h

10 hours released. The striped section is the time back.

Output per hour on that workScale: 0 to 1.5x today’s rate
  • Today1.0x
  • With the routine1.5x

30 ÷ 20 = 1.5x, or +50%.

The same change reads two ways. The work takes 33% less time, and each hour produces 50% more. Those are different measures of one change, so 33% and 50% are not interchangeable.

This assumes comparable accepted work. The 30 hours are one batch of proposal work, not a 40-hour week. It is an illustrative model, not a promise or a measured result.

Assistance prepares. Execution completes. You decide in between.

  1. Assistance
    Gives you a draft

    It organizes, summarizes, drafts and lists questions. What you get is something to check and use.

  2. You
    Approve or change it

    Prices, scope, customer fit, risks and final wording remain your call.

  3. Execution
    Does an allowed step

    It files the proposal, updates a record or opens the next task. This needs a real connection, permission for that step and a log you can check. Not every product does all of this.

What a schedule adds: it sets when the routine runs, such as every weekday morning. It repeats the check and the preparation. It does not decide what is correct. Automation links steps so you don’t have to restart each one, and your approval stays in the chain where it matters.
  • Straightforward tools
  • Relevant context
  • A routine you repeat

Together, these can produce strong gains. Buying tools covers only the first part.

Try it on one routine

The routine
Standard proposals, from new request to approved draft.
Input you can check
Approved price list, scope template and one recent accepted proposal.
Output you can check
A pack with the draft, the sources it used and its open questions.
What to measure
Over the next ten: minutes per accepted proposal including review, corrections per draft and missed information. Time a few of the same kind first.
What happens next
Fix the most common miss, put the routine on a schedule and run it again.

Three different results

  1. Hours releasedTime back on the same work.
  2. More accepted outputDepends on useful redeployment, demand and accepted quality.
  3. Financial returnAlso depends on delivered work and total costs. Collected cash is a separate check.

What this person needs

How much could one narrow task change?An assumed 3x to 10x example for one task, not a forecast or a whole week
Assumed minutes for one standard follow-up note from approved inputs, including reviewScale: 0 to 60 minutes
  • By hand60 min
  • Assisted20 min (3x)
  • Automated routine6 min (10x)
Gains can be large when the work is repeated, structured, information-heavy and easy to check.
Gains are smaller when every case is new or needs deep judgment.

These minutes are assumptions, not a rate or a forecast, and they need testing on your own work. A week holds many other tasks, so a task multiple does not carry over to the week. The main illustration stays at 10 hours and +50%.

Worked proposal setup, tools and costsWho does what, one deal start to finish, monthly cost and sources

Overview

One person can often move first. They usually start with the tools, files and routines they already use, which makes setup faster, cheaper and easier to control.

In this illustrative example, that person saves 10 hours a week and shows a 50% productivity increase. Those are two separate measures. Neither is a promise, and ten hours don’t turn into cash on their own. They are usable capacity, and the next question is what the person does with it.

Example values for one person who prepares standard sales proposals on their own accounts. A person approves every proposal before it goes out.

Hypothetical example · same weekly workload

  • 30 hToday
  • 20 hWith the setup
  • 10 hBack each week

One person completes their usual batch of work in fewer hours, with review and upkeep included.

How one proposal moves

  1. Deal in HubSpotProposal stage reached
  2. Approved sourceTemplate, pricing and examples in Drive
  3. Agent draftsGrok Bot drafts and organizes recurring steps
  4. Person checksClaude compares the draft with approved examples
  5. Person approvesOwner signs off and sends
  6. RecordedNote and file link saved in HubSpot

Who does what each day

  • Grok BotReads the approved queue or an exported deal and drafts proposals and recurring steps
  • ClaudeWrites longer pieces and reviews drafts against approved examples the owner provides
  • CodexBuilds and tests small scripts and reports in VS Code or a repo
  • HubSpotHolds deals, tasks and customer status
  • DriveHolds approved docs and working files

One deal, start to finish

  1. A deal in HubSpot reaches the proposal stage. The owner exports the deal details or adds them to the approved queue.
  2. Grok Bot reads that entry plus the approved template and pricing from Drive, then drafts the proposal and a checklist of recurring steps.
  3. The owner hands Claude the draft and approved examples as files. Claude flags gaps and differences. The owner checks facts, scope, pricing and any exceptions.
  4. The owner approves and sends the proposal. The note, file link and next task go back into HubSpot.
  5. When the routine needs a fix, the owner uses Codex in VS Code to update the script and tests it before the next run.

The owner stays in charge. They hold every account, review each draft and approve what goes out. Tools hand work over by file, link or repo commit.

Entry $30 Grok Premium + $20 ChatGPT Plus + $20 Claude Pro = $70 a month. Heavier tiers $300. New Workspace adds $16.80. CRM and extra usage are separate.

USD before tax. Sources xAI, ChatGPT, Claude.

Go deeper

Department of 10 · typical setup example

How one reusable workflow can raise a whole department

A department does not improve because everyone becomes an expert overnight. It improves when a proven routine becomes easy for other people to use reliably.

See what changes
Starts
With one strong user’s real proposal routine.
Becomes
Shared approved inputs, a template, training and checks.
Takes
More investment than one person, and people improve unevenly.
Ten people, two rows of five, connected through shared data.
Hypothetical rollout · a standard sales-proposal routine in a department of ten
  1. Strong user Capture one strong routine

    An experienced salesperson’s proposal process is written down: inputs, checks, template, handoff and review points.

    1 of 10 using it
  2. Shared inputs Adapt it into shared inputs

    The department uses approved pricing, scope fields, examples, language and required quality checks.

    1 of 10 using it
  3. Three pilot users Run a small pilot

    Test on a limited number of proposals. Measure preparation time, corrections, completion and adoption.

    3 of 10 using it
  4. Managers Train and check

    Show people how to use the routine. Managers review quality and reinforce the steps.

    3 using it, 7 in training
  5. Whole department Expand carefully

    Make it available to everyone once the pilot shows evidence. Track results by person and as a team.

    Open to all 10, use varies
Back to the shared routine: when real use reveals friction, the template and checks improve for everyone.

The same proposal on an ordinary day

Hypothetical workflow · one salesperson who is not the expert

Before: everyone works from their own version

  1. Salesperson Find the latest version

    Look for current pricing, a good past proposal and the customer’s notes.

  2. Salesperson Build it their own way

    Structure, wording and checks can differ from person to person.

  3. Salesperson and manager Review, send and update

    Quality depends on who wrote it and who checks it. The record is updated by hand.

  4. Salesperson What was learned

    Stays with the person who learned it.

After: one shared routine, with a named owner on every proposal

  1. Recurring schedule List the day’s work

    A scheduled check lists new requests, follow-ups and missing details, each with an assigned owner.

  2. Assistance Draft from shared inputs

    The assistant prepares a ready-to-check pack from approved pricing, scope fields, examples and the template.

  3. Human check Owner checks and approves

    The assigned owner confirms prices, scope, customer fit and wording. A manager handles anything unusual.

  4. Execution Record the approved result

    With the needed integration and permissions, the workflow files it and updates the shared record.

  5. Recurring review Improve it for everyone

    On a set schedule, corrections and misses are reviewed, then the shared template and checks are updated.

40 hours saved in total and +25% productivity: how the same work gives bothWorked example, with review and upkeep included
Staff-hours for the same batch of work, all ten peopleScale: 0 to 200 staff-hours
  • Today200 h
  • After rollout160 h

40 staff-hours released. The striped section is the time back.

Output per staff-hour on that workScale: 0 to 1.5x today’s rate, the same scale as the one-person example
  • Today1.0x
  • After rollout1.25x

200 ÷ 160 = 1.25x, or +25%.

The same change reads two ways. The batch takes 20% less time, and each staff-hour produces 25% more. Those are different measures of one change, so 20% and 25% are not interchangeable.

This assumes comparable accepted work. The 40 hours are a department total on one batch of work. They are not a 40-hour workweek, a payroll cut, a whole-company result or a proven outcome.

The same 40 hours, but not 4 hours each

One assumed spread of hours released per week, per personScale: 0 to 12 hours. Assumed, not measured.
  • Strong user12 h
  • Person 28 h
  • Person 35 h
  • Person 44 h
  • Person 53 h
  • Person 63 h
  • Person 72 h
  • Person 82 h
  • Person 91 h
  • Person 100 h

Total: 40 hours. 12 + 8 + 5 + 4 + 3 + 3 + 2 + 2 + 1 + 0

Do not expect equal gains. One person may go well beyond the others. Several may gain a useful amount. Someone may not be using it yet.

The strong user’s value can spread. Their routine helps others only once other people can use it reliably, through shared inputs, training and checks.

Measure both levels. Track results by person and as a team, because a team total can hide who still needs help.

Your department’s spread will look different. This one only shows that 40 hours need not be shared evenly.

What the department has to build that one person doesn’t

Test it with a small pilot

The routine
Standard proposals, from new request to approved draft.
Who tries it
Three people: the strong user and two others, so you can see how well it transfers.
Input you can check
Manager-approved pricing, scope fields, example proposals and the template.
Output you can check
A pack listing its sources, and a logged approval from the assigned owner.
What to measure
By person and as a team: preparation time per accepted proposal, corrections, completion and whether people keep using it.
What happens next
Fix what the pilot revealed. The other seven join once the evidence supports it.

Three different results

  1. Hours releasedTime back across the team on the same work.
  2. More accepted outputDepends on useful redeployment, demand and accepted quality.
  3. Financial returnAlso depends on delivered work and total costs, including the shared setup. Collected cash is a separate check.
What if one person becomes a standout?A possibility to think about, not a rate

With the right shared setup, an exceptional user can go far beyond the rest and help pull others up. In one hypothetical example, a team of twenty has one standout and some colleagues reach about 2x on work they have adapted.

Treat that as an assumption to test, not an established rate or a forecast. A department of ten may have no standout at all. The +25% example does not rely on it: it does not assume that everyone doubles, that everyone adopts equally or that any share of people becomes exceptional.

What published research shows about uneven gainsOne large study, in customer support rather than proposals

Among 5,172 support agents, AI assistance raised issues resolved per hour by 15% on average, with varied effects. Less experienced and lower-skilled agents gained more. The highest-skilled gained little speed, with a small quality decline. This fits the shared-practice idea in a narrow setting. It does not prove proposal or company results.

Source: Brynjolfsson, Li and Raymond, “Generative AI at Work,” Quarterly Journal of Economics, 2025.

Worked department setup, stack and costsHow a proposal moves, the stack, people and checks, monthly cost and sources

Overview

A department takes more coordination, but can create more total capacity. Equipping ten people takes more than giving everyone the same tool. It can take shared data, connected systems, team training, agreed ways of working and quality checks, and all of that takes more time and budget.

In this illustrative example, the department saves 40 hours a week in total and shows a 25% productivity increase. The percentage is smaller than the individual example, and the total capacity is larger. Neither figure assumes a 40-hour workweek, a payroll reduction or a specific financial return.

Example values for a department of 10 after rollout, preparing standard sales proposals on company accounts. Three people pilot it first. An assigned owner approves every proposal.

Hypothetical example · same weekly workload

  • 200 staff-hoursToday
  • 160 staff-hoursWith the setup
  • 40 hBack each week across the team

The full department after rollout completes its usual batch of work in fewer hours, with review and upkeep included.

How one proposal moves

  1. Deal in HubSpotStage and owner set
  2. Shared approved contextTemplates, pricing and examples from Drive
  3. Postgres queueProposal tracked by ID with an assigned owner
  4. Agent preparesGrok Bot drafts the proposal and evidence pack
  5. ChecksClaude review against approved examples
  6. Person approvesAssigned owner or manager signs off
  7. RecordedHubSpot status and run log updated

The stack

Records
HubSpot is the source of record, Supabase Postgres tracks the queue, Google Workspace holds approved docs
Agents
Grok Bot Teams seats on company accounts
Builders
Codex through ChatGPT Business, in VS Code and a repo
Reviewers
Claude Team for results and playbooks

One deal, start to finish

  1. A deal in HubSpot reaches the proposal stage and a work item enters the queue with an assigned owner.
  2. The queue service gathers the deal record, the shared approved template, pricing and examples.
  3. Grok Bot prepares a proposal draft and an evidence pack that lists the sources used.
  4. The owner hands the draft and evidence to Claude for a check against approved examples, then checks facts, scope, pricing and exceptions. A manager handles anything unusual.
  5. The owner approves and sends. The approval is logged and the status goes back to HubSpot.

People and checks

  • Team trainingThree pilot operators learn the routine first. All ten join only after the pilot shows evidence.
  • Quality checksEvery draft gets a human check before it goes out. Managers approve templates and exceptions.

The service delivers the working setup. BH Technology maps the workflow, cleans the source data, sets permissions per identity, builds the queue service, tests it in the pilot and trains the team. Each part is scoped and quoted separately.

Example monthly subtotal for licenses and the database is $545 (10 Grok Bot seats, 3 Codex through ChatGPT Business, 3 Claude Team, Supabase Pro). With new Google Workspace it is $713. Usage, CRM, hosting and the setup service are separate costs.

USD before tax. Sources xAI Teams, ChatGPT, Supabase.

Go deeper

Measure it

What changed?

Did the defined work improve, or did the measurement simply change? Time the same work before and after, with review and fixes inside both numbers.

Illustrative example · one weekly client report, start to approved finish · scale: 0 to 90 minutes
BeforeDraft, review and fixes90 min

Log real examples of this report, from start until it is finished and approved. The reading has to end at approval, because stopping at the first draft would hide the review work.

AfterDraft, review and fixes60 min

The striped part is the 30 minutes released. It counts only if review and fixes stay inside the 60. If drafting gets faster but fixing takes longer, the total shows it.

  1. 30 minsaved per report

    90 − 60 minutes, on the same kind of report.

  2. × 20 reportsa week

    Multiply only by comparable tasks completed. Other kinds of work do not inherit this saving.

  3. = 10 h released600 min a week

    Hours released are the starting point. They gain value once the team applies them to useful work.

    Next check: was the time used?

What keeps the comparison fair

  • Same defined taskBefore and after match

    If the task got simpler or the standard got lower, the time difference says little about the routine.

  • Enough real examplesOver the same kind of period

    One quick week or one unusually easy report can mislead you. Log enough cases on each side to compare like with like.

  • Everything includedReview, fixes and upkeep

    For the setup examples, time one real task from start to approved finish, with review, fixes and upkeep included. Then compare it with how long the same task took before.

Hours and output per hour are two different readingsWorked out from the same two timings
Output per hour on this report · scale: 0 to 1.5x the before rate
  • Before: 1 report per 90 min1.0x
  • After: 1 report per 60 min1.5x

90 ÷ 60 = 1.5x output per hour on this task. The same change also reads as about 33% less time per report. The two percentages describe one change, so they are not interchangeable.

This derived rate holds only if accepted quality stays the same, and it applies only to this report. It says nothing yet about revenue.

Original measurement steps and report exampleHow to measure hours freed, with the source calculation

What changed?

How to measure hours freed

  • Time one defined task from start to finished and approved, including review and corrections.
  • Log enough real examples, before and after, over the same kind of period.
  • Multiply the minutes saved by the number of comparable tasks completed.

Illustrative example · one weekly client report

Before90 min

After60 min

DraftReviewFixes

(90 − 60 min) × 20 reports a week = 600 min = 10 h released

Hours released are the starting point. They gain value once the team applies them to useful work.

For the setup examples · time one real task from start to approved finish, with review, fixes and upkeep included. Compare it with how long the same task took before.

Step 2 · Leaders first

Equip and teach leadership first

Give a trained leader the right context, and better information can support better decisions, coaching and team activity.

  1. Signal detected. Leader verifies.

    See activity

    Proposals sent this week

    • Rep A6
    • Rep B5
    • Rep C1

    Flag: 4 of Rep C’s open proposals are stalled

  2. Leader decides. Employee acts.

    Coach and set priority

    Rep C: follow up on the 4 stalled proposals today.

    Whole team: use Rep A’s follow-up template.

  3. Process is repeated. Team work changes.

    Same team measure after rollout

    Rep A’s template A B C

    Team proposals sent per week · illustrative, same team and definition

    • Before12
    • After18

Equip the right leader

  • The right tools
  • Relevant records and context
  • Training on what to ask and check
  • A real routine
  • ExecutiveAcross the company
  • Vice presidentAcross a function or region
  • Department headClosest to daily work

Illustrative sales example. Proposals sent measure activity.

Equip the right leader

What does a leader need beyond another software account?

Four supports around the person whose decisions shape the work, all feeding one decision that keeps coming back.

One leader, four supports, one recurring decision

The leaderAn executive, vice president or department head whose decisions shape the work.

Useful toolsSet up around their actual work.

An AI account on its own won’t change a team. The tools are set up around what this leader reviews, with prompts or reports that surface relevant signals, such as open items with no next step.

Approved recordsWhat is actually happening.

The sales, job or billing records this leader is cleared to use. AI can only work from what it has been given, so someone has to connect or supply these sources and decide who may see what.

Company and team contextWhat the records mean here.

Current priorities, who does what, how the work is defined and what good work looks like here. A record read without this can point the leader the wrong way.

TeachingWhat to ask and how to check.

Two skills: getting useful preparation from the tools, and checking it. That means opening the source record behind a claim, noticing what is missing and knowing when the context changes the answer.

All four feed one decision

One recurring decisionA review the leader already holds, or should hold: what comes first, who needs coaching and what gets followed up.

An illustrative Monday. Before the sales review, AI pulls the week’s proposal records into a summary, lists open items with no next step and drafts questions for the meeting. The sales head checks the summary against the records, then decides.

The leader is not being equipped with access alone. The leader is being equipped to make better recurring decisions.

AI
Prepares the information, organizes patterns and suggests where to look.
The leader
Verifies the situation, decides what matters and coaches the team.
Employees
Still do the work.

Which leader? Start from the work

Proposals keep going quiet in one sales teamThe sales head

They review follow-up and are closest to the daily work, so a problem in one team is a natural place to start.

Sales is doing well, but orders are waiting on deliveryThe leader who oversees both

Whoever can see and change the handoff between teams, for example a vice president. A vice president of operations might check whether work that was sold is being scheduled and completed, then coach the managers who run those teams.

Billing numbers arrive too late to useThe billing lead, then the executive team

A billing lead sees what is ready to invoice and what is missing. An executive team needs sales and delivery activity next to the financials, so it can see numbers and margins and decide where to invest next.

A faster leader is only the start. What actually reaches the team?

How one leader’s gain reaches many people
Full original explanationWhere to start and everything the setup has to give the leader

Start by asking where better work would matter most to the business. That might be sales follow-up, delivery that keeps falling behind or billing numbers that arrive too late to use. Then find the leader whose decisions shape that work. It may be an executive, a vice president or a department head.

Step 1 showed why one person is often the quickest and least expensive place to start. There is less to set up, and that person’s own work can improve by a larger percentage. When that person is a leader, the gain reaches further, because they set priorities, review the work and decide what gets followed up across many people.

An AI account on its own won’t do that. The leader needs the right tools, set up around their actual work, and needs to learn how to use them: what to ask for, which sources to rely on and how to check an answer before acting on it.

A leader doesn’t change a team just by becoming more productive personally. The change comes when better information, better questions and better use of their time reach the decisions that affect other people. So the setup has to give them:

  • The records needed to see what is happening
  • The company and team context needed to interpret it
  • Prompts or reports that surface relevant signals
  • Training on what to ask
  • A way to verify the information
  • A clear decision or coaching action

AI can prepare the information, organize patterns and suggest where to look. The leader still verifies the situation, decides what matters and coaches the team. Employees still do the work.

How one leader’s gain reaches many people

Back to section

How one leader’s gain reaches many people

How does a leader’s improvement spread beyond the leader?

Speed stays with the leader. Better decisions travel, through four channels that change what other people do.

What reaches the team, and what does not
One leaderExtra time and a clearer view of the work
PrioritiesWhere the week goes

People spend their week on the work that matters most, because the leader has decided from current records what comes first.

CoachingFeedback from real work

Feedback comes from a person’s real work, while it can still help. The conversation starts from a proposal, job or invoice, not a general impression.

AccountabilityAn owner and a next step

Work has an owner and a next step, and someone checks on it. That check is what makes the agreement real.

ProcessWhat works gets written down

What works gets written down and becomes how the team does it. At that point the improvement no longer depends on one person remembering it.

Several people’s workWhat they work on, how they do it and the standard they are held to
Dead end: the leader’s personal speedIt belongs to them. It can’t be multiplied across the people they oversee.

Say a department head gets through reporting and review preparation much faster. Nobody else suddenly works at the same rate. A faster task changes one person’s output. A better leadership decision changes what several people do.

Step 1’s illustrative 50% and 25% compare one person with a department-wide rollout. Neither is a leader’s percentage spread across a team.

Three levels, three different jobs

Bar width shows how much of the company the role looks across, not the size of any gain.

Executive teamAcross the companyWhere do we invest next, and which part of the business is running out of capacity?

They need activity from sales and delivery next to the financials, so they can see their numbers and margins and act on them.

Small illustrative trial. Choose one company priority. Give the executive the relevant records, a short weekly summary and four fixed questions: What moved? What stalled? What is creating the constraint? Which decision belongs to me? Verify the signal with the responsible leader and make one documented decision.

Vice presidentAcross a function or regionWhere is the handoff between my teams breaking down?

A vice president of operations might need to see whether work that was sold is being scheduled and completed, then coach the managers who run those teams.

Small illustrative trial. Choose one recurring process in the function. Compare two teams using the same definitions and records. Find one difference, ask the managers what caused it and choose one behavior or process to standardize.

Department headClosest to daily workWhat is moving, what has stalled and who needs help this week?

A sales head reviews follow-up. A billing lead sees what is ready to invoice and what is missing.

Small illustrative trial. Choose one weekly workflow. Give the department head a simple view of activity and stalled work, then require one daily review, one coaching conversation and one process adjustment. Track what changed the following week.

What the trial also teaches: which steps to keep, which tools are worth paying for, what the team will need to be taught and who may need to be hired. That makes a later rollout much easier.

Full original explanationThe 50% and 25% comparison, a practical first setup and what the leader has to learn

Two scopes, two percentages

In the illustrative comparison, a 50% gain for one person adds half that person’s usual output. A 25% gain for a department of ten adds a quarter of the department’s usual output. With comparable starting workloads, the team can add more work overall at the lower rate. That wider rollout takes more time, money and shared infrastructure.

What travels from the leader to the team

Say a department head gets through their reporting and review preparation much faster. That speed belongs to them. Nobody else suddenly works at the same rate, so a leader’s percentage can’t be multiplied across the people they oversee.

What reaches the team is what the leader does with the extra time and the clearer view. A faster task changes one person’s output. A better leadership decision changes what several people work on, how they do it and what standard they are held to. It shows up in four places:

  • Priorities. People spend their week on the work that matters most.
  • Coaching. Feedback comes from a person’s real work, while it can still help.
  • Accountability. Work has an owner and a next step, and someone checks on it.
  • Process. What works gets written down and becomes how the team does it.

Which level of leadership to start with

The right level depends on which decision or work is holding the business back.

  • Executive team. They decide where to invest next and which part of the business is running out of capacity. They need activity from sales and delivery next to the financials, so they can see their numbers and margins and act on them.
  • Vice presidents. They oversee several teams and can be the people who fix a handoff between them. A vice president of operations might need to see whether work that was sold is being scheduled and completed, then coach the managers who run those teams.
  • Department heads. They are closest to the daily work. A sales head reviews follow-up. A billing lead sees what is ready to invoice and what is missing.

As an illustration, if proposals keep going quiet in one sales team, the sales head is a natural place to start. If sales is doing well and orders are waiting on delivery, the leader who oversees both may be the better choice.

A practical first setup

The first setup can stay small. It needs four things:

  1. Current priorities. What the company or team is trying to get done right now.
  2. Approved records. The sales, job or billing records this leader is cleared to use. AI can only work from what it has been given, so someone has to connect or supply these sources and decide who may see what.
  3. Company and team context. Who does what, how the work is defined and what good work looks like here.
  4. One recurring review. A meeting the leader already holds, or should hold, where a real decision gets made.

Here is an illustrative version. Before a Monday sales review, AI pulls the week’s proposal records into a summary, lists open items with no next step and drafts questions for the meeting. The sales head checks the summary against the records, then decides what comes first, who needs coaching and what gets followed up.

A small trial for each level

These trials are illustrative. Each one tests the habit on real work before anything wider is built.

  • Executive. Choose one company priority. Give the executive the relevant records, a short weekly summary and four fixed questions: What moved? What stalled? What is creating the constraint? Which decision belongs to me? The executive verifies the signal with the responsible leader and makes one documented decision.
  • Vice president. Choose one recurring process in the function. Compare two teams using the same definitions and records. The vice president finds one difference, asks the managers what caused it and chooses one behavior or process to standardize.
  • Department head. Choose one weekly workflow. Give the department head a simple view of activity and stalled work, then require one daily review, one coaching conversation and one process adjustment. Track what changed the following week.

What the leader has to learn

Training covers two skills: getting useful preparation from the tools, and checking it. That means opening the source record behind a claim, noticing what is missing and knowing when the context changes the answer.

After running the review for real, the leader also knows which steps to keep, which tools are worth paying for, what the team will need to be taught and who may need to be hired. That makes a later rollout much easier than trying to work all of this out during the rollout.

Back to Equip the right leader

See the right work

Are you seeing activity, outcomes, or only more dashboards?

A measure earns its place by changing a decision. Put what people did beside what came of it, then look through one question.

Two kinds of measure, read side by side

Activity: what people didAlone, a busy team can look like a productive one.

Outcomes: what came of itAlone, they can arrive too late to coach from.

SalesProposals sentSales closed

Read together, they help decide who needs coaching and where the team should focus. The number points to the place. The proposal record shows what happened there.

OperationsJobs scheduledWork delivered

Read together, they help a leader see whether capacity is running out, while there is still time to act on it.

BillingInvoices issuedPayments collected

In this illustration, the invoice follows completed work and payment is the customer’s separate step. Read together, they help decide what to chase first and whether the numbers are ready for leadership to use.

The decision lensWhat would I do differently because of this?

With AI organizing the records, a leader can spot these sooner:

What is movingWork is advancing as planned.

Illustrative signal: jobs scheduled are turning into work delivered. The decision may be to leave it alone and spend the review on something else.

What has stalledWork with no clear next step.

Illustrative signal: an open proposal with no next step, or completed work not yet invoiced. The decision is who owns it and what happens next.

Who needs helpWhere a conversation comes next.

A signal is not a verdict. A missing entry might mean the work wasn’t done, or that it was done and never written down, so the leader asks before drawing a conclusion.

So which measures deserve a place on a leader’s screen?

Choosing what to track
Full original explanationWhy activity and outcomes belong side by side

More numbers won’t help a leader on their own. They need the few that answer a question they have to act on, and with AI organizing the records they can spot sooner what is moving, what has stalled and who needs help.

Two kinds of measure belong side by side. Activity shows what people did, such as proposals sent, jobs scheduled or invoices issued. Outcomes show what came of it, such as sales closed, work delivered or payments collected. Activity alone can make a busy team look like a productive one. Outcomes alone can arrive too late to coach from, so read both together.

So which measures deserve a place on a leader’s screen?

Choosing what to track

Back to section

Choosing what to track

What should leadership measure first?

Begin with the decision. If nothing would change whatever a measure says, leave it out.

  1. Decision
  2. Measure
  3. Records
  4. Owner
  5. Action
Illustrative chains: the question picks the measure
SalesWho needs coaching, and where should the team focus?MeasureProposals sent and follow-ups due; opportunities and closed salesRecordsEach proposal’s owner, last action, status and next stepOwner and actionThe sales head opens the records, coaches and sets the focus

Activity shows what reps did. Outcomes show what came of it. Neither alone is enough to coach from.

A variation. If the question is whether follow-up capacity is sufficient, measure open proposals by age, read the proposal IDs and next actions, then reassign or escalate.

OperationsIs capacity running out?MeasureJobs started and jobs waiting; work delivered and what it costRecordsEach job’s owner, what was done and when, status and next stepOwner and actionThe operations leader moves work or raises the capacity question

Delivered work on its own says little about what is queuing behind it. Jobs waiting on its own says nothing about cost. The decision needs both.

BillingWhat do we chase first, and are the numbers ready for leadership?MeasureCompleted work not yet invoiced and items missing; invoices paidRecordsCompleted jobs and their invoices, with what is still missingOwner and actionThe billing lead chases the gap and reports what is ready

The missing item is often the useful part. It names a specific record and a specific person who can complete it.

Each level asks a different question

Department headWhose work do I look at today?

The team’s numbers and the individual records beneath them, because that is where coaching happens.

Vice presidentWhere is work waiting between teams?

A view that compares teams and shows the queue between them, so the vice president can coach the managers who run them.

Executive teamWhere do we invest next?

Those same measures alongside revenue, costs and margins. The drawing shows the two kinds of information side by side, not any amount.

What has to be underneath

  1. 1. Structure the dataEach record shows who owns the work, what was done and when, where it stands and what happens next.
  2. 2. Reports and visualsPut it in a form people can understand.
  3. 3. Daily toolsLet each department use it in daily work.

Without that foundation, an AI summary is working from guesses and gaps.

Who keeps the view honest?AI, the leader and employees each have a part.

AI can gather the records, build the view and flag gaps. The leader chooses the measures and decides what each signal means. Employees record their work accurately and correct what is wrong.

Is the view earning its place?Look back after a few reviews.

Look at the decisions made from it. Keep the measures that changed what someone did. Replace the ones everyone glanced at and ignored.

Full original explanationThe examples, what each level looks at and how to check the view

Start from the decision

For each measure, ask what the leader would do differently depending on what it says. If the answer is nothing, leave it out. These illustrative examples show how a measure connects to a decision:

  • Sales. Proposals sent and follow-ups due show the activity. Opportunities and closed sales show the outcome. Together they help decide who needs coaching and where the team should focus.
  • Operations. Jobs started and jobs waiting show the activity. Work delivered and what it cost show the outcome. Together they help decide whether capacity is running out.
  • Billing. Completed work not yet invoiced and items missing from invoices show the activity. Invoices paid show the outcome. Together they help decide what to chase first and whether the numbers are ready for leadership to use.

What each level looks at

A department head needs the team’s numbers and the individual records beneath them, because that is where coaching happens. A vice president needs to compare teams and see where work is waiting between them. An executive team needs those measures alongside revenue, costs and margins, so it can decide where to invest next.

What has to be underneath

The order matters. First, structure the data. Next, put it into reports and visuals people can understand. Then build tools that let each department use it in daily work. Each record should show who owns the work, what was done and when, where it stands now and what happens next. Without that foundation, an AI summary is working from guesses and gaps.

Who keeps the view honest

AI can gather the records, build the view and flag gaps. The leader chooses the measures and decides what each signal means. Employees record their work accurately and correct what is wrong. A missing entry might mean the work wasn’t done, or that it was done and never written down, so the leader asks before drawing a conclusion.

How to check the view is earning its place

After a few reviews, look back at the decisions made from it. Keep the measures that changed what someone did. Replace the ones everyone glanced at and ignored.

Back to See the right work

Coach and hold accountable

How can a leader turn a record into a useful conversation?

A number tells a leader where to look. The improvement starts with what happens next, around the actual work.

The accountability loop: read in order from 1 to 6
  1. The actual work on the tableA real proposal, job or invoice, gone through with the person doing it.

  2. 1. RecordOpen the actual work.

    Not the count or the summary. The record shows who owns the work, what was done and when, where it stands and what happens next.

  3. 2. VerifyCheck what it means.

    AI can summarize records and flag gaps. The leader checks the facts. A missing entry might mean the work wasn’t done, or that it was done and never written down, so ask first.

  4. 3. ConversationGo through it together.

    That makes the feedback specific, and the person can use it today. They explain what is really happening and raise what is blocking them.

  5. 4. One ownerOne name on it.

    Accountability is not punishment. It is making the next action visible and owned. The owner may not be the person who first appeared in the signal.

  6. 5. One next actionClear enough to check later.

    Say what will happen and when, so it can be seen later. Rep C following up on four stalled proposals today is one example from this site’s illustrative sales story.

  7. 6. Follow-upThe leader comes back.

    At the next review, ask: Was the next action done? Did the work move? Is the same problem still coming back? Is the person handling it better without being asked?

Back to the work: people come to expect that what was agreed will be looked at again.

One leader doing this across everyone they oversee is a large part of how a personal improvement starts to change a team’s work. Department heads work from individual records, vice presidents coach their managers, and executive teams name an owner for problems that cross departments.

What does that look like with a real piece of work?

Coaching from the actual work
Full original explanationWhy the conversation and the follow-through matter

A number tells a leader where to look. The improvement starts with the conversation that follows. The leader opens the actual proposal, job or invoice and goes through it with the person doing the work. That makes the feedback specific, and the person can use it today.

Accountability comes from the follow-through. Each decision ends with one owner and one next action, and the leader comes back to check on it. People come to expect that what was agreed will be looked at again.

One leader doing this across everyone they oversee is a large part of how a personal improvement starts to change a team’s work. What does that look like with a real piece of work?

Coaching from the actual work

Back to section

Coaching from the actual work

What can a missing handoff teach the whole team?

One illustrative invoice, from the flag to the fix. Each step has its own owner.

Illustrative case: an invoice for a completed job
Job
Completed
Completion note from operations
Never arrived
Invoice
Flagged incomplete
  1. AIPreparing the weekly reviewFlags the invoice as incomplete

    AI can summarize records, surface gaps and draft questions or a possible next step from the sources it has been given. The flag is where the leader starts, not a finding.

  2. Billing leadAt the reviewOpens the record and decides who does what

    The record shows the note never arrived. The lead verifies the facts, assigns the owners and has the conversation on that record, showing what a complete handoff looks like and asking what got in the way.

  3. Operations coordinatorBy ThursdayGets the completion note over

    This person owns the handoff. They explain what is really happening, raise what is blocking them, complete the action and record it.

  4. Billing specialistOnce the note arrivesIssues the invoice

    This step depends on the one before it. Naming that dependency tells both people what they are waiting on and who is waiting on them.

  5. Billing leadNext reviewChecks both actions

    Four questions: Was the next action done? Did the work move? Is the same problem still coming back? Is the person handling it better without being asked?

If it happened onceThe coaching on that record may be enough.

If the same gap keeps appearing on other jobsThe fix moves from coaching one person to changing the process.

Perhaps the note becomes a required step when a job closes. Do not make AI responsible for judgment, or employees responsible for broken system design.

Who does what

AIPrepares

Summarizes, surfaces gaps and drafts from the sources it has been given.

LeaderDecides

Verifies the facts, weighs the context, makes the decision, assigns the owner and has the conversation.

EmployeeActs

Explains what is really happening, raises what is blocking them, completes the next action and records it.

The same habit, higher up

  1. Department leadOne record, with the person who owns it.

    The invoice above. Most issues can be handled at this level.

  2. Vice presidentA stalled account, with a sales manager.

    They look at the records and at how the manager coached the rep. The person being coached here is the manager.

  3. Executive teamA backlog that crosses departments.

    They name one leader to own it, with a date to report back. Each level coaches the people who report to it, which is how better habits can reach people several layers away.

Full original explanationThe whole case, each role and how to tell it is working

One billing problem, start to finish

This case is illustrative. While preparing the weekly review, AI flags an invoice for a completed job as incomplete. The billing lead opens the record and finds that the completion note from operations never arrived.

The billing lead now has a decision to make. The operations coordinator owns getting the note over by Thursday. The billing specialist issues the invoice once it arrives. The lead checks both at the next review.

The coaching happens on that record. The lead shows what a complete handoff looks like and asks what got in the way. If the same gap keeps appearing on other jobs, the fix moves from coaching one person to changing the process, perhaps by making the note a required step when a job closes.

Who does what

  • AI can summarize records, surface gaps and draft questions or a possible next step from the sources it has been given.
  • The leader verifies the facts, weighs the context, makes the decision, assigns the owner and has the conversation.
  • The employee explains what is really happening, raises what is blocking them, completes the next action and records it.

How this changes at higher levels

The same habit carries up through the company, with different work on the table. A vice president might go through a stalled account with a sales manager, looking at the records and at how the manager coached the rep. An executive team might see a delivery backlog that crosses departments and name one leader to own it, with a date to report back.

Each level coaches the people who report to it. That is how better habits at the top can reach people several layers away.

How to tell it is working

At the next review, ask four questions. Was the next action done? Did the work move? Is the same problem still coming back? Is the person handling it better without being asked?

Back to Coach and hold accountable

Improve work across the team

Can a useful leader practice spread before everyone receives new software?

Often, yes. Clearer priorities, better coaching and steady follow-up come from the leader and reach people right away. A wider rollout is a separate, bigger decision.

From one leader’s routine to a wider rollout
  1. 1. Leader’s routineReachThe leader, and whoever their decisions touchNeedsThe leader’s own setup

    Illustrative example: a department head creates a reliable proposal follow-up review and runs it on real work.

  2. 2. Proven experienceReachThe leader’s direct conversationsNeedsTime using it for real

    The leader now knows where it saves time, where a person has to check it and which steps matter. A process worked out during a rollout has none of this behind it.

  3. 3. Share and teachReachThe teamNeedsA written routine, template or checklist

    Before buying anything new, the team documents the review questions and tests them in the existing record system. A good practice can spread quickly.

  4. 4. Wider rolloutReachMany more people, where it is justifiedNeedsShared data, connected tools and training

    The percentage gain may be lower than one person’s. Step 1 illustrates +50% for one person and +25% for a department of ten. Total output can still be higher, because many more people are producing more. That is why it pays to choose carefully where to go next.

More shared setup and investment, more total reach

The steps show order and rising commitment. They are not measured amounts.

What has to be in place before a practice can really spread?

What lets the improvement spread
Full original explanationWhat improves first and why a rollout is a bigger decision

The team’s work can start improving before everyone has new tools. Clearer priorities, better coaching and steady follow-up all come from the leader and reach people right away.

Then the leader can turn what works into a repeatable process. They have used it themselves, so they know where it saves time, where a person has to check it and which steps matter. That makes it far easier to teach than a process being worked out during the rollout.

A wider rollout is a bigger decision. It needs more investment in shared data, connected tools and training, and the percentage gain may be lower than one person’s. Total output can still be higher, because many more people are producing more. That is why it pays to choose carefully where to go next.

What lets the improvement spread

Back to section

What lets the improvement spread

What turns one successful routine into a team capability?

Announcing a routine does not spread it. It spreads when it rests on shared foundations and the same team’s work actually changes.

What holds a shared practice up

The practice being testedIllustrative: Rep A’s follow-up template, used by the sales team

Repeatable workflowSteps written down.

The steps are written down with real examples, along with the cases that need different handling.

Shared dataOne set of definitions.

Everyone works from the same structured records and the same approved definitions, including what counts as a proposal sent.

Clear rolesWho does which part.

Each person knows who enters the information, who checks it, who acts on it and who coaches.

Training and feedbackOn their own real work.

People learn with their own proposals, jobs or invoices, and learn how to check what AI gives them. They also say when the process doesn’t fit a situation.

The team’s real work and accurate records

A small way to test the spread

  1. Try it for a set period

    One shared practice, with no new team software required. A template or checklist that has proved useful is enough to begin.

  2. Review the fit

    The leader reviews how it fits real work. Managers coach from that work and employees say where it doesn’t fit.

  3. Change what doesn’t fit

    The leader changes it where needed, so the team tests a practice that matches its own work.

  4. Compare the same team

    Same team, same definition of a proposal sent, compared with where that team started.

What counts as spread

Does not count

  • It was announced
  • It was made available
  • A finished checklist with no useful work behind it

Counts

  • People are really using the workflow
  • The records are accurate
  • The next actions are clear
  • The team’s own numbers moved from where it started
Can the neighbors keep up?Look on either side of the team.

This groundwork takes time and money, so the choice of team matters. Check whether the departments on either side can handle the extra work once this team speeds up.

How does this look at vice president level?Vice president, supervisors, coordinators.

In the illustrative operations case, each supervisor runs the vice president’s weekly review with the same definitions and coordinators update job status by an agreed time. Only issues that cross teams or need a bigger decision go back up.

Full original explanationThe operations example, who owns what and how the result gets checked

What can spread right away

Some improvements need no new software for the team. The leader can share what the priorities are, agree what each measure means, start a regular review and pass along a template or checklist that has proved useful.

A small way to test the spread

Before a wider rollout, try one shared practice with the team. In the illustrative sales example, that practice is Rep A’s follow-up template. The team uses it for a set period and the leader reviews how it fits real work. The leader changes it where it doesn’t fit, then compares the same team using the same definition of a proposal sent.

What a wider rollout needs

  • A repeatable workflow. The steps are written down with real examples, along with the cases that need different handling.
  • Shared data. Everyone works from the same structured records and the same definitions.
  • Clear responsibilities. Each person knows who enters the information, who checks it, who acts on it and who coaches.
  • Training on real work. People learn with their own proposals, jobs or invoices, and learn how to check what AI gives them.

This groundwork takes time and money, which is why the choice of team matters. It also helps to check whether the departments on either side can handle the extra work once this team speeds up.

An operations example

This case is illustrative. A vice president of operations has been using a weekly review to see which jobs are at risk. Once it proves useful, each supervisor runs the same review with the same definitions. Coordinators update job status by an agreed time. The supervisors handle most issues directly and bring the vice president only the ones that cross teams or need a bigger decision.

The vice president’s own routine has now become a way of working that many people share, and it no longer depends on one person looking at everything.

Who owns what

The leader decides what gets rolled out, explains why it matters and keeps reviewing it. Managers run it with their people and coach from the work. Employees do the work, record it accurately and say when the process doesn’t fit a situation.

How the result gets checked

Measure the team on its own numbers, compared with where the same team started. Then look at the work behind those numbers. Are people really using the workflow? Are the records accurate? Are the next actions clear? A finished checklist with no useful work behind it doesn’t count.

Back to Improve work across the team

See activity

What can a simple sales record reveal, and what can it not prove?

One illustrative week, two separate views. Counts show where to look. The records and a conversation decide what it means.

View 1: proposals sent this weekScale: 0 to 6 proposals
Rep A6

Six left this week. The count doesn’t say how good they were, or what came of them.

Rep B5

Five left this week, with the same limit. It is one week’s activity, not a result.

Rep C1

The example doesn’t explain why. Do not label Rep C unproductive from one count. It is a reason to look, nothing more.

Separate view. The flag below covers open proposals, not this week’s sent count.

View 2: open-work flag
4 of Rep C’s open proposals are stalled

This points to four specific proposals that someone can open and act on today. Like the count, it doesn’t explain why.

From a signal to what it means

  1. Open the recordsLast contact, what was promised, what happens next.

    Also useful: proposal age, missing information, customer response, scope and pricing.

  2. Check what you findIs the record right and complete?

    With access to the proposal records, AI can build this count and list the stalled items before the review. The leader still confirms what they show.

  3. Talk to the repAsk, then decide.

    Deciding what it means stays with the leader, and it comes before any coaching.

Higher up: a vice president of sales might look at the same kind of view team by team and ask each manager about what stands out.

Full original explanationWhat each view does and who decides what it means

In this illustrative week, the sales leader sees that Rep A sent 6 proposals, Rep B sent 5 and Rep C sent 1. Separately, 4 of Rep C’s open proposals are flagged as stalled.

The two views do different jobs. The count of proposals sent shows the leader where to look. The stalled flag points to four specific proposals that someone can open and act on today.

Neither one explains why. The records can show the last contact, what the customer was promised and what is meant to happen next, and the leader needs that before coaching anyone.

With access to the proposal records, AI can build this count and list the stalled items before the review. Deciding what it means stays with the leader. Someone more senior, such as a vice president of sales, might look at the same kind of view team by team and ask each manager about what stands out.

Back to section

Coach and set priority

What should the leader do with the signal today?

Two decisions come out of this illustrative review. They are different kinds of decision, and both get checked.

One review, two actions, one check

This week’s sales review

Accountability for specific work

Rep C follows up on the 4 stalled proposals today.

Owner
Rep C
Action
Follow up on these 4
Deadline
Today
What the conversation covers

They go through the four one at a time. What has happened so far? What does this customer need next? What help does Rep C need to move it today?

A useful thing to ask: was the blocker skill, information, process or demand?

A practice to test

The whole team uses Rep A’s follow-up template.

Who
Reps A, B and C
Purpose
A shared starting point for follow-up
Status
Being tested, not proven
Why it is a test

The example doesn’t tell us why Rep A sent more proposals, or whether the template had anything to do with it. It saves each rep writing their own, and it is worth trying on that basis.

Next review: check both

The four follow-upsDid they happen?

Confirm each of the four records received the right next action, and see what came of each one.

The templateDoes it fit the team’s work?

The leader looks at how it works across the team, including whether people are really using it, and changes it if it doesn’t fit.

The leader’s job is to turn a signal into an owned next step and a practice worth testing.

Full original explanationWhy the two decisions differ and what gets followed up

Two decisions come out of this illustrative review. Rep C follows up on the 4 stalled proposals today. The whole team uses Rep A’s follow-up template.

Why the two decisions differ

The first is accountability for specific work. It has a named owner, a clear action and a deadline. The second is a process decision. It gives everyone the same starting point for follow-up, so each rep doesn’t have to write their own.

What the coaching conversation covers

The leader and Rep C go through the four proposals one at a time. What has happened so far? What does this customer need next? What help does Rep C need to move it today? The conversation stays on those records, which gives Rep C something specific to act on.

What gets followed up

At the next review, the leader checks that the four follow-ups happened and what came of each one. The example doesn’t tell us why Rep A sent more proposals, or whether the template had anything to do with it. So the leader also looks at how the template works across the team and changes it if it doesn’t fit.

Back to section

Same team measure after rollout

What does a team-level change show, and what does it leave unanswered?

A change in recorded activity, and a good reason to ask what it produced.

Illustrative: same team, proposals sent per weekScale: 0 to 18 proposals per week
  • Before rollout12
  • After rollout18

+6 proposals per week, or 1.5x the earlier count. This counts activity. It is a different measure from Step 1’s productivity figures.

What keeps the comparison fair

Same team

If people joined or left between the two numbers, 18 would no longer describe the group that sent 12.

Same definition

“Proposal sent” has to mean the same thing both times. If the definition widens, the count can rise with no change in the work.

Same counting

Use the same way of counting from the same kind of record. A change in method can look like a change in the team.

What the number does not say: whyAI?Coaching?The template?Something else?

It doesn’t say why activity changed, or how much of the change came from any of these. It doesn’t prove that revenue, quality, delivery, billing or cash improved.

What did the extra activity produce?

  1. Measured hereSent

    18 per week in this illustration. Activity only.

  2. Not shownWon

    How many of the proposals were won? More sent does not mean more won.

  3. Not shownDelivered

    Did the work get delivered? Won work can wait if delivery has no room for it.

  4. Not shownInvoiced

    Did the invoice go out for the delivered work, complete and on time?

  5. Not shownCollected

    Did the customer pay? The business gets paid at this point, not when a proposal goes out.

Next: Step 3 follows what has to happen before activity becomes booked work, profit or cash.

Full original explanationThe fair comparison, what the number tells you and the question it leads to

In this illustrative example, the same team sent 12 proposals per week before rollout and 18 per week after.

Keeping the comparison fair

The two numbers can only be compared if they cover the same team and use the same definition of a proposal sent and the same way of counting.

What the number tells you

It tells the leader that recorded activity changed. It doesn’t say why, or how much of the change came from AI, coaching, the template or something else entirely.

The question it leads to

A proposal sent is activity. The business gets paid when a proposal is won, the work is delivered, the invoice goes out and the customer pays. So a leader who sees 18 proposals where there used to be 12 has a good next question: what did the extra activity produce? Step 3 follows what has to happen before activity becomes booked work, profit or cash.

Back to section

Back to section

Follow the gain through five kinds of work

Pick a department to see its own example. Each tab is a separate hypothetical case, so the results do not add together. Margins and cost bases differ by case, so read each one on its own assumptions rather than comparing percentages across tabs.

Step 3 · Revenue work · Sales example, hypothetical

40 hours put back into proposals could support $50,000 in booked work

A sample sales team frees 100 hours a month and puts 40 of them back into proposals. Follow those hours to the customer, the finished job and the bank.

Tap any picture for the math and the owner’s decision. Orange marks what has to be true.

  1. Freed time

    4 h before 2 h after Preparation per proposal, same quality One of five reps 50 proposals a month, team total 50 × 2 h saved = 100 h freed

    100 hours freed a month

    ÷ 2 h each
    No money counted until these hours get a job.
  2. Sales

  3. Handoff: can Delivery take it on?

Booked, delivered, profitable and paid are different states. Hours saved and output created are different measures. This hypothetical example is separate from Steps 1 and 2. It is not a client result or a guarantee.

The reasoning behind each step

Where did the 100 hours come from?

Before: 50 × 4 h 200 h
After: 50 × 2 h 100 h100 h freed
Preparation hours a month for the same 50 proposals. This is the total for all five reps.

The first value is released preparation time.

Five sales reps send 50 proposals a month in total. Before the improvement, each one takes four hours to prepare. After it, comparable accepted work takes two hours. The team no longer needs 100 of its 200 preparation hours for that same workload.

That is capacity, not “100 extra hours of revenue.” The comparison is fair only if the two hours still include the required review, corrections and approval. If drafting gets quicker but a manager now spends longer fixing scope or pricing, that time goes back in the count. If quality falls, the time saving is not real economic value.

Owner decision: define the work precisely, measure the original process, then measure the improved process using the same acceptance standard.

How to run a fair before-and-after
  1. Name one defined job, such as a standard proposal for a comparable customer and scope.
  2. Log the whole preparation time, including review, corrections and approval.
  3. Hold both versions to the same acceptance standard.
  4. Compare the same volume of work, so the saving comes from the method and not from a lighter month.
Hours and output are separate measures

Hours saved are production hours a person or team gets back. Productivity is how much more useful work they get done. Both create room for growth. To see the return, follow what the business did with that room and what happened as a result.

The 50 proposals are the team’s total. Do not multiply the 100 hours by five reps.

Next: why only 40 of these hours count

Back to the money path

Why are only 40 of the 100 hours counted?

Allocation of the freed hours
Where the hours goHoursWhat the example counts
Extra proposals4020 extra proposals (40 ÷ 2 h)
Not assigned yet60No financial credit
Total freed100Capacity, not money

Released time must be deliberately redeployed.

The example gives 40 hours one clear job: more proposals, at two hours each. The other 60 hours may go to follow-up, qualification, account research, training, delivery support or process improvement. They may also go to nothing valuable yet.

Counting all 100 hours as revenue would assume demand, action and accepted output that have not happened. Do not count the same 40 hours twice, either. The time is the capacity. The proposals are what the team produced by redeploying it.

Owner decision: choose the next valuable use for released time, assign an owner, and track whether the work is completed and accepted.

Choosing a job for the other 60 hours
Follow-up
Track follow-ups done, then the sales that result.
Qualification or account research
Track qualified opportunities added to the pipeline.
Delivery support
Track days to onboard and rework rate.
Training or process improvement
Name the measure it should move before the time is spent.

If nobody can name a use yet, record that plainly. Unassigned time stays out of the financial story until it has a job and a result.

Next: do the 20 proposals have real buyers?

Back to the money path

Do the 20 extra proposals have real buyers?

40 h ÷ 2 h each = 20 extra proposals

  1. Qualified opportunity
  2. Correct scope, price and customer facts
  3. Reviewed by your team
  4. Actually sent
  5. Follow-up with a next action
Each of the 20 has to clear this path before it can become a sale.

More capacity is not the same as more opportunity.

Those proposals matter only if they reach qualified prospects with a real opportunity to buy. Otherwise, the business has produced more documents, not more value. Each one must also use the correct scope, pricing and customer information and enter a real sales process.

The 20 are proposals. Customer wins are a separate assumption on the next step.

Owner decision: confirm whether the pipeline can supply 20 additional qualified opportunities. If not, use the released capacity first for qualification, follow-up or improving conversion on existing opportunities.

What the 2 hours has to cover

The extra proposals are counted at the same two hours as the first 50, so they must meet the same standard. Rushing the extra proposals with a lighter review would make the arithmetic look right while the comparison stops being fair.

If the pipeline cannot supply 20

Change the number in your own version of this chain. Your count of real opportunities sets how many extra proposals are worth sending, even when the hours would allow more.

Next: how five assumed wins become $50,000 booked

Back to the money path

How do five assumed wins become $50,000 booked?

20 proposals × 25% assumed close5 new clients

5 clients × $10,000 each$50,000 booked

Bookings begin only after an actual sale.

$50,000 is booked value. It is not collected cash, delivered revenue or profit. The sale must be real, accepted by the customer and recorded under the company’s normal definition of a closed deal.

The 25% close rate and $10,000 value are assumptions for this example. They are not conversion claims, typical results or evidence from a client. Five wins are not guaranteed.

The sales team should track the actual path:

  1. Opportunity
  2. Proposal
  3. Accepted sale
  4. Contract or order
  5. Delivery handoff

Owner decision: compare additional proposals with actual accepted sales, not activity alone.

If proposals rise but sales do not
Qualification
Are the extra proposals reaching people who can buy?
Offer quality
Does the proposal answer what this customer asked for?
Pricing
Where do lost proposals stall once the price is on the table?
Follow-up
Does every sent proposal have a defined next action?
Demand
Is there enough real demand for this many proposals?

Next: what has to happen during delivery

Back to the money path

What has to happen before there is gross profit?

  1. $50,000 booked
  2. All 5 jobs served and accepted
  3. Direct cost holds at the assumed level
$35,000 $15,000

Direct cost implied by a 30% margin Conditional gross profit: $50,000 × 30%

A sale creates an obligation, not profit by itself.

The $15,000 makes sense only if the company can deliver the work at the assumed direct cost and accepted quality. It is still before AI setup and running costs.

Check before trusting the number
CheckIf it fails
Enough delivery capacity?Orders wait and the profit waits with them.
Completed on time?Revenue the company can recognize, and the bill, may slip.
Staff hours and direct cost as assumed?The 30% margin is no longer the right figure.
Rework under control?Repeat work reduces the margin.
Delivered and earned?Apply your company’s accounting rules before counting it.

Owner decision: confirm delivery capacity and measure accepted completion, direct cost, staff hours per job and rework before scaling the sales input.

Why $50,000 × 30% is only shorthand

The formula assumes the same $50,000 is fully served and earned at the assumed direct cost. Serve fewer clients or spend more delivering, and the result changes. Use it to size the opportunity, then replace it with actual delivered value and actual direct cost.

Why sales and delivery gains do not simply add up

Sales capacity and delivery capacity are related, but their returns are not automatically additive. A proposal creates value only if the promised work can be delivered. Step 4 shows what happens when one department speeds up and the next one does not.

Next: where AI costs fit

Back to the money path

Where do AI costs fit?

$15,000Conditional gross profit minus Your amountAI setup, one time minus Your amountAI running costs, recurring equals Net returnCalculate once costs are known

The improvement has an investment side.

This example does not supply AI setup or running costs, so it stops here instead of inventing them. Subtracting a made-up figure would produce a confident answer with nothing behind it. A workflow can cost more than a recurring license, so list the full set:

Costs to record separately
One timeRecurring
Setup, integration and configurationLicenses and usage
Source cleanup, permissions and testingSupport and upkeep
Staff trainingOngoing quality review

Owner decision: record one-time and recurring costs separately, then compare them with actual incremental gross profit or other verified financial benefit.

Why this page shows no ROI percentage

A percentage needs a real cost to divide by. None is supplied, so any figure here would be fiction. Calculate yours after actual costs and actual incremental profit are known.

Avoid deducting the same cost twice

If a cost is already inside direct cost, it already reduced the 30% margin. Do not subtract it again as an AI cost. Decide where each item belongs, and compare benefit and cost over the same period.

Next: when booked value becomes cash

Back to the money path

When does booked value become cash?

  1. Booked sale
  2. Delivered work
  3. Correct invoice
  4. Invoice sent
  5. Payment received
Measure the time from invoice sent to payment received. Your own records supply that time.

The final handoff is invoice to payment.

A $50,000 booking is not $50,000 collected cash. Payment depends on delivery, billing accuracy, payment terms, customer approval, disputes and collection timing. Billing can only follow what delivery recorded, so the invoice is built from that handoff.

One sale, four separate totals
StateIn this example
Booked$50,000, assumed
DeliveredFrom your delivery records
InvoicedFrom your billing records
CollectedFrom your payment records. No amount or date is assumed.

Owner decision: measure booked, delivered, invoiced and collected amounts as separate states. Improve the handoff where money is getting stuck.

What Finance should be able to see

When sales records connect to delivery and billing records, the owner can answer five questions: Which accepted work has been delivered? Which completed work has been invoiced? Which invoices remain unpaid? How long does payment take? Does the margin survive through collection?

Why the $15,000 is not cash either

The same discipline applies to the assumed gross profit. It is not net profit, and it is not cash in the bank. Profit describes what the work earned. Cash describes what has been paid.

Next: how Finance tracks this

Back to the money path

Sales: use freed time where demand can absorb it

  1. AI-assisted actionDrafts proposals and follow-ups for review
  2. Activity measureProposals sent, follow-ups done
  3. Business resultNew clients and revenue booked
  4. Next decisionChoose the next priority from the records

Sales can apply the gain to qualified prospect research, proposal preparation, better follow-up and opportunity management. AI can organize opportunity information and prepare a review-ready proposal pack. Do not treat extra proposals as financial return until a customer accepts the work and the sale enters the delivery process.

What the source records may tell you
If the records showNext priority
Proposals and accepted sales both riseCheck that Delivery can take more before pushing further.
Proposals rise, wins do notInspect qualification, scope, pricing, follow-up and demand.
Proposals sent but follow-ups lagPoint freed hours at follow-up on open proposals.
What else to count

Add qualified opportunities to proposals sent and follow-ups done. It shows whether activity is reaching real buyers before sales results arrive.

See this in the worked example

Back to the money path

Delivery and service: turn capacity into completed, accepted work

  • Days to onboardBefore: your recordAfter: your record
  • Rework rateBefore: your recordAfter: your record
Two measures to fill in from your own job records. No figures are assumed.
AI-assisted action
Speeds onboarding and catches rework early. It can also organize service information, prepare work and flag missing inputs.
Activity measure
Days to onboard and rework rate, alongside jobs completed, staff hours per job, response time and service exceptions.
Business result
More work delivered and clients retained, with accepted completion at the expected direct cost and quality.

Next decision: determine whether delivery can absorb more sales without delays, quality loss or margin compression.

Where else freed delivery time can go

Delivery can use released time to complete more work, improve service, reduce rework or protect client retention. These are choices. Pick one, track what gets delivered and at what cost, and keep that result separate from the sales example.

See this in the worked example

Back to the money path

Finance: connect activity to the actual economics

  1. Sales record
  2. Delivery record
  3. Invoice
  4. Payment
Finance needs timely records from each department to see what happened after the activity count.
From measure to decision
MeasureDecision it supports
Margin per serviceWhich services to price differently or promote
Staff hours per jobWhere to staff up, and where work takes too long
Invoice sent to cash receivedWhere billing or collection needs attention. Track this separately.
Outstanding invoicesWhich delivered work still has to turn into cash

AI can organize approved activity and financial records for review and show margin by service and staff hours per job. The result is clearer pricing, staffing and cash decisions, based on current records.

Next decision: determine whether the work was delivered, invoiced correctly, paid on time, and profitable after direct costs and AI costs.

Why these stay in separate layers

Margin, cost, payment terms and collection answer different questions. Keep them visible separately so that a healthy booking total cannot hide a thin margin or a slow-paying customer.

See this in the worked example

Back to the money path

Step 3 · Business development example, hypothetical

Better partner research could lead to one assumed $12,000 customer

A sample BD team spends less of its month on research and more on relevant partner follow-up. Follow those hours through the network, across the handoff to Sales and into finished work.

Tap any picture for the math and the owner’s decision. Orange marks what has to be true.

Follow-ups, introductions, qualified opportunities, booked sales, delivered work and gross profit are different states, and each step can fail. All figures are hypothetical for one month, including the 25% close rate. This is not a client result, a typical result or a guarantee.

The reasoning behind each step

Where did the 12 released hours come from?

Before: 24 × 45 min = 1,080 min 18 h
After: 24 × 15 min = 360 min 6 h12 h released
Research hours for the same 24 briefs in one month.

Research became faster without removing review.

The team prepares 24 partner or account briefs each month. AI can organize approved information and prepare a research pack, so each brief falls from 45 minutes to 15. That frees 18 − 6 = 12 hours for the same workload.

The 15 minutes has to include the review. A responsible person still confirms what is worth using, and checks the four things below against what they know.

Research brief: reviewed before use

Account
Is this the right company to approach?
Relationship
Who can actually make the connection?
Timing
Is there a reason to reach out now?
Context
What is relevant to this partner and this account?

Owner decision: define a research brief that Sales trusts.

When a fast brief costs more later

If the brief is fast but inaccurate, the business has reduced preparation time while increasing downstream waste. Follow-ups go to the wrong partner, and Sales spends time on accounts it would have turned down. Count that rework against the 12 hours before treating them as released.

Next: why only 8 of these hours are reused

Why are only 8 of the 12 hours reused?

8 h × 60 min ÷ 30 min each = 16 prepared follow-ups

Each block is one released hour. Each green hour holds two 30-minute follow-ups. The 4 dashed hours get no financial credit.

Redeployment creates the opportunity.

Released time earns nothing by itself. This example gives 8 hours one clear job and leaves the other 4 outside the money. They may support relationship maintenance, account planning, training or other work, but they do not automatically become revenue.

A follow-up counts only if it does the job. This is not a license to send generic automated messages.

  1. Built onThe reviewed account research
  2. Says whyA relevant reason to contact this partner
  3. Asks forThe specific introduction requested

Owner decision: assign the eight hours to a named BD owner and measure whether the follow-ups are relevant, completed and responded to.

What if nobody owns the eight hours?

Then they tend to dissolve into the rest of the month, and the 16 follow-ups never exist. The count in this example starts only when a named person has the hours and the list of partners.

Next: how follow-ups become qualified opportunities

How do follow-ups become qualified opportunities?

  • 16 follow-ups from BD
  • 8 partners introduce an account
  • 4 accepted by Sales
Both step-downs are assumptions for this example, not typical rates.

The relationship pathway matters.

A warm introduction is not revenue. It is an upstream event that may create access to a real buying conversation. Sales then decides whether the opportunity meets its qualification standard.

The context has to survive the handoff, or Sales starts again from nothing:

Handoff note: BD to Sales

Who and whom
Who introduced whom
Why
Why the connection is relevant
Problem
What problem may exist
Next action
Who owns it

Owner decision: inspect the step from introduction to qualified opportunity.

If introductions happen but qualification does not, check
TargetingAre these the accounts Sales wants?
Partner selectionCan this partner reach real buyers?
Message relevanceDid the follow-up give a reason that fits?
Qualification definitionDo BD and Sales mean the same thing?

Next: how one assumed win becomes $12,000 booked

How does one assumed win become $12,000 booked?

4 qualified opportunities × 25% assumed close1 win

1 customer × $12,000$12,000 booked

A qualified opportunity still has to become a sale.

The 25% rate is an educational assumption, not a typical result or promise. The sale must be accepted by the customer and recorded under the company’s actual definition of booked business.

BD does not get credit for revenue merely because a partner made an introduction. Sales has to confirm five things first:

  • Need
  • Fit
  • Scope
  • Price
  • Buying decision

Owner decision: compare partner source, qualification, accepted sale and eventual delivery. Keep introduction activity separate from sales performance.

One record, four separate columns
ColumnThe question it answers
Partner sourceWhich relationship started this?
QualificationDid Sales accept it for active pursuit?
Accepted saleDid the customer actually buy?
DeliveryWas the work completed?

Read across a row to see which partners bring real customers, not just busy introductions.

Next: where the conditional $3,600 fits

Where does the conditional $3,600 fit?

$8,400$3,600
Gray is the direct cost implied by a 30% assumed margin. Green is conditional gross profit: $12,000 × 30%. Both apply only if the work is delivered at that cost.

Booked value is not profit yet.

The $3,600 depends on successful delivery at the assumed direct cost. It is before AI setup costs and any additional BD costs, and no amounts are supplied for either. Use your actual costs rather than a made-up figure.

Each step on the value path can fail. A strong partner network does not replace Sales, Delivery or Finance.

  1. Partner research
  2. Warm introduction
  3. Qualified opportunity
  4. Accepted sale
  5. Delivered work
  6. Gross profit

Owner decision: track whether the customer was delivered, what direct costs were incurred, and whether the margin matched the assumption.

Why the 8 follow-up hours are not a cost line here

The 8 hours were already being paid for, so moving them to follow-up does not add a new expense or a payroll saving to this chain. New spending is different: extra BD tools, travel or staff belong in the additional BD costs. Record them in the same period as the benefit.

Back to the start: the research brief

Step 3 · Marketing example, hypothetical

The same $2,000 of media is assumed to bring 10 more qualified leads

A sample marketing team spends less time preparing content and uses part of that time on reviewed tests. Two comparable months then show what changed, what stayed equal and what it could be worth.

Tap any picture for the math and the owner’s decision. Orange marks what has to be true.

Two comparable months, the same media spend

The Improved month shows what the example assumes after testing. It does not prove AI caused the difference.

Raw responses equal too

Baseline month: 40 Improved month: 40

Qualified leads this is what moved

Baseline month: 20 Improved month: 30

Cost per qualified lead $0 to $100 scale, rounded

Baseline month: $100 Improved month: $66.67

Accepted wins 10% of qualified leads in both

Baseline month: 2 wins Improved month: 3 wins

Gross profit before media and AI

Baseline month: $6,000 Improved month: $9,000

Less media deducted once in each month

Baseline month: − $2,000 Improved month: − $2,000

Contribution after media, before incremental AI and test costs

Baseline month: $4,000 Improved month: $7,000

Dollar bars from Booked down share one scale, $0 to $30,000.

Published content, raw responses, qualified leads, wins, booked sales, gross profit and contribution are different measures. All figures are hypothetical for two comparable months. This is not a client result, a benchmark or a guarantee.

The reasoning behind each step

Where did the 24 released hours come from?

Before: 12 pieces × 4 h 48 h
After: 12 pieces × 2 h 24 h24 h released
Preparation hours for the same 12 content pieces in one month.

Comparable content work required less preparation time.

The improved process may help organize approved audience information, customer language, prior campaign learnings and draft content. Human review still determines whether the message is accurate, appropriate and worth testing.

The 24 hours are capacity, not cash savings. Fixed payroll does not fall merely because preparation is faster. The value of this step depends on what the team does with the time.

Owner decision: identify whether the released time will improve testing, audience research, content quality or another approved marketing task.

Value is not the number of posts

The team could spend all 24 hours publishing more. That would raise output without showing that anyone qualified to buy responded. Marketing value is the ability to create relevant audience and message learning that produces more qualified demand from comparable campaign conditions.

Next: what the 12 reused hours do

What did the 12 reused hours do?

One test sheet, sample entry
InputThis test
AudienceHeld the same
MessageChanged and recorded
Offer framingHeld the same
Creative angleHeld the same
Call to actionHeld the same
Changing one meaningful input at a time, where practical, makes the result easier to read.

Testing converts capacity into learning.

The example reuses 12 of the 24 released hours for reviewed audience and message tests. The other 12 hours receive no financial credit. Comparable campaign conditions make the result easier to interpret.

AI may help prepare variations and organize prior learning. A marketer still approves the test, checks compliance and brand fit, and records what changed. Without that record, next month’s team cannot tell which change mattered.

Owner decision: select the next test based on an observed weakness in qualified demand, not simply on the desire to produce more content.

Who does what in a reviewed test
AIPrepares variations and organizes prior learning.
MarketerApproves the test, checks compliance and brand fit, records the change.
OwnerPicks which weakness to work on next.

Next: what improved in the demand path

What improved in the demand path?

Baseline month

40 raw → 20 qualified → 2 wins

Improved month

40 raw → 30 qualified → 3 wins

Each square is one response from one monthly cohort at $2,000 media. Green squares met the qualification standard. Wins use the same 10% rate in both months.

Raw responses stayed the same; qualified demand increased.

The useful change is not more raw activity. It is a larger share of responses meeting the qualification standard, followed by more accepted sales. A qualified lead is still not revenue. It only becomes a win if Sales closes it.

The comparison is illustrative. It does not prove that AI caused the extra win. These could also explain a difference:

  • Offer
  • Audience
  • Seasonality
  • Sales execution
  • Campaign conditions

Owner decision: define “qualified” before testing and inspect the records behind each stage.

Why the definition comes first

If the standard loosens during the test, 30 can look better than 20 with no change in real demand. Hold the standard steady across both months, and check it against what Sales later accepts.

Next: what each qualified lead cost

What did each qualified lead cost?

Baseline: $2,000 ÷ 20 qualified leads

$100.00

Improved: $2,000 ÷ 30 qualified leads

$66.67

Media cost per qualified lead in one monthly cohort. $66.67 is rounded to the nearest cent.

The price of a lead fell because more responses qualified, not because media got cheaper.

Both months spend the same $2,000 and get the same 40 raw responses. Keeping those two inputs equal is what makes the comparison fair. Change the budget at the same time and the unit cost stops saying anything about the message.

This figure counts media only. It excludes staff time, AI costs and test costs, and no amounts are supplied for them. A lower cost per lead is also not a result by itself. A cheap lead that never closes is still a cost.

Owner decision: track cost per qualified lead beside accepted wins from the same cohort, so a falling unit cost cannot hide weak leads.

Why the rounding is shown

$2,000 ÷ 30 does not end in whole cents. Multiplying the rounded $66.67 by 30 gives $2,000.10, so use the $2,000 media figure, not the rounded unit cost, for the money calculation that follows.

Next: how the two months compare financially

How do the two months compare financially?

Baseline: $20,000 booked

Improved: $30,000 booked

Direct cost implied by 30% margin Media, same in both Contribution

Separate bookings, margin and media contribution.

One monthly cohort each, if delivered
LineBaselineImproved
Wins × $10,000 booked$20,000$30,000
Gross profit at 30%, once delivered$6,000$9,000
Less media, once− $2,000− $2,000
Contribution after media, before incremental AI and test costs$4,000$7,000

The gross profit appears only if the accepted work is delivered at the assumed 30% direct-delivery margin. Media is not inside that margin, so it comes out separately, once in each cohort.

The illustrative difference is $7,000 − $4,000 = $3,000. It is conditional, and it stands before incremental AI and testing costs. It is also a comparison of two months, not proof of what caused the change.

Owner decision: compare the full cohort records, then deduct actual incremental AI and testing costs.

Why the 24 hours are not added here

Released hours are capacity, and fixed payroll does not fall because preparation is faster. Adding a dollar value for those hours to the $3,000 would count the same improvement twice: once as time, again as the better results that time made possible.

Back to the tests: choosing the next one

Operations example · one hypothetical month

Cleaner handoffs could make room for 6 more onboardings

A sample onboarding team catches missing inputs before work moves on, so each accepted onboarding takes 4 staff hours instead of 5. Follow the freed time to accepted work first, and to money only after that.

Tap any picture for the math and the owner’s decision. Orange marks what has to be true.

  1. The handoff: catch the gap before the next person starts

  2. The hours: the same month of work, with room left over

  3. The result: accepted work comes first, money after

The 40 hours are capacity, not a payroll savingNo payroll expense disappears unless the company actually avoids a real cost. Count each result once.What must not be counted twice

Hours released, accepted work, delivered value and gross profit are different measures. This hypothetical example stands alone: it is not a client result, researched average or guarantee, and it does not add to the other tabs. If Operations gains room and the next team cannot keep up, the limit simply moves. See how the bottleneck moves

The reasoning behind the Operations example

How did a cleaner handoff release 40 hours?

Onboarding record at the handoff
Customer informationReceived
Required documentsMissing, flagged
Assigned ownerNamed person
Next actionSupply the documents by the due date
Exception statusOpen, so the file cannot move on
The gap is visible at the handoff, with a person and a date attached, before downstream work begins.

The same accepted work required fewer staff hours.

A useful onboarding workflow shows what must exist before work moves forward: customer information, required documents, an assigned owner, the next action and the exception status. If a required input is missing, it goes back to the responsible person first. That prevents the next employee from discovering the problem halfway through the job.

Before: 40 × 5 staff hours 200 h After: 40 × 4 staff hours 160 h40 h
Monthly staff hours for the same 40 accepted onboardings: 200 − 160 = 40 hours released.

The improvement comes from an approved checklist, complete inputs, clearer handoffs and early exception review. The four-hour figure includes the required review and any rework that remains, so the time has not just moved to another desk.

AI may help organize the queue or flag a missing item. It should not silently mark an onboarding complete. The responsible employee confirms whether the file is complete and acceptable, and the 40 hours remain capacity until someone assigns them.

Owner decision: verify that the four-hour process produces the same accepted onboarding standard, not merely a faster incomplete handoff. Then review the most common rework causes and fix the earliest handoff where each one appears.

Who owns each part of the handoff
AI, where used
Organizes the queue and flags a missing input. It does not decide that the file is acceptable.
Responsible employee
Confirms the file is complete and acceptable before it moves.
Owner of the missing item
Supplies it by the due date shown on the record.
Operations leader
Sets the acceptance standard, reviews exceptions and fixes recurring causes at their source.
How to test that four hours is real
  1. Compare the same kind of onboarding and the same acceptance standard.
  2. Log the whole effort, including review, chasing, exceptions and rework.
  3. Follow the files downstream, so problems pushed to the next team go back into the count.

What happens to the 40 freed hours

How do 40 hours become 6 additional onboardings?

The same 200-hour month, reallocated 160 h2416
Where each hour goes
UseMathHours
Original onboardings40 × 4 h160
Additional onboardings6 × 4 h24
Remaining, no financial credit40 − 2416
Total month160 + 24 + 16200

Capacity only becomes value when demand and quality allow it.

The example reuses 24 of the 40 freed hours. At 4 hours each, 24 ÷ 4 = 6 additional onboardings, so accepted starts move from 40 to 46. Saving time does not create those six by itself. They need real customers, a workable schedule and accepted completion.

  • Six customers are waiting. With fewer waiting, there are fewer starts, and the unused hours stay unassigned.
  • Staff can be scheduled. The freed time has to exist in the right people’s weeks, not just as a total on a spreadsheet.
  • Downstream teams hold quality. If the next team cannot absorb six more, the queue has only moved.

The remaining 16 hours may become room for exceptions, training or process improvement. Whatever they are used for, this example gives them no dollar value.

Owner decision: confirm the queue and downstream capacity before allocating the 24 hours to more onboardings, and name who is responsible for them.

What “46 accepted starts” does and does not say

It says 40 original plus 6 additional onboardings met the acceptance standard to begin. It does not say that 46 customers have been fully served, or that the money has arrived. Those are later events with their own records.

How the additional work reaches delivered value

How does capacity become delivered value?

  1. Accepted start6 additional
  2. Completed and servedMust actually happen
  3. Delivered value6 × $2,000 = $12,000
  4. Gross profit$12,000 × 40% = $4,800
The $12,000 at the assumed margin $7,200 cost$4,800
Cost includes direct cost and allocated staff cost. Gross profit is before AI costs.

The six additional starts must reach delivery.

The illustration assumes each additional onboarding earns $2,000 when delivered: 6 × $2,000 = $12,000 of additional delivered value. At a 40% assumed gross margin, $12,000 × 40% = $4,800 of gross profit.

This is conditional. It depends on completing the onboardings, serving the customers and incurring costs at the assumed level. Because the 40% margin already includes allocated staff cost, the staff time is not deducted a second time. AI setup and running costs are not included, and no amount is assumed here. Take them from your own records before calling anything a return.

What to measure, and what it answers
MeasureQuestion
Accepted onboardingDid it meet the same standard as the original 40?
Time to activationDid customers get going sooner, later or at the same pace?
ReworkDid problems return further down the line?
Direct costDid costs stay near the assumed level?
Delivery completionWas the work actually finished?

Owner decision: measure accepted onboarding, time to activation, rework, direct cost and delivery completion before expanding the queue.

What must not be counted twice

What must not be counted twice?

40 freed hours The same hours can take only one road.
This exampleReuse 24 h for more accepted work6 onboardings, then $12,000 delivered and $4,800 gross profit if the conditions hold.
A different, separate eventActually reduce paid hours or a roleNeeds its own evidence of a real expense avoided. Not claimed here.
Hours used for added work cannot also be claimed as a payroll saving.

Released capacity is not avoided payroll by default.

The 40 hours freed from the original 40 onboardings are already used in the capacity model. Claiming those same hours as payroll savings would count them twice. No payroll expense disappears unless the company actually avoids a real expenditure, such as reducing paid hours or eliminating a role, and that would be a separate financial event needing separate evidence.

Allocated staff cost has a similar trap. It already sits inside the 40% margin, so it should not also be subtracted from the $4,800.

One label for each result
LabelExampleWhat it is
Hours released40 hCapacity
Additional accepted work6 onboardingsOutput, if demand exists
Delivered value$12,000Revenue, once delivered
Gross profit$4,800Conditional, before AI costs
Actual AI costYour recordsNot assumed here

Owner decision: label each result correctly as hours released, additional accepted work, delivered value, gross profit and actual cost, and keep them separate in every report.

When could a payroll saving be real?

When the payroll actually falls, and the records show it. That is a decision about paid hours or roles, with its own evidence and its own effect on capacity. Those hours would no longer be available for additional onboardings, so the two stories cannot share them.

Back to where the hours came from

Billing & Finance example · one hypothetical monthly batch

The same $40,000 could arrive 8 days sooner

A sample business finishes 60 jobs, and 20 invoices wait on missing completion records. Cleaner records bring that cash in sooner. They do not create more of it. A separate job then shows what good records reveal about margin.

Tap any picture for the math and the owner’s decision. Orange marks what has to be true.

  1. The batch: work is finished, but not all of it can be billed

    Existing work, recorded as completed $120,000 to bill 60 completed jobs × $2,000 each at the assumed agreed price, subject to price and scope checks. Each square below is one invoice.
  2. The route: one handoff, a different owner at each step

    AIFlags missing completion data Accountable employeeAdds the completion record Authorized reviewerChecks price and scope BillingSends the invoice FinanceTracks the outstanding balance CustomerPayment received Who owns each handoff

    The completion record is accurate

  3. The timing: only the 20 held invoices, days after completion

    Before: 10 days to invoice + 30-day terms = paid on day 40 10 d30-day terms After: 2 days to invoice + 30-day terms = paid on day 32 30-day terms8 d Waiting to be invoiced Customer’s payment terms Cash in 8 days earlier The same 20 × $2,000 = $40,000 in both lanesEarlier cash, not new revenue or profit. A one-time timing shift for this cohort, not a monthly gain.How to read the 8 days

    Customers pay on time in both lanes

Timing questionHow quickly does completed work become cash? Margin questionDid the work earn what was expected? The owner’s next interventionBilling workflowCollection follow-upPricingStaffingDelivery processDecide where to act next

The $40,000 cohort and the $4,000 job are separate illustrations, and their numbers do not add together. AI costs are not assumed here. Take them from your own records and assess them once, not out of invoice principal. This hypothetical example stands alone: it is not a client result, researched average or guarantee, and it does not add to the other tabs.

The reasoning behind the Billing & Finance example

What is delaying the $40,000?

60 completed jobs × $2,000 = $120,000 to bill 40 ready · $80,00020 held · $40,000
One held invoice
JobCompleted
Completion evidenceMissing, flagged
Responsible employeeNamed, with a deadline
Price and scope checkWaiting for the record
The $40,000 is part of the $120,000, not an addition to it.

The work is complete, but the record is not.

The monthly batch is 60 completed jobs at $2,000 each, or $120,000 to bill once price and scope are checked. Forty are ready to invoice, worth $80,000. The other 20, worth $40,000, are held. They are not new sales. They are completed existing work that cannot yet be invoiced because the completion evidence is missing.

The workflow should identify the missing record, name the responsible employee and show the deadline. AI may flag the gap. The employee must add the completion record, and an authorized person must check price and scope. Billing can only be as good as the record Operations hands over.

Owner decision: find the exact handoff causing invoice delay, then give that handoff one named owner.

What a billing-ready record has to answer
Was it finished?
Completion evidence exists, and the responsible employee has recorded it.
What can be billed?
Price and scope match what was agreed, confirmed by an authorized person.
Who acts next?
Any gap shows a named person and a deadline, not just a warning.

How earlier invoicing changes cash timing

How does earlier invoicing change cash timing?

Before: 10 + 30 = day 40 10 d30-day terms After: 2 + 30 = day 32 30-day terms8 d
Days after completion for the 20 held invoices only. Both lanes assume customers pay on time.

The same $40,000 arrives sooner, not larger.

For the 20 held invoices, the delay before invoicing falls from 10 days to 2. Payment terms stay at 30 days. Cash therefore arrives 32 days after completion instead of 40, moving the same 20 × $2,000 = $40,000 eight days earlier. The 40 ready invoices are not part of this comparison.

This is earlier collection timing, not additional revenue, profit or guaranteed cash. It can make cash easier to manage, but the $40,000 is the expected billable value of work already done. Do not annualize it, or count it as a monthly financial gain or a return on AI.

The dates that prove it
RecordWhat it shows
Completion dateWhen the clock starts
Invoice dateThe delay the workflow can change
Due dateWhat the terms require
Payment dateWhen the cash actually arrived
Collection statusWhat is still outstanding

Owner decision: measure completion date, invoice date, due date, payment date and actual collection status, then compare them with the assumption.

What if customers don’t pay on time?

Then the eight days is not what you will see. An earlier invoice only moves the due date. Late payment is a separate collection problem, and it needs its own follow-up and its own measurement.

What the shared workflow actually does

What does the shared workflow actually do?

  1. AIFlags missing data
  2. EmployeeAdds the record
  3. ReviewerChecks price and scope
  4. BillingSends the invoice
  5. FinanceTracks balance and payment
One handoff connects completion to billing. Each step has a different responsibility.

One handoff connects completion to billing.

AI can organize or flag information. The employee owns the missing operational record. The reviewer approves the invoice inputs. Finance tracks the outstanding balance and the payment. Treating these as one automated step is how errors go unnoticed.

If the completion record is inaccurate, faster invoicing only creates faster disputes. So the review stays in the workflow, and the time it takes stays in the count. The gain comes from finding the gap early, not from skipping the check.

If nobody owns the flag
The warning sits in a list, and the invoice stays held.
If the record is guessed
The invoice goes out fast and comes back as a dispute.
If nobody checks price and scope
The customer may be billed the wrong amount.
If the balance isn’t tracked
“Sent” gets mistaken for “paid”.

Owner decision: assign one owner to every handoff and review the exceptions, rather than assuming the software has completed the process.

Why this depends on Operations

Billing and Finance need timely numbers from each department. The completion record starts in the team doing the work, so a billing delay is often an operations handoff problem that only shows up in Finance. Fix it where it starts.

What the margin lens reveals

What does the margin lens reveal?

Planned $800$2,000$1,200 Actual $1,200$2,000$800
One job at a $4,000 price, split into staff cost, other direct cost and gross profit.
The job sheet
LinePlannedActual
Price$4,000$4,000
Staff hours4 h6 h
Staff cost at $200 per hour$800$1,200
Other direct cost$2,000$2,000
Total cost$2,800$3,200
Gross profit$1,200$800
Gross margin30%20%

Earlier billing does not repair weak job economics.

This is one separate $4,000 job, not part of the $40,000 cohort. The $200 an hour is an internal allocated staff cost, not the rate charged to the client. Two extra staff hours at $200 add $400, taking total cost from $2,800 to $3,200 and the margin from 30% to 20%.

The records reveal that $400 overrun. They do not recover it, and neither does collecting the invoice sooner. The job still earned $800 instead of $1,200. The value of seeing it comes only if the business changes something on future work.

Owner decision: use actual job records to change future pricing, staffing, scope or process.

Where do AI costs fit?

They come from your actual records, and no amount is assumed here. Charge a cost to one place only: if it is already in a job’s direct cost, don’t subtract it again in the overall assessment. Never deduct it from invoice principal to create a cash “return”, because the principal was already owed.

What the leader should measure next

What should the leader measure next?

Cash timingCompleted → invoiced → outstanding → paidThe $40,000 cohort: how quickly does completed work become collected cash?
Unit economicsPrice → staff hours → direct cost → gross profit → gross marginThe $4,000 job: did the work earn what was expected?
Two lenses on the business. Neither creates new sales, and their numbers do not add together.

Separate cash timing from profitability.

Finance should maintain both lenses. Earlier payment can improve cash availability, but it does not turn a low-margin job into a high-margin job. A strong margin does not help if finished work sits unbilled. When the activity records and the financials sit together, leaders can see their numbers and margins and decide what to improve next instead of guessing.

What you see, and where to act
What the records showLook first at
Finished jobs wait to be invoicedBilling workflow and the completion handoff
Invoices are sent, but paid lateCollection follow-up
Costs are on plan, but margin is thinPricing
Jobs regularly take more hours than plannedStaffing or scope
The same overrun or rework keeps returningDelivery process

Owner decision: decide whether the next intervention belongs in billing workflow, collection follow-up, pricing, staffing or delivery process.

How to assess this properly, including AI costs
  1. Report cash timing as days and timing, without converting the invoice principal into a gain.
  2. Report margin changes from actual job records on future work, not from the overrun already revealed.
  3. Enter actual AI setup and running costs from your records once, in the overall assessment.
  4. Keep the timing and margin results side by side, not added into a single return figure.

Back to the held invoices

Step 4 · Bottlenecks

AI can grow useful capacity. The next team has to keep up.

In this illustration, AI is scaled across one department. Its extra work can outgrow the next team’s capacity.

Illustrative AI capacity path, not a required order

  1. 1One person

    AI added
    Customer context and first drafts.
    Capacity gained
    One salesperson does more useful work and reviews every draft.
    New pressure
    No downstream queue shown in this example yet.
  2. 2The sales lead

    AI added
    Sight of team activity, in the lead’s own work.
    Capacity gained
    Faster decisions and coaching reach the team.
    New pressure
    Not yet shared department infrastructure.
  3. 3The whole Sales department

    AI added
    Shared customer data, connected tools, training.
    Capacity gained
    AI increased Sales capacity across the team.
    New pressure
    Extra won work reaches Operations, still at its prior pace.

    Only if the demand, quality and conversion are real.

  4. 4Equip Operations

    AI added
    Planning from agreed scope, shared context, training.
    Capacity gained
    More accepted delivery. Sales stays enabled.
    New pressure
    Accepted work waits on Billing’s prior pace.
  5. 5Equip Billing

    AI added
    Timely completion records; invoice drafts a person reviews.
    Capacity gained
    Invoicing keeps pace with delivery.
    New pressure
    None automatic. Paying is still the customer’s step.
  6. 6Why return to demand?

    Your teams can now handle more work. Next, check whether enough right-fit customers are coming in.

    AI added
    Research into which customers fit.
    Capacity gained
    Sales, Operations and Billing have room.
    Next question
    Is enough qualified demand coming in? Explore what to check.
Illustrative capacity, no numeric scale and not a required order. People are artwork, not department sizes. Start where the constraint is, with the right lead, and prepare the next team.
Explore each department

Sales · moments 1 to 3

How does AI add Sales capacity, from one person to the whole department?

AI’s reach can grow from one salesperson, to the sales lead, to the whole team. Each step adds useful capacity. A whole department with more capacity can then send more work to Operations than it can handle.

  1. One person

    Their own files, customer context and AI first drafts. They check and send. Quick to set up, and the gain can show sooner, with a narrower direct reach than equipping the leader or team.

  2. The sales lead

    Uses AI in their own work, sees team activity sooner and gives faster feedback. Better placed to choose tools, train the team and hire.

  3. The department

    Shared customer data, connected tools, training and a review routine across Sales. It takes more time, money and infrastructure, and it adds capacity across the whole team.

An illustration of how far AI reaches, not a required order. A department lead is often the practical place to start.

The same inquiry, before AI support

An inquiry arrives late in the week. Days later the rep writes a proposal from scratch, from memory.

The customer has moved on, or is won with a vague scope that Operations has to rebuild.

The same inquiry, Sales equipped

AI drafts the first reply and a proposal from the call notes and the customer record. The rep checks, corrects and sends it.

The sales lead sees which opportunities have no next step and coaches that day. The won order reaches Operations as a complete handoff.

Why more Sales capacity can outrun Operations

Reclaimed time goes into reaching more qualified prospects and following up better. If that turns into more won work, it arrives at an Operations team still set up for its usual workload. The orders wait. Sales did nothing wrong. It now does more than the next team can handle.

Handoff to Operations

  • Customer and contact
  • What was sold, in plain words
  • What was promised, and by when
  • A named delivery owner
  • Documents and details to start

What must be in place

  • The demand is real. Qualified opportunities, not a list of names.
  • A person reviews. AI drafts and flags. The salesperson confirms what goes out.
  • One customer record. Sales and Operations read the same details.
  • Sell what can be delivered. A faster close with a vaguer scope only moves the problem along.
  • Ask Operations now. While Sales gains capacity, ask what delivery needs to handle more work. Don’t wait for a pile-up you can see coming.

Next question: is Operations ready for the extra won work? If customers won are waiting to start, equip Operations next.

Sales · a deeper question

How do we roll this out, department by department?

Use the same method in every department. Add capacity where the work is worth doing, check the work and its quality, and get the next team ready before the extra work reaches it.

  1. 1 · Choose work that matters financiallyLook for the work people could do faster or better. Check whether the rest of the business can handle the gain.In Sales: replies, follow-up and proposals for real opportunities.
  2. 2 · Equip the leaderTheir own context and tools, sight of team activity, and a daily routine that uses them.In Sales: the sales lead drafts with AI and reviews pipeline gaps each morning.
  3. 3 · Build shared data, tools and trainingStructure the data first, then reports people can read, then tools for daily work. Train the team on them.In Sales: one customer record, connected tools and a review routine.
  4. 4 · Check useful work, quality and cost, and prepare the next teamTrack what people do and what gets done, alongside the financials. Ask the next lead what more work will need.In Sales: follow won customers into a clean start in Operations.
  5. 5 · Reassess and extendWhen the next team can’t keep up, equip it, building on what the first leader learned.In Sales: won work now waits for delivery, so Operations is next.

Then repeat in the next department: Operations, then Billing, then back to demand.

One method, repeated. The examples are illustrative.

Leader first, then the department

Setting up one person takes less time and infrastructure, and the gain can show sooner. A leader’s gain spreads further: they watch the work, give feedback, and are better placed to choose tools, train the team and hire.

A department rollout takes more time, money and shared infrastructure, such as a shared database and connected tools. It adds output across the whole team.

Look ahead while you equip the current team

  • Don’t deploy everywhere at once. Don’t ignore the next team either.
  • Ask the next lead now. What would break if more work arrived? Prepare before work piles up.
  • Fix the right work. Doing the wrong work faster may save time without improving the business result.
  • Keep a person accountable. AI drafts and flags. The owner confirms.

Owner’s next step: choose one department and its leader. Equip them, check the useful work and its quality, and ask the next team what it needs before the extra work arrives.

Operations · moments 3 and 4

Sales gained capacity. Why does work now wait in Operations?

At first, delivery can still handle only its usual workload. More customers won means more work to deliver. If Operations still plans, schedules and checks work the old way, the extra work waits and quality is at risk.

Before its rollout
Plans rebuilt from email threads. Same pace as before while more won work arrives. Commitments queue.
With AI support
Plans drafted from agreed scope, shared job context and team training. The lead confirms. Sales stays enabled.
Downstream
More accepted delivery reaches Billing, which is still at its prior pace.
Illustrative people and work. Operations plans from the Sales handoff: customer, scope, expectations, owner and information.

A new job, before Operations is equipped

The job arrives with its scope spread across an email thread. The team rebuilds the plan, finds a missing document halfway through and stops.

Finished jobs are reported as “done” in a chat message.

The same job, Operations equipped

AI checks the incoming handoff against what the job needs and drafts the plan and schedule. The operations lead confirms them. Gaps go back to a named person before work starts.

AI drafts the completion record from the work log, and whoever did the work confirms it.

Owner, and the team setup

Owner: the operations or delivery lead. Once equipped, they can see which jobs are stuck, give feedback sooner and decide where the team needs tools, training or another hire.

What changes: Operations can deliver more work, improve service and keep up with what Sales brings in. Track what gets delivered and at what cost.

Handoff to Billing

  • Work finished, listed against what was sold
  • Completed by a named person
  • Accepted, where required
  • Billable extras agreed along the way
  • Ready to bill, confirmed by a person

What must be in place

  • Freed time reaches the right people. Hours saved and useful output are separate. Check whether the gain reaches the people and steps that govern delivery.
  • Quality holds. Faster delivery to a lower standard creates rework later.
  • One written meaning of “done.” Operations and Billing use the same one.
  • Cost is tracked. Delivering more only helps if the margin holds.
  • Ask Billing now. Can it handle more completion records before they arrive?

Next question: is Billing ready? If jobs finish on time and accepted work waits for an invoice, equip Billing next.

Billing · moments 4 and 5

Delivery gained capacity. Why is Billing now behind?

Operations finishes more, but Billing was set up for the old pace and may struggle to see what was completed or ready to bill. Delivered, invoiced and paid are three separate events, each with its own owner and record.

Delivered
Owner: Operations. Completion record, accepted where required. Not yet an invoice.
Invoiced
Owner: Billing. An invoice a person reviewed, sent to the right contact. Not yet payment.
Paid
The customer pays. In this example, Billing or Finance records the payment and matches it to the invoice, and the named owner follows up if it is late.
Three separate markers. One moving does not prove the next. Nothing here gets paid automatically.

The same job, before Billing is equipped

Delivery posts “done” in a chat. Billing asks what was finished, whether the customer accepted it and whether extras were agreed. The invoice waits until someone answers.

Unpaid invoices get chased only when someone remembers.

The same job, Billing equipped

AI assembles a draft invoice from the completion record and flags anything missing, such as an approval. A billing person confirms it and sends it.

Open invoices get a scheduled follow-up, and the billing lead can see which are overdue without building a report.

Owner, and what changes

Owner: the billing or finance lead. Billing and finance get timely numbers from each department, so leaders can see revenue, costs and margins and decide what to improve next.

What must be in place

  • One meaning of “done.” The same one Operations uses.
  • Billing sees completed work. It shouldn’t have to ask for it.
  • A person confirms. AI can assemble the invoice and flag gaps. The responsible person says it is ready.
  • Watch the three separately. Track invoice delays and time to payment on their own.

Next question: if invoices go out promptly and every team has room, is enough qualified demand coming in?

Marketing & demand · moment 6 · reassessment

Every team has room. Is there enough qualified demand that fits?

When Sales, Operations, and Billing have room, “back to demand” means checking whether enough right-fit customers are coming in for the capacity the business can actually deliver. AI may support research and follow-up. It does not create automatic demand or automatic payment.

Work Marketing does
Decide who the business serves best, shape offers for them, and pass qualified opportunities to Sales.
With AI support
Research who to reach, draft and test messages, reply to inquiries faster. A person decides.
Handoff to Sales
Who, need, source and why they fit, with enough context to reply well the same day.
Going back to the front means reassessing demand. Cash is not automatically reinvested.
Signs that tell you where to look next
What you seeWhere to look first
Teams have room and little work is waitingDemand: are enough qualified opportunities coming in?
Opportunities arrive but rarely fitTargeting and qualification, before more volume
Finished work comes back for reworkQuality in Operations, before more demand
Invoices go out but payment lagsPayment follow-up in Billing

Owner

The marketing lead, or the business owner if there isn’t one. The lead sees which sources produce opportunities that become paying customers.

  • Numbers from Billing. Know which work pays before going after more of it.
  • Room confirmed. Ask Sales and Operations how much room they really have, and check again as volume rises.

Owner’s next step: walk one customer from first inquiry to payment with the person who owns each handoff. Find where real work now waits, equip that team, check the result, then repeat.

Step 5 · Our assessment

How we decide where AI should work first

Find the work that matters to the business result, from revenue and margin to service and quality. Equip its lead, then check the business can handle the gain.

Evidence first department and leader checked rollout reassessment

  1. Evidence Raw records become something leaders can read 1 Map where money is made 2 Read the data
  2. Decision A leader picks one priority that matters financially 3 Pick the first priority 4 Equip the lead, then the team
  3. Checked rollout The team adopts it, and the result is checked 5 Measure the result 6 Reassess
A new limit appears → back to the evidence
Illustrations show the kind of work involved, not a client, headcount or result.

How the assessment works, step by step

Step 1 of 6

Map where money is made

Start with the activities that drive the business: sales, delivery, customer service and finance. This is a map of the work, not a list of software.

  1. Opportunity
  2. Customer commitment
  3. Delivered work and service
  4. Completion information
  5. Invoice
  6. Customer payment separate from delivery and invoicing
Amber marks a handoff, where one team passes information to the next. Invoicing and payment are separate steps.

Illustrative example

A service business is winning new customers, but its delivery teams spend time rechecking what was promised, answering avoidable questions or correcting incomplete handoffs.

The map shows where that effort sits between the commitment and the delivered work, before anyone decides that this is where AI should go.

What the owner checks

  • Which activities directly affect sales, delivery, service or margin?
  • Where do people repeat work, wait for information or make avoidable decisions manually?
  • What must pass from one department to the next?
  • Could the rest of the business handle more useful work if this improved?

Condition: the first department isn't assumed. It's chosen once the business evidence supports it.

Next: read the data →

Step 2 of 6

Read the data

Read team activity and financial information together. Neither view is enough on its own.

ActivityWhat work is happening, where time goes, where people wait or repeat tasks

FinancialsWhether that work affects revenue, cost or margin

Read togetherDoes this work matter, and could the next team absorb an improvement?

Two partial views become one picture a leader can act on.

Illustrative examples

A sales team may be responding quickly, yet the business still loses value because customer commitments are unclear, or because Operations can't deliver what Sales promised.

Operations may look busy because the team is doing rework rather than producing accepted delivery.

Hours saved and useful output aren't the same thing. Time back is room to work with. Useful output is what actually gets done with that room.

What the owner compares

  • What people are doing
  • What useful output is being produced
  • Whether quality is maintained
  • What the work costs
  • Whether revenue or margin is affected
  • Whether downstream teams can absorb an improvement

Next: pick the first priority →

Step 3 of 6

Pick the first priority

Choose where improvement could matter most, not where AI looks easiest to install.

  • SalesQualified follow-up is delayed
  • DeliveryAn activity creates rework
  • ServiceWork consumes leadership attention
  • FinanceCompletion and invoicing information arrives late

Ask each one the same questions: does it matter financially, is the information there, is the next team ready?

One first priority, chosen from this business's evidence

These are possible priorities, not a score or a recommendation. The evidence decides which comes first.

Follow the mechanism

If improving one activity creates more customer commitments, can Operations deliver them? If delivery improves, can Billing get complete information and issue invoices? Even when invoices go up, customer payment is still a separate step.

Speed isn't the only gain. Accuracy, service and quality can be the thing worth improving.

What the owner checks

  • Does the opportunity connect to meaningful business value?
  • Is the work understood well enough to improve?
  • Is the information available, or could it be structured?
  • Which downstream handoffs need preparing first?
  • Is this really a process, prioritisation, quality, staffing or information problem?

Condition: buying software or adding staff is not a diagnosis.

Next: equip the lead, then the team →

Step 4 of 6

Equip the lead, then the team

Start with the head of the department where improvement will matter most, then build on what they learn.

Leader firstTheir own tools, files and review routine. One person's setup is simpler and can show a larger percentage gain sooner.

Then the departmentShared data, connected tools and team training. This takes more time and cost, and may show a smaller percentage gain, but it adds more total useful output.

Illustration of the sequence, not a required headcount or timeline.

Why the leader first

When a sales, operations or billing leader uses AI in their own work, they can see team activity sooner, give faster feedback and coach more effectively. One setup then has a wider effect, and the leader is better prepared to choose tools, train the team and hire where needed.

This isn't a rule every business must follow. It's a way to widen reach while keeping control of quality and adoption. A person still confirms AI-assisted work.

What the owner checks

  • Is this the leader where improvement matters most?
  • What does the leader's routine show that should be standardised?
  • Is the department ready for shared data, tools and training?
  • Who reviews the work before it moves on?

See the data foundation behind both setups →

Next: measure the result →

Step 4 · Foundation

Build the data foundation

Structure the data first, then turn it into reports people understand, then build tools the department uses every day.

  1. 1 Structured dataActivity and financial records structured consistently, with clear sources and ownershipA person checks it's complete
  2. 2 Reports and visualsNumbers and margins leaders can actually readA person checks it makes sense
  3. 3 Daily toolsEach department using that data in its everyday workA person confirms the work
Each layer produces something different and relies on the one beneath it.

What it makes possible

Track what people do and what gets done. Combine those measures with the financials so leaders can see their numbers and margins, understand where capacity runs out and decide where to invest next.

Why the order matters

Incomplete or inconsistent records can carry gaps into reports and daily tools. Structure and check the information first, so each layer gives leaders a clearer view of activity and results.

Step 5 of 6

Measure the result

Look at output, quality, actual cost and margin together. "The team is faster" is not where the check stops.

  1. Delivered
  2. Invoiced waiting on completion information
  3. Paid the customer's step, not proved by delivery or invoicing
  • Useful output
  • Quality
  • Actual cost
  • Financial result
  • Next team ready
Delivered, invoiced and paid stay separate. A gain in one doesn't prove a gain in the next.

Illustrative example

A delivery team completes more work, but Billing receives incomplete completion information. Delivery has improved, but the business hasn't yet turned that improvement into invoices.

Faster work helps most when it stays accurate, supports the customer and contributes to the result being pursued.

What the owner checks

  • Did useful output increase?
  • Was quality maintained?
  • What did the work actually cost?
  • Did the relevant financial result improve?
  • Was the next department ready?
  • Where did useful work start to wait?

Condition: prepare the next team before work piles up. Don't wait for a preventable failure to prove the handoff mattered.

Next: reassess →

Step 6 of 6

Reassess

After an improvement, map the flow again. A successful change can expose a different limit.

  1. More useful sales capacity can outrun Operations
  2. Improved Operations can outrun Billing's completion and invoicing
  3. Sales, Operations and Billing all have room. Is there enough right-fit demand?
  4. Back to the evidence step 1, with the new limit
Illustrative sequence. The next limit in a real business isn't predetermined.

Return to the evidence

  • What improved?
  • What became newly limited?
  • What should be addressed next?

The next priority could be another department, a handoff, quality control, how information is structured, or demand fit.

What "back to demand" means

When Sales, Operations and Billing all have room, check whether enough right-fit customers are coming in for the capacity the business can actually deliver. AI can support research and follow-up. It doesn't create demand or payment automatically.

Improve useful work, check the result, prepare the next handoff and reassess before adding more complexity.

Start again: map where money is made →

Find your first priority

We start with the activity that can change a business result.

Book a consultation