A developer who builds sites for small-business clients posted the dilemma plainly: keep it simple — a fast site with contact info and a service list — or build in the features that feel more complete, booking, customer accounts, a dashboard, a few integrations. The replies split the way most agency conversations do. A handful of owners wanted the full system. Most just wanted the phone to ring.
That split is the actual answer. Not every business needs the same site, and the features that feel like an upgrade often aren't one.
What every small-business site needs, full stop
Three things, in order. What you do, and roughly what it costs — even a range beats nothing, because "call for pricing" usually reads as "we're more expensive than we want to admit." Proof you're good at it: real project photos, real client names where you have permission, reviews you didn't write yourself. And one obvious way to reach you, not four competing ones. A phone number, a contact form, and a booking widget all fighting for attention on the same page means most visitors pick none of them.
No login. No dashboard. Nothing that needs a password reset flow. A five-figure custom build and a five-page marketing site solve the same problem for most small businesses: someone lands on the page, understands what you do in ten seconds, and knows exactly what to click next.
Do you need online booking?
Only if you're already booking constantly by phone. That's the actual test — not whether booking sounds modern, but whether phone tag is already costing you real time. A salon fielding twenty calls a day for appointments has a problem software solves. A contractor who gets three inquiries a week and prices every job after a site visit doesn't; a booking link there just hands strangers a slot to fill before you've seen the work.
The middle case is more common than either extreme. A dentist's office might take fifteen booking calls a week, which sounds like plenty of volume, but half of those calls are also insurance questions or reschedules a booking widget can't handle anyway. There, the right build is a booking link for new-patient exams — the repetitive, low-context call — and a phone number that stays front and center for everything else.
The feature only pays for itself if it replaces something you're already doing by hand, a lot.
Do you need customer accounts or a dashboard?
Almost never, and this is the one that keeps showing up as "we should probably have that." A login system means password resets, a security surface you now own, and a customer who has to remember one more set of credentials for a business they might use twice a year. Most people won't log in twice. They'll just email you instead, which is the thing the account was supposed to replace.
We broke down what a website actually costs a couple months back: a well-scoped marketing site runs roughly 48 to 52 hours at our shop, at somewhere around $95 to $100 an hour. A blog add-on alone is another 8 to 12 hours on top of that. A real account system with a dashboard isn't an add-on at that scale — it's a different project, closer to $12K-and-up territory, with its own maintenance bill every time a dependency needs a security patch. Price it like a marketing-site extra and you get surprised twice: once by the invoice, once by how few customers ever log back in.
Where integrations actually earn their spot
The exception is anything that removes a manual step you're already doing between two systems — a form that writes straight into your CRM instead of you copy-pasting from an inbox, a payment link instead of chasing an invoice by text, an automated reminder instead of a sticky note on the monitor. That's less a website feature than a small piece of automation sitting behind the site, and it earns its place the moment you can name the exact manual task it replaces. We cover this same scoping question from the build side in full-service vs. piecemeal builds. If you can't name the task, you're building the feature because it exists, not because you need it.
The gut check before you build anything
Three questions, in order. What does this replace that you're doing by hand right now? How often does that actually happen — daily, weekly, or once a quarter? And what happens if you just don't build it, and answer that need by hand for another six months? If the third answer is "nothing bad," the feature can wait. Most small-business sites are better off shipping the simple version first and adding exactly one thing once it's obviously earned its keep.
If you're not sure which side of that line you're on, that's a fifteen-minute conversation, not a guess. Tell us what the site needs to do and we'll tell you honestly whether it's a marketing site, a booking site, or something bigger.
Sources
- r/smallbusiness, "How do small businesses decide what features they actually need?": reddit.com/r/smallbusiness/comments/1wgyw7p
- Genesis Web Digital, "The math on a $5K website": genesisweb.org/blog/the-math-on-a-5k-website
— Cole