gitfut pulled 45K visitors in 48h with $0 captured
The Case: 45K visitors, 127K cards, one weekend of code
What he does. Turns any GitHub username into a FIFA Ultimate Team-style card rated out of 99 using public stats — commits, stars, top language, followers, account age.
Backstory. World Cup 2026 kicked off. Younes noticed two facts colliding: every dev on Twitter was watching football, and FIFA Ultimate Team cards are the most screenshotted format in gaming. He spent a weekend gluing GitHub's public API to a card renderer and pushed it to r/SideProject on a Saturday. The share loop did the rest — every card generated is a self-contained ad with the domain stamped in the corner.
Product. - One input: a GitHub username - Output: a shareable PNG card rated 0-99, position inferred from top language, country flag pulled from the profile's location field - Editable before sharing — fix your country, swap position - Public GitHub repo, MIT-flavored, open source - No login, no account, no email, no paywall
Pricing. Free. $0 one-time, $0 recurring, 0 paid tiers, 0 upsells at launch.
Key numbers. - Time to 11K visitors: 48 hours - Peak measured: 45K visitors, 127K cards generated - Cards per visitor: 2.82 (users generate ~3 each) - GitHub stars in 48h: 820 - r/SideProject post score: 1,167 upvotes, 203 comments - r/coolgithubprojects: #1 with 300 votes - Build time: ~1 weekend, per the operator - Hosting cost: near-zero (static + serverless) - Emails captured: 0 - Revenue on 45K visitors: $0
Stack. Next.js, Vercel, GitHub public API, OpenScreen (launch video), Reddit + LinkedIn as distribution rails.
Why this works (and what most readers will miss)
1. Cultural window as free acquisition. The World Cup opened a 30-day arbitrage where dev-Twitter overlapped with football-Twitter. You can't manufacture that overlap. You can only catch it. The same tool shipped in September is a curio. Shipped during matches, it's a share-vector.
2. The share loop is native, not bolted on. The product is the marketing asset. Every card contains the URL and begs to be posted. Younes never had to ask users to share — the artifact itself is inherently postable. Compare to a SaaS pleading for referrals: friction versus zero friction.
3. The non-obvious one — it's a leaderboard disguised as a card. Devs don't share their FIFA card because it's cute. They share it because "94 overall" invites the exact comparison-brag mechanic that powers every viral dev tool from Wrapped to Duolingo streaks. Status framing beats utility framing every time in developer audiences. This is why 45K happened. Not creativity. Ranked ego.
The Distilled Read
Ship the smallest thing that hooks a cultural moment already in motion. gitfut is one page. One input, one output, one share button. Boring tech, one weekend, no auth, no dashboard, no drip. This is the correct posture. Most indie builders spend six months building a "platform" that solves a problem nobody in a stadium is talking about. Younes built a toy in 72 hours that intersected the exact conversation 200 million people were already having. The tool doesn't matter. The overlap matters.
Treat the card engine as a template, not a product. You built a renderer that takes public API data and outputs a status-symbol image. That engine ports directly to Strava ("marathon card"), Spotify ("listener card"), LinkedIn ("career card"), Steam ("gamer card"), Duolingo ("polyglot card"). Same code, new skin, new endpoint, new cultural wedge. Ship one every 60 days timed to a different event — Wrapped in December, Olympics in July 2028, tax season for finance nerds. You are not in the FIFA-card business. You are in the identity-artifact business, and you already own the assembly line.
Price something before the traffic dies. Look at this as a bet. Capital at risk: near-zero. Time: one weekend. Attention captured: 45K humans. Decay curve on cultural relevance: 4-6 weeks. A $9 "premium card in 4K + custom background" tier live at launch, converting a conservative 1.5% of 45K visitors, prints $6,075. A $19 "team card for your GitHub org" upsell doubles that. Instead the entire viral moment printed dopamine and a resume line. Attention that isn't converted the same week it arrives is attention you rented, not owned.
The share loop is the entire distribution strategy — but only if you close it. Every card generated is a piece of user-produced marketing with your domain in the corner. This is the Wrapped mechanic, the BeReal mechanic, the Cluely mechanic. It works, and it works for free. But 127K share-events with no capture is winning the lottery and refusing to sign the ticket. The share loop brings them in. Something else has to keep them.
Here's the observation nobody in that Reddit thread made. The moat 18 months from now isn't the card. It's the developer newsletter Younes should have started on Day 1, gated at the moment of maximum dopamine — right when the card renders. "Enter your email to download in HD" converts developer audiences at 25-40% because they want the artifact more than they resist the field. On 45K visitors, that's an 11-18K email list of developers who self-identified as caring about their GitHub identity. That list is worth $40-80K/year at standard newsletter economics, forever, from a weekend of code. The corpses in 2027 will be the "went viral once" indie devs whose Vercel graph looks like a heart attack and whose bank account looks like a flatline. The winners run the exact same 72-hour + share-loop playbook, but they wire the email field in before they push to Reddit. The tool is the bait. The list is the business. The timing is the moat.
Steal-the-Playbook
- Pick one vertical, not the category. Developers, marathoners, Spotify heavy-listeners, Duolingo streakers, Steam achievement hunters. One audience with a public API telling their story and an ego attached to it. Not "identity cards for everyone."
- Anchor to a cultural window 60-90 days out. Wrapped in December, March Madness in March, Olympics in July 2028, tax season for finance nerds. Reverse-engineer your ship date from the moment attention peaks.
- Build the card renderer in 48-72 hours. Next.js + Vercel + one public API + a Figma-designed card template. No auth, no database, no accounts. Anything more is procrastination.
- Wire one email gate at HD-download, nowhere else. Not on landing. Not "for updates". Ask at the peak of user delight — the second the finished card renders and they want the high-res version. This is the step 90% of viral-tool builders skip, and it is the step that turns the moment into a business.
- Reskin the same engine every 60 days. Same codebase, new API, new vertical, new event. Two products in six months from one weekend of engineering. That's the compounding move.
Stack: Next.js + Vercel + Resend (email) + Plausible (analytics) + one public API. ~$0-20/mo. 48-72h from zero to live.
Bottom Line
Going viral isn't a business. It's a receipt for one you forgot to build. The tool is the bait, the email is the asset, and the cultural window is a moat that closes in six weeks whether you captured value from it or not.