Last updated: June 2026
If you've worked with a web designer before, handover might mean getting a WordPress login and being done. My sites are built differently. They're custom-coded with Next.js, hosted on Vercel, with the code stored in GitHub, so I want to explain plainly what you'll actually receive.
The short version: once you've paid in full, everything is transferred to you by default. If you'd rather I keep managing the technical side, that's available as an optional monthly arrangement.
Why handover looks different from WordPress
WordPress works well for many businesses, and plenty of good developers build on it. I use a modern custom stack because it tends to load faster and needs less ongoing plugin maintenance, which suits the simple, enquiry-focused sites I build for Singapore service businesses.
The tradeoff is that handover isn't just "here's one login." This page walks through exactly what that means, so there are no surprises.
Compare WordPress, builders, and custom sites.
What is always yours
No matter which path you choose after launch:
- Your domain name, registered in your name under an account you control
- All content, photos, and branding on your site
- The custom design and code I built for your project, once full payment is received
- A clear understanding of what was built, in plain language
Your two options after launch
You choose this before or at launch. If you don't say otherwise, the default is full transfer.
Included after full payment
Option 1: Full transfer (default)
Once your final payment is received, I transfer everything to accounts under your name. You hold the keys. I don't keep access unless you ask me back for a specific piece of work.
Step 1
GitHub repository
I transfer the code repository to a GitHub account you create (free). This is where the website's source files live.
Step 2
Vercel hosting
I transfer the live hosting project to your Vercel account using their built-in transfer feature, designed to do this without taking your site offline.
Step 3
Domain and DNS
If your domain needs repointing to your new hosting account, I'll either handle it or walk you through it step by step.
Step 4
Handover walkthrough
A short call (around 15 minutes) to show you around your new accounts, plus a brief written summary of what was built in case you bring in someone else later.
I'm still relatively new to LocalLaunch, so I haven't done a huge number of full transfers yet. I'll always walk through it carefully with you rather than rush. I'd rather take a bit longer and get it right.
Vercel has a free tier that covers most small business sites. If your site needs a paid plan, you pay Vercel directly, typically around $20/month for their Pro plan, though many sites never need it.
$50/month
Option 2: Managed care
If you'd rather not think about GitHub, Vercel, or technical maintenance, I can keep managing the setup for you. Optional, not required, and never pushed.
What's included
- I hold and manage the GitHub repository and Vercel hosting on your behalf
- Keeping the site online and deployments working
- Routine technical maintenance and dependency updates
- Small content updates: phone number, service list, swapping a photo
- A direct line to me when something needs fixing
What's not included
- New pages, redesigns, or features beyond small text and image changes
- Domain registration fees (you still own and pay for your domain)
- Vercel hosting fees if your site outgrows the free tier (billed by Vercel, not marked up by me)
You can end managed care at any time. When you do, I'll transfer everything to your own accounts (same as Option 1) so you're never stuck.
Making changes after launch
On full transfer (Option 1), day-to-day updates aren't something you'll do yourself in a dashboard. This isn't WordPress. For small changes, you can either message me and I'll quote the work, or bring in another developer who works with Next.js.
On managed care (Option 2), small content updates are included in the monthly fee. Anything larger (a new page, a new section, a redesign) is quoted separately before I start.
Which option is right for you?
Full transfer is probably right if…
- You want full independence from day one
- You might hire a different developer later
- You're comfortable creating free GitHub and Vercel accounts (I'll help)
- You don't want an ongoing monthly fee
Managed care is probably right if…
- You'd rather not think about hosting or code at all
- You want someone on call for small updates without quoting each time
- The monthly fee is worth not having to coordinate technical changes yourself
A fair question: what if you're not around?
That's a reasonable thing to ask when working with one person rather than an agency.
On full transfer, you hold everything yourself from launch. There's no dependency on me to keep the site running. On managed care, your domain is still registered in your name, and you can end the arrangement at any time with a full transfer.
I'm a solo freelancer who's still building LocalLaunch. I'd rather be upfront about that than pretend otherwise. What I can promise is that I'll be straight with you about what's possible, and I'd rather under-promise and follow through than oversell.