Flowscale
FOR AGENCY OWNERS WHO CLOSE DEALS · MODULE #5 OF FLOWSCALE · RUNS IN YOUR OWN CLAUDE

// THE ONBOARDING MODULE · THE CLOSE AND ONBOARD ROOMS

They signed.
Now don't fumble the first two weeks.

The window between "yes" and "we've started" is where deals quietly die: chasing logins, no clear kickoff, a client wondering if they made a mistake. This makes onboarding one clean command: convert a signed prospect to a client, generate the contract record, access checklist, kickoff doc, deliverables schedule, and welcome email, from one sentence. $97 USD once, your own Claude.

See what's inside ↓

Runs entirely in YOUR Claude account · get-you-running-or-refund guarantee · keep the files either way

// THE PART THAT LOSES CLIENTS

The gap between "they signed" and "we're delivering" is where churn starts.

Marcus Webb at Lakeline Roofing Co. just signed a $2,500/mo USD retainer. This is the moment the relationship is warmest, and the moment most agencies wing it. The deal moves from the salesperson's head into nobody's hands. Logins get half-collected over three email threads. The kickoff call gets scheduled but nobody writes an agenda. Week-one deliverables exist in someone's memory, not on a schedule.

So the new client sits in limbo for two or three weeks, and the only signal they get is silence. That silence is the exact feeling they had right before they fired their last agency. You won the deal and then handed them a reason to doubt it.

Closing the deal isn't the finish line. Setting it up cleanly, the night it closes, so the client feels handled instead of dropped, is the rest of the job. That's the room this module gives you.

// WHAT IT ACTUALLY IS

One skill that runs the whole handoff, in your own AI.

A "skill" is a file of operating instructions your Claude reads and follows. This module installs the client-onboard skill plus the folder convention that makes a closed deal turn into a set-up client. You type one sentence; the skill loads, confirms the terms with you, and writes everything into your repo. Nothing gets emailed on its own.

STEP 1 · THE CONVERSION

signed prospect → set-up client

Moves the prospect folder into clients/ (keeping the research and the timeline), writes the contract record from the terms you confirm, and opens a health file that starts at 100.

STEP 2 · THE SET-UP PACK

one command → the whole kickoff

Builds the week-by-week deliverables schedule from a playbook, drafts the access-collection checklist, writes the kickoff doc the client reads before the call, and hands you a welcome email ready to send.

THE PART THAT KEEPS IT HONEST

The contract record ships blank and stays a record, never a negotiation: it writes only the terms you confirm, and never invents money. The welcome email is always a draft written to a file, never a send, so it goes out from your own inbox under your own email law. And it never assumes a deliverable shipped just because the contract is signed. One command, nothing dropped, nothing faked.

// WHAT SHIPS

Every file, annotated. No mystery box.

my-agency/ · THE ONBOARDING MODULE
├── clients/
│   ├── README.md <- the client folder convention, explained
│   ├── _templates/ <- blank contract.yaml + onboarding-checklist you copy per client
│   └── lakeline-roofing/ <- a full worked example: the bar to match
│       ├── contract.yaml <- the terms, as a record you read in five seconds
│       ├── health.yaml <- the dashboard primitive, starts at 100
│       ├── deliverables/schedule.yaml <- weeks one through four and beyond
│       └── onboarding/ <- checklist.md, kickoff.md, welcome-email.md
├── playbooks/onboarding/ <- the SOP: signed to kicked-off, in order
└── .claude/skills/
    └── client-onboard/ <- SKILL.md: the conversion + the set-up pack

Plus the install walkthrough on the delivery page, written for someone who has never opened a terminal. You get the source in copy-paste blocks AND a zip. Edit anything; it's yours.

// WHAT YOU ACTUALLY NEED · READ THIS BEFORE BUYING

The honest requirements.

Why it works this way: I never resell Claude access, and your client list never touches my servers. The module runs entirely inside YOUR account. That's the design, not a disclaimer. You wanted in on AI. This is what in looks like: the real stack, in your hands.

// HOW IT WORKS

Install, set your playbook, then onboard every win the night it closes.

01

Install

Unzip into a folder, install Claude Code, log in. About 5 minutes with the walkthrough.

