The Setup
I needed a real site. Not a Squarespace template with a stock photo and three paragraphs about “marketing strategy.” Something that read like a senior consultant wrote it. A free PDF good enough that other consultants would actually link to it. An interactive calculator a founder could run on their own account. And the voice across every page had to sound like one person, not like a marketing team trying to sound like one person.
24 hours. Solo. With the right tooling on the keyboard and voice input replacing the typing bottleneck.
Not 24 hours of agency project management with weekly check-ins. 24 hours of actual hands on the keyboard. Diagnose, scope, ship, audit, deploy. Same day.
The fix was the input layer. Typing at 60 words per minute is the bottleneck nobody talks about. Speaking at 150-plus words per minute and letting the tooling do the actual keyboard work changes the math. You stop being the typist and start being the director.
What I Built
The site itself. Astro + Tailwind v4 + MDX, deployed to Cloudflare Pages with a single push. The full page count covered home, about, services, /audit landing, /calculator, /for-home-brands (vertical specialty page), /process, /tools index, /faq, /newsletter, /contact, /blog and /results. All on the same design system. All in the same voice.
A 25 page editorial PDF. “The Google Ads Setup Checklist,” available at /audit. Designed to look like a Stripe Press book, not a marketing freebie. Custom build pipeline: HTML source rendered to PDF via headless Chrome, then PyMuPDF overlays interactive form fields on the calculator page. Anchor markers in the HTML let the script find positions for the form widgets, then strip themselves out so they don’t leak into PDF text extraction or screen readers. The whole thing rebuilds with npm run build:pdf.
A live wasted spend calculator at /calculator, since retired (October 2026) in favor of the free written audit. The same worksheet that lives on PDF page 17, but rendered as a real form with auto calculating outputs. QR code in the PDF links here so anyone reading the PDF on a phone can run the math without retyping.
A LinkedIn cover, freebie launch image, and full LinkedIn profile rewrite. Cover and audit launch image both rendered with a HTML and Chrome headless screenshot pipeline, not image generation. Typography is real Fraunces variable, real italic axis, exact 1584 by 396 dimensions. Profile headline, About section, experience entries, skills, services list, and Featured pins all rewritten to match the new positioning.
The Operator Method, Applied to Me
The same engagement pattern I run with clients: diagnose, scope, ship, compound. For my own site:
Diagnose. Reviewed the existing freebie PDF, the old site copy, and what other senior solo consultants in the space were doing. Mapped the gaps. Picked an editorial publication aesthetic over the SaaS template aesthetic everyone else uses.
Scope. Locked the brand system. Three colors only: ink, paper, and a single oxblood accent. Three fonts: Fraunces serif for display, Inter for body, JetBrains Mono for technical labels. Italic emphasis renders in oxblood as the brand signature. Wrote it down. Stuck to it.
Ship. Built page by page. The harder pieces (the PDF pipeline and the calculator interactivity) got their own dedicated build sessions. Every page committed and deployed the same day it was written.
Compound. Ran a parallel voice audit at the end. Eight passes, one per major content surface, each handed the brand canon and a tells checklist. The reports flagged every passage that read as machine written. I pulled the highest impact rewrites into one pass and shipped them, 14 files, one commit.
What Surprised Me
The voice audit pattern works. I knew some patterns had crept in during the build. What I didn’t realize was how concentrated they were. Decorative triplets, “not just X but Y” constructions, and adjective stacks topped the list of what the agents flagged. Em dashes had snuck back into the tracking stack page. None of it would have been visible to me on a re-read because I wrote it. The agents read it cold.
HTML beats image generation for typography. I tried a hosted image model for the LinkedIn cover three times. It dropped a dollar sign and a digit from “$11,250” the first time. It misplaced the avatar safe zone the second time. It hit the monthly spending cap before I could iterate further. The fix was to write a small HTML file at exact LinkedIn dimensions, load Fraunces from Google Fonts, and screenshot it with Chrome headless. Same result, free, exact, and reusable. Image generation is for photographic assets, not for typography-heavy posters with brand fonts.
Free PDFs without an email gate work better than gated ones. Gated downloads tend to convert worse, and the email captures from a free PDF are mostly junk. A founder who downloads, reads the PDF, and sends read-only access for the free written audit is a far stronger lead than someone who traded an email for a download. The PDF itself is the email sequence. Page 23 is the conversion event. Pixels do the retargeting work an email list would normally do.
The Stack
- Voice input as the bandwidth multiplier. Speaking intent at conversational speed and letting the tooling do the typing is what made the 24 hour timeline possible.
- A coding assistant on the keyboard, with parallel dispatch for research-heavy passes (competitor research, freebie patterns, positioning) and voice audits (one pass per page).
- Astro 5 for the site, static output, deployed to Cloudflare Pages.
- Tailwind v4 for the design system, custom tokens for colors and type scale.
- MDX for blog posts and case studies.
- Keystatic in dev only for content editing UI.
- PyMuPDF for PDF form field overlay.
- Headless Chrome for HTML to PDF and HTML to PNG rendering (used for the 25 page checklist, the LinkedIn cover, the freebie launch image).
- GTM + GA4 for the analytics layer.
- Calendly + Web3Forms for booking and form handling.
What This Means For Anyone Reading
You can build the senior consultant version of your site, with real custom artifacts, in a day. Not a Squarespace template. Not a $30K agency rebuild that takes 12 weeks. A real site, with a real PDF, with a real voice, in the time most agencies take to send back the kickoff deck.
The same play built a client storefront: Emma Grace Home, 150+ products on Shopify, live in under a month.
The hard parts are the brand voice and the structural decisions, both of which are yours to make. The execution work, the pages, the PDF pipeline, the voice audit, all of that is now operator level work that one person can ship in a day with the right tools.
The sites that read as senior in 2026 are the ones built with the operator’s voice on top and tooling underneath. Not the other way around. The hours that used to go into pixel pushing and copy iteration now go into the decisions only the founder can make.
The whole engagement is documented on the /process page. If you want me to look at your Google Ads account, start with the free written audit: you send read-only access and get it back within 24 hours.
