Backrail - Angel invest in indie hackers from $100
by•
Backrail lets anyone back indie SaaS founders from $100 — no equity, no VC. Founders connect Stripe (read-only), show verified MRR, and open revenue-share rounds. Backers pledge, and earn a share of revenue up to a cap when rounds execute.
Replies
Hey PH 👋
I built Backrail because I kept seeing the same gap: indie hackers with real, profitable SaaS ($1-15K MRR) who need $15-30K to go full-time — too small for VCs, and they don't want to give up equity anyway. Meanwhile, thousands of people watching build-in-public threads think "I'd put $200 into that founder."
Backrail connects them: founders show Stripe-verified revenue (read-only key, they control it), open a revenue-share round (e.g., 7% of revenue until backers earn 2.5x), and anyone can pledge from $100.
Being fully transparent: we're early. Pledges today are commitments, not charges — real money movement comes via licensed partners as we grow. Right now I want to prove both sides of this market exist.
I'd love brutal feedback, especially from founders: would you ever take revenue-share money from your own audience? Why or why not?
Ask me anything — I'll be here all day.
Love the simplicity here. One thing that would make me more confident as a backer: a public leaderboard or trust score for founders who have completed rounds and paid out backers on time. Something like a verified track record badge showing past rounds, total paid back, and whether backers got their full cap. That kind of social proof would really help lower the hesitation for first-time backers like me.
@cpham33672
This is exactly the kind of feedback I was hoping for, thank you.
You're completely right, and it's on the roadmap: every executed round on Backrail will build a public, verifiable track record, rounds completed, total repaid to backers, on-time payment history, and whether caps were reached.
Since repayments flow through Stripe-verified revenue, that history can't be self-reported or embellished, it's the same trust mechanism as the MRR verification, applied to payouts.
Being transparent: no rounds have executed yet (we're in the pledge phase while the money-movement side goes through licensed partners), so day one every founder starts without a track record. But that's also why we gate listings hard upfront, verified revenue, 12+ months of operating history, so the entry bar does some of the work a track record will do later.
Longer-term I love the idea of this becoming a portable founder reputation, a "paid backers in full, twice" badge would be worth more than any pitch deck. Adding your framing to the roadmap.
What would matter most to you in a v1: on-time payment %, total repaid, or completed rounds count?
It'd be really helpful to see a simple projection of when a round is likely to execute based on the founder's growth trajectory, so backers can size their pledges against realistic timelines.
@ramazaner8k
This is a really useful push, thanks.
Two parts to the honest answer:
On repayment timeline. This is exactly what the simulator on each startup page is for, and you've made me realize it should go further: instead of a single estimate, we should show scenario ranges built from the founder's actual verified growth history (e.g., "if growth continues at their trailing 12-month rate → cap in ~4 years; if it halves → ~6; if revenue declines → cap may never be reached"). Since the MRR history is Stripe-verified, the scenarios can be grounded in real data rather than founder optimism, that's a genuine advantage over pitch-deck projections.
One thing we'll always be careful about: these will be clearly labeled as illustrative scenarios, not predictions. The downside case (you don't recover your pledge) will be shown just as prominently as the upside, that's both the honest thing and what keeps this from becoming the kind of rosy-projection marketing this space doesn't need more of.
On round execution timing (when a round fills and money actually moves), that's driven by pledge momentum and our execution pipeline rather than founder growth, and each round has a defined pledge window + execution deadline, so backers always know the outer bound before committing.
Does a scenario-range approach (rather than a single "expected date") give you what you need to size a pledge?