Building Product Revenue Funnels in Public
A product page is not proof by itself. The funnel needs visible outcomes, demo evidence, and a reason to stay connected.
This week I started treating the site less like a portfolio and more like an operating surface for the products I am building.
The product funnel was too thin:
- A visitor could land on the homepage.
- They could browse the product list.
- They could open a product page.
- Then they either bought or left.
That is not enough.
The missing layer is trust. People need to see what the product does, who it is for, why it matters now, and what they can do if they are not ready to buy.
So I am rebuilding the funnel around a few visible pieces:
- Product pages need demo media, not just copy.
- Product pages need outcomes, use cases, and sharper before/after framing.
- Non-buyers need a way to stay connected through updates or useful lead magnets.
- Notes need to become distribution assets, not just private thinking.
- The build log needs to show what is changing over time.
The small detail I care about most: the page should make the work inspectable.
If ResistGate blocks distraction, show the moment where friction appears. If Amethyst helps reading focus, show what the reading experience feels like. If the product is evolving, show the evolution.
That is why I added demo slots before polishing the final sales copy. A product without visible evidence asks the visitor to imagine too much.
The next habit is simple: when I ship something meaningful, I write the build note here first, then cross-post a condensed version to LinkedIn and X with the site as the canonical link.
Owned site first. Social distribution second.
That gives the work a memory.
Building in public
Follow the journey
as I build AI tools, products, and a serious founder life.
No spam. Unsubscribe anytime.