Ends
A new site, finished and handed over.
Fixed scope, fixed price, written down before anything starts. It’s the one thing we do that ends rather than renews.
Who this is for
The site was built on a platform that made sense years ago and now charges you to leave. Nobody can change a page without calling somebody. The documents people actually need open as scans. Someone asked whether a screen reader can use it and the room went quiet.
That’s not something to look after. That’s something to replace, once, at a price you agreed first.
What you get
What’s in, what’s out, page by page. You approve it before we book the work.
It moves only when you change the scope, and a change gets written down and agreed before we build it.
Not a range that slides. You know the week it goes live and what we need from you to hold it.
Rather than remediated two years later once somebody complains. It costs less at the start and holds up better.
The code, the accounts, the domain, the content, and the notes to pick it up.
How it works
We go through what’s there now first: the pages worth keeping, the ones nobody has opened in a year, the documents, the forms. That’s what makes a scope honest instead of a guess.
Then you get it in writing, with a price and a date, and nothing gets built until you’ve said yes to it.
There’s a working version you can open whenever you want, and a short note from us each week on what moved. What sinks a rebuild is a client going quiet for a month and then seeing it all at once.
The same person start to finish. Whoever writes your scope builds it and hands it over at the end.
What happens the day after
A project ends. That’s the deal, and it’s the only reason we can put a price on it before we start.
A site starts drifting the day after it launches, though. Somebody has to own the certificate that expires, the update that breaks a page, the small change that comes up in month three.
If that’s someone on your team, good. We’ll set them up properly and hand over everything they need. If it isn’t anyone, it’ll be nobody, and you’ll be back here in three years reading the same page again.
How it’s priced
Against the scope, and the scope gets written first. The estimate is the price. It changes only when you change what’s in it, and you see the new number before we start. No hourly billing, and nothing extra at the end for the parts that ran long.
If the price is fine but finding it all at once is the problem, the same build can be paid for through a Webmaster agreement over a fixed term, with the care included the whole way. The project still has one scope, one price and an end date. What renews is the looking after, not the build.
When it’s done you own it
All of it. The code, the accounts, the domain, the content. Always, including if you walk away and never speak to us again.
Every shop says that, so here’s what it means on the day.
- 01The code sits in your account.
Your repository, your organization. We’ve access because you gave it to us, and you can take it back.
- 02The accounts are in your name and billed to you.
Hosting, the domain, anything with a login, registered to your email rather than ours. Your site never depends on us paying a bill.
- 03You get the notes, not just the files.
Where things live, what runs on a schedule, what to touch carefully, and what we’d do next. Enough for the next person to start without calling us.
A site you can’t leave is a site somebody else owns. We’d rather you stay because the work is good.
For public entities
Priced to survive a purchase order
Quoted as an annual not to exceed, with a scope of work written to attach to a purchase order. Named deliverables, a ceiling on the price, and a finish date inside the fiscal year.
Accessibility is part of the build rather than a later line, which is usually what has to be answered in writing.
Questions
What if the scope changes halfway through?
It often does. We write down what’s changing, what it does to the price and the date, and you say yes or no before any of it gets built.
Small things we absorb. If a change is an afternoon’s work, we’d rather do it than write a memo about it.
What happens to the site after it ships?
It’s yours and it keeps working. Nothing switches off and nothing reports back to us.
Sites do drift, though. Certificates expire, software ages, somebody uploads a document nobody checks. We’ll offer to look after it, but you’re just as welcome to hand it to someone in house.
Have something with a start and an end?
Tell us what you’re trying to replace and we’ll come back with a scope and a price.