When I started building sites for local businesses, the shape of every project was the same. Same page structure, same contact form wiring, same analytics setup, same favicon generation, same deployment steps. Only the content and the trade were different.
I was spending the first two or three days of every engagement doing work I had already done, which meant the client waited days to see anything real. That is the worst part of a project to be slow at, because it is the part where they are deciding whether they trust you.
The problem was never the typing
It would be easy to describe this as “I automated the boring parts,” but that undersells what was actually wrong.
The real cost was that repetitive setup crowded out the conversation. By the time I had a site skeleton standing up, I had spent my energy on boilerplate instead of on the questions that decide whether a site works: who is actually calling this business, what do they need to see before they trust it, and what is the one action the site should push them toward.
A roofer and a wedding-dress shop need very different homepages. But I was arriving at that conversation tired.
What I built
I wrote down the entire repeatable part of a build as a set of instructions my tooling can follow — the folder structure, the page skeleton, the form wiring, the analytics snippet, the favicon set, the deployment config. All the decisions that are the same every time, captured once.
Now the mechanical layer of a new project stands up in minutes rather than days. What used to be a two-day setup is an afternoon, and most of that afternoon is spent on content and photos.
You do not need to be technical to apply the idea. Any task you do the same way more than three times is a candidate. Write down the steps once, precisely enough that someone else could follow them, and you have converted a recurring cost into a one-time one.
What changed for clients
Three things, and only one of them is speed.
They see something real on day one. Instead of describing what their site will look like, I show them a working draft with their business name on it. Reactions to a real page are far more useful than reactions to a description. People who cannot tell you what they want can immediately tell you what is wrong with what is in front of them.
Changes stop feeling expensive. When the structure is generated rather than hand-assembled, moving a section or restructuring a page is not a painful rebuild. That means I stop defending decisions just because they were slow to make, which is a trap I have watched plenty of agencies fall into.
More of the budget goes to thinking. The hours that used to disappear into setup now go into the parts that actually change outcomes — what the page says, what order it says it in, and what happens when somebody wants to get in touch.
The handoff matters more than the speed
The part I care about most is what happens at the end. Because the whole setup is written down rather than living in my head, I can hand it over. A client gets the site, the repo, and the same tooling I used to build it, already configured for their business.
That is the difference between hiring someone and depending on them. If a client wants to change a price, add a service, or update their hours six months from now, they are not waiting on my schedule. I am glad to keep doing it for them — most small business owners would rather run their business than edit a website — but it should be a choice, not a hostage situation.
I have written before about what it looks like when that goes wrong, and it is common enough in this industry that avoiding it is worth designing for.
Where this applies outside web work
If you run a service business, you almost certainly have your own version of this. The quote you rebuild from scratch each time. The onboarding email you rewrite from memory. The job checklist that lives in your head and occasionally drops a step.
None of that requires software to fix. It requires writing the thing down once, properly, and then using what you wrote. The speed is nice. The real win is that it stops being possible to forget a step, and your attention goes to the part of the job only you can do.
If you want to talk through what that would look like for your business, get in touch — it is usually a shorter conversation than people expect.