Services / Build & launch
02Build & launch
Hand-built, fast, and yours
A site nobody can edit and nobody can move is not an asset. It is a subscription with extra steps.
The build is where most of the promises made during design either hold or quietly collapse. A layout that looked fast in a mockup arrives as four megabytes of images. A design that read cleanly turns out to be unusable with a keyboard. Nothing about a good design guarantees a good build.
Static first
Most small-business websites do not need a database. They have a fixed set of pages that change occasionally, and every dynamic feature underneath them is a thing that can break, need patching, or get exploited. We build static-first: HTML and CSS served from a CDN, with JavaScript added only where a page genuinely needs it.
The difference shows up in three places. Pages arrive faster, because there is nothing to compute before the server can answer. There is no software to keep patched, so a site left alone for a year is exactly as secure as the day it launched. And hosting costs almost nothing, which matters if you take the site and run it yourself.
This site is the example nearest to hand. Three of its five pages ship zero JavaScript — not "minimal", none. Its hero image is 102 KB, down from a 1.9 MB source. That is not a trick; it is what happens when someone checks.
Tested where people actually are
Every build is checked on real phones, not just a narrowed browser window, because the two are not the same thing. Touch targets, tap-to-call, the keyboard covering half the form — none of that shows up at a desktop.
Accessibility gets the same treatment. Semantic markup, one heading order that makes sense read aloud, visible focus outlines on everything you can tab to, and motion that respects a visitor's reduced-motion setting. This is not a compliance exercise; it is the same work that makes a site usable in bright sunlight, on an old device, or by someone in a hurry.
Launch is a handover, not a disappearance
At launch you get a recorded walkthrough of how to change copy and images on your own site. If you took the self-managed option, the repository transfers to you and we keep no deploy access — you can hire anyone, or nobody, from that point on.
Every site is built handover-ready by default, because the choice is not made until the project is sold. That constraint has a useful side effect: nothing in the code depends on an account only we can log into.
What you get at launch
The site, live on your domain
DNS configured, HTTPS on, redirects in place, old URLs pointed at new ones.
Search essentials wired up
Sitemap, robots, canonical tags and structured data — submitted, not just present.
Analytics installed and verified
Confirmed receiving real traffic. A tag that was never checked measures nothing.
A recorded walkthrough
Yours to keep and re-watch, so the knowledge does not leave with one employee.
03Boundaries
What we don't do
- No page builders. Fast to start, slow forever after. They ship far more markup than the page needs and leave you unable to change hosts without rebuilding.
- No plugin stacks. Every plugin is a dependency that can break on someone else's release schedule. If a feature can be twenty lines of our code instead, it is.
- No hosting lock-in. Nothing in the build depends on an account only we control. If you leave, the site keeps working.
- No launching without analytics. A site live for a month with no measurement has a month of baseline that cannot be reconstructed afterwards.
04Questions
Asked
about the build
Static-first HTML, CSS and the minimum JavaScript a page actually needs, deployed to a CDN. Pages that need no JavaScript ship none. Where a site needs a framework it gets one, but the default is the simplest thing that does the job.
If you choose the self-managed option, yes — the site and its repository transfer to you at launch and we keep no deploy access. Every site is built handover-ready by default, so the choice is not made for you in advance.
On a CDN host, which serves pages from a location near the visitor rather than from a single server. If you take a care plan we manage it; if you take the site outright, hosting a static site is inexpensive and there is no database to maintain.
You get a recorded walkthrough at handover covering how to change copy and images. Anything larger is a care-plan task or a quoted piece of work, and you are never obliged to come back to us for it.