The Practice · Guides
What to send a client after they say yes
The short answer
Send six documents in order: a welcome, a form the client fills in before the first call, an access page, a kickoff agenda, a progress file the client keeps, and a handover. The first three go out together the day the client says yes, the agenda the day before the first call, and the handover the day the client signs off on the finished work.
Two rules run through all six. You never ask for a password: the client invites you into each system from their own account and removes you at the end. And there is no hosted portal: you write one progress file, send it at each step, and the client files it in their own workspace, where it stays.
What goes in the welcome?
The welcome tells the client how the work will run: how you work, the dated plan, who does what, how to reach you, and what you never do. It is the first thing they read after signing, so make it the plan, not a bill.
Keep it to two pages. Write the plan as numbered phases with real dates and a status in words ("Done", "Now", "Next"), not a progress bar. Name every person on both sides and the one job each does. State a reply time you can keep, such as 24 hours, and send one ask per message.
Add what you never do: for example, host the client's data, hold their passwords, or give legal advice. Then add "What you will hear from us": each message the client will get, and when, such as a first-step note a few days after the start, a confirmation within a day of the kickoff, one the day each access grant arrives, and any notes after sign-off. List only what you will send every time.
What goes in the form before the first call?
The form holds the questions every client answers before the first call: the shape of the business, why now, the recurring task they most want off their desk, what they have already tried, what good looks like at ninety days, and who else has a say in the decision. Send it with the welcome and ask for it back the business day before the call, so the call confirms answers instead of collecting them.
Under the ninety-day question, print a line saying the client's words describe their goal, not a promise from you. A blank answer is fine; it gets asked on the call.
What goes in the access page?
The access page lists each system you need, the role the client grants, and the date you need it. Its first line is the first rule: you never ask for a password, because the client invites your own user from their own account.
That is delegated access: you sign in with your own credentials, theirs never leave them, and they can remove you at any time without asking. Build the page as a table, one row per system: the system, its owner on the client's side, the narrow scope (one folder, one channel, one form), the role, and the date. As of October 30, 2026, Google Drive and SharePoint both let an owner give one person editing rights on one folder and remove them later, though an organization's settings may limit sharing outside it.
The role is never an administrator; where a change needs one, the client's own administrator makes it while you guide. Confirm each grant by email the day it arrives and date it in the progress file. Say that at the end the client removes you from every system, and name what never to send: a password, a recovery code or a customer record, by any channel.
What goes in the kickoff agenda?
The kickoff agenda is one page: date, time, length and attendees; five agenda items with minutes against each; what the client brings; and what happens the day after the call. Send it the day before the call, with the calendar invitation.
A sixty-minute call holds five items: read back the client's answers (10 minutes), agree how each result will be checked (15), walk the access page (10), name who runs what (15), and start the progress file with the first decisions (10). Ask the client to bring the person who manages each system and two or three recurring tasks, each with a recent example.
What replaces the client portal?
A progress file the client keeps replaces the portal. You write it and send it by email at each step; the client files it in their own workspace, such as a folder in their Google Drive or SharePoint.
Put five things in it: where things stand and the next date; the phases with their dates and a status in words; each deliverable and where it lives; every decision with its date and who made it; and every access grant and removal with its date. Rows are added, never rewritten, so the file is also the history.
Because the client holds every copy from the first day, nothing about their project lives only in your account, and nothing needs handing back when you leave.
What goes in the handover?
The handover says what was delivered, where each piece lives in the client's accounts, which access was removed and when, and how to run it without you. Send it the day the client signs off on the work, not the day you deliver it.
Between delivery and sign-off you are still making corrections and still hold access. A handover sent at delivery either misstates the access or cuts the corrections short.
Write "running it without us" as numbered steps: where the manual lives, how to change an output, where decisions are logged, how to train a new person. Close with one request: a few sentences in the client's own words, published only with written consent to the exact wording, with nothing offered for it, and silence read as a no.
Why are the invoice and the contract not in the set?
Each already has its own instrument. The invoice belongs to your payment processor, which sends it, takes the payment and keeps the record; the contract belongs to whoever drafted it, usually a lawyer, and it governs the work.
A designed copy of either is a second version that can drift from the real one. The welcome carries one line for each instead: how invoices arrive, and which agreement governs, adding that these pages change nothing in it.
How does the set change for an agent?
The sequence holds and the names change. An agent's set is a "how I work" page, a needs form, a list of the documents you need, the first-meeting agenda, a one-page "where we are" snapshot sent with each milestone, a keys-day page, and a feedback page.
An agent's set carries no invoice and no agreement: the agent is paid through the brokerage, usually at closing, and the agreement is the brokerage's form. Questions about what it says go to an attorney of the client's choosing.
The needs form asks what the home must have and where the client needs to be, never who will live there. The access page becomes a documents page with two standing lines: "Wiring instructions come only from the closing firm. Before sending money, confirm by phone at a number you find yourself, never one in an email." And: "Never send a Social Security number or bank statement by email or text." Keep closing content to a pointer: the closing office's own instructions, the county's homestead page.
Next rung
Two editions are in the build: The After-Yes Set, an Instrument for service businesses; and The After-Yes Book, for agents, the buyer and seller set in the agent's own brand, a Built for You build. Until their pages open, the next step is the Letters: the AI frontier as it bears on professional work, sourced, twice a month, free.
Revision history
1.0, October 30, 2026, first version.
Educational, not professional advice. Nothing on this page is affiliated with or endorsed by its publisher.

