howtodistribute
← Back to the index

How Zenvoice got its users

HARDFounder-ledsolob2bno ads
Visit zenvoice.io

Solves a specific Stripe annoyance, sold to an audience of founders who all have that exact annoyance.

Confirmed. The team said it publicly, or the signals leave no room for doubt.

Can you run this?
HARD

Reproducible, but it will cost you real money, real months, or a skill you may not have.

The edge you do not have: A maker audience already assembled before the product

Your time
Audience first
Your money
Nothing on ads
First signal
Immediate given the audience
Upside
  • A launch that does not start from zero
  • A direct relationship that survives algorithm changes
Price of entry
  • 12 to 36 months of publishing before launch
  • Accepting that you are the face of the product
  • A topic where you have standing

Founder-led in 2026

Works extremely well, but it is an asset you build before the product, not during.

Everything on this channel →

The play

5 steps, in the order they ran them.

  1. 1

    ZenVoice's spec came out of Marc Lou's own Stripe bill: $1,600 paid in 2023 just to generate PDF invoices. He turned Stripe Invoicing off, his inbox filled with invoice requests, and that inbox was the product. Getting that bill takes sales volume you may not have. Without it, borrow the complaint: Stripe support threads, r/stripe, maker forums asking how to send a customer an invoice. Collect 20 verbatim complaints, build only what all 20 ask for.

    done whenAt least 10 of your 20 saved complaints name the exact tool and the exact fee or hours it costs them. Vague irritation is not a spec.

  2. 2

    One feature, and a third of the build goes to the page. ZenVoice was built in 31 hours, 11 of them on the landing page, and shipped with no password reset, no invoice preview, no account deletion. Marc's rule: 1 startup = 1 feature. He built it live on his YouTube channel, where viewers fed him headlines and debugged, which is his asset. Without viewers, drop the half built version into the thread where you found the complaint and ask the complainer to break it.

    done whenYour whole feature list fits in one sentence with no 'and'. If you cannot name three standard features you deliberately did not build, the scope is still too wide.

  3. 3

    Write the page as a fee comparison, not a product tour. zenvoice.io opens with 'Stop paying 0.4% for Stripe invoices' and runs a two column table against Stripe Invoicing: 0.4% per invoice, not editable after sending, none for past payments. The only outbound link in the body goes to Stripe's own invoicing pricing page, anchored on the fee sentence. Price against the meter: $49 once for one Stripe account, sold through a plain Stripe payment link, no account before paying.

    done whenEvery row of your comparison table describes a behaviour of one named incumbent. Swap a different competitor in and at least four rows should turn false.

  4. 4

    Trade pre-launch access for one sentence with a number in it. ZenVoice's page carries eight named quotes, each showing the person's X follower count (Tony Dinh, Dan Kulkov, Nico Jeannen). That format needs peers who already have audiences, which is Marc's asset and not yours. Substitute: give the tool free to ten people off your complaint list, and ask for their unit, like 'requests 2-3 times A DAY' or 'saving 3-4 hrs a month'.

    done whenEvery testimonial you collect contains a unit: hours, requests per week, dollars. If a quote has no number, it is decoration and you should not ship it.

  5. 5

    Same product, four places, same day, rewritten per platform: Product Hunt, Reddit, Hacker News and X, cold tech words on HN, emoji and friendly tone on PH. What moved the traffic was a launch skit video on X, the 31 hour livestream, and ShipFast, the boilerplate he had already sold to the founders who pay Stripe fees every day. With none of that, the honest version is slow: answer the Stripe invoice threads you saved, and message sellers whose checkout is visibly Stripe.

    done whenCount the people who will see your launch because of you, not the platform. If that count is zero, plan the first buyers as conversations and judge the day on replies, not upvotes.

The product itself

read from zenvoice.io, live

Stop paying 0.4% for Stripe invoices

6 public pages

Run this against your own product

In your chat

Carries the play above, and is written to tell you no when this channel is out of reach for you.

In your editor

The same twelve channels as an agent skill. It reads your repository and eliminates what you cannot run. Open source, MIT.

curl -o ~/.claude/skills/howtodistribute/SKILL.md https://howtodistribute.com/skill.md

One-time payment product, revenue published by the founder

What else they ran

They ran the same play

Want this verdict on your product?

Describe it. You get back the channel I would run in your place, the 30-day plan, and the number at which you stop.