Client accounts: who owns what

About 50 minutes to plan, then a 60-minute setup session with each clientYou need: your agreement template (Lesson 14.3), Google Sheets, your password manager, and your notes on the accounts you've used in this course (Hostinger, Cloudflare, Supabase, Resend, Vercel, GitHub, Google)
This video is in the full courseGet the course to watch every video and read every lesson in full. GHS 399, paid once.Get the course · GHS 399
Video · 13:44
Goal

Set up every client project so the client owns their domain, DNS, database, email sending and Google accounts, with you added as a member, while the code and hosting run from your own GitHub and Vercel accounts, and record it all in an accounts register with no passwords in it.

Why this matters

Here's a story that happens far too often. A web designer builds a site, registers the client's domain on their own account "to keep it simple", and puts the database in their own Supabase. A year later they fall out, or the designer moves abroad, or simply stops answering. The client can't renew their own domain, can't reach their own customers' orders, and can't move the site. Their business is held hostage, even if nobody meant it to be.

You'll do the opposite, from the first client. The business owns what belongs to the business: its name on the internet, its customers' data, its Google presence. You're a trusted helper with access that they can remove at any time. That's fairer, it's safer for both of you, and it's a selling point: "You'll own everything. I'll never hold your website hostage."

In the full lesson

  1. The idea in plain English
  2. Do it
  3. Check it worked
  4. Quick check
  5. What you can do now
Stage 3 · Get paidYou’ve seen the why. The how is in the course.

The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.

Get the course · GHS 399See what’s inside
Already have the course? Open the full lesson