Handover
Client-ready handoff packs for finished projects.
not a lost day
shipped to clients
mapped and handed over
Point Handover at a finished project and get a client-ready handoff pack in minutes — a plain-English owner’s manual, developer notes, a credentials ledger of every account, and a verified, clean source archive.
The handoff is the most-skipped deliverable in agency work — so clients end up unsure what they actually own, and developers keep fielding one-off questions long after a project wraps. A clear handover pack gives the client real independence and gives you a clean finish.
Handover scans the project for the hard facts, asks the handful of questions only a human knows, and generates a branded pack that makes the client genuinely independent — domain, hosting, code and accounts all accounted for.
How it works
Three steps from sign-up to something useful. No manual, no onboarding call.
- 01
Scan the project
Handover reads the stack, services, deploy setup and env vars — and blocks if it finds a live secret committed in the code.
- 02
Answer a few questions
About ten questions only a human knows: who the client is, who holds the domain and hosting, the support arrangement.
- 03
Generate the pack
Owner’s manual, developer notes, handover checklist, credentials ledger and a clean source archive — branded and ready to send.
Here’s what Handover makes from a finished project — the pack on the right, the accounts it hands over, and the safety gate that refuses to ship a live secret to a client. Flip the toggle to watch it block.
Project
Riverside Dental
Stack
Static site · Vite · Tailwind
Hosting
Vercel (under the studio’s account)
Domain
riversidedental.com.au — registrar: Netregistry
Services detected
- · Resend — email delivery
- · Stripe — deposit payments
- · Google Fonts
Secrets (set in hosting, not the code)
- RESEND_API_KEY
- STRIPE_SECRET_KEY
The pack
- ✓Owner’s ManualPlain-English, for a non-technical client (HTML + PDF)
- ✓Developer NotesStack, commands, services, outstanding items
- ✓Handover ChecklistOwnership decisions + go-live steps
- ✓Credentials LedgerEvery account, who holds it, what transfers
- ✓Source archiveA clean, verified copy of the code
Credentials ledger
The web address itself
Where the site runs
Holds RESEND_API_KEY · most-overlooked
Holds the payment keys
Where enquiries land
What you get
- 01Plain-English owner’s manual (and PDF)
- 02Credentials ledger — every account, who holds it
- 03Refuses to package if it finds live secrets
- 04Verified, clean source archive
Pricing
In active development — used on live C4 client handovers.
Get in touchNo pressure · just a friendly chat
Common questions
Will my client actually understand it?
Yes. The owner’s manual assumes zero technical knowledge — every term is explained, with a quick-reference card to keep.
What if there is an API key in the code?
Handover refuses to build the pack until it is removed, so a live secret never ships to a client.
Does it work on any project?
Any git repository. It is stack-aware, so the notes and manual fit what the project actually is.
