DEV Community

Your Wish Is Our Code for Your Wish Is Our Code

Posted on Originally published at yourwishisourcode.com

A warranty and a care plan: which one pays when your site breaks

Two lines on the proposal, two different promises

A proposal from us carries two lines that look alike: a warranty and a care plan. They pay for different things. When something on your site breaks, the first question is which line it falls under.

The warranty comes with every site we build, whether or not you take a care plan. It covers bugs found in a stated window after launch. The care plan is a separate monthly agreement under which we keep the live site in working order.

The FTC draws the same line for products: its Businessperson's Guide to Federal Warranty Law says a warranty comes with the product and is included in the price, while a service contract is a separate agreement. That guide is about consumer products, and nothing here says federal warranty law applies to a website. The split is still the clearest way we know to read our two lines.

What the warranty covers

The warranty is about the thing as built. If a form we built stops sending, or a page we built breaks, and you find it inside the window, we fix it under the warranty. You do not need a care plan for that.

The FTC's consumer page on warranties tells buyers to check how long a warranty lasts and what the company will do if the product fails. Those are the right two questions for a website warranty too. For ours, the length is the stated window after launch, and what we do is fix the bug. The full terms are in the guide what a care plan covers.

When the window closes, the warranty is done.

What the care plan covers

The care plan picks up where the build leaves off. Under it, we watch that the site stays up, back it up, apply the updates its code depends on and make small changes when you ask. Each month that means monitoring, backups, security and dependency updates tested before they go live, and a set number of hours for small changes.

The word tested is the one to look for. An update that goes straight to the live site without a test is how an order page breaks on a Friday night.

The plans, and what each one includes, are on the care plans page.

Why a finished site still needs upkeep

A site that works on launch day still sits on software that keeps changing under it. If your site runs on PHP, each PHP release branch gets two years of full support, then two years of security fixes only, then reaches end of life and is no longer supported. The dates for each branch are on PHP's supported versions page.

The padlock in the browser bar is the same story. Let's Encrypt says its certificates, now valid for 90 days, will be cut to 45 days by 2028. That means the renewal behind the padlock has to keep running on its own, every time. The details are in Let's Encrypt's post on shorter certificates.

None of this is a bug in what was built. It falls under the care plan, which covers security and dependency updates, and not the warranty, which covers bugs found in the window.

What neither one covers

A care plan never pays for hosting, the domain or software subscriptions, and it does not include new features. Those accounts stay in your name, and their bills are yours.

Watch out: if the card on your hosting or domain account expires, neither the warranty nor the care plan pays that bill. Check the card on each account now, not when the site is already down.

New pages and features are change orders, priced in writing and built only after you approve. So a new booking page is neither a warranty fix nor a small change under the plan.

The FTC also tells buyers to check whether a warranty covers problems that come from changing the way a product works. Ask the website version before you sign: if someone else edits the code after launch, who fixes what breaks, and under which line? Get that answer in writing.

How to read the two lines

Put your proposal next to the FTC's questions and read each line on its own.

Warranty Care plan
What it covers Bugs in what was built Upkeep of the live site
When it runs A stated window after launch Month by month after launch
How it comes With the build A separate monthly agreement
What it leaves out New pages and features Hosting, domain, subscriptions, new features

If a line on a proposal does not say how long it lasts or what happens when something fails, ask before you sign.

What to do

  • Look up the warranty window in the guide what a care plan covers, count it from your launch day and put the end date on your calendar.
  • Inside that window, send yourself a test message from every form and open every page on your phone. Report anything broken while the warranty still covers it.
  • List who holds the hosting, domain and software subscription accounts, and check the card on each. A care plan does not pay those.
  • If your site runs on PHP, find out which version it uses and look that version up on PHP's supported versions page.
  • Write down the new pages you want, and ask for each one as a change order, priced in writing before any work starts.

Every site we build comes with a warranty, and the care plan is there for after, with both written out on the care plans page.

Top comments (0)