Notes
The first two weeks of a care-plan client
10 November 2026
The retainer starts when I can see the site and they have a letter, not when the invoice is paid. I have taken money on a Friday and spent the next month asking for a login. That month is not care. It is a queue. The first two weeks are the job of turning a yes into a row I can run without another meeting.
The price and the package are already decided by then. How I build that offer is the pricing note. The hour I repeat after this is the monthly pass. A book that is not all WordPress still uses one letter, which is the mixed-stack process. This note is only the start: access, the roster, and a first page they can open before I have changed anything.
Do not start on a handshake
A signed plan with no roster is a mood. I do not book the first pass until the row exists. The row is short on purpose. If it needs a workshop, the scope is still a project.
Client, and the person who answers email:
Public URL, and the money path:
Stack:
Who may edit content, by name:
Who may deploy or update, by name:
Registrar: owner, and the expiry date if we do not hold the login:
Certificate: who issues it, and the expiry date:
Where the monthly letter will live:
Plan name, price, start date:
Previous maintainer, if any, and the date they stop:
Blank cells are the first week’s work, not a reason to improvise. A missing domain date is not “probably fine.” It is the thing that expires while everyone is being polite. I would rather delay the kickoff by three days than invent the date.
Ask for a seat, not the owner password
I want my own user. I do not want the password that also opens their billing and their email. A shared owner login means I cannot leave cleanly, they cannot see what I did, and the next person inherits a secret that has been in three inboxes.
WordPress: an administrator account in my name, with whatever second factor the host actually supports. Not a login called admin, and not their personal address. If a previous agency is still an administrator, I do not delete them on day one. I list them, I show the client the list, and I remove them on the date the client says the handoff is finished. Deleting the old agency before the files are copied is how a site loses the only person who knew where the backup lived.
Webflow: I need a role that can see the things the plan claims I will watch. Their backup help says only Site managers can open site backups. If I am a designer who cannot open Backups, I cannot honestly tell them I will restore a bad publish. Either the role includes that, or the plan says they hold restores and I hold the outside checks. Write which one it is in the row. Do not discover it in month four.
Squarespace: a contributor seat that matches the work. Code injection is not on every plan. Their help, updated 27 August 2026, limits that tool to Core, Plus, Advanced, and some legacy plans, and calls it outside their support. If the care plan mentions a script I added, I confirm in week one that the plan still has injection and that I can see it. If it does not, the script is not my lever and the proposal was wrong.
A custom app is the opposite problem. People hand me a server password because it feels faster. I want a deploy path I can explain, a health URL, and a named person who gets paged. The shape of that box, when I am the one running it, is the hosting stack. Onboarding still does not include “while we are here, let me rebuild it.”
The one login test
A seat in the inbox is not a seat that works. I log in once on the real site and I write down the role name the screen shows me. Then I log out and log in again from a private window. The first session is sometimes their browser still holding them as the owner. If the second login fails, I do not have a seat. I have a tab they left open, and the letter is not allowed to say otherwise.
What I look at in that session is small. The list of other people who can publish. The place where the plan name is visible, if this tool shows it. The form or the checkout, opened while I am logged out in the other window, so I see the public path and the editor in the same hour. I do not open billing. I do not download a full export on day one unless the plan already said a copy is part of week one. I do not click publish to see what happens.
I write the role in the roster in their words. Site manager. Administrator. Contributor. If I cannot name the role, the letter says “I can log in, and I cannot yet see which permissions that login has.” That sentence is the difference between a restore I can click and a login that only looks like access. Webflow’s backup article is explicit that only Site managers can open backups. I would rather write the lesser role down in week one than discover it when a publish needs undoing.
What I will not begin without
Four things. The public URL. The name of the person who is allowed to publish. A domain expiry I have seen, or the name of the human who will read the registrar mail. An address for the monthly letter that is not a black hole. Billing can lag a few days. These cannot.
I do not require the registrar password in week one unless the plan says I renew the domain. Most plans should not. The client owns the name. I own the date. If they will not tell me the date and will not add me as a user who can see it, I tell them the domain is outside the retainer. That sentence belongs in the kickoff, not in the apology after it expires.
I also do not require a full content audit. The first pass is the outside look from the monthly note: homepage, the money path, both dates, logged out. I am confirming I can see what a stranger sees. I am not delivering a redesign critique in the same email as the welcome.
The first fourteen days
I put this on a calendar when they say yes. The days are a sequence, not a pile.
- Day 0. Send the access list and the roster questions. One email. No attachments they have to sign before I know the URL.
- Days 1 to 3. Seats arrive. I log in once, confirm the role, and log out. I write down every other administrator I can see. I do not click update.
- Days 3 to 5. Outside pass, logged out, on the real hostname. Certificate date, domain date, homepage, money path. If a date is inside 30 days, that becomes the first task and the first line of the letter. It is not a footnote under the welcome.
- Days 5 to 7. First letter, even if I changed nothing. Same headings I will use every month after.
- Days 7 to 14. Only now, small fixes that were already in the plan: a form going to a dead address, an old agency login they asked me to remove, a health URL that 500s. New pages wait. The change budget, if there is one, starts on the plan’s start date, not during the scramble to get in.
If day 7 arrives and I still cannot log in, the letter says that. “I do not have a seat yet. The outside checks are below. I have not changed the site.” Silence reads as if the care has started. A plain sentence reads as the truth, and it is the thing that gets the login sent.
The first letter is allowed to be boring
People wait to send a report until they have something impressive. The client then has two weeks of silence and decides the retainer is vapor. The first letter’s job is to teach them where to look. Impressive can wait until there is something true to say.
Here is a first letter for a site I am inventing. Not a client. The dates are not a measurement.
Harbour Studio
https://harbour.example
First note, 12 November 2026
Work
Nothing changed yet. I can see the public site and I have a seat in Webflow. You still publish the copy.
The site, watched
Homepage and the booking page answered when I checked on 12 November.
Certificate is on Webflow’s side. I will keep the date in this letter each month.
Domain expires 9 January 2027. The card is in your account. I cannot renew it.
Also
Two other people can publish. I have not removed anyone. Tell me if one of them should go.
That is enough. A sample digest is what I show before they sign, labeled as a sample. This first real page replaces the sample. Same headings, their URL, their dates. The blank version, if you want the headings without my wording, is the report template.
The kickoff email
I send this the day they accept. It is the list, not a tour of the product.
Subject: Starting care for [site]
I need four things before the first pass.
1. A seat of my own on [WordPress / Webflow / Squarespace]. Not the owner password.
2. The person, by name, who is allowed to publish.
3. Who renews the domain, and the expiry date. I do not need the registrar password.
4. Where to send the monthly letter. The first one will say what I found, including if I have not changed anything.
I will not remove the previous maintainer until you say the handoff date.
Small edits start on [start date]. New pages are still quoted separately.
If they reply with a shared password in the body of the mail, I do not use it. I ask again for a seat, and I tell them to change the password they just emailed. That feels fussy. It is the difference between a retainer and a liability. I would rather lose a day than store their billing login in my inbox.
The previous person
If someone else has been “keeping an eye on it,” I want their name and the date they stop. I do not want a fight. I want the backup location and the list of logins they hold. I ask the client to ask them, in the client’s voice, not mine. A note from the new freelancer that opens with “please send all passwords” gets ignored, correctly.
Until that date, I do not change DNS and I do not delete users. I can still do the outside pass. The outside pass does not need their blessing. The inside pass does. Mixing those up is how two people update the same plugin on the same afternoon.
When the handoff date arrives, I remove the access the client named, I confirm I still have mine, and I write one line in the letter. “The previous maintainer no longer has a login.” No story about how the relationship ended. The letter is a record, not a side.
What I write down and do not touch
Week one collects names. It does not collect every password in the business. I want the public site, the editor, the two dates, and the person who answers. I do not want the email host, the card on the registrar, the analytics property, or the payment login, unless the plan named them. Those are other jobs wearing this one’s coat, and they will expand until the care plan is a junk drawer.
DNS is the request I refuse most often in the first week. “Can you just point it?” Not on a Watch plan, and not before the first letter. A record change can take the site and the mail down in the same minute. If the plan includes DNS, it is a named task with the current records written down first, and it waits until they have already seen the site in the state I found it. I have moved a record during onboarding because the old agency was slow to reply. The contact form’s mail followed the record to nowhere. The client experienced that as the new retainer breaking the site. They were right about the timing, even if the record was the one they had asked me to change.
Mail is the same trap. The website and the mailbox often share a domain and nothing else. I say so in the kickoff. I am looking after the site. Mail stays with the person who already has it, unless we have written a separate line. If I do not say that, the first bounced invoice becomes my incident, and I will not have a login that can fix it.
If the previous person does not answer
I give the handoff a date, and I do not pause the outside work while I wait for them. The client asks, in the client’s voice, for the backup location and the list of logins. If a week passes and nothing arrives, the first letter says that in one line. I asked, through you, for the previous backup location. I do not have it. The checks below are from the public site only. I do not invent a copy I have not opened. I do not tell them the old agency is withholding it. I do not know that. I know I do not have the file.
What I will not do is start a second copy of the site in week two so that I “have something.” A rebuild during onboarding is a project. It has a price, a scope, and a moment where the client chooses it with their eyes open. Slipping it in because a login never arrived is how a care plan becomes an unpaid migration. The pricing note already split care from projects. I keep the split when the inbox is quiet, which is exactly when I am tempted to fill the silence with work they did not buy.
If they do answer, I still do not treat their export as proof until I have opened it. A zip in a shared folder is a claim. Opening it belongs to the restore drill, and that drill is not a requirement for calling the retainer started. Started means the roster, the seat, the outside pass, and the first letter. A copy I have actually opened can be the first real task after that. Pretending the link was a restore, because someone sent it, is the sentence I regret the first time a page is missing.
What week two is not
It is not a strategy workshop. It is not a redesign proposal wearing a care-plan hat. It is not the moment I install five tools so the stack matches mine. If the site is on Squarespace and the plan is Watch, week two is me knowing the form recipient and the domain date. Installing a monitoring stack they did not ask for, on a site I cannot deploy, is theatre.
It is also not the time to promise a response window I did not sell. If they bought Watch, the incident note they will get later is the one Watch described. Onboarding does not quietly upgrade them to a same-hour page. If they need that, it is a plan change, said out loud, with the worksheet from the pricing note. I have made the mistake of being heroic in week one and then being the slow person in week six. They remember week one.
A checklist before I call it started
- Roster row filled. URL, editor’s name, registrar owner, both dates, plan, letter address.
- My own seat works. I have logged out and back in once.
- Other admins are listed. None removed unless the client named the date.
- Outside pass done, logged out, on the hostname customers use.
- Any date inside 30 days is a task, not a welcome gift.
- First letter sent inside seven days, including a letter that says nothing was changed.
- Change budget, if any, starts on the plan date. It does not backfill the onboarding scramble.
- I can point at the letter without explaining a second system.
When that list is true, the retainer has started. The invoice was just the permission to make the list true. If you want the page they will keep opening after week two, it looks like the sample, with their name on it instead of the stand-in.
Sources
- Webflow, save and restore backups. Only Site managers can open backups. A lesser role cannot promise a restore.
- Squarespace, custom code. Updated 27 August 2026. Code injection is outside their support and is not on every plan.
- How to price a care plan. The offer this onboarding assumes.
- Report template. The headings of the first letter.
Monthly agency tip
One tip a month.
One practical tip a month on proving your retainer is worth it. No spam.
I email a confirmation link before I add you. I store the address, this page, and the date. Unsubscribe any time. Read the privacy page.