I Found a Business Idea and Shipped It in One Claude Code Session
How a Reddit thread became a live product in under an hour
I shipped a new product landing page yesterday. Not “finished the design.” Not “pushed to staging.” Live. Accepting waitlist signups. DNS propagated. The whole thing.
Time from “huh, interesting Reddit post” to “supabyoi.com is live”: under an hour.
This is either impressive or terrifying, depending on how you feel about the pace of software development in 2026.
The Setup
I’ve been building a Reddit research tool that lives inside Claude Code. It monitors subreddits, scores posts against your interests, and helps you find signals in the noise. The tool uses Reddit’s public JSON endpoints—no API keys required, because Reddit doesn’t issue them anymore.
That’s not hyperbole. Reddit recently announced they’re “ending self-service API access.” You can’t just create an app and get keys anymore. You have to submit a request form, explain your use case, and wait for approval. The approval that, according to r/redditdev, never comes. “Tickets rejected, modmail ignored, admin DM ignored.” One developer summed it up: “I don’t believe anyone is getting API access for small personal use at this point.”
They’re pushing everyone to Devvit, their walled-garden platform. JavaScript only. Runs on their servers. Limited to what they allow.
If you want Reddit data for your own tools, you either pay enterprise rates, beg for approval, or use public endpoints like a normal browser would. I chose option three.
GummySearch learned this the hard way. They built a Reddit research tool, hit $11k/month MRR, served 135,000 users. Then Reddit wouldn’t give them a commercial license. They’re shutting down by December 2026. The founder didn’t want to operate “looking over your shoulder every day.”
Public endpoints don’t have that problem. Same data. No license to revoke.
I had the tool pointed at r/Supabase, watching for pain points. Standard demand validation stuff.
It surfaced a pattern across multiple threads. “I’m a mass-project starter. Supabase ain’t for me?” (41 upvotes, 27 comments). “Is Self-Hosting Supabase Worth It?” (73 upvotes, 60 comments).
The pain: Supabase’s free tier caps you at 2 projects. Pro tier is $25/month plus $10 per additional project. If you’re an indie dev shipping lots of small bets, you burn through that limit fast.
Supabase is genuinely great for rapid prototyping—I use it myself. The pricing just doesn’t fit the small bets workflow.
The comments were gold:
“It feels like a bait-and-switch where the upgrade appears to remove project limits, only to hit you with unexpected per-project fees”
“Setting it up properly takes time, maintaining it takes time, keeping the server secure takes time”
“The setup process is extensive, unclear and often frustrating”
“Very strange pricing model, which is kind of unacceptable”
Translation: Indie devs love Supabase for building fast. They hate the pricing when they ship a lot. They want to self-host but are terrified of maintaining it.
The Evaluation
I have a framework for this. Open source project + operational complexity + permissive license = potential hosting business. I’ve been running variations of this for a while.
I asked Claude—right there in the same session—to run the threads through the framework:
Pain point: Real. Multi-project pricing punishes prolific shippers.
License: Apache 2.0. Clear.
Operational complexity: High. Supabase runs ~12 services.
Existing managed option: Yes, but that’s the pain source—not the solution.
Then the key insight: I’m not competing with Supabase Cloud on hosting. I’m offering care and feeding for self-hosted instances. Different model entirely.
They bring their own VPS (Hetzner, $10-15/month)
I handle upgrades, backups, security
Fixed monthly fee: $25. Unlimited instances.
One customer with 5 projects: $25 from me + $15 VPS = $40 total vs $75 on Supabase Cloud.
The Build
Here’s where it gets fast.
I told Claude:
“Create a landing page. Tailwind, not CDN. Minimal. Dev-focused. Static HTML.”
Claude scaffolded the project structure, wrote the copy, set up the build pipeline. I tweaked the value prop and added my ConvertKit form.
Then:
“Push to GitHub, I’ll deploy to Cloudflare Pages.”
Done.
Total time building the landing page: maybe 20 minutes. Most of that was me fiddling with colors.
The Stack
For the curious:
Landing page: Static HTML, Tailwind CSS, Cloudflare Pages
Waitlist: ConvertKit embed
Domain: Namecheap (purchase) → Cloudflare (DNS)
Total cost so far: $12 for the domain
The actual product will be FastAPI + Supabase (yes, the irony) + HTMX. SSH into customer VMs. Cron jobs for backups. Simple. I can ship a working beta this week.
The Point
This isn’t about Supabyoi specifically. It’s about the workflow.
Old way:
Have idea
Think about it for weeks
Research competitors
Write PRD
Design mockups
Build MVP
Realize nobody wants it
Total time: 3 months
New way:
Tool surfaces interesting signal
Ask Claude to validate against framework
Ask Claude to build landing page
Ship
See if anyone signs up
Total time: 1 hour
The landing page is a hypothesis test. Not a commitment. If I get 50 waitlist signups, I build the thing. If I get 5, I move on. The cost of being wrong is $12 and an hour of my time.
About That Reddit Tool
I’ve been quietly building this for months. It’s how I found the signal that led to this post.
The key: it lives inside Claude Code. Not a separate app. Not a browser tab. Right there in my terminal, in the same session where I’m writing code and shipping products.
The architecture: Crawler runs locally or on your VPS (Reddit can’t shut you down if they can’t block your IP). Data syncs to a backend. You query it with natural language through Claude. “What are people complaining about in r/Supabase?” → ranked list of pain points with source threads. Then in the same breath: “Evaluate this against my validation framework.” Then: “Build me a landing page.”
One session. Research to shipping.
No Reddit API keys because Reddit killed self-service access. Uses public endpoints. Same data you’d see browsing the site. Your IP, your rate limits, no approval form that never gets answered.
I’m not ready to launch it yet, but if you want early access, DM me on LinkedIn or Twitter/X.
The Takeaway
The leverage is real. One person, one AI assistant, one hour, one live product.
The bottleneck isn’t building anymore. It’s finding the right thing to build. That’s why the Reddit tool matters more than the Supabase thing. The tool finds signals. Claude validates them. Claude builds the test. You watch the data.
Small bets at scale.
supabyoi.com is live. Let’s see what happens.
<fingers-crossed/>