I’ve built or overseen the build of more than 600 websites in 16 years. Most of them solved problems we’d already solved.
Hero sections. Testimonial layouts. Service grids. Conversion patterns that work because they’ve worked everywhere. We rebuilt all of it, project after project, like we’d never seen any of it before. When I finally stepped back and looked at what we’d been doing, the truth was uncomfortable. We weren’t selling custom websites. We were selling expensive reinvention.
The realization that took years
There was no single moment where it clicked. The pattern was easy to miss because it was always there.
We’d finish a project, feel proud of it, and start the next one as if we were beginning from zero. New components. New templates. New ways of solving the same problems we’d just solved. Every kickoff felt familiar. Every build felt hard. Every postmortem listed the same issues. After hundreds of projects, that consistency stopped looking like coincidence and started looking like a system that produced it.
The thing that finally got my attention was noticing that every project felt hard, even when the goals were familiar. That told me the problem wasn’t the clients, the briefs, or the team. It was the system we used to do the work.
Three teams solving the same problem three different times
For most of those years, our workflow was fragmented in a way I’d struggle to defend now.
Strategy happened in one place. UX prototyped in a different tool, often building net-new components from scratch. Design rebuilt those ideas in Figma with another layer of custom decisions on top. Then development rebuilt the whole thing again in code.
Three teams. Three tools. Three rounds of decisions about the same hero section.
The embarrassing part is that this was considered normal. It was professional. It was the process. I sold it as craftsmanship. I told myself that reinventing every project was what separated us from agencies producing template work. What I was actually doing was burning my team’s time on predictable problems and leaving less energy for the parts of the work that actually mattered.
By the time a project reached the parts that genuinely needed creative judgment, the team was already half-spent on rebuilds. The strategic work, the moments specific to the client, the things that should have gotten our best thinking: those got the energy we had left after recreating the same patterns we’d built two hundred times before.
Why discipline doesn’t fix this
Before I ever thought about standardizing the build itself, I tried to fix the problem with discipline.
We wrote process documents, SOPs, onboarding guides, naming conventions. We added kickoff meetings and design reviews and approval gates. We hired better project managers and gave them more authority. We ran retrospectives and updated the docs based on what we learned. Some of it helped around the edges. None of it touched the core problem.
You can’t out-manage a broken production model.
If every project still requires rebuilding common patterns from scratch, no amount of project management saves your margins or your timelines. Better handoffs make the rebuild smoother. They don’t eliminate the rebuild. The fix isn’t tighter discipline around an inefficient process. It’s changing what the process produces at each step.
That was the lesson that eventually moved us from standardization through oversight to standardization through systems.
What standardization actually is
Standardization is not the opposite of craft, not making every site look the same, and not removing creative judgment from the team.
It’s removing the cost of rebuilding the parts that should never have been custom in the first place. The hero section that is structurally identical to 200 other hero sections doesn’t need a creative direction meeting. The grid system doesn’t need to be re-derived for every project. The button styles, the type scale, the spacing presets are not where the value lives, and treating them like they are is what was eating our margins.
What does need creative judgment is everything else. The strategy. The design decisions that are specific to this client. The custom moments that make the project feel like it was made for them. Standardization is what frees a team to do that work, by removing the cost of doing the work that nobody should have been doing manually anyway.
What most agencies protect, and what they should
Most agencies protect the wrong thing.
They protect custom code, bespoke workflows, and the idea that every project should be handcrafted from scratch. They mistake the inefficiency for the value, because the inefficiency is what they’ve always done and what their team is built around. I made the same mistake for years.
Clients don’t care about any of it. They care that the site looks great, performs well, ranks in search, converts visitors, and can evolve without becoming an expensive headache. They have never once asked us how many of the components were built fresh for them. The agencies still selling reinvention as a virtue are selling something the market stopped paying for.
If your secret sauce depends on repeating manual work nobody values, it isn’t an asset, but an overhead.
The future belongs to agencies that standardize production and customize strategy. The standardized layer is what makes the customized layer profitable. Without the system underneath, the strategic work gets squeezed into whatever time is left after the rebuilds. With it, the strategic work is what the team actually spends its time on.
What 600 sites taught me
The lesson took longer than it should have, and most of it was hidden in plain sight.
We systematized the parts that were predictably the same, so we could spend more time on the parts that were uniquely valuable. That sentence is the entire argument. It also happens to be the answer to most of what slowed us down for the first decade of running an agency.
If you’re running production right now and recognize the pattern in any of this, the work isn’t to write better process docs. Audit what your team rebuilds every month. The bottleneck usually isn’t talent or effort. It’s repetition dressed up as craftsmanship.
