1. Your website brief
- Business / project: - Responsible owner: - Target buyer and situation: - Problem the buyer recognizes: - Service and practical outcome: - Primary visitor action: - What makes an inquiry qualified: - Required pages / sections: - Must-have workflows (pass/fail): - Nice-to-have features: - Explicitly out of scope: - Launch budget and date: - Person responsible after launch:
Complete: I help [buyer] address [problem] through [service], so they can [practical outcome].
2. Copy workbook
Homepage - Headline with a recognizable benefit: - Supporting line identifying audience and problem: - Primary action, with a real destination: - Evidence supporting the claim:
Service page - Who is it for? - What recognizable problem does it address? - What work and deliverables are included? - What is explicitly outside the scope? - What must the customer contribute? - How are scope and price agreed? - What happens after an inquiry?
Evidence register - Claim: - Supporting source or permissioned result: - Date and context: - Client permission status: - Attribution limits:
If no publishable client evidence exists, create a clearly labeled sample deliverable or worked example. Never invent testimonials or results.
Reader review Ask an unfamiliar reader to explain the audience, offer, evidence and next step. - What they understood: - Where they hesitated: - First revision:
3. Vendor trial
Use identical copy, image and tasks for every candidate. 1. Build one actual service page. 2. Change the scope and replace an image without outside help. 3. Test the mobile and keyboard journey. 4. Send a test inquiry and confirm delivery and reply routing. 5. Find the export and list what needs rebuilding.
- Candidate: - Required workflow pass/fail: - Observed task outcomes: - Assistance needed: - Unresolved concerns: - Full quote and renewal terms saved at:
Use vendor-scorecard.csv. Score each criterion 0–5. Suggested weights total 100. Overall score = sum(score × weight) / 100. Disqualify any failed must-have before considering the score.
4. Budget and commitment
Use budget-template.csv and the online calculator. Record the full first bill, coverage period, renewal interval and renewal amount. Keep owner time separate from cash. Use one currency and actual tax-inclusive quotes if tax is to be included.
- Amount due at launch: - Next subscription renewal date: - Other renewal dates: - Assumed maintenance hours: - Uncertain costs / contingency: - Cancellation and export terms saved at:
5. Launch checklist
- [ ] Name one audience and one useful outcome. A visitor should be able to explain who you help after reading the first screen. - [ ] Agree the smallest useful scope. Home, service, proof, about and contact sections are enough to start; they need not all be separate pages. - [ ] Get permission for every client claim and logo. Replace unsupported results with an honest description of your process. - [ ] Record the full commitment and renewal date. Include the prepaid term, domain, email, booking, maintenance and tax. - [ ] Put the domain and platform account under your control. Use your own recovery email, a unique password and multifactor authentication. Save recovery codes securely. - [ ] Keep source copy and original media outside the platform. Make an export, record what it omits and know who can restore the site. - [ ] Read every page on a real phone. Check menu, line lengths, buttons and tables in both orientations. - [ ] Complete the main journey with a keyboard. Every interactive element needs a visible focus state and a useful label. - [ ] Test an inquiry all the way to your inbox. Check success and failure messages, reply routing and spam folders. Send no sensitive test data. - [ ] Test the booking journey, if you use one. Verify time zones, availability, confirmation, cancellation and rescheduling. - [ ] Check links, downloads and a missing URL. Missing pages should return a real 404. Remove draft buttons and placeholder destinations. - [ ] Describe the data your actual tools collect. Minimize form fields; explain storage and contact routes. Get relevant legal advice for your markets when needed. - [ ] Save existing DNS before connecting the site. Preserve mail records. Confirm HTTPS works without certificate warnings. - [ ] Check search basics. Give each page a descriptive title and canonical URL; publish a sitemap and remove accidental noindex directives. - [ ] Write a short maintenance and access handover. List the responsible person, subscriptions, renewal dates and support routes. - [ ] Schedule a review of real inquiries. After launch, compare visitors’ questions with the promise and next step on the page.
6. Operational handover
Never put passwords, recovery codes or private keys in this workbook. Use a secure password manager. - Domain registrar and account owner: - DNS provider and access owner: - Hosting provider and access owner: - Email provider and support route: - Other services and renewal owners: - Secure credential location (reference only): - Backup location and contents: - Last isolated restore test: - Update and monitoring owner: - What triggers urgent action: - Recovery contact / escalation route:
Use maintenance-log.csv to record each change, verification and follow-up.
Use permission
You may adapt this kit for your business or client projects. Do not resell or redistribute the unchanged kit as your own product. This is planning material, not specialist legal, security or accessibility certification.