02

Read the worked example

Open the Lakeline Roofing folder, see the full onboard end to end, adjust the playbook to your services. 15 minutes, once.

03

Onboard on command

Type "Lakeline Roofing signed, onboard them." Confirm the terms, get the whole set-up pack written into your repo. Send the welcome email yourself.

THE SYSTEM BEHIND IT

This module is the onboarding discipline I run my own agency on. A closed deal gets fully set up the night it closes instead of three weeks later: contract on record, health file open, schedule built, kickoff doc and welcome email drafted before I leave my desk. The first impression a new client gets is "these people are organized," which is exactly the impression that survives the first rough week of delivery.

// THE MATH

$97 USD. Once.

One command turns every signed deal into a fully set-up client: contract on record, health file open, schedule built, kickoff doc and welcome email drafted. Unlimited clients, no monthly fee to me. It's one of seven rooms; when you want them connected, OS Pro is $997 USD.

The guarantee: if you can't get it running, I will personally get you running, or refund the $97. And you keep the files either way. This pays for itself the first time a closed deal gets fully set up the night it closes instead of three weeks later.

// STRAIGHT ANSWERS

Questions a smart buyer asks.

Does it actually email my client?+

No, and that's deliberate. The module writes the welcome email to a file as a draft. You read it, tweak it, and send it from your own inbox under your own email law. The system never emails a client on its own. Same for the contract: it writes down only the terms you confirm, and it never changes a contract without you saying yes first.

I've never opened a terminal in my life.+

Then the walkthrough was written for you. It's click-by-click: install one app, paste one command, log in with the Claude account you already have. The whole point is that the machine does the technical part. About 25 minutes, once, most of it reading the worked example. Stuck? Email me and I'll get you running, that's the guarantee.

Does it need ClickUp, or a specific PM tool?+

No. The onboarding form ships as a local document you send as-is, and the week-one task list is a portable markdown checklist. Paste it into ClickUp, Asana, or Trello if you use one, or just work the file. Nothing here depends on an account you don't already have.

Where does the deliverables schedule come from?+

From a playbook that ships with the module. It front-loads setup: week one is access and tracking, week two is build, week three is launch, week four is the first report. The skill adjusts the wording to the services actually in the contract, and it won't promise a deliverable the contract doesn't cover. Edit the playbook to match how your agency works.

Does my client data touch your servers?+

No. The module runs entirely inside your own Claude account, and the files live on your own machine (and your own GitHub, if you set that up, which I recommend). I never see your clients or their terms. Because a client folder holds real names and access notes, use a Commercial Claude tier (Team, Enterprise, or API) for that data, not the free plan.

Where does this fit in the bigger system?+

This is module #5 (CLOSE and ONBOARD) of a seven-module agency operating system. It reads a signed prospect from the QUALIFY room's prospects/ folder and creates the clients/ folder that the Delivery and Retention modules read: the deliverables/schedule.yaml tells a delivery module what's due, and the health.yaml tells a retention module which accounts are slipping. It stands alone, and when you want all seven wired into one system, OS Pro ($997 USD) merges them with a brain that routes the whole loop.

// FOR THE SCROLLERS

The short version: the Onboarding Module is the CLOSE and ONBOARD stages of a real agency, installed in your own Claude. Type "Lakeline Roofing signed, onboard them" and the client-onboard skill converts the prospect to a client, writes the contract record and a health file (starts at 100), builds the deliverables schedule from a playbook, and drafts the access checklist, the kickoff doc, and the welcome email. Nothing sends on its own; nothing money gets invented. You need Claude Pro ($20/mo USD, from Anthropic) and about 25 minutes of setup with a hand-holding walkthrough. $97 USD once, unlimited clients, keep-the-files guarantee.

// ONE ROOM OF A BIGGER HOUSE

Onboarded. Now deliver the work and report it.

You've turned a signed deal into a set-up client with a schedule and a health file. The full system this comes from also hunts the leads, qualifies them, writes the outreach, prices the proposals, ships the delivery, and watches client health, sibling modules that share these exact files. They release one at a time. The natural next one: The Delivery Module, which reads the deliverables/schedule.yaml this module wrote and turns it into the work and the reports you send.