All news

Process24 September 20264 min read

Twenty days of warranty — what it covers

No care plan after launch doesn't mean no cover. Here's exactly what the 20-day warranty includes, what it doesn't, and when it runs out.

A smartphone on a worn wooden counter in a small back office, lit by a single overhead bulb.

The site goes live on a Friday. Over the weekend, the contact form stops sending emails. Nobody notices until Monday morning.

That's the warranty's job. We fix it, no invoice, no argument.

What the 20 days actually covers

Every project we launch includes a 20-day post-launch warranty, whether or not the client takes a care plan afterwards. It runs from the day the site goes live.

During those 20 days, we fix anything that's broken in our own work. That means:

  • A form that doesn't send
  • A page that errors on mobile but not desktop
  • A booking flow that breaks at a specific step
  • An integration we built that stops passing data correctly
  • Anything we wrote, configured or connected that isn't doing what the brief said it should

No support ticket queues. No waiting to see if it qualifies. If it's our code or our configuration and it's not working, we fix it.

What it doesn't cover

The warranty covers our work. It doesn't cover decisions made after launch.

If a plugin the client installed breaks a page, that's not our build. If the client edits a template section and removes a navigation element, that's not a fault in what we delivered. If a third-party service — a payment gateway, a delivery API, a Google integration — changes its own behaviour, the issue is upstream of us.

The warranty also doesn't cover new features. If a client decides after launch that they want an additional page, a second language, or a different booking flow, that's a new brief, not a warranty claim. The 20 days is there to catch genuine faults, not to extend the build at no cost.

This isn't small print designed to avoid responsibility. It's a clear line between what we control and what we don't. Most studios don't draw it at all — which is how "free support" becomes a conversation about what counts.

What happens after 20 days without a care plan

The warranty closes. At that point, if something breaks, fixing it is a paid piece of work.

That sounds stark, but it's honest. A site is software, and software changes around it — browser updates, operating system changes, third-party services shifting their APIs. Something that worked at launch can stop working six months later for reasons that have nothing to do with the original build. That ongoing maintenance is what a care plan covers.

Care plans start at €19 per month and include updates, monitoring and support. The first month is free on every project above €500. If a client isn't sure whether they need one, the 20-day window is a reasonable trial: see how much changes, see how much you actually need someone watching it.

For a small brochure site that doesn't connect to anything, a care plan is often unnecessary. For a restaurant site with delivery integration, a booking system and live reviews — something with moving parts — it's worth the cost.

The difference between a warranty and a care plan

A warranty is retrospective. It covers what was built and whether it works as specified.

A care plan is ongoing. It covers what happens next — updates, new browser behaviour, small edits, monitoring that catches a problem before a customer does.

They're not the same thing, and confusing them is how businesses end up surprised when a warranty call gets declined three months after launch.

We try to be direct about this on every project. The 20-day window is clearly documented in the written agreement each client signs. So is what it excludes. Nobody should read this article and discover something they weren't told.

How to use the 20 days well

Test on real devices, not just the browser you used during approval. Test the contact form — send yourself a message and check it arrives. Go through the booking flow as a stranger. Check every page on a phone.

If something is wrong, the sooner it's reported, the faster it's fixed. A fault reported on day two takes hours. The same fault reported on day nineteen, after two weeks of customers quietly failing to book, is harder to unpick.

If you're not sure whether something counts as a fault or a new request, ask. We'd rather answer that question than have a client sit on a broken form because they assumed it wouldn't qualify.

For anything built above €500, we include the first month of care free — which means in practice, most clients have 20 days of warranty plus 30 days of care before they spend anything on support. That's seven weeks to understand what the site needs after launch.

Questions about what's covered, or ready to talk about a build? Contact us or see what's included at each tier on the pricing page.

Got a build in mind?

Tell us what you need. We'll come back with a fixed price and a timeline in weeks.