TechnicalCollectible prompt
Website handoff guide for a non-technical client
Act as a web agency project lead. Write a handoff guide for {{business_name}}, whose new website at {{website_url}} is built with {{tech_stack}}. What we built: {{features}}. The reader is the owner, who isn't technical.
Sections:
1. What you have: pages and features in one short list
2. Accounts you own: domain registrar, hosting, database, email sending, analytics, payments and the code repository. For each: what it does, the login email, and a checkbox confirming ownership has moved to the client. Never put passwords in this guide; share them through a password manager
3. Costs: each monthly or yearly bill, its renewal date and what happens if it lapses, especially the domain
4. Common edits, step by step: update hours or prices, add a photo, publish a post, and answer form messages
5. What not to touch, and why
6. Backups, security updates and who handles them
7. If the site goes down: what to check first and who to call
8. Support: what's included, response times and what counts as new work
9. A 30-minute handoff meeting agenda and a sign-off checklist
Use plain language, short steps and no jargon. Mark anything I need to fill in, such as renewal dates. When you're done, list the details you still need from me.
Technicalnvoka.com/library/nvoka-website-handoff-guide-for-a-clientScan to open
Technical
Website handoff guide for a non-technical client
Hand over a finished site with accounts, costs, how-to steps and a support plan your client can follow.
Curated by Nvoka
ClaudeChatGPTClaude Code
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 4 filledYour prompt
Act as a web agency project lead. Write a handoff guide for {{business_name}}, whose new website at {{website_url}} is built with {{tech_stack}}. What we built: {{features}}. The reader is the owner, who isn't technical.
Sections:
1. What you have: pages and features in one short list
2. Accounts you own: domain registrar, hosting, database, email sending, analytics, payments and the code repository. For each: what it does, the login email, and a checkbox confirming ownership has moved to the client. Never put passwords in this guide; share them through a password manager
3. Costs: each monthly or yearly bill, its renewal date and what happens if it lapses, especially the domain
4. Common edits, step by step: update hours or prices, add a photo, publish a post, and answer form messages
5. What not to touch, and why
6. Backups, security updates and who handles them
7. If the site goes down: what to check first and who to call
8. Support: what's included, response times and what counts as new work
9. A 30-minute handoff meeting agenda and a sign-off checklist
Use plain language, short steps and no jargon. Mark anything I need to fill in, such as renewal dates. When you're done, list the details you still need from me.