Miquel Palet: From a 120-Person Startup to $1M ARR With Zernio
After building a venture-backed edtech company to more than 120 employees, Miquel Palet chose a narrower path: a developer-first social-media API. Zernio reached a reported $1M ARR in about 10 months.
Miquel Palet
@miquelpalet · XZernio
Miquel Palet had already experienced the startup path most founders spend years trying to reach.
He had built a company.
He had experienced venture capital.
He had grown a team.
He had seen what happens when a software company becomes an organization rather than a product.
Then he chose a different game.
Instead of building another large company, Palet focused on a narrow developer problem: integrating social-media APIs.
The result was Zernio, a developer-first API platform that reportedly reached $1M ARR in roughly ten months.
The interesting part is not only the revenue milestone.
It is how deliberately narrow the product was.
Palet previously worked on Ucademy, a Spanish edtech company.
He dropped out of university to pursue the business and helped grow it to more than 120 employees.
That experience taught him something that is easy to miss when looking only at startup success stories.
Scale creates operational weight.
More employees mean more coordination.
More customers mean more support.
More products mean more complexity.
More capital creates more expectations.
There is nothing inherently wrong with that model.
But after experiencing it, Palet wanted a different type of company.
The idea for Zernio came from a frustrating engineering problem.
A side project needed to publish to multiple social networks.
The task sounded simple.
It was not.
Every platform had different APIs.
Different authentication.
Different permissions.
Different edge cases.
Different documentation.
Different approval processes.
The team was spending time dealing with social platforms instead of building the actual product.
That pain became the product opportunity.
Zernio's promise was simple:
Build social functionality once.
Use one API.
Let Zernio handle the platform differences underneath.
Developers could integrate publishing, analytics, direct messages and advertising functionality without separately learning every platform's API.
That is a classic infrastructure opportunity.
The customer is not paying because the feature is exciting.
The customer is paying because the alternative is painful.
One of the strongest parts of the story is the speed of the initial build.
Palet's team built the first version around several major integrations in a weekend.
There was no elaborate validation campaign.
No giant pre-launch.
No months of market research.
They built the solution to a problem they already understood.
Then they watched whether developers used it.
This is an important distinction.
The product was not validated by surveys.
It was validated by being useful.
The engineering was not the hardest part.
The platforms were.
Social APIs often require permissions, scopes and reviews.
Some approvals could take months.
That creates an unusual constraint for a developer infrastructure company.
You can build your API abstraction quickly.
But you cannot force Meta, LinkedIn, TikTok or other platforms to approve your application tomorrow.
Zernio had to operate inside that reality.
Palet made a deliberate choice about the customer.
Developers.
That sounds obvious.
But it changes the entire product.
Developers want documentation.
They want SDKs.
They want predictable APIs.
They want quick setup.
They want examples.
They want to know exactly what happens when an API call fails.
They are less interested in a giant dashboard if the underlying API works.
That focus kept Zernio narrow.
The company was originally known as Late.
In March 2026, it rebranded to Zernio.
The underlying product and team remained focused on the same core opportunity.
The rename is a useful reminder that branding does not have to mean rebuilding the business.
Sometimes the product is already right.
The name is what needs to change.
The growth strategy was unusually practical.
Instead of chasing broad startup keywords, Zernio targeted developers who were already searching for the problem.
Queries such as:
“social media API”
“Instagram API”
“LinkedIn posting API”
and related developer searches have strong commercial intent.
Someone searching for those terms is not casually browsing.
They are trying to build something.
That makes bottom-of-funnel SEO extremely powerful for infrastructure businesses.
SEO is often criticized because broad traffic does not necessarily produce customers.
But Zernio had a different advantage.
The search intent was extremely specific.
A developer searching for a social-media API already understands the problem.
The website does not have to convince them that social APIs exist.
It only has to convince them that Zernio is the easiest answer.
That dramatically shortens the marketing funnel.
Zernio also used paid acquisition.
That combination is interesting.
SEO compounds over time.
Paid acquisition provides immediate traffic.
For high-intent keywords, both can work because the visitor already has a problem.
The product did not need millions of visitors.
It needed developers who were actively trying to integrate social platforms.
According to 2026 reporting, Zernio reached approximately $1M ARR within ten months.
The number is reported rather than independently audited, so it should be treated as a founder-story milestone rather than financial disclosure.
Still, the growth shape is notable.
The business reportedly doubled MRR repeatedly during the early phase.
The product expanded from a handful of social integrations to more than twenty platforms.
The company remained much smaller than the venture-backed organization Palet had previously experienced.
That contrast is the real story.
Zernio's technology stack reflects the type of product it is.
Next.js.
MongoDB.
Tinybird.
Vercel.
Cloudflare.
Axiom.
Crisp.
Fumadocs.
The stack is not the moat.
The moat is the accumulated work required to make dozens of unreliable, changing platform APIs feel like one coherent API.
That is what customers are actually buying.
For infrastructure companies, documentation is part of the product.
A developer should be able to discover Zernio through search, read the documentation, copy an example and make the first successful API call quickly.
Every minute removed from setup increases the probability of adoption.
This creates a simple optimization loop:
search → documentation → API call → success → production integration → subscription
The website is therefore not just marketing.
It is part of the product funnel.
Zernio did not begin by saying:
“We will build the ultimate marketing platform.”
It started with:
“Developers have a painful social API problem.”
That is much easier to build.
A narrow problem gives you a narrow roadmap.
A narrow roadmap gives you faster shipping.
Faster shipping gives you earlier customer feedback.
And early customer feedback tells you where expansion is justified.
The irony is that Zernio's small-company strategy may have been enabled by Palet's experience running a larger company.
He already knew what complexity looked like.
He had experienced large teams.
He had experienced venture expectations.
So the appeal of a focused developer product was not theoretical.
It was practical.
The goal was not necessarily to build the next 120-person organization.
It was to build a valuable software company with far less organizational overhead.
Miquel Palet's story has several lessons for technical founders.
The strongest problem statements often come from work you already hate doing.
“Everyone who uses social media” is not a buyer.
“Developers who need social APIs” is.
A small number of highly relevant visitors can beat a huge audience.
You do not need a consumer app.
Removing technical complexity can be extremely valuable.
A 10-person company with strong economics can be more attractive to a founder than a 100-person company with a much larger operational burden.
Zernio is an example of a post-venture founder deliberately moving down the complexity curve.
Palet had already seen the giant version.
He chose the narrow version.
A focused product.
A clear buyer.
A painful problem.
High-intent acquisition.
Self-serve software.
And a business that could reach meaningful revenue without recreating the organizational machine he had already experienced.
That is a very different definition of startup success.