SHT-01Elevation · front door
Most sites end at a contact form and an inbox, which means every lead waits for a person to notice it. Ours end inside the system: the enquiry arrives as a record, with its source attached, on the board the business already works from.
SHT-02Detail A · the handoff
On the system we built for a car brokerage, the public site and the CRM are one deployment. Somebody fills in the form on the marketing site and the lead lands as a record with its source attached, on the same pipeline the brokers already work, no forwarding, no copy-paste, no message sitting unread under a receipt.
SHT-03Detail B · build spec
None of this is exotic. It is the set of things a site has to get right before design is worth arguing about, and the set most cheap builds skip because nobody checks.
The layout is designed at phone width and grown from there, not shrunk down afterwards. On a trade site most of the traffic is somebody standing in the problem, holding a phone, looking for a number to tap.
A title and description written per page rather than generated, canonical URLs so two addresses do not compete with each other, a sitemap the build keeps up to date, structured data describing the business, and images sized so the page is not waiting on them.
Service and city pages for the areas the business actually covers, the same name, address and phone everywhere they appear, and business schema so a search engine is told what this is and where, instead of guessing from the footer.
What the work costs, what happens on the first visit, what a licence number means, which brands are carried. The specifics are the part a competitor cannot copy, and they are also the part an AI summary quotes.
In South Florida a bilingual site is not a nicety. Where a business serves both markets, the site is built to serve both, with the language switch on every route rather than a single translated page.
Your domain, your repository, your analytics. If you stop working with us nothing switches off, and the next developer inherits a normal codebase rather than a proprietary builder.
SHT-04Assembly sequence
The date is only honest if the scope is. Everything is priced and written down before the first line of code, and anything added later is re-quoted rather than quietly absorbed into the same deadline.
Step 1
A look at where the enquiries actually leak: the form nobody answers, the page that loads slowly on a phone, the number that is not tappable.
Step 2
Structure, copy skeleton, and the lead flow agreed in writing. This is the step where changes are cheap, so it is the step that gets the arguing.
Step 3
Built and reviewed on a live preview link, on a real phone, not in a slide deck. You click the thing rather than approve a picture of it.
Step 4
Domain, analytics, search console, sitemap submitted, and the lead route tested by actually submitting the form and watching where it lands.
SHT-05Index · by trade
Each of these is a page about what the site has to do for that trade specifically, what the visitor is looking for, and what the owner needs to happen when they find it.
SHT-06General notes
SHT-08Issued for construction
A short video walkthrough of where your lead flow leaks and what it would take to close it. Free, and there is no call afterwards unless you want one.
Get my free audit →
