Service Business Website + CRM: A Repeatable AI Build
Website and CRM lead pipeline for a trades service business — built with AI-augmented harness engineering. Discovery to live in days, near-zero ongoing platform cost.
The Problem
Most residential contractors and service business owners are running their business on a phone number, a referral network, and a Facebook page they update twice a year. When a website exists, it’s often three years out of date and doesn’t have a contact form that actually goes anywhere useful.
The deeper problem isn’t the bad website. It’s what happens to the leads that do come in: a voicemail that doesn’t get returned for two days, a text conversation that never makes it into a quote, a referral that went to a competitor because the callback was slow. For a one- or two-person operation, that leakage is invisible until it isn’t — and by then, a competitor who looks more professional online has the job.
The ask was straightforward: a production website that reflects the quality of the work, connected to a CRM lead pipeline that captures every inbound contact and makes sure nothing falls through.
What I brought to this that most web developers don’t: I’ve run this kind of business for 25 years. I know what the operator actually needs — and I know which software decisions look good in a demo but fail on a real jobsite.
The Workflow
This build used the same harness engineering methodology I apply to enterprise implementations — scaled to fit a single-operator service business.
The methodology works like this:
1. Structured discovery. Before any design or code, I run a scoped discovery session: business goals, services offered, target customer profile, geographic service area, differentiators, preferred tone, how leads currently come in, what happens after they arrive. The discovery output becomes the spec. The spec drives everything downstream.
2. Constrained AI output. With a well-scoped spec in hand, AI generation works within strict boundaries — the model can’t invent scope, add pages that weren’t requested, or drift toward generic filler content. The harness constrains the output to match the discovery. What comes out the other end is usable, not aspirational.
3. Human QA layer. I’m the QA layer. I catch where the model breaks down, enforce consistency, and make judgment calls that require knowing the customer’s world — in this case, the trades. That’s the irreplaceable part.
4. Deployment and handoff. Static site on Cloudflare Pages, Cloudflare Worker handling form submissions, leads routed to a KV pipeline and CRM. The operator gets a production system they can explain to anyone in sixty seconds.
The result is a build cycle measured in days, not the weeks or months a traditional agency engagement takes — and at a fraction of the cost.
What Was Built
Website: Static Astro site deployed on Cloudflare Pages. Zero runtime cost, fast global delivery, mobile-first responsive design. Content organized around the actual services offered, the geographic service area, and the differentiators that make the business worth calling. Local SEO structure built in from the start: NAP consistency, service area markup, structured data for the business entity.
Contact form + lead capture: A contact form connected to a Cloudflare Worker that routes every submission to a KV store and CRM pipeline. No third-party form subscription, no per-submission fees. Every lead is logged, timestamped, and visible in the pipeline.
CRM pipeline: Inbound leads routed to a lightweight CRM view that shows open inquiries, contact information, and follow-up status. The operator sees every lead in one place. Nothing gets buried in an email inbox.
Operational design: The system is designed for a single operator who is on a job site during business hours. Lead capture is automatic. Follow-up is manual — but the operator now has a queue to work from, not a pile of voicemails to sort through.
The Outcome
Time from discovery session to a live production site: days.
Ongoing platform cost: near zero. Cloudflare Pages and Workers have generous free tiers. There’s no monthly SaaS subscription for the website, no per-seat CRM fee, no hosting invoice to manage.
Lead pipeline coverage: every inbound contact through the website is captured, logged, and visible. The operator knows what came in and when. That’s a different operational reality than a phone number alone.
The less obvious outcome: the website looks like the business deserves to win the job. That matters in a market where most competitors have worse-looking sites or none at all. A professional online presence is a closing signal before the first conversation happens.
Why This Is Repeatable
The methodology doesn’t change between a construction business and a landscaping company, a flooring contractor, an HVAC service, or a property management outfit. The discovery questions shift. The service area schema adapts. The CRM fields map to whatever the operator’s follow-up process actually looks like.
What stays constant is the workflow: structured discovery → constrained spec → AI-augmented build → human QA → fast deployment → production system that costs almost nothing to run.
The differentiator I bring to this vertical specifically is that I’m not designing for a buyer persona I’ve researched — I’m designing for an operational reality I’ve lived. I know what the data entry moment actually costs when you’re on a job. I know what “the office” means when there’s no office. I know what a lead pipeline needs to look like for someone who checks it between jobs, not between meetings.
That’s not a standard offering from a web agency. It’s a specific capability from someone who has been on both sides of the software for a long time.
What I’d Do Differently
On the next engagement of this type, I’d bring the CRM schema design into the discovery session earlier — before the form fields are finalized. The first time through, lead field mapping required a second pass after launch when it became clear the operator’s follow-up workflow didn’t match the form structure. That’s a 20-minute fix, but it’s unnecessary friction. Getting the CRM schema right during discovery means the form, the pipeline, and the follow-up process are aligned from day one.
Interested in this for your service business? Get in touch — the first conversation is a scoped discovery discussion, not a sales call.