Lesson 7 of 7 · 8 min

Packaging a workflow as a Blueprint for the next client

Package a workflow as an Agent Blueprint you can rebuild for the next client.

Read the lesson

Goal: Turn a working build into a documented Agent Blueprint. You or an assistant can then rebuild it in under an hour.

You need: Lessons 1 to 6 of this course. At least one workflow live and proven for a client.

Why this matters

Your first build of anything takes hours. You learn the trigger, the checks, the words and the timing. If you start from zero for every client, your time never gets cheaper. An Agent Blueprint captures what you learned. The next build becomes a rebuild from a recipe. That is how one Operator grows from 3 clients to 20 without working nights.

What a Blueprint is, and is not

An Agent Blueprint is SAU's name for a documented build. There is no Blueprint feature in the app. There is no button to export or install one. Each Blueprint is a written recipe that you rebuild in the client's organization with real tools:

  • workflow templates and recipes in Workflows → Templates and Create,
  • Build with Emma, using the saved 7-part prompt from lesson 6,
  • Build from scratch, following the written steps,
  • the voice agent Use template button, for agent builds.

Because it is a rebuild, the document must be complete. Anyone on your team should get the same result.

The 8 parts of a Blueprint document

  1. Name and version. For example "Post-Job Thank-You v1.2."
  2. The leak and the KPI. The problem it fixes and the KPI that proves it.
  3. Lowest plan. Core, Growth or Franchise. Note if it needs AI chat replies (Growth) or webhooks (Franchise).
  4. Build steps. The trigger, every Condition, every action and every delay, in order.
  5. Message copy. The exact words, with fields to fill in, such as the business name.
  6. Credits per run. The run plus each message. Show the monthly math for a sample client.
  7. Test script. The builder Test samples, the gated live test and what "pass" looks like.
  8. Client one-pager. One paragraph for the owner: what it does, what it costs and what it moves.

Keep a short change log at the bottom. Each change gets a date and one line.

Fig 1

A filled Blueprint: Post-Job Thank-You v1.1

PartWhat the document says
1. Name and versionKeep, Post-Job Thank-You v1.1
2. Leak and KPICustomers hear nothing after the job; count replies
3. Lowest planCore
4. Build stepsAppointment Completed, 2 gates, Delay 2 hours, Send SMS
5. Message copyThanks for choosing [BUSINESS NAME] today...
6. Credits per run1 run + 2 for the text = 3
7. Test scriptTest with 3 samples, gated live test, remove the gate
8. Client one-pagerWhat it does, what it costs, what it moves
Every part is written down. Anyone on your team should get the same result.

What changes and what stays

A rebuild is not a copy. Some parts stay fixed. Other parts change for each client.

These stay the same in every rebuild:

  • the trigger and the order of steps,
  • every Condition that protects customers, such as the staff and test-contact gates,
  • the test script and the pass rules.

These change for each client:

  • the business name, services and phone number in the message copy,
  • the timing, if the trade needs it, such as a longer delay for roofing,
  • the task owner, which must be a real person on the client's team,
  • the location, for multi-location clients.

Mark each changeable item in the document in square brackets, such as [BUSINESS NAME]. Then a rebuild is a fill-in task, not a design task.

Fig 2

The same copy, before and after the fill-in

In the Blueprint document
  • Thanks for choosing [BUSINESS NAME] today.
  • Any questions about the job?
  • Reply here or call [PHONE].
In the Pine Street rebuild
  • Thanks for choosing Pine Street Electric today.
  • Any questions about the job?
  • Reply here or call 555-0198.
Square brackets mark what changes. The rebuild becomes a fill-in task, not a design task.

Where to keep your Blueprints

Keep every Blueprint in one shared folder, one document each. Name them the same way: Job Loop stage, then name, then version. For example "Keep, Post-Job Thank-You v1.2." Keep a short index at the top of the folder. List each Blueprint, its stage, its lowest plan and the clients that run it. When you fix a Blueprint, the index tells you which clients need the fix too. Plan a short visit to each of those clients in the next monthly service rhythm.

By business size

For an owner-operator, use the simplest version of each Blueprint. Fewer steps, fewer things to break. For a fleet, add the checks the office needs, such as a task owner per crew. For a multi-location client, rebuild in each location. Each one counts as its own workflow. On Core, each published workflow that is switched on counts as 1 of 10 active automations. A client with many Blueprints may need Growth.

Working with assistants

Blueprints are what let you hand work to an assistant. Give each assistant their own login. Never share yours. Then Audit logs show who changed what. Have the assistant rebuild and run the test script. You review the Summary tab before publishing. After 3 clean rebuilds, let the assistant publish on their own and review weekly.

Fig 3

Handing a rebuild to an assistant

  1. AssistantRebuilds from the Blueprint document
  2. AssistantRuns the test script
  3. YouReviews the Summary tab and publishes
  4. AssistantAfter 3 clean rebuilds, publishes alone
  5. YouReviews the work weekly
Each assistant has their own login, so Audit logs show who changed what.

Blueprints and your pricing

