You've won the work.
Let's get it moving.

THE SITUATION

Your team is busy. Why is the handoff still waiting?

Imagine you're responsible for getting 40 new engagements from sales to delivery each month in a US professional-services business. A client says yes, but your team still has to prepare the record, get internal contract approval and schedule a kickoff. Missing billing contacts and unclear acceptance rules keep people chasing the next step.

Before you automate anything, let's find out why the handoff keeps getting stuck. Is information missing? Are approvals being batched? Or does nobody know who should move it forward?

01 / DIAGNOSE

Find where the work waits.

Let's follow the same ten fictional cases through each stage, from preparing the client record to scheduling the kickoff. We'll compare sequential stage averages here; we are not adding time from overlapping work.

Add those timings and you get 25.25 hours: 1.25 hours of active work and 24 hours of waiting. Contract approval accounts for the longest mean wait. Keep the backlog snapshot separate; you don't add those cases to the time total.

Start with approvals. That's where most of the waiting happens in this example. Check for incomplete submissions, batched reviews and limited approver capacity before deciding what to change. The longest wait tells you where to investigate; it does not prove what limits overall throughput.

Open the example, review the inputs and select “Build diagnostic brief” to see the result for yourself. You can also work through the diagnostic guide.

02 / STANDARDIZE

Agree what “ready for delivery” means.

Before you connect the systems, bring your sales lead and delivery coordinator together. What would each of them need to call this handoff complete? Sending a notification will not fill in the missing information for them.

Trigger

Signed agreement and commercial approval are recorded.

Required inputs

Signed scope, client contacts, dates, exclusions, billing details and dependencies.

Acceptance

The delivery coordinator verifies the fields and records acceptance in the project system.

Incomplete work

Return it to the sales owner with the missing fields listed. Record the reason and pause the review clock while awaiting the missing information.

Response and escalation

Review within one business day; escalate unaccepted briefs to the operations manager. Urgent work requires explicit approval.

Review

Test the next five handoffs with both teams; record returns, delays and missing data. The example review date is a placeholder to replace.

Agree the rules before you build. Settle the required fields, owners and response-time clock with both teams. Then test the draft together before asking everyone to use it.

Open the draft, check whether the rules make sense for this scenario and generate the agreement. For more help, work through the standardization guide.

03 / CHOOSE THE APPROACH

Start with rules the team can explain.

Look at what you need the system to do here: check required fields, assign an owner and notify the coordinator. Those steps follow explicit rules, so let's evaluate a rules-based workflow first. Keep approvals and exceptions with the people responsible for them.

We have not found a reason to introduce an autonomous AI agent in this example. If client documents later need interpretation, evaluate that task separately, with an appropriate test set, data permission and human review.

Use the AI vs automation decision tool ↗ · Read the comparison guide.

04 / MODEL THE ECONOMICS

Let's work out what the change could be worth.

Now let's look at the active work involved in preparing and coordinating the handoff. Your fictional 75-minute baseline is the same as the diagnostic's 1.25 active hours. The proposed 45-minute saving has not been tested, and we have not shown any reduction in the 24-hour wait.

For the example, use USD 1,800 upfront and USD 60 a month in running costs over 12 months. Assume 25% of released capacity reduces overtime or contractor spending that you can substantiate. You would need evidence for that cash effect in a real decision. We'll count no extra avoided costs or revenue.

1. Released capacity: 40 × 45 ÷ 60 × 80% = 24 hours per month.
2. Capacity value: 24 × USD 40 = USD 960 per month.
3. Assumed cash benefit: USD 960 × 25% = USD 240 per month.
4. Net monthly cash benefit: USD 240 − USD 60 = USD 180.
5. Total first-year cost: USD 1,800 + (12 × USD 60) = USD 2,520.
6. First-year net cash benefit: (12 × USD 240) − USD 2,520 = USD 360.
7. First-year cash ROI: USD 360 ÷ USD 2,520 = 14.29%. Simple payback: USD 1,800 ÷ USD 180 = 10 months.

Now try lower adoption. Keep the other assumptions unchanged, but reduce adoption to 40%. You release 12 hours, first-year cash ROI drops to −42.86%, and simple payback becomes 30 months. Before you invest, find out whether the adoption and cash realization assumptions stand up.

Open the calculator and generate the result to check these estimates and the sensitivity table. This link loads our handoff example; the calculator's usual invoice example is separate. You can also work through the ROI guide.

05 / TEST BEFORE EXPANDING

Make the next decision smaller.

Try the agreement manually on your next five handoffs. Ask both teams where it helps and where they still have to chase or guess. Treat that as an early usability check, not proof of a lasting financial return. Use what you learn to design a representative implementation test.

• Record: missing fields, return reasons, acceptance timestamps, approval waits, active handling minutes and exception volume.
• Check: normal submissions, missing contacts, duplicate events, rejected approvals and urgent exceptions.
• Keep control: the delivery coordinator records acceptance; the operations manager handles exceptions. Retain a manual handoff route.
• Stop or revise: if work is lost, duplicated, sent without approval, or made less clear for either team.
• Decide: continue only after reviewing actual handling time, adoption, quality, costs and the evidence for any cash realization.

If you later decide AI belongs in the workflow, use the AI pilot planner to define your evaluation, approvals and rollback. If you need an implementation partner, the consultant scorecard helps you compare their evidence and handover arrangements.