Chattermill
Still supportedJan 2025under our care since
- Channel
- One shared Slack channel with their team
- The work
- New pages, new collections, scores checked after each release
- Their team
- Publishes in Webflow without us
A monthly retainer for the edits, new pages and checks a live site needs. Faults after launch are rarely dramatic: they are small, silent, and found by a visitor first. Below is one year of a site, left alone and looked after.
6faults live on the siteVisitors have met all six. Nobody has told you.
An example site. The months are illustrative; every fault is real.
One shared channel with your team, the way Chattermill works with us in Slack. A fix is asked for where it gets answered, and small ones go live without a ticket.
Speed, accessibility and structure measured again after each change, so a page that slipped is caught on the day it slipped.
PageSpeed on mobile, page by page. An average hides the one template that got heavy.
Webflow stays in your hands. We take what needs code, structure or a check, and leave the rest to you.
A reply within a few hours, weekends included. The same promise our contact page makes, kept for the whole retainer.
The automated audits we run on this site before every release, pointed at yours: lost titles, broken links, pages nobody links to, markup that stopped matching the words.
Almost never on launch day, because launch is the one day everybody checks everything. The trouble starts in month two: a page added in a hurry, a script that changes, a job that ran every night and quietly stopped. Each fault is small. What it costs is how long it stays live before anyone notices.
Checks run after every release and on a schedule, so the first person to meet a fault is one of us.
Small edits are part of the month. Only new work, a new template or a new section, gets its own estimate.
A check passes only when the thing it guards is really done. Ours had to learn that too, and the lesson is fault six in the year above.
At Chattermill the work has run without a break since January 2025: new pages, new collections, and the scores checked again after every release.
Most uptime monitoring asks whether the page answered, and it did. What it cannot tell you is that the headline sat invisible for ten seconds while a script loaded, which is exactly what a visitor met.
We ask the element, not the page. Our checks read the finished page the way a visitor gets it, on a phone and on a wide screen, and ask what matters directly: is it visible, is it linked from somewhere, does it fit the screen.
A pass has to mean the job is done. When a nightly job on this site cleaned one store and missed the other, it still reported success. Now a run passes only when every copy is clean, and a failure changes the status you see.
By the month
The number comes from three things.
Jan 2025under our care since
Day onesupported from launch, on the same terms as the build
Yes. The first month starts with a check of the whole live site, the same one we run on our own, so we know what we are taking on before we promise anything about it.
Within a few hours, seven days a week. Small edits usually go live the same day; a new page gets a date when we reply.
We agree that before the first month, in writing, so nobody has to remember it later. The retainer is sized to how often your site actually changes, which keeps unused hours rare.
No. Your team keeps publishing in Webflow on its own, and we take the work that needs code, structure or a check afterwards.
Yes, with a month of notice. The site, the Webflow project and everything in it stay yours, the same as after a build.