Most small businesses don’t need a developer. A good website builder will carry you further than anyone selling custom work wants to admit, and that includes me. You need a developer when your website has to do something the builder can’t be bent into doing. The whole skill is knowing which side of that line you’re standing on, and most people guess wrong in both directions.
What do website builders actually do well?
More than they get credit for. Squarespace, Shopify, Wix, WordPress, the newer AI-assisted builders, they’ve all gotten genuinely good. If what you need is a fast, clean site that shows who you are, lists what you do, puts your hours and photos up, and gives someone a way to reach you or buy a few things, a builder does all of that well, cheaply, this week.
A lot of businesses in Sault Ste. Marie live right here and should stay here. The contractor who needs a credible page and a phone number. The shop that wants twenty products online by Friday. The studio that needs to look like it knows what it’s doing. Paying a developer to hand-build any of that is paying for a tailor to sew you a t-shirt. It’ll fit, and it’ll cost you ten times what the rack does for a difference nobody will ever notice.
So the honest starting point is this: assume you don’t need me. Most of the time it’s true.
So when do you actually need a developer?
When the site has to do something specific to your business that the builder has no setting for.
Notice that’s not about how it looks. Builders look great now; that argument’s over. It’s about what happens when someone uses the thing. The moment your site needs to think, calculate a number, connect two systems that don’t speak to each other, follow a rule that’s yours and nobody else’s, you’ve walked past what a kit includes.
A few that come up around here:
- A real shipping price pulled live from the carrier at checkout, not a flat guess that loses you money on the heavy orders.
- Your bookings, your inventory, and your accounting staying in sync without you retyping the same thing into three places.
- A quote tool that asks five questions and gives a customer a real number instead of “call us.”
- Pricing or availability that changes on rules only you know, by season, by job type, by who’s asking.
None of those are page problems. They’re behaviour problems. That’s the tell.
Where do templates quietly fail?
Builders rarely fail loudly. They fail at the edges, on the one thing you assumed would just work. Four spots where it happens:
- Anything with custom logic. The second your site needs an “if this, then that” the builder didn’t ship with, you’re stuck. There’s no plugin for the way your business actually works.
- Connecting systems. Two tools that each work fine alone but need to hand information back and forth cleanly. That handoff is where templates run out of road and where a lot of quiet, expensive manual work hides.
- The unusual-but-real case. This is the big one. A store can look flawless and still quote the wrong shipping price, or none at all, the moment an order doesn’t match the simple case the template planned for. I spend a real chunk of my time on exactly that part of a build, the bit that only surfaces when a live customer does something slightly off-script. It’s invisible in a demo and very visible in a refund.
- Performance and control once it counts. When a site gets heavy or busy enough that speed and reliability turn into money, you eventually want to own how the thing is built, not hope the platform agrees with you.
How do you tell which side you’re on?
Listen to how you describe what you want. The words give it away.
If you’re describing a brochure, who you are, what you do, how to reach you, that’s a template, and a developer would only charge you more for the same result.
If you keep catching yourself saying things like:
- “I need it to automatically…”
- “It has to connect to our…”
- “When a customer does X, it should do Y.”
- “Nobody else does it the way we do.”
…that’s developer work, and a template will fight you the whole way.
Any two of those sentences coming out of your mouth and you’ve found the line. You’re not asking for a nicer page. You’re asking for a behaviour.
What’s the honest cost difference?
A template build runs from a few hundred to a few thousand dollars and you can be live this month. Custom is a different number and a longer timeline, and it’s only worth it when the custom thing earns or saves you real money: more orders, fewer hours of retyping, a checkout that stops leaking sales you never knew you were losing. (I broke the tiers down properly in what a small business website should actually cost.)
Pay for custom you won’t actually use and you’ve just bought a more expensive template. That’s the mistake on the other side of the line, and it’s just as common as under-building.
What I tell people in the Soo
Start with the builder. I mean that. Most businesses should launch on a template, get found, make some money, and only call someone like me when a specific need turns up that the platform genuinely can’t reach. And you’ll know when you hit it, because you’ll be describing something the site has to do, not something it has to say.
Sometimes the right answer is “you don’t need me yet.” That’s a real answer, and I’d rather give it than sell you a custom build you’ll spend half of. The good news is the jump is rarely all-or-nothing. Plenty of businesses run a perfectly good template for the front of the house and bring in custom work for the one part that has to be theirs, the checkout, the booking flow, the tool that does the thing nobody else does. Right tool, right job.
The line isn’t about budget or ambition. It’s one question: does your website need to do something, or just say something? Answer that honestly and you’ll almost always know who to call, including when the answer is nobody, yet.
Bunker41 is a one-person studio in Sault Ste. Marie, Ontario building custom websites and web apps for small businesses, usually for the part of the job a template can’t reach. If you’ve hit that line, say hello.