So I shipped SportzGenesis Arena last week. Sports prediction platform, covers cricket and football, no gambling. 58 users right now. Here's what actually happened.
Why I built it
Every IPL season, my friends and I argue endlessly about match outcomes on WhatsApp. Same thing with Premier League. Nobody keeps score. Nobody remembers who called what. The arguments just reset every week.
I looked for an app that would let us track our predictions. Options were:
Dream11 and Fantasy Premier League. Too complex. Nobody in my group wants to research player lineups for 2 hours every weekend.
Superbru. Fine platform but looks like it was built in 2010. Clunky on mobile.
Most other fantasy apps. Either gambling-based (illegal in a lot of places) or too focused on one sport.
Also, here's a detail I didn't know until I started researching: India passed the Promotion and Regulation of Online Gaming Act in August 2025. Real money fantasy sports are effectively banned there now. Dream11 had to pivot its entire model. That left a gap for simple, free prediction games.
So I decided to build one.
I am not a developer
Need to be upfront about this. I've never taken a CS class. I can read code but I don't write it from scratch. What I do have is patience, an LLM subscription, and enough stubbornness to debug stuff at 2am until it works.
If you're a non-technical founder reading this thinking you need to learn to code before you build, you probably don't. You need to learn how to ask good questions, test things properly, and notice when something feels wrong. The rest of it, tooling handles.
The stack
Kept it boring on purpose.
Next.js with App Router, TypeScript, Neon Postgres (Frankfurt region), NextAuth with Google, Vercel for hosting. Plain CSS, no Tailwind. Total monthly cost right now is one dollar for the domain.
If you're bootstrapping, don't pick trendy tech. You don't have time to debug a bleeding-edge framework AND your actual product.
What the product does
Two sports, two different prediction formats.
For football, you predict the half-time and full-time scores. Max 8 points per match. Exact score gets 3, correct result gets 1, and if you nail both HT and FT exact you get a 2 point bonus.
For cricket, you predict five things: toss winner, toss decision, first innings score, match winner, and second innings wickets. Max 10 points. Cricket needed more prediction fields because a cricket match has more meaningful events than football.
Predictions lock 30 minutes before scheduled toss for cricket, and at kickoff for football. The 30 minute buffer was important because cricket fans react to team news and pitch reports that drop an hour before the match. If you lock predictions too early, you lose engagement. Lock them too late, people wait until the toss happens.
The cricket thing was harder
Football is clean. 90 minutes, one winner, done. Cricket has:
- A toss, which is a separate event with its own outcome
- Two innings with wildly different strategic considerations
- Rain interruptions, super overs, DLS method calculations
- Last minute lineup changes that matter a lot
I cut corners. Instead of modeling all of this perfectly, I shipped the prediction layer first and decided I'd deal with edge cases as they came up. A rain-shortened match still works with my scoring, it's just less points available. Good enough for v1.
Social features were the surprise
Thought people would come for predictions. They actually came for the chat.
I added a match chat feature almost as an afterthought. Each match gets its own comment thread where people can talk while watching, react with emojis, reply to each other. Most-used feature after predictions themselves.
Turns out people don't just want to predict. They want to predict loudly, in front of their friends, and then roast each other when predictions go wrong.
Also added private leagues. Users create a league, share the invite code, everyone in the league sees a separate mini-leaderboard. This is where most new signups come from now, people inviting their friends to compete.
Growth is the hard part
Product was the easy bit. Getting users is where I'm currently struggling.
What worked:
WhatsApp to friends and family. First 15 users, 100% conversion, immediate feedback. No surprise here.
SEO landing pages. Wrote 13 pages targeting specific keywords. Too early to measure impact, but Google indexed them within 5 days. This is a slow compound play, probably 6-8 weeks before I see real traffic.
Cultural moments. Added a small joining bonus during Vishu (Kerala new year) which brought in a handful of users from that community. Worth doing for any festival your target audience cares about.
What absolutely did not work:
Instagram stories. Zero impressions. Found out stories only reach existing followers. When you have 10 followers, you get 10 views. Complete waste of time.
Twitter. Brand new account, algorithm suppresses you for weeks. Posted content for two weeks straight, got nothing.
LinkedIn company page. Reach is apparently 10% of personal profile reach. Should have posted from my personal profile instead.
Meta ads. Account got banned mid-campaign. Appeal rejected without explanation. Don't know what happened.
WhatsApp status updates. Worked initially, then my friends got tired of it. Had to stop because it was becoming spam.
The uncomfortable truth
Indie hacker Twitter makes growth sound easy. "Just ship it." "Build in public." "Growth hack to 10k users."
Reality for a small account with no following: social media platforms actively throttle your reach. Paid ads are gatekept by policies that change without notice. Organic reach on a new account is basically zero.
What actually works is slower. Direct messages to real people. SEO that compounds over months not days. Making something genuinely good so that the users you do have tell their friends.
Lessons I'm taking into week 2
Build for real users not imaginary ones. My first version had an AI generated match preview feature. I spent days on it. Nobody used it. Deleted it.
Simple beats clever. Predict the score is something casual fans understand. Building a 15 player fantasy squad is not.
Community features punch above their weight. Match chat took almost no engineering but drives more engagement than sophisticated features I built.
Growth is a separate full time job. Building is fun and creative. Growth is grinding. Writing copy, sending messages, replying to comments. Most founders prefer building. Most products fail to find users. These two facts are connected.
SEO should start day one. I added landing pages in week two. Should have been week one. Google takes weeks to index and rank. Every day without SEO pages is lost compounding.
B2C proof matters before B2B. I have plans for a white label version for sports federations and colleges. Nobody will sign up with a platform that has 58 users though. The consumer traction is the credibility for the business pitch.
What's next
Get to 500 users. That's the number I need before I can credibly pitch to federations, colleges, corporate sports organizers.
Keep writing SEO pages. Google rewards consistency.
Launch on Product Hunt after I hit 500 users. Not before. A Product Hunt launch with 58 users is embarrassing. With 500 users, it's a launch moment.
Probably write a week 2 update here on dev.to if I have anything interesting to say.
Feedback welcome, especially roasts of my homepage. Growth tactics that worked for you, please drop in the comments.
Thanks for reading.
Top comments (0)