Swole Labor Services
Day 15 of 30 — a game-day swap, and a different kind of build
Swole Labor Services is a junk-removal business in Fort Myers, Florida — owner-operated by Max Small, who shows up, quotes fair, hauls it, and donates what he can. Today it has a website: swolelaborservices.com, built start-to-finish in a day with the Velocity Process.
Day 15 was on the calendar as the audience-pick “I’ll Build Your Idea” build. That build is being pushed — it now lands after Monday’s TIE Connect TC1 napkin-submission raffle, so the submissions can run through the event instead of closing in a 48-hour window. Day 15 needed a build off the bench, the way Day 3 swapped PartFoundry in when the primary wasn’t ready. Swole Labor Services is that build.
It is also, deliberately, a different kind of Day. Most of the run is Silverback ventures — products with a business model, a co-founder seat, a market thesis. This is a client services build: a free site for a real, named local operator, hosted on the cohort-tenant model. Day 11’s ChamberAdvance and Day 12’s PlanCheck were client builds too — but those are SaaS platforms. This is the smallest, most ordinary version of the question the whole month is asking: what can one person plus an AI coding agent plus thirty years of CTO judgement do in a day? The answer today is: give a one-truck business the web presence a national franchise has, without the franchise.
What shipped
A complete, fast, mobile-first marketing site — 18 statically-rendered pages, built on Astro 5 and deployed on AWS.
The pages. A home page that leads with the flyer’s own promise — “We Don’t Cut Corners. We Clear Them.” — and the truck, the services, how it works, and the service area. Five service detail pages (junk removal, garage & storage cleanouts, yard cleanouts, furniture removal, donation pickup), each with what-we-take / what-we-don’t and upfront pricing guidance. Five Lee County area landing pages — Fort Myers, Cape Coral, Lehigh Acres, Bonita Springs, Estero — each tuned for the local search a homeowner actually types. An about page, a quote page, a thanks page.
Mobile-first, because the traffic is. Junk-removal search is overwhelmingly mobile and high-intent — someone standing in their garage deciding to deal with it today. Every page is built and tested at phone width, and a fixed bottom bar follows the visitor down the page with one-tap Call, one-tap Text, and Get a Quote. The tap-to-call and tap-to-text links go straight to Max’s phone.
Built to be read by a model. The same architectural posture silverbackcto.com has run since Day 1, applied to a local-services site: LocalBusiness JSON-LD on every page with the full service catalog and area-served list, an llms.txt written in the business’s own voice, a robots.txt that explicitly welcomes every major AI crawler, and an auto-generated sitemap. When someone asks an assistant “who does honest junk removal in Fort Myers,” the answer is assembled from pages — and these pages are legible to the thing doing the assembling.
Lead capture, v1. The fastest path to a quote for a solo operator is the one his flyer already names: text a photo. So that is what the site leads with — prominent text-photos and call CTAs everywhere, a thanks page wired for a conversion event. The quote page is also built to upgrade itself: it detects when the client’s CRM intake form and Calendly booking link are connected and swaps them in automatically, with an honest “coming online” panel until they are. No dead buttons, no form that posts into a void — the site is truthful about exactly what is live today and what arrives this week.
Three choices that made this a one-day build
Scope to the operator, not the spec. The original technical design called for a full photo-upload form on a custom AWS backend — API Gateway, Lambda, SES, presigned S3 uploads. For a one-truck business taking its first jobs off a website, that is the wrong v1: it is more backend than the lead volume justifies, and it delays launch for infrastructure the business does not need yet. The shipped build inverts it — text-first lead capture now, with the form and booking embed built to drop in the moment Max’s CRM and Calendly accounts are live. The site is useful on day one and grows into the heavier integration when the volume earns it.
Inherit the brand, don’t invent one. Max already has a brand — a printed flyer with the S↕S mascot, a forest-green palette, and four taglines that say exactly who he is. The build’s job was not to design a brand; it was to carry his onto a screen faithfully. The color tokens, the voice, the headline copy, the services list — all lifted from the flyer. The about page literally puts the flyer next to the site and says: same business, same person showing up, same fair price.
AWS-native, on the cohort model. The whole thing runs on the standard Velocity Process stack — S3 + CloudFront + ACM + Route53, provisioned by CDK on the VelocityStack base class so the cost tags and the monthly budget alarm are enforced, not optional. It deploys on a GitHub Actions OIDC pipeline with no long-lived keys. Hosting runs about $5–$15/month, Silverback carries it on the cohort tenant, and the domain transfers to Max whenever he wants it. A static site is the right tool here — it is fast, it is cheap, it is durable, and there is nothing to patch.
Why this build belongs in the run
The 30-day run is a proof about speed — but speed at the venture scale can read as a stunt if it never touches the ordinary. Swole Labor Services is the ordinary case, and it is the one most small businesses actually live in: a person who is good at the work, underserved by the tools, and quoted franchise prices for a website that should cost a fraction of that and ship in a day.
That is the whole argument. The same process that produced a multi-tenant civic-permitting platform on Day 12 produces a fast, honest, discoverable site for a one-truck junk hauler on Day 15 — and the second one matters because there are far more Max Smalls than there are county governments. AI-native delivery does not only change what venture-scale software costs. It changes what a real local business can have.
The Velocity Process notes
What Claude Code handled: the entire Astro 5 site — 18 routes including the dynamic service and area page templates, the shared Base layout with the JSON-LD / OpenGraph / meta wiring, the component library (hero, mobile sticky bar, service and review cards, trust strip, CTA bands, nav, footer), the LocalBusiness / Service / breadcrumb schema builders, the Tailwind theme tokens carried over from the flyer, the llms.txt and robots.txt, and the CDK SiteStack — S3 with origin-access-control, CloudFront with the directory-index rewrite function, ACM, Route53, and the VelocityStack tag-and-budget base class — plus the GitHub Actions OIDC deploy pipeline.
What required human judgement: the scope-down decision — cutting the custom photo-upload backend out of v1 and shipping text-first lead capture instead. That is not a technical call; it is a read on what a solo operator’s first website actually needs, and it is the difference between launching today and launching in three weeks. And the brand-inheritance discipline — the instinct of a coding agent is to design; the right move with a real client who already has a flyer is to carry his identity over faithfully and add nothing. Both calls came from knowing the client, not from the spec.
What broke — and what the readiness pass caught: this build is the second case in the run, after GEOPress on Day 14, where the readiness audit caught the same specific failure — placeholder content presented as real. The site shipped with six fabricated five-star customer reviews, named and attributed to Google and Facebook, with the reviews page calling them “verified.” They were pulled before launch. The entire 30-day run is built on real proof and real, named people — Jim Hasty, James Liebman, Dave McMullen, and here, Max Small — and a fabricated review on a real client’s site is exactly the kind of credibility break the readiness pass exists to stop. The honest version is the one that shipped: the reviews page asks Max’s real, recent customers to be the first to leave one.
What I’d do differently: treat “placeholder content” as a launch blocker by default, not a thing to remember to swap. Twice now in two days the same class of problem — invented testimonials — made it into a finished build and had to be caught at T-1. The lesson is a process one: placeholder layout is fine, placeholder claims are not, and the build should never generate a fabricated named human, a fake review, or a false badge even as a stand-in. It is easier to never write it than to remember to remove it.
What’s next
- Day 15 (today): the site is live at swolelaborservices.com; the Notion card moves from Business Plan to Coded on the first confirmed CloudFront deploy.
- This week: wire the client’s accounts as they come in — the GHL intake form, the Calendly booking link, the GA4 measurement ID — each of which the site already detects and upgrades into with no code change. Get Max’s sign-off on the published price ranges, and collect the first real reviews from recent happy customers.
- Monday, May 18: TIE Connect TC1 — the napkin-submission raffle that the audience-pick “I’ll Build Your Idea” build now follows. Enter at silverbackcto.com/launch.
Want to talk
If you run a small local business — one truck, one chair, one crew — and you have been quoted franchise money for a website, this is the counter-example: a fast, discoverable, AWS-hosted site built in a day. The Velocity Process cohort exists for exactly this. Email todd@silverbackcto.com or book through Calendar.
And if you are in Fort Myers or anywhere in Lee County and you have a garage, a yard, or a storage unit that needs to be cleared — that is what Max actually does. swolelaborservices.com.
Swole Labor Services is built with the Velocity Process. Live today at swolelaborservices.com.