A Blueprint makes your delivery faster. It does not make the result worth less to the owner. Price each package on the result it moves, not on your build hours. The time you save goes into more clients, better tuning and the monthly review. The model does not change this. In an agency-run account, you pay ServiceAgent and bill the client. In a client-signed account, the client pays ServiceAgent and you earn 20% referral revenue. Either way, you set and collect your own fees.

Build it in ServiceAgent

You rebuild the Blueprint in a new client's organization.

  1. Open the Organisations page (/multi-account). Pick the client.
  2. Check Working in at the top. Pick the right location.
  3. Check the plan and the active count. On Core, make sure there is room in the 10 active automations.
  4. Open Workflows. Start the way the Blueprint says. Use a named template, Build with Emma with the saved prompt, or Build from scratch.
  5. Follow the build steps exactly. Paste the message copy. Fill in the client's fields.
  6. Compare the result with the Blueprint, step by step, in the Summary tab.
  7. Run the test script: Test, then a gated live test, then remove the gate.
  8. Publish. Write the Blueprint name and version in your client notes.
  9. Check it works: read View run history daily for the first week.
Fig 4

Rebuild in a client account

  1. 1Organisations pagePick the client
  2. 2Working inPick the location
  3. 3Check plan and active countRoom for 1 more on Core?
  4. 4Start the buildTemplate, Build with Emma or Build from scratch
  5. 5Summary checkStep by step against the document
  6. 6Test script, then PublishWrite the version in your client notes
There is no install button. You rebuild from the recipe.

Worked example: Hilltop Plumbing and Pine Street Electric

You first built the post-job thank-you for Hilltop Plumbing (lesson 1). It took about 3 hours, or 180 minutes. You wrote the Blueprint the same week.

Pine Street Electric has 3 people on Core. Owner Mark signed up with ServiceAgent themselves and pays monthly. You earn 20% referral revenue on their plan. The billing model does not change the build. You still rebuild it the same way.

Using the Blueprint, the rebuild for Pine Street took 40 minutes. That saves 180 − 40 = 140 minutes on this client. Across 9 rebuilds, Pine Street included, you save 140 × 9 = 1,260 minutes. That is 21 hours.

Fig 5Example numbers

Time saved by a Blueprint

First build180 minutes
−Rebuild from the Blueprint40 minutes
=Saved per client140 minutes
×Rebuilds, Pine Street included9
Total saved1,260 minutes = 21 hours
The tenth build is far cheaper than the first.

One rebuild found a gap. Mark's office manager uses their personal email, so the staff-skip condition missed them. You added a line to the Blueprint: "Also skip each staff member's personal email." That is version 1.1. Every future rebuild gets the fix for free. You also checked the index. Hilltop runs version 1.0, so it needed the same fix. You added it during Hilltop's next monthly visit and noted the date in both clients' notes. Now both clients run version 1.1, and the index shows it. Small, dated fixes like this are how a Blueprint gets better with every client.

Fig 6

How version 1.1 reached both clients

  1. Week 1Hilltop build; Blueprint v1.0 written the same week
  2. Pine Street rebuildStaff-skip misses a personal email
  3. Same dayFix added; Blueprint becomes v1.1
  4. Index checkHilltop still runs v1.0
  5. Next monthly visitHilltop gets the fix; both notes dated
One dated fix helps every client that runs the Blueprint.

Common mistakes

  • Mistake: Promising clients a one-click install. Fix: Say you rebuild a proven recipe in their account.
  • Mistake: Writing steps from memory. Fix: Write them from the Summary tab of a live, proven build.
  • Mistake: No version or change log. Fix: Version every change and note the date.
  • Mistake: Rebuilding in the wrong organization or location. Fix: Check the Organisations page and Working in first.
  • Mistake: Skipping the test script on a rebuild. Fix: Every rebuild gets the full test.

Do this now

Pick one workflow you have built and proven. Write its Blueprint with all 8 parts. Ask a friend or assistant to rebuild it in a practice account using only your document. Note every question they ask. Deliverable: a Blueprint document, version 1.0, plus the list of questions. Time: 30 minutes.

Practice the conversation

  1. Owner Is this something you built just for me?
  2. Operator It is a proven recipe. I rebuild it in your account and tune it to your business.
  3. Owner Has it worked for others?
  4. Operator Yes. I have run it for other trade businesses and fixed the rough edges.
  5. Owner So it is faster to set up?
  6. Operator Yes. About 40 minutes instead of 3 hours.
  7. Owner Do I pay less, then?
  8. Operator You pay for the result. You also get every fix I learn from other clients.
  9. Owner And it uses my words, not someone else's?
  10. Operator Yes. Your name, your services and your tone.

Quick check

  1. A new client asks you to "install your Blueprint." What do you do?
    • Click the Blueprint install button in the client's account.
    • Rebuild it in the client's organization from your documented steps.
    • Copy your own account's workflows with an export file.
    • Ask ServiceAgent support to install it.
  2. A first build took 150 minutes. A rebuild takes 30 minutes. How many minutes does a Blueprint save across 6 more clients?
    • 120
    • 180
    • 720
    • 900
  3. A rebuild finds a missing staff check. What do you do with the Blueprint?
    • Fix it only in this client's account.
    • Add the fix, raise the version and note the date.
    • Start a new Blueprint for this client.
    • Leave it, because the first client never had the problem.

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

Learn

Get certified

Community