Zernio: A Weekend-Built Social API Reached $1M ARR in 10 Months — Five People, $83K/Month

Dollar figures below are accompanied by an approximate yen conversion at ¥150 to the dollar.

Miquel Palet was a founding member of Ucademy, a Spanish EdTech startup. He dropped out of university in his final year to launch it, spent three years there, and watched the company grow past 120 employees, a VC-backed company on the “raise, then scale” side of the table.

He left, and chose a path with no fundraising. What he built is Zernio, a developer-facing social media API that lets posting, analytics, DMs, and ads across multiple social platforms be handled through a single interface. Version 1.0 was written over a weekend.

That product reached $1,000,000 ARR (about ¥150 million) in 10 months from launch. Monthly revenue at the time of the article’s publication exceeds $83,000 (about ¥12.45 million), with a team of four engineers and one marketer, five people total.

The skeleton of the numbers

The claim of “MRR doubling every month” can be checked with arithmetic. If MRR doubled every month for 10 months to reach $83,000, the first month’s MRR would be $83,000 ÷ 2^9, or roughly $160. In practice the exact figure will shift depending on whether the launch month is counted, but either way it lands in the range of “a few hundred dollars in the first month.” Doubling, in other words, isn’t an exaggeration. It reads as the naturally large multiplier of starting from near zero.

Still, the breakdown of the $83,000 isn’t disclosed. If it were entirely the $19 Starter tier, that would take roughly 4,400 subscriptions. Entirely the $999 Unlimited tier, roughly 83. With a 50x+ spread between the price tiers on offer, “how many customers there are” can’t be inferred from this number alone.

What is being sold

What Zernio takes on is the tedious part of social integration. It eliminates the need for developers to individually implement each platform’s distinct authentication, posting formats, rate limits, and analytics APIs. From a SaaS company’s perspective, it removes the need to keep chasing each platform’s API spec just to add a feature like “schedule a post to Instagram” or “pull engagement data from LinkedIn.”

The stack is Next.js 14 (App Router), MongoDB for the database, Tinybird for analytics, Vercel for hosting, Cloudflare Queues for some processing, Axiom for logging, Crisp for support, and Fumadocs for documentation. There are no sales demos. It’s fully self-serve, letting anyone sign up for the free plan and try it themselves.

The decisive move: choosing “someone I could sell to myself”

A pace of $1M ARR in 10 months can’t be explained by a single event. But what Palet cites as the most important decision is how he chose the customer, not the product idea. “It was easier to sell to myself than to a profile I didn’t understand.” He set developers as the ideal customer.

That choice constrained every decision that followed, in a chain. Because the customer is a developer, v1.0, a rough API written over a weekend, was enough to start a conversation. Because the customer is a developer, self-serve works and there’s no need for a sales organization. Because the customer is a developer, documentation itself functions as sales collateral. The productivity of $83,000/month with 5 people traces back to this.

The contrast with his time at Ucademy is stark too. Someone who ran a 120+ person organization for three years next chose a product where he himself was the customer. In before-and-after numbers, it’s “3 years, 120+ people” versus “10 months, 5 people.”

What drove the growth

The acquisition channels named are SEO, paid ads, feature launches, YouTube videos, and creator partnerships. Of these, the first two are the ones that can be explained structurally.

For SEO, the target was bottom-of-funnel (BOFu) keywords, terms like “social media API.” In Palet’s words: “these don’t need to have high search volume, because they convert extremely well.” Knowing the search volume was small, he targeted only that from day one.

The mechanism here is simple but strong. Someone typing “social media API” has already resolved, before searching, the decision of whether to build the integration themselves or outsource it. What’s left is just “which vendor.” Unlike top-of-funnel content SEO that starts from awareness, this is closer to placing a product on the shelf at the final stage of a purchase decision. This only works, though, in a market where the category name already exists as a search term. In a brand-new category no one has named yet, BOFu keywords simply don’t exist.

On paid ads, he states plainly: “I always start with paid acquisition, ads.” But he also acknowledges: “I’ve never been able to fully attribute growth, or accurately know where users came from.” Per-channel contribution, then, is unknown even to the person running it. $1M ARR in 10 months is a fact, but its breakdown can’t be decomposed even by the founder’s own account.

Another point: what Palet calls “the single best decision” was building a team early. Putting one engineer on dedicated support meant customer feedback reached development faster. Bootstrapping discourse tends to favor not hiring. This case runs the opposite direction.

What didn’t work, and the risk that remains

What Palet openly names as a failure is infrastructure design. “If you’re going to scale an infrastructure product, it’s critical to harden your infrastructure from day one. We didn’t do that. We chose simplicity instead.”

Two concrete reversals followed. MongoDB became slow and expensive for analytics data, leading to a migration to Tinybird. And Vercel’s serverless execution couldn’t handle high-concurrency tasks, so some processing moved to Cloudflare Queues. In both cases, choices made for “ship fast” came back as a bill once things grew.

Another constraint sits outside the business itself. Getting the required scope approvals from each social platform takes anywhere from one to six months, time that simply has to be waited out.

Yet this slowness is also a barrier to entry. Going from 5 supported platforms at launch to 20+ now means going through that approval process 20-plus times. A later entrant matching the same coverage needs the same number of months. For Zernio, API approval delay is both the single biggest operational pain point and the single biggest moat, simultaneously, a structure specific to this kind of infrastructure business.

The flip side is the same risk. Each of those 20+ platforms can unilaterally change its terms of service or API spec. Zernio’s revenue sits on top of 20 decision-makers it doesn’t control.

What can be carried out

What’s transplantable is the acquisition design of targeting BOFu keywords from day one, running self-serve without sales demos, and the principle of “choose a domain where you are the customer.” None require capital.

What’s hard to transplant is the underlying premise. The technical ability to write v1.0 in a weekend, three years of experience running a 120+ person organization, and the capital and network to hire four engineers early aren’t things available on day one of going independent. The advice to “always start with paid ads” also only works for someone who can afford to pay for ads first. Though written as “bootstrapped,” this reads more accurately as a case of redirecting resources built up running a VC-backed company into a different form, not a launch from nothing.

And the “$1M ARR in 10 months” figure itself owes much to having a price ceiling of $999 in a category, SNS API, where demand clearly exists. Follow the same steps in a market where the unit price tops out at $19, and the same curve doesn’t happen.

Related reading

• Two failures → $5M ARR → an eight-figure cash exit. ScrapingBee’s “by-the-book” full journey
• Growing OSS solo to over $7M/year. Sidekiq’s 20-year “open source + paid tier” strategy, fully realized