After Launch

Your site goes live. I don't disappear.

Published August 2026 ยท 6 min read

"Will they vanish once I pay?" is one of the most common unspoken fears in web design, and it's a reasonable one. Here's exactly what happens after launch: what's free, what's covered under warranty, what isn't, and who owns what from day one.

Why this matters

Post-launch is where most trust gets lost

The project isn't done the moment the site goes live. This is where a lot of client-developer relationships quietly fall apart, and where mine is built to hold up.

๐Ÿ“…30 days

Most warranties end right when problems show up

The typical web design warranty runs 30 days, sometimes less. That's barely enough time for real traffic to find the edge cases. Mine runs a full year on technical issues, not a month.

(Paper Leaf)
๐Ÿ”‘Yours

Your domain should never sit in someone else's account

If a developer's name is on your domain registration, you don't fully own your business's front door. Every site I build gets its domain and hosting set up under your name from day one, not mine.

(GoDaddy)
๐Ÿ’ฌ2โ€“3 hrs

"Will you vanish after I pay?" is a fair question

It's the quiet worry behind most final-payment hesitation, and it's a reasonable one in an industry with plenty of vanishing acts. I reply within 2 to 3 hours, warranty period or not.

๐Ÿ“Clear

New requests get a number, not silence

If something you ask for falls outside the original scope or the free-change window, you get a clear estimate before any work starts, never a vague delay while I figure out how to bring it up.

The timeline

From launch day to a year out

No renewal surprises, no mystery ticket queue. Just what's covered, when, and for how long.

01

Launch day: everything transfers to you

Domain, hosting, and source code are set up under your name and accounts from the start, not mine. There's nothing to "hand over" later because you already own it.

02

Days 1โ€“30: free content changes

Text edits, swapped images, small tweaks: no invoice, no ticket system, just a message. This window exists because the first month after launch is when you notice what needs adjusting.

03

Month 2 through month 12: the technical warranty

Any broken layout, browser compatibility bug, or form error gets fixed at no charge for a full year. New features and content edits aren't included; if you want to add something, that's scoped and quoted separately.

04

After the warranty year ends

Nothing changes automatically and nothing gets billed without you asking. If you need ongoing changes, we talk about an hourly arrangement or a retainer at that point, not before.

05

Any time, something breaks

You message me. Most replies land within 2 to 3 hours. If it's a warranty-covered bug, it gets fixed for free. If it's new work, you get a price before I touch anything.

Wondering how the initial price gets set before any of this starts? See how I price a website.

What's covered

Warranty coverage, spelled out

No guessing whether something qualifies. If it's not on this list, ask, and you'll get a straight answer before anything gets billed.

SituationUnder warranty
Broken layout or visual bug Covered
Form or contact submission failing Covered
Browser compatibility issue Covered
Text or image swap in the first 30 days Covered
New feature or page after launch Not covered
Content edits after day 30 Not covered
Issue caused by a third-party plugin or API change Covered
FAQ

Common questions

What people ask most before they've committed, and after they've paid.

What does the 1-year technical warranty cover?+
Any technical issue that arises after launch: broken layouts, browser compatibility bugs, form errors, or anything that stops working as originally built. It doesn't cover new features or content changes, but it does mean the site stays exactly as delivered for a full year.
What happens after the 30 days of free changes end?+
Nothing gets shut off. You can still reach me any time, and small requests are usually quick and low cost. Anything larger just gets a clear quote first instead of being automatically included.
Do you disappear once I've paid?+
No. Most replies land within 2 to 3 hours, warranty period or not, and that doesn't change once the invoice clears. If you've had a developer go quiet after final payment before, that's exactly the pattern this is built to avoid.
Who owns my domain and hosting?+
You do, from the first day. Domains and hosting get set up under your own accounts, not mine, so there's never a scenario where you need my permission to keep your own site running.
What if I need something fixed after the warranty year ends?+
You message me and I quote it. Most post-warranty fixes are small and don't take long, priced fairly for the actual work involved. There's no forced retainer and no pressure to sign anything to keep getting support.
What's not included, even during the warranty?+
New features, added pages, and content updates after the first 30 days. If something breaks because of an update on your end, that's covered too, and I'll get it running again.
Will my site still work years from now?+
That's the point of building on stable, actively maintained package versions instead of chasing every bleeding-edge release. It's also why dependencies get kept current rather than frozen at launch and forgotten: a site running on years-old, unpatched packages is far more likely to break or become a security risk than one kept on well-supported, up-to-date versions.
Why is post-launch support better with a solo developer than an agency?+
No timesheet, no billed-hours approval chain, no account manager deciding whether your fix is worth logging. A small post-launch tweak just gets done, instead of sitting in a queue until it clears an agency's minimum-billable-hour threshold. That flexibility is one of the bigger, less obvious differences between hiring one person and hiring a team; see what else changes between the two.

Still worried about being left with a broken site?

A year of technical warranty, 30 days of free changes, and a reply time measured in hours, not weeks.