Work

Problem. What we discovered. What we built. Result.

Every project answers the same four questions. Some clients are named, with permission. Others are described without identifying details until they launch.

Branded Detailing KC, the website we built
Branded Detailing KC, the previous website
Drag the line, or focus the handle and use the arrow keys. Left: the site they had. Right: the site we built.

Before: the site captured at cutover. After: the live production site. Both taken by the go-live engine.

Branded Detailing KC case study

Flagship · Auto and boat detailing, Kansas City

Branded Detailing KC

A Wix site, a third-party booking system, Google Workspace email, and a business that lives on its phone. Everything had to keep working through the switch.

Problem

The old site was slow on phones, the pricing on it had drifted from the booking system, and the owner wanted to move to a site he owns without any risk to the inbox customers use to reach him.

What we discovered

  • Prices on the site were behind the booking system on every ceramic-coating tier, so the site was quoting the wrong numbers.
  • Reviews (4.9 stars, dozens of them) were buried; the first thing a visitor saw was a stock-style hero.
  • Domain registrar and DNS host were different companies, which matters for a safe cutover and is easy to get wrong.
  • No SPF or DMARC records on the email domain.

What we built

  • Hand-built multi-page site produced by Site Forge: services, ceramic coating, paint correction, boats, tint, PPF, FAQ, contact.
  • Image pipeline (AVIF and WebP with correct dimensions), self-hosted fonts, security and caching headers, branded 404, sticky mobile call and book bar.
  • FAQPage, Service and Offer, and Breadcrumb structured data; a review funnel tied to the verified Google listing; Web Vitals measured from real visitors.
  • Go-live through the engine: DNS replicated, MX and DKIM copied, SPF and DMARC added, parity gate passed, nameservers switched.
  • Afterwards: a 3D tint and paint-protection visualizer.

Result

  • Live on the client's own domain since July 2026, on hosting he owns, with the demo subdomain retired.
  • Email never went down. The parity gate checked MX, SPF, and DKIM before the switch.
  • Pages roughly three quarters lighter after the image pipeline, measured before and after the polish pass.
  • Ongoing edits by text: reviews refreshed, new services and photos added, pricing kept in sync with the booking system.
Visit brandeddetailingkc.com

Rebuild and launch · Front Range, Colorado

A handyman company whose old developer kept the domain

Problem

A veteran-owned handyman company wanted a new site, but the previous developer controlled the domain and the email that ran on it, and would not hand either over.

What we discovered

  • With the old domain out of reach, no redirect was possible: the new domain would start with zero search history, and any mailbox on the old domain could be cut off at will.
  • The old site's copy had been written by the prior agency, so the rebuild had to be written fresh rather than carried over.
  • The strongest asset the owner did control was the Google Business Profile, which drives most local ranking.

What we built

  • A 21-page site plus a service-area layer: fourteen city pages written with real local substance (housing stock, weather, permitting) rather than the same paragraph with a city swapped, which search engines demote.
  • Fresh copy measured against the original for overlap (longest shared run: eleven words, all factual).
  • Forms wired to our handler, structured data with the full service area, sitemap, and a validation script that fails on dead links, duplicate titles, or leftover gate markup.
  • A cutover script that rewrites every absolute URL and opens indexing only when run with an explicit confirm flag.

Result

  • Live on a new domain the client owns, served through Cloudflare, with forms delivering and indexing open.
  • A documented evidence file for the domain dispute, gathered alongside the build.

Anonymized at the client's request pending their public announcement.

In progress · 42-page site, proofed line by line

A family-law firm, Denver metro

Problem

A firm with strict rules about what can and cannot be said needed a large site where every sentence could be traced, reviewed by the partners, and reverted if necessary.

What we discovered

  • The firm's mail runs on Microsoft 365 with a DMARC policy already enforced; DNS sat with the previous agency, so launch had to be staged without touching mail.
  • Copy review is the bottleneck, not design: hundreds of individual edits across three rounds.

What we built

  • A build system that generates all 42 pages from structured content, with a launch mode and a switch to hold back the community guides for a later drip release.
  • A proof ledger: every edit recorded with its selector, the original text, and the replacement, so any change can be reverted individually. 308 rows across three rounds.
  • A staged Cloudflare zone with the firm's mail records copied exactly and web records pointed at the new site, waiting on a single nameserver change.
  • Contact form and fee calculators routed to both partners through our forms handler.

Result

  • Every approved edit is live on the review site; nothing is waiting on us.
  • Launch is one nameserver change away, with mail continuity verified in advance.

Anonymized until the firm launches publicly.

Software we have shipped

We don't just recommend technology. We build it.

Platforms and products built to solve operational problems we identified ourselves, running in production.

Behind you.

Your project, answered the same four ways.

Tell us the problem. We will tell you what we would discover, what we would build, and what result to expect, in writing, before you spend a dollar.

Book a 30-minute callText (816) 237-0141

Or start with the free website report card. A real person answers either way, usually the founder.