The system

From a first website to the whole machine.

Every site we make comes out of the same system: shared parts, measured before they ship, watched once they're live. What changes between a startup and a corporate storefront is how much of that system we run for you.

Three layers — design and build at the base, keeping it online above it, keeping it right on top. Startup covers the base layer, Storefront the lower two, Corporate all three. L3 Keep it right EDITS · WEEKLY AUDIT · MONTHLY REPORT L2 Keep it online HOSTING · DOMAIN · SSL · HOURLY CHECKS L1 Design and build TEMPLATE · YOUR CONTENT · SEARCH DATA 01 02 03 01 STARTUP 02 STOREFRONT 03 CORPORATE — EVERYTHING
Uptime checks
Hourly
Site audit
Weekly
Report
Monthly
Server-side code
None
01

Three tiers, and one foundation under all of them.

Every tier starts from the same build. The higher ones add the layers that keep a site online and keep it right — the part most websites are missing six months after launch.

  1. 01

    Startup

    A first website

    Design and build. A finished, tested site made from a template and fitted to your business.

  2. 02

    Storefront

    An established shop

    The build, plus the layer that keeps it online: hosting, your domain, a certificate that renews itself, and hourly checks that it's up.

Specification — what each tier includes
Included 01 Startup 02 Storefront 03 Corporate
L1Design and build
Designed from a vetted template Fitted to your business with your words, hours and brand Included Included Included
Fast, mobile-first static build No server-side code, no plugins, no CMS to patch Included Included Included
Accessibility checked before it ships Every text colour measured against WCAG AA Included Included Included
Search-ready structured data Hours, phone and service area in the format search engines read Included Included Included
Preview before launch Two rounds of revisions included Included Included Included
L2Keep it online
Hosting on a global CDN Not included Included Included
Domain registered in your name Registered and renewed by us Not included Included Included
SSL certificate Renews itself Not included Included Included
Uptime and certificate checks Hourly, around the clock; a person follows up any failure Not included Included Included
A restore point for every published version Any earlier version can be put back Not included Included Included
L3Keep it right
Unlimited content edits Preview by next day; live once you approve Not included Not included Included
Same-day urgent fixes Wrong hours, wrong number, a closure, a site that's down Not included Not included Included
Weekly audit Broken links, security headers, page weight Not included Not included Included
Structured data kept in step Change your hours once; the page and its search data change together Not included Not included Included
A one-page monthly report Uptime and speed, sent by a person Not included Not included Included

Not sure which fits? Tell us what you run and we'll say — including when the smaller tier is enough.

02

What runs, and how often

Three schedules, because the things being watched go wrong at different speeds. A check that passes stays silent. One that fails reaches a person.

A monitoring panel: uptime history, response time, and scheduled check results SITE STATUS ALL SYSTEMS UP UPTIME · LAST 30 DAYS 99.98% 30 DAYS AGO TODAY LOAD TIME 0.41s MON SUN SCHEDULED CHECKS SSL certificate VALID · 78d Security scan PASSED Broken links NONE FOUND Backup 12 RESTORE POINTS
FIG. 02 Illustrative readout — not live data. The checks are real and run on the schedule below.
Hourly
Is it up, how fast did it answer, and when does the certificate expire.
Weekly
Every internal link, the security headers, the https redirect, page weight.
Monthly
A one-page report of the month, generated automatically and sent by a person.
Every change
A restore point. Any published version can be put back.
03

Some things the build refuses to ship.

A site isn't published because someone clicked a button. It's published because it passed. These checks run on every build of every site, and a failure stops the build before a single file is written.

  • Unreadable colour. Every text and background pairing is measured against WCAG AA. Below the line, it fails.
  • Placeholder details. A made-up phone number, a sample address or a note left for later blocks a live deploy.
  • Missing pieces. A section with no words, an unknown font, a missing file — each names itself and stops the build.