Lesson 7 of 7 · 8 min

Scaling to a 20-client book with Blueprints and assistants

Grow to 20 clients with Blueprints and assistants.

Read the lesson

Goal: Plan a 20-client book: the revenue, the hours, when to hire and the systems that keep quality steady.

You need: Lessons 1 to 6. At least three live clients helps.

Why this matters

Most Operators stall between 6 and 10 clients. Every hour is booked. New installs slip. Tuning gets skipped. Results fade, and clients leave as fast as new ones arrive.

The way past this wall is not working harder. It is three systems: documented Blueprints, a fixed weekly rhythm and the right people with their own logins. With these, one Operator can lead a book of 20 clients or more.

Scale also raises the stakes of a mistake. One wrong price in a shared template can reach every client. So the systems that save time must also protect quality.

The 20-client book in numbers

SAU's example agency book mixes the three packages:

  • 10 clients on Never Miss a Job at $397 = $3,970
  • 7 clients on Business on Autopilot at $997 = $6,979
  • 3 clients on Growth Engine at $1,997 = $5,991
  • Total fees: $3,970 + $6,979 + $5,991 = $16,940 a month

If all 20 accounts are agency-run, the platform cost is about $1,890 a month in SAU's example model. That leaves about $15,050 before people and overhead.

Fig 1Sourced figures

The example 20-client book

10 × $397, Never Miss a Job$3,970
+7 × $997, Business on Autopilot$6,979
+3 × $1,997, Growth Engine$5,991
=Fees a month$16,940
−Platform, all agency-runabout $1,890
Left before people and overheadabout $15,050
SAU's example book. Use your own prices and costs.

The hours. Use your own numbers from lesson 5. As an example:

  • Never Miss a Job: 10 × 3 hours = 30 hours
  • Business on Autopilot: 7 × 5 hours = 35 hours
  • Growth Engine: 3 × 8 hours = 24 hours
  • Delivery total: 30 + 35 + 24 = 89 hours a month

Add new installs, sales and admin. Two installs a month at about 15 hours each is 30 hours. Sales and admin can take 25 more. That is 89 + 30 + 25 = 144 hours, close to a full-time month. One person cannot also grow past this.

Fig 2Example numbers

Where 144 hours a month go

  • Never Miss a Job: 10 × 3 hours30
  • Business on Autopilot: 7 × 5 hours35
  • Growth Engine: 3 × 8 hours24
  • 2 installs × 15 hours30
  • Sales and admin25

Total144 hours

About 144 hours is a full month for one person. Nobody is left to grow the book.

When and whom to hire

Hire when delivery work fills most of your week and sales start to slip. A common first hire is a junior Operator who does weekly tuning and installs.

SAU's research gives a junior Service Operator range of $55,000 to $75,000 base, plus up to 10% bonus. Add about 30% for taxes and benefits. At a $65,000 base:

  1. Loaded cost: $65,000 × 1.3 = $84,500 a year
  2. Per month: $84,500 ÷ 12 = about $7,042

After that hire, the example book leaves $15,050 − $7,042 = about $8,008 a month. That is before your own pay and other costs. The hire is worth it only if it frees you to sell and grow past 20 clients. Run this math with your own numbers before you hire.

Fig 3Example numbers

What a junior Operator costs the book

Loaded cost: $65,000 × 1.3$84,500 a year
Per month: $84,500 ÷ 12about $7,042
Book left before peopleabout $15,050
−Junior Operator a monthabout $7,042
Left after the hire, before your payabout $8,008
The hire pays off only if it frees you to sell past 20 clients.

A part-time assistant is a lighter first step. Give them the weekly tuning checklist for your simplest clients first.

The three systems

1. Documented Blueprints. A Blueprint is SAU's name for a documented build. There is no Blueprint feature in the app. For each Blueprint you use, keep three things: a setup guide, a test script and a one-page client summary. Rebuild each one in the new account. Use workflow templates, Build with Emma and the voice agent's Use template. Test every rebuild. A copy is only as good as its test.

2. A fixed weekly rhythm. Give each client a fixed tuning slot. For example, clients 1 to 5 on Monday, 6 to 10 on Tuesday, and so on. Reports go out in week 1, review calls happen in week 2.

3. Own logins at the lowest working role. Every person gets their own login. Never share yours. The roles are OWNER, ADMIN and USER. The app does not show a full permission list, so test what each role can do in your own account. Give each person the lowest role that lets them do the work. Audit logs in Settings → Connections & developer tools show who changed what.

Fig 4

Three systems for scale

  • Documented Blueprints, each with a setup guide, test script and client summary
  • A fixed weekly tuning slot for every client
  • Own logins at the lowest working role, checked in Audit logs
Systems save time and protect quality.

Watch the Core seat limit. Core has 2 users, and your login takes the second. On a Core client, only one person from your team can have a login. Name that person for each Core account. If more of your team need access, the client needs Growth.

