Writing the one-page Leak Report
Put your findings on one page the owner can read in two minutes.
Read the lesson
Goal: Combine the Grader report, your findings and your leak math into one page. The owner reads it in two minutes.
You need: Lessons 2 to 5. Your Grader result, 3-call scores, online baseline and leak math.
Why this matters
You now have a lot of findings. If you hand the owner ten pages, they read none. If you hand them one clear page, they read it twice and show their office manager.
The Leak Report is the report the Operations Grader produces. There is no separate template file. When you present it, you add your own page on top. That page holds your 3-call test findings and your leak math. Together, they are the Leak Report the owner keeps.
This page often decides the deal. A good one makes the next step obvious. A weak one makes the owner say, "Let me think about it."
What goes on the page
Your page has six parts, in this order:
- The headline number. The pitch number from lesson 5: revenue at risk each month, halved. One line.
- Three findings, with evidence. Each finding has a date, a time and what happened. Use your strongest three, not all of them.
- The math. The formula with the owner's own inputs. Show each step, so they can check it.
- Three fixes. One per finding. Name the Job Loop stage and what ServiceAgent does about it, in plain words.
- The next step. Usually a 30-day pilot of the first fix, with two measures agreed in advance.
- Assumptions. A short line that lists any input that is not the owner's own number.
The page, top to bottom
- 1Headline numberRevenue at risk a month, halved
- 2Three findingsEach with a date, a time and what happened
- 3The mathTheir inputs, every step
- 4Three fixesStage and what ServiceAgent does
- 5Next stepA 30-day pilot with two measures
- 6AssumptionsEvery input that is not their own
Keep it to one page. If it spills over, cut a finding, not the white space. Use a large font for the headline number. Owners often read the report on a phone.
Choosing the three findings
You may have ten findings. Pick three with a simple test. A finding makes the page if it meets at least two of these:
- Confirmed twice. Two sources show it. A missed evening call plus low reviews that say "nobody called back" is confirmed twice.
- Priced. You can put a dollar number on it with leak math.
- Fixable in the pilot. The first 30 days can fix it and measure it.
Missed calls usually pass all three. Old photos usually pass none. Move the findings that miss the cut to a short "also worth a look" line. Or leave them for a later meeting. Three findings is a ceiling, not a target. Two strong findings beat three weak ones.
The order matters too. Put the most expensive finding first. The owner's attention is highest at the top of the page.
Which findings make the page
Writing rules
Lead with their numbers. Page one opens with the owner's own leak and test results. National statistics go in the assumptions line, if anywhere. An owner trusts their own call log more than any study.
Use times, not adjectives. "Saturday, 11:05 am: rang 8 times, mailbox full" beats "weekend coverage is poor". Times are facts. Adjectives are opinions.
Never blame staff. Write "the call went to voicemail", not "the office missed it". The office is often doing its best. The gap is a system problem, and staff will read the report too.
Say what the AI will do, not what it is. Describe what happens to the customer. Avoid product words such as "containment", "workflow" or "omnichannel". Write this: "answers every call at night and books the job".
Make no promises you cannot keep. Do not promise revenue. Promise to measure the answer rate and jobs booked each week, and to show them.
Label every assumption. If you used the 42% booking rate, say so. If the owner gave you the average job, say "your number".
Weak vs strong wording
- Weekend coverage is poor
- Your office misses calls
- You will make $6,000 more
- Saturday, 11:05 am: rang 8 times, mailbox full
- The call went to voicemail
- We will measure answer rate and jobs booked weekly
How to deliver it
Do not email the report before the meeting. An owner who reads it alone may reject it before they hear the story. Bring it to the meeting, printed or on screen. Walk them through it in order. Bring a second copy if the office manager joins.
After the meeting, send the PDF the same day. Add one line that repeats the next step and the date you agreed. If they asked for changes, make them before you send.
Keep a copy for yourself. In 30 days, you fill in the "after" column. In 90 days, it becomes the first page of your monthly report. A report that shows before and after on one page is the strongest proof you will ever give an owner. It also becomes a case study for your next prospect, with the owner's permission.
The report's life
- Before the meetingDo not email it
- In the meetingWalk the owner through it in order
- Same daySend the PDF with the next step and the agreed date
- Day 30Fill in the after column
- Day 90It becomes page one of the monthly report
Size changes the page
For an owner-operator, the page is about their time and their phone. Frame the fix as "you stop answering calls from under a sink".
For a fleet, the page is about peak days and the office. Add one line on the 10-call limit if storm or heat-wave days matter. The AI takes up to 10 calls at the same time. An 11th caller hears ringing with no pickup.
For a multi-location brand, add a small table: one row per location, with answer rate and leak. The weakest location is often the best pilot.
Build it in ServiceAgent
You write the page outside the app. You use ServiceAgent to keep it and to measure it later.
- Save the Grader result and your page as a PDF.
- In your own account, open the prospect's contact. Attach or note the report in the
Activitytab with today's date. - After the pilot starts, open
Analytics→Callseach week. ReadSuccess Rateand the AI vs human split. - Count the jobs the AI booked from
Jobs, filtered by the pilot weeks. - Check it works: in 30 days, you can fill an "after" column next to "before" on the same page.
Leave room for the after column
| Measure | Before | After 30 days |
|---|---|---|
| Answer rate | 86% | Measured in Analytics, Calls |
| Jobs booked by the AI each week | 0 | Counted in Jobs |
Worked example: Northside Plumbing's page
Here is the page you wrote for Carol, in full.
Northside Plumbing: Leak Report, page 1
About $6,145 a month in calls is at risk today.
What we found
- Tuesday, 7:15 pm: the call rang 6 times, then went to voicemail. A callback came 14.5 hours later.
- Saturday, 11:05 am: the call rang 8 times. The voicemail box was full.
- Your web form took 26 hours to get a reply. Six of your last 10 low reviews say nobody called back.
The math, with your numbers
25 calls a day × 22 days = 550 calls. 14% missed = 77 calls. 77 × 42% × $380 = about $12,289. Some callers call back, so we use half: about $6,145 a month.
What we would fix
- Catch: an AI agent answers every unanswered call, day and night, and books the job.
- Catch: a text goes to every missed caller within a minute.
- Keep: a review request goes to every customer after the job.
Next step
A 30-day pilot of the first two fixes. We measure your answer rate and jobs booked by the AI each week.
Assumptions
The 42% booking rate is a trade-wide benchmark. Calls, miss rate and the $380 average job are your own numbers.
That page has fewer than 250 words. Carol can read it in two minutes.
Common mistakes
- Opening with national statistics. Open with the owner's own numbers.
- Listing every finding. Pick the strongest three.
- Blaming the office. Describe what happened to the call, not who failed.
- Promising revenue. Promise measurement instead.
- Emailing it cold. Walk the owner through it first. Send the PDF after the meeting.
Do this now
Write the one-page report for the business you audited. Use the six parts in order. Read it aloud in under two minutes. If you cannot, cut. Then give it to a friend who does not know the business. Ask them to tell you the main number and the next step. If they cannot, rewrite the top.
Practice the conversation
- Operator Carol, here's your Leak Report. It's one page.
- Owner Only one page?
- Operator Yes. The top line is the number: about $6,145 a month at risk.
- Owner How did you get that?
- Operator It's right there. Your calls, your miss rate, your average job. And we halve it to be fair.
- Owner And these times are the calls you made?
- Operator Yes. Each one is a real call with the date and time.
- Owner What's this pilot?
- Operator We fix the phones for 30 days. You see answer rate and booked jobs every week.
Quick check
- Your draft report opens with national missed-call statistics. The owner's own numbers sit on page 2. What do you change?
- Keep the statistics, since they prove the problem is common
- Add a revenue guarantee to page 1
- Put the price on page 1
- Open page 1 with the owner's own leak and test numbers
- Which finding is written correctly for the report?
- "Your office manager ignored my call."
- "After-hours response is weak."
- "Tuesday, 7:15 pm: voicemail after 6 rings. Callback 14.5 hours later."
- "You lose thousands every week."
- What are the two pilot measures you put in the next step for a Catch pilot?
- Credits used and AI call minutes
- Answer rate and jobs booked by the AI each week
- New reviews and accepted estimates
- The owner's opinion on day 30
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.