Launch and support questions, answered

It covers the window right before and after go-live. Final QA, the domain and DNS switch, redirects, analytics checks, and being on call to fix anything that breaks in your first week.

Every project comes with 30 days where bugs get fixed at no cost, and you can add a monthly plan if you want me around past that.

Your call. Some clients take the site and run it themselves, others keep me on monthly for updates, edits and small improvements. Both are fine, and the handover is the same either way.

A short kickoff call and a shared document. Brand assets, logins and goals get gathered up front so nothing stalls halfway through the build.

Yes. Old URLs get mapped, redirects set up, content moved, and everything tested on staging before the domain is pointed, so you keep your traffic and rankings.

I jump on it. During launch week the site gets watched closely, and any bug is patched at no cost inside the 30-day window.

Yes. During handoff you get short recorded walkthroughs and a plain written guide, so your team can edit pages without messaging me for every change.

It depends on scope and how much you want covered. Most plans are a flat monthly fee with a set number of hours for edits, updates and fixes, all agreed before anything starts.

Launch support is short and aimed at getting you live cleanly. A retainer is ongoing, covering edits, new sections and maintenance month to month after that.

Usually within one business day. A site going down gets same-day attention, and retainer clients come first on routine edits.

Yes, on a support plan. Plugins and integrations stay current, backups run, uptime gets watched, and the small fixes that pile up when a site is left alone get handled.