Template or custom? It's usually the first question a business asks once its current setup starts creaking. Our honest view, which annoys developers and founders about equally: templates are fine for far more businesses than most agencies will admit, and custom becomes necessary much sooner than most owners expect. Which side you fall on comes down to one thing. How unusual is your workflow?
When a template is the right answer
If what you need is common, a template built for that need is a very good place to start. Restaurant site with a menu. Standard online store. Portfolio. A landing page for a CA firm or a clinic. Thousands of businesses want the same things, so a lot of people have put a lot of work into making those templates good.
Using one isn't settling. It's the sensible engineering call, because you get work that's already been built, tested and debugged by someone else. Where people go wrong is treating it as "temporary until we can afford custom." If the template fits how you work, it can carry you for years. We've told clients exactly that and turned down the project.
When the template becomes a liability
Trouble starts when your workflow drifts away from what the template was designed for. It rarely happens in one go:
- You add a plugin for something the template can't do. Then a plugin to fix the plugin. Then two of them clash after an update and checkout breaks on a Saturday.
- You need data to move between the website, your operations system and your reports. Wiring them together becomes its own project, and it never quite stays fixed.
- Your team builds habits around what the tool can't do instead of what the business needs. Nobody notices the workarounds anymore. They're still costing you.
An outgrown template never shows up as one big invoice. It shows up in lost hours, short tempers, and the ideas you quietly stop pursuing.
The inflection point
Most growing businesses hit a point where the template costs more, in upkeep, workarounds and missing capability, than building it properly would. You rarely spot that moment while you're in it. It's obvious in hindsight.
Here's the tell. If your team keeps saying "the system doesn't support that" about things that are central to how you operate, you've already passed it.
A practical test
Answer these three honestly before you decide anything:
- Can you run your three most important workflows in the template without a workaround?
- If you doubled in size tomorrow, would it hold? Or would the small cracks turn into proper fractures?
- Is the template limiting what you can offer customers, or only how it looks?
If any answer makes you wince, it's worth at least finding out what custom would involve. Finding out costs nothing.
We'll give you a straight opinion on whether you need custom web development or custom software, and if you don't, what you could do with what you already have. Ask us.