Care plan tier sheet
Turn your care plan prices into tiers a client can compare: what each tier includes, task credits, add-ons and who may buy them, backups and response times.
Free template for designers
Client access request email
A ready-to-send email asking a client (or a previous developer) for every login and account you need before you start, with safer ways to share each one.
Email 1: To the client
Subject: Access we need before we start on [site name]
Hi [Client name], before we start on [project] we need access to the accounts below. Where you can, please add us as a user at [your email] rather than sending passwords. Please never send passwords in plain email: use [password manager share link or secure form] instead.
- Domain registrar ([company, if known]): add us as a user, or share the login securely. We change nothing without telling you.
- DNS host or Cloudflare: add [your email] as a member.
- Web hosting: add us as a user, or create a panel and SFTP login for us.
- WordPress: create an Administrator account for [your email].
- Email admin (Google Workspace, Microsoft 365 or other): only if the project touches email.
- Google Analytics, Tag Manager and Search Console: add [your email].
- Premium theme and plugin licenses: the account email or license keys.
- Payment, shipping or booking services: only if we will work on them.
If a previous developer holds any of these, tell us who and we will ask them directly. Not sure who owns something? That is fine, we will work it out together. We will keep a list of every account, its owner and renewal date, and give it to you at the end. Thanks, [Your name], [Business name].
Email 2: To a previous developer
Subject: Handover of [site name] for [client business]
Hi [Developer name], [client business] has asked us to take over their website. To keep it simple for you, could you please, by [date, about 10 business days away]: move [domain] into the client’s own registrar account, or send the transfer (EPP) code and remove the lock; send a full backup of files and database, or transfer the hosting account to the client; add [your email] as a WordPress Administrator; and list any licenses, services or API keys the site relies on. Any outstanding invoice can go to [client contact] and will be handled separately. Thank you for your help. [Your name], on behalf of [client business].
Before you send
- Run an RDAP lookup and DNS checks first, so you name the right companies.
- Agree in writing what you may change, and when.
- Store everything you receive in a password manager, never in email or chat.
- Take a full off-server backup before you change anything.
More templates
The rest of the kit
Maintenance agreement outline
The sections a solid website maintenance agreement covers, with numbers where they belong. An outline, not legal advice.
Incident log and post-incident report
A running incident log to fill in while a site is down or hacked, plus a short post-incident report for the client: timeline, impact, cause, fix and the changes that stop a repeat.
Website project contract outline
The topics a website design contract usually covers, from scope and payment to ownership, licenses, warranty and termination. An outline for your lawyer, not legal advice.
Vulnerability report replies
Two replies for unsolicited security reports: a polite decline for beg bounty emails, and a professional acknowledgement for a genuine, detailed disclosure.
Client leaving: website offboarding checklist
When a client moves on, a calm reply and a checklist for a clean, professional exit: accounts in their name, a tested backup, licenses sorted, your access removed and everything confirmed in writing.