One person
Simpler, quicker, lower-cost start
ROI for AI · A five-part guide
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.
Step 1 · Capacity
Start with the work that matters, then equip the right person or group to do more of it.
Simpler, quicker, lower-cost start
More shared setup and budget, more total capacity
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.
Step 2 · Leaders first
Give a trained leader the right context, and better information can support better decisions, coaching and team activity.
Signal detected. Leader verifies.
Leader decides. Employee acts.
Rep C: follow up on the 4 stalled proposals today.
Whole team: use Rep A’s follow-up template.
Process is repeated. Team work changes.
Team proposals sent per week · illustrative, same team and definition
Illustrative sales example. Proposals sent measure activity.
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.
The leaderAn executive, vice president or department head whose decisions shape the 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.
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.
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.
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
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.
They review follow-up and are closest to the daily work, so a problem in one team is a natural place to start.
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.
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 peopleStart 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:
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 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.
People spend their week on the work that matters most, because the leader has decided from current records what comes first.
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.
Work has an owner and a next step, and someone checks on it. That check is what makes the agreement real.
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.
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.
Bar width shows how much of the company the role looks across, not the size of any gain.
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.
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.
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.
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.
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:
The right level depends on which decision or work is holding the business back.
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.
The first setup can stay small. It needs four things:
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.
These trials are illustrative. Each one tests the habit on real work before anything wider is built.
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.
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.
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.
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.
Read together, they help a leader see whether capacity is running out, while there is still time to act on it.
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:
Illustrative signal: jobs scheduled are turning into work delivered. The decision may be to leave it alone and spend the review on something else.
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.
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 trackMore 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?
What should leadership measure first?
Begin with the decision. If nothing would change whatever a measure says, leave it out.
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.
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.
The missing item is often the useful part. It names a specific record and a specific person who can complete it.
The team’s numbers and the individual records beneath them, because that is where coaching happens.
A view that compares teams and shows the queue between them, so the vice president can coach the managers who run them.
Those same measures alongside revenue, costs and margins. The drawing shows the two kinds of information side by side, not any amount.
Without that foundation, an AI summary is working from guesses and gaps.
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.
Look at the decisions made from it. Keep the measures that changed what someone did. Replace the ones everyone glanced at and ignored.
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:
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.
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.
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.
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.
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 actual work on the tableA real proposal, job or invoice, gone through with the person doing it.
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.
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.
That makes the feedback specific, and the person can use it today. They explain what is really happening and raise what is blocking them.
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.
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.
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 workA 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?
What can a missing handoff teach the whole team?
One illustrative invoice, from the flag to the fix. Each step has its own owner.
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.
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.
This person owns the handoff. They explain what is really happening, raise what is blocking them, complete the action and record it.
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.
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.
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.
Summarizes, surfaces gaps and drafts from the sources it has been given.
Verifies the facts, weighs the context, makes the decision, assigns the owner and has the conversation.
Explains what is really happening, raises what is blocking them, completes the next action and records it.
The invoice above. Most issues can be handled at this level.
They look at the records and at how the manager coached the rep. The person being coached here is the manager.
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.
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.
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.
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?
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.
Illustrative example: a department head creates a reliable proposal follow-up review and runs it on real work.
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.
Before buying anything new, the team documents the review questions and tests them in the existing record system. A good practice can spread quickly.
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 spreadThe 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 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.
The practice being testedIllustrative: Rep A’s follow-up template, used by the sales team
The steps are written down with real examples, along with the cases that need different handling.
Everyone works from the same structured records and the same approved definitions, including what counts as a proposal sent.
Each person knows who enters the information, who checks it, who acts on it and who coaches.
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
One shared practice, with no new team software required. A template or checklist that has proved useful is enough to begin.
The leader reviews how it fits real work. Managers coach from that work and employees say where it doesn’t fit.
The leader changes it where needed, so the team tests a practice that matches its own work.
Same team, same definition of a proposal sent, compared with where that team started.
Does not count
Counts
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.
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.
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.
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.
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.
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.
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.
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.
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.
Separate view. The flag below covers open proposals, not this week’s sent count.
This points to four specific proposals that someone can open and act on today. Like the count, it doesn’t explain why.
Also useful: proposal age, missing information, customer response, scope and pricing.
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.
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.
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.
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.
This week’s sales review
Rep C follows up on the 4 stalled proposals today.
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?
The whole team uses Rep A’s follow-up template.
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
Confirm each of the four records received the right next action, and see what came of each one.
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.
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.
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.
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.
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.
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.
+6 proposals per week, or 1.5x the earlier count. This counts activity. It is a different measure from Step 1’s productivity figures.
If people joined or left between the two numbers, 18 would no longer describe the group that sent 12.
“Proposal sent” has to mean the same thing both times. If the definition widens, the count can rise with no change in the work.
Use the same way of counting from the same kind of record. A change in method can look like a change in the team.
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.
18 per week in this illustration. Activity only.
How many of the proposals were won? More sent does not mean more won.
Did the work get delivered? Won work can wait if delivery has no room for it.
Did the invoice go out for the delivered work, complete and on time?
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.
In this illustrative example, the same team sent 12 proposals per week before rollout and 18 per week after.
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.
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.
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.
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
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.
100 hours freed a month
Full delivery team? Orders wait. See how the bottleneck moves
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.
Sales, Delivery and Finance are ways to use an improvement. Their results are not separate returns to add together.
The reasoning behind each step
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.
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.
| Where the hours go | Hours | What the example counts |
|---|---|---|
| Extra proposals | 40 | 20 extra proposals (40 ÷ 2 h) |
| Not assigned yet | 60 | No financial credit |
| Total freed | 100 | Capacity, 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.
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.
40 h ÷ 2 h each = 20 extra proposals
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.
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.
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.
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:
Owner decision: compare additional proposals with actual accepted sales, not activity alone.
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 | If 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.
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.
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.
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:
| One time | Recurring |
|---|---|
| Setup, integration and configuration | Licenses and usage |
| Source cleanup, permissions and testing | Support and upkeep |
| Staff training | Ongoing quality review |
Owner decision: record one-time and recurring costs separately, then compare them with actual incremental gross profit or other verified financial benefit.
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.
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.
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.
| State | In this example |
|---|---|
| Booked | $50,000, assumed |
| Delivered | From your delivery records |
| Invoiced | From your billing records |
| Collected | From 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.
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?
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.
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.
| If the records show | Next priority |
|---|---|
| Proposals and accepted sales both rise | Check that Delivery can take more before pushing further. |
| Proposals rise, wins do not | Inspect qualification, scope, pricing, follow-up and demand. |
| Proposals sent but follow-ups lag | Point freed hours at follow-up on open proposals. |
Add qualified opportunities to proposals sent and follow-ups done. It shows whether activity is reaching real buyers before sales results arrive.
Next decision: determine whether delivery can absorb more sales without delays, quality loss or margin compression.
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.
| Measure | Decision it supports |
|---|---|
| Margin per service | Which services to price differently or promote |
| Staff hours per job | Where to staff up, and where work takes too long |
| Invoice sent to cash received | Where billing or collection needs attention. Track this separately. |
| Outstanding invoices | Which 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.
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.
Step 3 · Business development example, hypothetical
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.
12 hours released a month
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
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
Owner decision: define a research brief that Sales trusts.
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.
8 h × 60 min ÷ 30 min each = 16 prepared follow-ups
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.
Owner decision: assign the eight hours to a named BD owner and measure whether the follow-ups are relevant, completed and responded to.
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.
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
Owner decision: inspect the step from introduction to qualified opportunity.
| Targeting | Are these the accounts Sales wants? |
|---|---|
| Partner selection | Can this partner reach real buyers? |
| Message relevance | Did the follow-up give a reason that fits? |
| Qualification definition | Do BD and Sales mean the same thing? |
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:
Owner decision: compare partner source, qualification, accepted sale and eventual delivery. Keep introduction activity separate from sales performance.
| Column | The question it answers |
|---|---|
| Partner source | Which relationship started this? |
| Qualification | Did Sales accept it for active pursuit? |
| Accepted sale | Did the customer actually buy? |
| Delivery | Was the work completed? |
Read across a row to see which partners bring real customers, not just busy introductions.
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.
Owner decision: track whether the customer was delivered, what direct costs were incurred, and whether the margin matched the assumption.
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.
Step 3 · Marketing example, hypothetical
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.
24 hours released a month
The Improved month shows what the example assumes after testing. It does not prove AI caused the difference.
Contribution after media, before incremental AI and test costs
Baseline month: $4,000 Improved month: $7,000Dollar 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
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.
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.
| Input | This test |
|---|---|
| Audience | Held the same |
| Message | Changed and recorded |
| Offer framing | Held the same |
| Creative angle | Held the same |
| Call to action | Held the same |
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.
| AI | Prepares variations and organizes prior learning. |
|---|---|
| Marketer | Approves the test, checks compliance and brand fit, records the change. |
| Owner | Picks which weakness to work on next. |
Baseline month
40 raw → 20 qualified → 2 wins
Improved month
40 raw → 30 qualified → 3 wins
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:
Owner decision: define “qualified” before testing and inspect the records behind each stage.
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.
Baseline: $2,000 ÷ 20 qualified leads
$100.00
Improved: $2,000 ÷ 30 qualified leads
$66.67
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.
$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.
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.
| Line | Baseline | Improved |
|---|---|---|
| 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.
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.
Operations example · one hypothetical month
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.
The 24 hours only count if:
Six customers are waiting Staff can be scheduled Downstream teams hold qualityHours 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
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.
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.
| Use | Math | Hours |
|---|---|---|
| Original onboardings | 40 × 4 h | 160 |
| Additional onboardings | 6 × 4 h | 24 |
| Remaining, no financial credit | 40 − 24 | 16 |
| Total month | 160 + 24 + 16 | 200 |
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.
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.
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.
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.
| Measure | Question |
|---|---|
| Accepted onboarding | Did it meet the same standard as the original 40? |
| Time to activation | Did customers get going sooner, later or at the same pace? |
| Rework | Did problems return further down the line? |
| Direct cost | Did costs stay near the assumed level? |
| Delivery completion | Was the work actually finished? |
Owner decision: measure accepted onboarding, time to activation, rework, direct cost and delivery completion before expanding the queue.
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.
| Label | Example | What it is |
|---|---|---|
| Hours released | 40 h | Capacity |
| Additional accepted work | 6 onboardings | Output, if demand exists |
| Delivered value | $12,000 | Revenue, once delivered |
| Gross profit | $4,800 | Conditional, before AI costs |
| Actual AI cost | Your records | Not 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 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.
Billing & Finance example · one hypothetical monthly batch
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.
A separate lens, not part of the $40,000
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
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.
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.
| Record | What it shows |
|---|---|
| Completion date | When the clock starts |
| Invoice date | The delay the workflow can change |
| Due date | What the terms require |
| Payment date | When the cash actually arrived |
| Collection status | What is still outstanding |
Owner decision: measure completion date, invoice date, due date, payment date and actual collection status, then compare them with the assumption.
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.
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.
Owner decision: assign one owner to every handoff and review the exceptions, rather than assuming the software has completed the process.
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.
| Line | Planned | Actual |
|---|---|---|
| Price | $4,000 | $4,000 |
| Staff hours | 4 h | 6 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 margin | 30% | 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.
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.
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 the records show | Look first at |
|---|---|
| Finished jobs wait to be invoiced | Billing workflow and the completion handoff |
| Invoices are sent, but paid late | Collection follow-up |
| Costs are on plan, but margin is thin | Pricing |
| Jobs regularly take more hours than planned | Staffing or scope |
| The same overrun or rework keeps returning | Delivery process |
Owner decision: decide whether the next intervention belongs in billing workflow, collection follow-up, pricing, staffing or delivery process.
Step 4 · Bottlenecks
In this illustration, AI is scaled across one department. Its extra work can outgrow the next team’s capacity.
No AI change yet
Prior capacity
Handoff: Qualified opportunity →
Demand & fitAI: shared data, tools, training
AI increased Sales capacity
Handoff: Won work →
Sales capacityNo AI change yet
Operations: prior capacity. Won work waits
Handoff: Accepted delivery →
OperationsNo AI change yet
Prior capacity
Handoff: Invoice. Customer pays separately
Billing & paymentTeams have room. Are enough right-fit customers coming in? Explore demand →
Only if the demand, quality and conversion are real.
Your teams can now handle more work. Next, check whether enough right-fit customers are coming in.
Step 5 · Our assessment
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
We start with the activity that can change a business result.
Book a consultation