Why a platform
Every small-business site needs the same hard parts: booking, forms that stop spam without stopping customers, analytics, search markup, and servers that stay patched. Rebuilding those per client is slow and makes every site a little different in the ways that break.
So I built them once. Each site is its own project, but they share conventions, server configuration, and a set of packages that get fixed in one place.
The parts
A booking package with an admin panel, calendar sync, reminders, and email confirmations, distributed from a private package registry so every site gets the same fixes.
Client Hub, a customer-intelligence service with its own API and generated client libraries. It collects form submissions and bookings from multiple sites into one database, along with the context of where each lead came from.
Hardened server configuration: firewalls, intrusion blocking tied to the contact forms' spam log, automatic security updates, and deploys that can't take a site down for long.
What it looks like in practice
I built one small business's site to work as a front desk rather than a brochure. Customers could browse a product catalog before calling and book a consultation online. A gallery and reviews synced from the business's Google profile, and the contact form's layered spam filtering fed leads into Client Hub.
Then I moved that business's calls and messaging. Its customers needed to text photos of what they wanted, so picture messages were essential, not a nice-to-have. A phone plan comparison won't show you that.