๐Ÿš€ Launch Checklist

Everything you need to build and test the first 20 sites. No automation yet. Just prove it works.

0 / 0
๐Ÿ”‘
Accounts & Access
Sign up for everything. Get the keys.
โœ“
Create Cloudflare account FREE
cloudflare.com โ€” This hosts all the sites. Free plan is all you need to start.
โœ“
Enable Cloudflare Pages
Dashboard โ†’ Pages. Deploy a "Hello World" HTML file to make sure it works. 500 free deploys/month.
โœ“
Generate Cloudflare API token
My Profile โ†’ API Tokens. You'll need this so n8n can deploy sites automatically later. Permissions: Cloudflare Pages Edit, DNS Edit.
โœ“
Stripe account (UK) FREE
stripe.com โ€” If you don't already have one for RDM. You'll create products and checkout links here.
โœ“
Create Supabase project FREE
supabase.com โ€” Free tier = 500MB database + 50K API calls/month. This tracks all clients, builds, and statuses.
โœ“
Create Resend account FREE
resend.com โ€” 3,000 free emails/month. For onboarding confirmations, preview links, approval requests.
โœ“
Verify sending domain in Resend
So emails come from hello@ryandoesfreewebsites.com not some generic address. Add DNS records they give you.
โœ“
Anthropic API key (Claude) PAY AS YOU GO
console.anthropic.com โ€” This is what actually builds the sites. ~$0.10-0.30 per site build. You already have this.
โœ“
GitHub account FREE
Optional but recommended. Store your template code and deploy to Cloudflare Pages via Git. Makes version control easy.
๐ŸŒ
Domain & DNS
Your domain. Your brand. Your email.
โœ“
Confirm ryandoesfreewebsites.com ownership โœ…
You already own this. Done.
โœ“
Transfer DNS to Cloudflare (or point nameservers)
Add the domain to your Cloudflare account. Update nameservers at your registrar if it's not already on CF.
โœ“
Set up email (hello@ryandoesfreewebsites.com)
Google Workspace, Cloudflare Email Routing (free), or whatever you prefer. This is for client comms.
โœ“
Build a simple landing page on ryandoesfreewebsites.com
Doesn't need to be fancy yet. "Free professional website for your business. Apply now." + form. Deploy to CF Pages.
โœ“
Decide subdomain structure for client sites
e.g. smithsplumbing.ryandoesfreewebsites.com for previews โ†’ then custom domain when live. Or use CF Pages default URLs for previews.
๐ŸŽจ
Templates & Design System
The AI needs a starting point. This is it.
โœ“
Screenshot 30-40 best existing client sites KEY TASK
Group by trade: plumber, electrician, roofer, cleaner, landscaper etc. These become visual references for the AI prompts.
โœ“
List your top 10 trade categories
Which trades do you serve most? Plumbers, electricians, roofers, cleaners, landscapers, painters, locksmiths, pest control, aerial installers, builders? Rank them. Start there.
โœ“
Define standard page structure
Hero โ†’ Services โ†’ About โ†’ Reviews โ†’ Areas Covered โ†’ Contact. Define what every site MUST have. This is the brief you give the AI.
โœ“
Choose 3-4 base design styles
Modern dark, clean light, bold colour, classic professional. Each trade gets matched to a style. Keeps variety without chaos.
โœ“
Write the master AI build prompt KEY TASK
The prompt that takes form data (business name, services, area, phone) and outputs a full HTML/CSS site. This is the engine. Test it. Refine it. Test it again.
โœ“
Build 3 template sites manually using AI
Pick 3 different trades. Feed the AI real data. Get 3 complete sites. Review quality. Are they good enough to charge for?
โœ“
Build LocalBusiness schema template
Structured data (JSON-LD) that gets injected into every site. Business name, address, phone, services, opening hours. Google loves this.
โœ“
Test mobile responsiveness on all templates
80%+ of Dave's customers find him on their phone. If it doesn't look good on mobile, it doesn't exist.
โœ“
Run PageSpeed Insights on test sites
Target: 95+ performance score. Static HTML on Cloudflare should smash this. Fix anything that doesn't.
๐Ÿ”ง
Build & Deploy Process
Can you go from form data to live site? Prove it.
โœ“
Document the manual build process end-to-end KEY TASK
Write down every step. Form data in โ†’ AI prompt โ†’ HTML out โ†’ Upload to CF Pages โ†’ Custom domain โ†’ Live. Time it. How long does it take?
โœ“
Deploy a test site to Cloudflare Pages
Take one of your template builds, upload it to CF Pages, get it live on a URL. Click around. Does everything work?
โœ“
Test custom domain connection on CF Pages
Can you point a real domain (or subdomain) to a CF Pages project and get it live with SSL? Do it once. Prove it works.
โœ“
Test the "changes" process
Client says "change my phone number" โ€” how fast can you update and redeploy? Under 5 mins? Good. Over 15? Problem.
โœ“
Set up preview URL workflow
Client needs to see their site before it goes live. CF Pages gives you preview URLs automatically. Decide how you send these โ€” email? Text?
โœ“
Set up GA4 + Search Console for one test site
Manual for now. Create GA4 property, add tracking code, verify in GSC, submit sitemap. Time how long it takes.
โœ“
Create sitemap.xml template
Simple XML sitemap that gets generated for each site. Auto-submitted to Google. The AI can generate this per build.
๐Ÿ’ณ
Payments & Billing
No money, no build. Keep it simple.
โœ“
Create Stripe products and prices
Starter: ยฃ27/mo (billed ยฃ81 quarterly). Growth: ยฃ47/mo (billed ยฃ141 quarterly). Both as recurring subscriptions.
โœ“
Build Stripe Checkout links for both tiers
Payment Links or hosted Checkout. Client clicks โ†’ pays โ†’ done. No faffing about. Test both with test mode cards.
โœ“
Set up Stripe webhook to catch payments
When someone pays, you need to know. Stripe โ†’ webhook โ†’ n8n (or Supabase directly). Triggers onboarding form send.
โœ“
Define cancellation / failed payment process
What happens when payment fails? 3 days grace โ†’ reminder email โ†’ 7 days โ†’ site paused โ†’ 14 days โ†’ site taken down. Write it out.
๐Ÿ“‹
Onboarding Form & Flow
This is where the client gives you everything. Make it idiot-proof.
โœ“
Define all onboarding form fields KEY TASK
Business name, trade/service, phone, email, services list, areas covered, about text, logo upload, photo upload, colour preference, existing website URL (if migrating), social links.
โœ“
Build the onboarding form
Tally, Typeform, GHL form, or custom. Needs to be mobile-friendly. Dave's filling this in on his phone in his van.
โœ“
Test form โ†’ AI build pipeline (manual)
Fill in form as a fake client. Copy data into AI prompt. Get site. Is the output usable? How much editing needed?
โœ“
Build the application form (separate from onboarding)
Application = name, email, trade, area. No payment. You review, approve within 48 hours, THEN send payment link. Keeps out time-wasters.
๐Ÿ“ง
Client Communications
Every email. Every text. Written once, used forever.
โœ“
Write "Application Approved" email
Welcome! You're in. Here's your payment link. Pick your tier. We start building as soon as you pay.
โœ“
Write "Payment Received" email + onboarding form link
Thanks for paying. Fill in this form and we'll start building your site. Takes 5 mins.
โœ“
Write "Your Preview Is Ready" email
Here's your site. Click to preview. Happy? Reply APPROVE. Want changes? Reply with what you need. 3 rounds of changes included.
โœ“
Write "Your Site Is Live" email
Congratulations! Your website is live at [URL]. Here's what happens next. Include Google Business Profile link guidance.
โœ“
Write "Application Not Approved" email
Polite rejection. "This isn't quite the right fit right now." Keep it kind. They might come back.
๐Ÿงช
First 20 Test Builds
Build. Break. Fix. Repeat. No paying clients yet.
The plan: Pick 10-20 existing GFOG clients who don't have websites (or have terrible ones). Build them free sites as a test. They don't pay extra. You get real data, real feedback, and real portfolio pieces. Win-win.
โœ“
Pick 20 existing clients for free test builds KEY TASK
Mix of trades. Some with no website. Some with terrible websites (migration test). Get a good spread.
โœ“
Build first 5 test sites
Go slow. Time each build. Note every problem. What's the AI getting wrong? What needs manual fixing? This is learning time.
โœ“
Refine prompt and templates based on first 5
What patterns emerged? Same issues every time? Fix the prompt. Fix the template. Then build the next batch.
โœ“
Build next 10 test sites
Should be faster now. Target under 30 mins per site including QA. If it's longer, something's wrong.
โœ“
Build final 5 test sites
These should feel routine. If it still feels clunky, you're not ready for paying clients yet.
โœ“
Collect feedback from test clients
Send them the preview. What do they think? What would they change? This is gold for refining the process before launch.
โœ“
Document average build time and cost per site
How long does each site take? What's the AI cost? What's the total unit cost? Confirm your margins are where you think they are.
โœ“
Confidence check: "Am I ready for paying clients?" YOU DECIDE
Can you reliably go from form submission to live site in under 7 days? Can you handle 5 at once? 10? If yes โ†’ launch. If no โ†’ keep testing.
Copied to clipboard