The short answer
Agree before you sign what happens after launch: how long support lasts, what it covers, and what comes after it. Then spend the first 90 days checking a short list on a schedule: forms and tracking in week one, search and speed in the first month, real results by month three.
Most problems with a new site show up after launch, when real visitors, real editors and real data arrive. A plan for that period matters as much as the build.
What a support window should cover
Almost every builder offers some support after launch. The words vary a lot, so pin down three things.
| Question | A clear answer looks like |
|---|---|
| How long? | A number of days from the launch date |
| What kind of changes? | A list: fixes to what was built, small content changes, and what is out |
| How fast? | How you send requests and how quickly you hear back |
The fair line is usually this: anything the builder made that does not work as agreed gets fixed, and small safe changes are covered for a while. New pages, new sections and redesigns are new work. If that line is not written down, expect friction over it later.
Kookies' 30 days of support
As one example, this is how our own support window works, from our pricing and our terms.
- Every Kookies project includes 30 days of support after launch.
- It covers safe changes: copy edits, image swaps, colour tweaks and link updates.
- It covers fixes to anything we built that does not work.
- New sections, page redesigns and new features are not part of it. We quote those separately, or they are covered by a care plan.
We keep it narrow on purpose, so it is clear. Thirty days is also long enough for you to see how often you really need help, which is the best input for the next decision.
Care plan, hourly or in-house
After the support window, you have three main options. The right one depends on how often your site changes.
| Option | Suits | Kookies' version |
|---|---|---|
| Hourly help | A few changes a month, or a few a year | $35 an hour, logged in 15 minute steps, with a cap you set |
| Care plan | New pages and changes every week, with no developer on staff | $4,000 a month, or $3,000 a month on a 6-month term; unlimited requests, worked one at a time |
| In-house | So much work that a full-time person is busy | Not ours: a hire on your team |
| Do it yourself | Content changes your editors can make alone | Covered by the training at handover |
The prices in the right column are Kookies' own. On our care plan, small fixes usually land within 24 hours and a new page of about five sections usually takes 2 to 3 days. Migrations are quoted as their own projects, not part of the plan. See the Webflow care plan, the Astro care plan and how hourly work runs.
Decision rule Count your change requests in the first 30 days. A handful means hourly is cheaper. Several a week, every week, means a plan or a hire will cost less than waiting.
The first 90 days
Put these checks in a calendar, with a name beside each.
| When | Check | Looking for |
|---|---|---|
| Day 1 to 3 | Send every form, check where leads land, check tracking events | Anything broken at launch |
| Week 1 | Old URLs, if you redesigned: do they redirect to the right page? | 404s and wrong targets |
| Week 2 | Search Console Pages and Sitemaps reports | Crawl errors, pages not indexed |
| Week 4 | Speed on your top pages, on a phone | Pages slowed by new scripts or large images |
| Week 4 | Editors: what did they try to change, and what stopped them? | Training gaps or build limits |
| Month 2 | Leads and bookings against the goal in your brief | Whether the site does its main job |
| Month 3 | A short written review: what worked, what to fix, what to build next | The plan for the next quarter |
If you moved from an old site, our first 30 days chapter of the site move playbook has a more detailed schedule for search.
What to measure
Go back to the goal from chapter 1. That is the main number. Everything else explains it.
- The goal metric. Bookings, sign-ups, enquiries or whatever you wrote in the brief. Compare it with the same period before launch, and with the same weeks last year if your business is seasonal.
- Conversion on key pages. Of the people who reach pricing or the demo page, how many act?
- Search. Impressions and clicks on the pages that matter, in Search Console.
- Editor time. How long does it take your team to publish a post or a page? If it is getting longer, something in the build or training needs fixing.
Measurement only works if tracking was set up right. If you are unsure, our tracking setup guide shows what a sound setup looks like.
When to fix it yourself and when to call
A simple split saves money and time.
| You can usually fix | Call your builder |
|---|---|
| Typos, copy and images in the editor or CMS | Something the builder made that does not work as agreed |
| New blog posts and CMS items | A form that stopped sending leads |
| Swapping a link or a button label | Layout breaking on a screen size |
| Unpublishing an old post | Anything touching the domain, DNS or redirects |
Keep a short running list of things you notice in the first weeks, and send them in one batch rather than one at a time. It is quicker for everyone, and on hourly work it is cheaper. For a wider view of what tends to break once a site is live, read what breaks after launch.