Agency tools. Run all clients from the Organisations page (/multi-account). The Client Billing tab sits under Billing. If you sell under your own brand, set up the White-Label tab. It has Brand Identity, Colors, Custom Domain and Email Branding.

By way of working. A freelancer can stay at 8 to 10 clients and skip hiring. An agency builds all three systems early. A full-time Operator inside a multi-location group uses the same systems across locations instead of clients.

What to delegate first

Delegate the work that has the clearest checklist. Keep the work that needs judgment or the owner's trust.

  1. First: weekly tuning steps for Never Miss a Job clients. The checklist is short and the risk is low.
  2. Next: installs, following the 7-day SOP. You still run day 0 and the day 6 go or no-go.
  3. Later: report drafts. You check the numbers and write the "next fix" line.
  4. Keep: sales, quarterly reviews and the monthly calls with owners.
Fig 5

What to delegate first

Needs judgment or owner trust
KeepSales, quarterly reviews, owner calls
NextInstalls; you run day 0 and day 6
LaterReport drafts; you check the numbers
FirstWeekly tuning for Never Miss a Job
Clear checklist
Start bottom right: a clear checklist and low risk. Keep the work that needs the owner's trust.

Quality checks at scale

More people and more accounts mean more ways to slip. Build three checks into your week.

  • Spot-check transcripts. Each week, read five transcripts from accounts an assistant tuned. You learn how the work is going without redoing it.
  • Scan Audit logs. Look for changes to prices, greetings and transfer numbers. These matter most to owners.
  • Retest after template changes. When you improve a Blueprint, rebuild and test it in each account that uses it. Do not assume a fix in one account reached the others.

Build it in ServiceAgent

  1. List every client on the Organisations page. Check each one's plan and billing model.
  2. For each Core client, check Team members & invites. Confirm the second seat belongs to one named person on your team.
  3. Invite each assistant with their own login at the lowest working role.
  4. Open Audit logs once a week and scan for changes you did not expect.
  5. Store your Blueprint guides, test scripts and one-pagers in one shared folder outside the app.
  6. Check it works. Ask an assistant to rebuild one Blueprint in a practice account from the guide alone. Fix every step they could not follow.

Worked example: a wrong price in 15 accounts

Your agency runs 15 client accounts. Two assistants share your login. One day, Maple Leaf Cleaning's agent quotes an old price. Nobody knows who changed it or when.

You fix it in this order:

  1. Give each assistant their own login at the lowest working role.
  2. From then on, Audit logs show who changes what.
  3. Correct Maple Leaf's quick answer and test it with Talk in browser.
  4. Check the other 14 accounts for the same old price.
  5. Add "check price answers" to the weekly tuning list.
Fig 6

Fixing a wrong price across 15 accounts

  1. YouGive each assistant their own login
  2. ServiceAgentAudit logs now show who changes what
  3. AssistantCorrects Maple Leaf's quick answer; tests in Talk in browser
  4. AssistantChecks the other 14 accounts for the old price
  5. YouAdds price answers to the weekly tuning list
Own logins come first. Then every later change has a name on it.

Maple Leaf has 9 cleaners. Its account was on Core, so only one team login fits. You name one assistant as its owner on your team.

Common mistakes

  • Shared logins. Nobody knows who changed what. Fix: one person, one login, lowest working role.
  • Copying builds without testing. One error spreads to every client. Fix: test every rebuild before Publish.
  • Hiring before the math works. Fix: run the loaded-cost math with your own book first.
  • No fixed slots. Tuning gets skipped in busy weeks. Fix: give every client a weekly slot.
  • Ignoring the Core seat limit. Fix: name one team member per Core account, or move to Growth.

Do this now

Write your own book plan: clients per package, fees, platform cost and hours. Mark the month when hours pass 120. Write one Blueprint guide in full. Time: 30 minutes.

Practice the conversation

  1. Owner You've got 15 clients now. Will my account get less attention?
  2. Operator No. You have a fixed tuning slot every Tuesday.
  3. Owner Who works on it?
  4. Operator Jordan, on my team. They have their own login.
  5. Owner Why does that matter?
  6. Operator Every change shows who made it. Nothing is anonymous.
  7. Owner What if they make a mistake?
  8. Operator We test every change before it goes live. I check the log weekly.
  9. Owner And I still get the monthly call with you?
  10. Operator Yes. The report and the call stay with me.

Quick check

  1. Your agency runs 15 accounts. Two assistants share your login. A wrong price shows up and nobody knows who changed it. What do you fix first?
    • Give each assistant their own login at the lowest working role
    • Make one assistant approve the other's changes
    • Change the shared password weekly
    • Stop all tuning until the next review
  2. A client is on Core. You and an assistant both need a login, plus the owner. What is true?
    • Core allows 3 users, so it fits
    • Core has 2 users, so only one of you fits; move to Growth for more
    • Assistants do not count as users
    • Share the owner's login
  3. A junior Operator's base pay is $60,000. With 30% for taxes and benefits, what is the monthly cost?
    • $5,000
    • $6,000
    • $6,500
    • $7,800

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community