The case at a glance
- Launched: April. May revenue: ~$300/mo
- August revenue: ~$26,000/mo (his framing: ~100X)
- Signups: 9,000
- Team size: 3
- Enterprise contracts behind the August number: 2–3
- Product usage before those accounts converted: at least 3 months
- Users naming customer service as the sticky factor: 4 of 5 interviewed
- Stated next target: $100,000/mo
A data/API product (structured social data by endpoint instead of by scraper script), sold two ways at once: self-serve credits for developers, plus a handful of enterprise contracts. Three people, a public revenue tracker, no disclosed pricing, no disclosed stack.
The operator hit the problem himself, then noticed competitors already had paying customers — validation without a validation phase. He built the product first and the audience second, and calls that his mistake. Distribution is a content library spread across X, Reddit, YouTube, Hacker News and a blog.
What he's actually selling: a 90-day enterprise sales cycle disguised as a free tier
The product isn't the data. The product is a self-qualifying sales pipeline that he doesn't have to staff.
Those 2–3 enterprise contracts didn't come from demos, pilots, or procurement theater. They came from developers who found him through content, wired an endpoint into production, ran it for a full quarter on their own budget, and then raised their hand. The buyer conducted their own diligence for 90 days and closed themselves.
Two mechanics make that work, and neither is "posting consistently."
First, the customer writes the switching cost. An API embedded in someone's codebase isn't a subscription, it's a dependency. Ripping it out is a sprint nobody wants to schedule.
Second, usage logs are a lead-scoring system — and nobody in that thread called it one. The accounts hammering endpoints for three straight months are pre-qualified enterprise buyers. He can see them before they contact him.
That's why three people can hold $26K/mo. An API is the most honest product shape there is: it returns clean data on the first request, or the developer closes the tab. No onboarding calls, no dashboard nobody logs into.
He thinks he won on consistency. He won on structure — and the difference is the only thing worth copying.