Problem
The client is a fractional COO. For twenty years he won work through a closed-loop referral network in the Pacific Northwest. That network was aging out. His introducers were retiring, and the two long-term offers on the table both required moving back to Washington, which he didn't want to do from Spain.
He needed a new channel: VC proxy networks. Talent partners and operating partners who route warm intros to portfolio CEOs. That channel converts at 50-80% when the intro is warm, versus 2-10% cold, but it only works if a partner can skim something in 30 seconds and forward it. He had a solid case-study site and nothing built for that job. His marketing was fine. The gap was in how he reached people.
Solution
I proposed building him the credibility surface that channel needs, and I built the proposal itself as that surface.
Instead of a PDF, the proposal was a bilingual interactive site - the same kind of asset Phase 2 of the engagement would produce. If he doubted I could build the thing I was pitching, the thing he was reading answered the question.
Approach
Four days, intro email to live site. Solo, every layer:
- Strategy. Diagnosed the distribution gap and defined a "founder-led to founder-leveraged" positioning. I structured the work in two phases with a decision gate at week three, where he could walk away owing nothing. He'd told me twice he couldn't bet on something that takes two years to pay off, so I capped his risk to a small first phase and three weeks before the larger commitment.
- Research. Built and verified the VC partner target list, cutting three programs that show up on every stale fractional-COO list but had quietly wound down.
- Engineering. Built and shipped the site from scratch in Next.js. Bilingual infrastructure with a real Spanish translation and glossary, not a machine swap. Six interactive sections, including an engagement timeline that doubles as the decision gate. Full test coverage on every interactive piece (Vitest and Playwright, desktop and mobile), accessibility audited to zero serious violations, performance held to Lighthouse budgets. Four days didn't mean cutting corners, and the tests are the receipt.
One more judgment call worth naming. I worked backward from what he already had. He'd shelved a seminar series and built a rough CRM over a weekend. Rather than propose replacing either, I framed the content engine to extract from the seminar and pitched the CRM recommendation as a 30-day parallel run. If his own build kept earning its keep, he'd keep it.
Results
- The engagement was accepted. I'm mid-delivery now, building out what the proposal laid out.
- Four days from first contact to a deployed bilingual site, with accessibility tests, end-to-end coverage, and performance budgets intact.
The proposal argued I could build him a credibility surface. The proposal was that surface. He signed soon after reading it.