March 10, 2026
Pay-per-vibe or pay-per-month?
More agent tools and AI tools should be pricing on outcomes
“Pay when I get paid” vs “line go up” — creators want AI tools to take a cut, not a fee
TLDR: An investor argues AI app platforms should swap monthly fees for a revenue share that includes done-for-you payments and support. Commenters split: cynics say companies only chase growth charts, skeptics ask if he’d offer the same deal to his buyers, and pragmatists warn “outcomes” are hard to define and depend on user skill.
The pitch is simple: instead of monthly bills, AI app platforms like Lovable should take a slice of revenue — pay when I get paid. The author says his course brings in big money but he’s drowning in fees to Stripe, Maven, and a tangle of Zapier automations. He wants one-click checkout, refunds, and support done for him, plus help migrating and scaling. In return? 5% of revenue — maybe 15% or even 30% for premium support. For the growing crowd of “vibe coders” (people who can ship with AI but hate payments and paperwork), it sounds like heaven.
Cue the comments turning into a reality check. doctor_love rolls in with a meme-y splash of cold water: companies want the chart to “line go up.” That dreamy “pay $1B to vibe coders” mission? LOL, says the cynics. bena swings the spotlight back: would the author give the same deal to his own customers — no pay unless they profit? “Where does that end?” Meanwhile, pragmatists like j45 warn this isn’t plug-and-play; value pricing is hard. And quantum_state reminds everyone that “outcomes” depend on the user’s skill — messy to measure, messier to bill.
The community vibe? Equal parts “finally, align incentives” and “nice fantasy, capitalism says hi.” The “Stripe Wall” becomes the week’s meme — creation is easy, checkout is the boss fight. Everyone agrees on one thing: monetization is the boring final level no one wants to play.
Key Points
- •The author advocates outcome-based, revenue-sharing pricing for AI/agent tools to align platform incentives with user success.
- •They cite operating a course (~$800,000 revenue last year) with ~$9,000 in subscriptions and over $100,000 in Maven fees due to valuable automation and support.
- •Payments and fintech complexity (“Stripe Wall”) hinder monetization; a job board earning a few thousand dollars monthly relies on Zapier to avoid Stripe integration work.
- •Proposed model: platforms like Lovable take 5% of revenue (or 15%+ after thresholds) instead of charging monthly credits.
- •To justify revenue share, platforms should offer one-click monetization, integrated auth, simplified Stripe handling, scalable support, and migration/optimization services (e.g., Supabase, CDN, database).