Build Log

Two Products, Zero Revenue: Why I'm Adding Distribution to the Machine

2026-03-30·4 min read

March 2026 · Fixing the obvious weak spot

Last week I archived my second product. Two complete cycles through my Idea-to-Market Machine. Combined revenue: £0.

Both products died from the same cause. Not bad ideas. Not bad execution. No distribution.

So I spent one evening building a content machine. Not a pause. Not a pivot. Just fixing the obvious gap before Product #3.

The Pattern I Finally Noticed

Product #1 (ConfidentYou) died with zero sales despite a warm list of 300 former coaching clients. They opened my emails at 45%. Three people replied. Nobody bought.

Product #2 (YouTubeKB) died after three pivots in a single week. MCP plugin to dashboard to transcript export. Each pivot stripped away what made it special until I was left with a generic tool competing against a dozen alternatives.

Different products, different markets, different tech. But the same root cause: I had no distribution.

4,500 email subscribers but they're all public speaking people who don't care about AI tools. A Twitter account with 5 followers. About 2,000 LinkedIn connections but I haven't posted in years. No community. No audience of builders or PMs who might actually want what I build.

I could build Product #3 next week. Claude Code means I can ship in days. But ship to whom?

The Uncomfortable Maths

Here's what two failed launches taught me:

  • Building is no longer the bottleneck. Claude Code collapsed that to 1-2 weeks.
  • Marketing and distribution are the bottleneck. And AI doesn't compress trust-building.
  • Each launch to zero audience is basically a lottery ticket.
  • I was optimising the wrong side of the equation.

The Idea-to-Market Machine works. The build phase is proven. The decide phase is honest. But the market & test phase keeps failing because I'm launching into a vacuum.

One Evening to Fix It

Content has always been my weakness. I know I should do it. I never do. So I treated it the same way I treat product work: build a system, automate what I can, remove the friction.

In one evening I set up the whole thing:

  • Typefully for scheduling (API connected, CLI working)
  • Two separate pipelines: X for indie builders, LinkedIn for PMs
  • 7 tweets scheduled for the first week
  • 4 LinkedIn posts drafted
  • Session logs automatically capture content seeds

Total time cost going forward: about 40 minutes per week on top of the building I'm already doing.

I'm not pausing to "become a content creator." I'm still ideating on Product #3 this week. The content machine just runs alongside everything else now. Every build session already generates notes and decisions. I'm just making that process public.

Two Channels, Two Angles

Twitter/X: Build in public. Real numbers, real failures, the honest builder journey. Starting from basically zero followers.

LinkedIn: Different angle. "PM who builds with AI tools." Same stories, professional framing. For PMs and non-technical builders curious about vibecoding. I've got about 2,000 connections here already, so I'm not starting cold. First post this week hit 2,200+ impressions and 32 likes. The audience is there. I just wasn't talking to them.

The 6-Week Checkpoint

By May 9, 2026:

  • +200 followers (across X and LinkedIn)
  • 6-week posting streak (no gaps)
  • 4+ blog posts published
  • 10 inbound DMs from builders/PMs
  • If an audience conversation surfaces a strong product idea, even better

If those numbers look good, Product #3 launches with an audience behind it. The idea pipeline keeps running in parallel. I'm not waiting for permission to build.

The Lesson

Two products. Zero revenue. The instinct is to build faster, build better, build something different.

But the real lesson is simpler: it doesn't matter what you build if nobody sees it.

The machine keeps running. I just added the missing gear.