SaaS vs. Voting Platform RankInPublic: Scaling from $300/Month to $17,000/Month

AI Summary · Indie Hacker Perspective

24-year-old founder Antonio launched RankInPublic with just $4k—a "SaaS Product A vs B Community Voting" platform. Monthly revenue exploded from a stuck $300 to $17k. Key pivot: he discovered the sponsorship model for tournaments instead of relying on traditional ads or subscriptions. Currently at 8k users and $33k cumulative revenue. Extremely low barrier to entry (under $50 to start), but revenue is volatile—primarily driven by one-time sponsorship fees, not recurring income. Ideal for indie hackers/small teams validating ideas; not for those seeking stable cash flow. Biggest pitfall: unsustainable revenue requires constant prospecting for new sponsors.

• Cold start stack: Gemini 2.5 Pro + Vibecod
• Monetization breakthrough: Don't rely solely on ads/subscriptions; proactively reach out to SaaS brands to sponsor comparison votes
• Domain strategy: Grab a .xyz domain for $2/year—don't let .com prices scare you off
• Location arbitrage: Moved to Da Nang, Vietnam; cost of living is $190/month, extending runway; started with $4k
• Iteration lessons: Why the first 3 projects failed (high capital, no marketing, network effect barriers)

1. What's the Opportunity?

Who: 24-year-old indie developer, CS dropout. For Whom: SaaS founders, AI tool builders. Solving: Information asymmetry in product selection—helping users quickly compare similar SaaS tools via community voting. Monetization: Brand-sponsored comparison tournaments, premium placement, ad spots. Market ceiling: 50,000+ SaaS tools globally; each category has at least 2-5 competitors, creating rigid demand for comparisons.

2. Independent Assessment

Worth pursuing? Worth validating, but don't go all-in. Verdict: Lightweight model, low startup cost, short validation cycle (P&L visible within 1 month). Suitable as a side hustle or MVP test. Risk lies in fragile revenue structure—$17k/month comes mostly from one-off sponsorships, not subscription recurring revenue, leading to unstable cash flow. Great for indie hackers looking to build skills and user assets; not for those chasing stable income. (Inference: A sustained tournament series could improve LTV, but requires operational muscle.)

3. Cold Start Path

Step 1: Create an X account and post daily SaaS comparison votes (e.g., "Notion vs. Coda: Which is better for notes?") to drive traffic to a simple comparison page. Costs: .xyz domain ($2), Supabase free tier ($0), Cloudflare free. Timeline: Accumulate 500 users within 30 days to start sponsorship negotiations. Action: DM 10 SaaS companies: "Sponsor our next vote and get a dedicated comparison page for your product." (Inference: Average ticket size $500–$2,000; prepare user metrics as leverage.)

4. Biggest Risks & Pitfalls

Pitfall 1: Revenue non-sustainability—sponsorship fees are one-time; next month could be zero. Mitigation: Build a 3–6 month operating reserve and incubate a subscription product (e.g., RankLoop) to hedge risk. Pitfall 2: Network effect trap—the reason the first 3 projects failed. Mitigation: Choose a track with no network effect (comparison votes don't require two-sided user growth), but maintain active content operations to sustain engagement. (Inference: Without new sponsors for 3 months, the 8k user base may lose activity.)

5. Case Breakdown (How Others Did It)

• What product: Minimalist SaaS comparison pages with only core "Product A vs B + user voting" functionality; no complex membership system (source fact)
• How they acquired users: Founder posted vote threads on X → drove traffic to the platform → invited users to register and vote → UGC content fed back into X (source fact)
• How they priced: Sponsored tournaments at $500–$2,000 per round (tiered by SaaS MRR); non-standardized subscriptions (inference: no public pricing table disclosed)
• Sequence: Built the site (1 day) → posted on X for traffic (ongoing) → after hitting $300/month, sought sponsors → landed first major sponsorship → revenue jumped to $17k (source fact)
• Key numbers: $4k startup capital, $190 monthly costs, first sponsorship in 30 days, 8k users, $33k cumulative revenue (source fact)
• Pitfalls hit: First 3 projects failed due to high capital, lack of marketing, and network effect barriers → new project deliberately chosen for low cost and no barriers (source fact)

Original source · Indie Hackers · Case study: Read original →