He Sold 2 Products Before $1K MRR — and Landed $2,200/mo Anyway

The Case: $30K+ across 5 products, 2 exits, 1 niche that finally clicked

What he does. Jonathan builds and sells API products in the scraping and data-extraction space, working nights and weekends while employed full-time.

Backstory. The no-code and automation wave hit a real ceiling in 2024: operators could automate anything except the data pipelines feeding their workflows. Screenshot APIs, social scraping APIs, and posting schedulers became the boring infrastructure layer everyone needed but nobody wanted to maintain. That gap opened a window for a solo developer who could ship a functional API faster than a funded team could schedule a kickoff call.

Product. - LectureKit: education tool, ~190 users, 0 paying customers, sold for $6,750 after ~1 year - NextUpKit: Next.js starter, ~$300 total revenue - CaptureKit: screenshot automation API, 300+ users, 7 paying customers, $127 MRR at exit, sold for $15,000 after ~2.5 months - SocialKit (current): social media scraping API, 11,000+ registered users, ~100 paying customers - PostPeer.dev (next): social media posting API for scheduling and automating content, pre-launch

Pricing. Not disclosed per product tier. SocialKit generates ~$2,200 MRR plus ~$800/month in one-time purchases.

Key numbers. - LectureKit sale price: $6,750 - CaptureKit MRR at exit: $127 (7 paying customers) - CaptureKit exit price: $15,000 - CaptureKit time to exit: ~2.5 months - NextUpKit total revenue: ~$300 - SocialKit registered users: 11,000+ - SocialKit paying customers: ~100 - SocialKit MRR: ~$2,200 - SocialKit one-time purchase revenue: ~$800/month - SocialKit total monthly revenue: ~$3,000 - Total across all products: ~$30K+

Stack. Not disclosed.

Why this works (and what most readers will miss)

1. He validated market size with competitor revenue before building. The framework is concrete: three-plus competitors, each doing $20K–$80K/month. That's not a vibe check — that's a floor assessment. If the ceiling of the market is visible and the incumbents are reachable by SEO, the bet is bounded. Most builders skip this step and call it "research."

2. The early exits weren't failures — they were capital recycling. CaptureKit at $127 MRR sold for $15,000. That's roughly 118x monthly revenue. No VC-backed company sells at that multiple this early; a small operator buying infrastructure traction will. Selling early converts uncertain future ARR into certain present capital, which buys time to find the next, better-positioned product. The pattern isn't inconsistency — it's portfolio construction.

3. The ICP flip is the non-obvious one. He built for developers. The people who stayed and paid were no-code users, marketers, and automation operators. This happens constantly in API products: the technical builder assumes technical buyers, but the actual demand comes from people who want the output of the API, not the craft of integrating it. The product doesn't change. The docs, the landing page, the support tone, and the upsell path all do. He caught this by watching who stayed — not by surveying who signed up.

The Distilled Read

Build the product that survives your own boredom. Jonathan killed WaitlistKit after one $30 pre-sale because the category bored him. That's not a mistake — that's accurate self-knowledge applied early. The operator who ships a product they don't care about will stop responding to support tickets at month four, let churn go unaddressed, and watch MRR flatline while they mentally move on. Boredom is a leading indicator of abandonment. The $30 refund cost him nothing. Staying would have.

One niche, then clone the motion. APIs in the scraping and automation space aren't five different businesses — they're one playbook repeated. CaptureKit, SocialKit, PostPeer: same buyer, same distribution, same integration layer, same competitor-benchmarking methodology. The operator running this correctly doesn't reinvent anything. He rewrites the landing page, points the docs at a new endpoint, and drops the new product into an audience that already trusts the last one. Two products from one playbook is not luck. It's the only sensible way to build when you have 10 hours a week.

The economics only make sense if you treat the exits as part of the model. CaptureKit generated $127 MRR — a number that, compounded forward, is not interesting. But $15,000 at 2.5 months is real money that arrived in a single wire transfer and funded the next 6 months of runway. The operator who holds everything waiting for "real scale" is playing a different game, one that requires either patience he doesn't have or hours he can't spare. If you're building nights and weekends, early exits are not a concession — they're the correct financial instrument. My read: at $127 MRR with 7 customers, a buyer who has distribution is worth more to that product than the builder who's running out of attention.

The 11,000 registered users on SocialKit did not come from luck. SEO, blog posts, free tools, feature pages, building in public on Reddit and LinkedIn, WhatsApp conversations with early users — this is unglamorous compound distribution. None of it is a hack. All of it is an audience that arrived already understanding what the product does, which means support load is lower and conversion is higher. The automation people and marketers who became his actual buyers found him because the content was written for developers — and they translated it themselves. That's the signal: when your wrong-audience content converts your right audience anyway, you've found something real.

The actual moat is the exit multiple, not the MRR. Here's what nobody in the thread centered on: Jonathan has now demonstrated twice that he can build API products to small but real traction and sell them at multiples that would embarrass a SaaS broker handling $50K MRR companies. The moat 18 months from now is not SocialKit's feature set or PostPeer's integrations. It's the reputation of being a builder who ships real, sellable infrastructure — and the network of micro-acquirers who will pay a premium for his next exit because they already made money on the last one. Most operators treat a sale as an endpoint. He's treating it as a credential. The difference is that one of them gets better deal flow every year, and the other starts from scratch.

Steal-the-Playbook

1. Pick one API category — scraping, webhook delivery, screenshot, PDF generation — not "APIs." Specificity is what makes the SEO land and the competitor benchmarking possible.

2. Before writing a line of code, find three competitors each doing $20K–$80K/month. Use tools like SimilarWeb, Indie Hackers public revenue, or TrustMRR to verify. No comps in range = no build.

3. Ship the MVP in 3 weeks, hard stop. Set a public launch date on day 1. Launch to a relevant subreddit, a LinkedIn post, and one free-tool page optimized for a long-tail keyword. Track who actually activates, not who signs up.

4. Watch your activation cohort for 30 days and note every job title that upgrades or asks a non-developer question. That's your real ICP. Rewrite your homepage for them within 60 days of launch.

5. At month 3, run the exit math. If MRR is under $500 but traction is real (users, signups, inbound questions), list it on Acquire.com or MicroAcquire with a plain description and honest numbers. Reinvest the proceeds into the next product in the same niche.

Stack: Not disclosed by the operator. Budget estimate for a comparable API product: Hetzner or Fly.io for hosting, a simple docs tool, a payment processor — likely under $50/month to run at early scale.