GenAI wrappers are quietly printing millions. Stop theorizing & start building—there’s still time to make a fortune.
When GPT-3.5 and ChatGPT dropped in December 2022, it opened floodgates for new opportunities in text, voice, image, video, and beyond.
Two tribes emerged: those who started building—the makers—and those who objected that building on top of AI models was not defensible—the thinkers.
Spoiler: tons of makers got rich.
It’s a new gold rush.
Opportunities are aplenty. Every corner of the web & the world is ripe for the taking.
And it’s not too late to join the wave. It’s even better than the 2010s SaaS era:
Many of you are skeptics, and rightfully so, so let’s start with a list of successful GenAI wrappers from the GPT-era [1] ⬇️
Bootstrapped
VC-backed:
Other Hot Segments:
These examples show that success is possible—but how can you replicate it? It starts with understanding the common patterns among these winning products.
These makers built something people wanted:
Does it mean it’s easy and trivial? No. Building profitable software is still tough. But it’s never been easier.
Take RizzGPT. It seems trivial, but it works because it’s convenient. People won’t realize they can use ChatGPT for dating tips, but an app spoon-feeding the solution? Game on.
Vatsal Sanghvi’s sums it up:
Users don’t care whether you are building a wrapper or not, as long you solve a problem for them — Users will use your product
Of course, not everyone is convinced. As the success of these wrappers has grown, so have the criticisms. Let’s tackle the most common objections head-on.
Sure, GenAI tech alone isn’t defensible, but moats come later. Use the wow-effect as a lead magnet and monetize fast. Then expand your product with regular features to lock in users.
To see how this objection plays out in reality, consider these case studies of companies that adapted and thrived, despite the perceived challenges:
2024 — Revid.ai by Tibo Louis-Lucas
They generate videos with GenAI, building on top of a lot of common models / APIs.
But they don’t stop here: they integrate with your social media accounts, so you can post directly from Revid. They also have a “worker” that automatically creates and posts videos for you every day. While these automations are not per se AI features, when combined with Revid’s GenAI, it creates a sort of agent, like a content creator who works for you and posts day and night. The combination is powerful. I suspect that these automation features were attempts to add layers of value on top of the GenAI, in order to increase the moat.
These are just smart ways to extend the scope of the product in order to cover more of the user journey, i.e. what the user would do before/after the GenAI part. And these are great ways to reduce friction for your user, therefore increasing the value of your product.
Start with a GenAI entry point, then build a workflow product to cover your user’s journey.
2016 — Doctrine.fr (Google for lawyers, in France)
I worked at Doctrine as a Product Manager and still am a shareholder — so I’m well-versed in the company history, and maybe biased 😁.
Once upon a time there was a $10B market called “legal information” - databases of laws, court decisions, and other legal docs.
In the 2010s, these expensive oligopolistic products looked like peak clunky 90s software.
In the age of Google, this status quo was growingly intolerable.
Came the founders of Doctrine, who very astutely built a Google-like interface for legal information: a unique search bar, letting users search in natural language (👋 goodbye disgusting search forms).
Lawyers loved it. It felt like magic.
Now here’s a secret: Doctrine was a simple wrapper on top of Elasticsearch, a search engine technology.
Incumbents didn’t realize it — and clients didn’t care.
This initial feature was enough for Doctrine to get a growing user base, revenue, and eventually funding.
With the cash, Doctrine hired a bunch of brilliant engineers and built more tech-heavy features, developing its own in-house AI models.
Doctrine started to also tackle more use cases, upstream or downstream of the user journey.
Eventually, the company got acquired 8 years after its founding for 9 figures.
In other terms, a simple wrapper allowed Doctrine to create a wow effect — and then they built a successful workflow product.
The playbook to build a successful wrapper is still the same, be it in 2016 with Elasticsearch, or in 2024 with GenAI models: in the early days, speed beats strategy.
But the “no moat” crowd isn’t entirely wrong either—AI wrappers face fierce competition, especially as more entrepreneurs spot the opportunity. The secret is understanding that you don’t need a moat to start, but you’ll need one to keep growing.
So you can stop after the first few millions and sell your business—but if you’re in for the long-run, to survive the next phase, you’ll need to think about defensibility. In B2C, this often means building a brand. In B2B, it’s about embedding into workflows, as explained by NFX.
Reality check: most people aren’t techies, and even fewer will use open-source models from Hugging Face. Only 43% of 18-29-year-olds had used ChatGPT by Feb 2024 (source).
Yes, someone could copy-paste their Bumble chat into ChatGPT, but they won’t. Convenience wins, and techies underestimate how lazy or uncreative people are.
Sure, it might. But as a wrapper, you’re adaptable. Swap models as better ones emerge—Claude 3.5 Sonnet (new), GPT-5, whatever. Let the AI giants play war games while you focus on serving users.
Companies that got crushed by ChatGPT (like Jasper) built basic wrappers on GPT-3. When ChatGPT (3.5) was released, they got steamrolled — to use Sam Altman’s lingo — because they weren’t adding value. Lesson: Make your product something that improves as foundational models improve, not a product that dreads the next OpenAI release.
Success is still hard, but building profitable software has never been easier:
But yes, failure is a likely option. Even the best indie hackers like Pieter Levels fail most of their ventures, with a 4/70 success rate over 11 years.
Verticalized GenAI Wrappers are at the same time:
I loved this Twitter thread that explained why more and more Gen-Z founders prefer to bootstrap AI wrappers instead of looking for VC money:
I will give it to you, among the list of winners that I shared, a lot of them had a first-mover advantage. I wouldn’t recommend you to build a RizzGPT copycat today.
But you could be the next first-mover.
Because new technologies are released every other week.
Anthropic released its “Computer Use” API 10 days ago (Oct. 22, 2024), it uses computers the way people do—by looking at a screen, moving a cursor, clicking, and typing text.
OpenAI released a public real-time API for its advanced voice mode 30 days ago.
So many use cases that were impossible before are now solvable through a simple wrapper.
And so many more get unlocked every passing day.
Even without new technologies, there is an infinite number of industries, use cases, niches, that are still waiting for their GenAI savior app to come fix their problems.
Problems are everywhere. Hidden in plain sight. Waiting for you to solve them.
I was yet reminded of this underrated truth this week, while hanging out at a friend’s rooftop party in San Francisco.
I met with Alex Andrei, who’s co-founding Claritycare AI. Their founding story was quite simple: they were in the middle of an EntrepreneurFirst batch (startup incubator), looking for problems to solve in the healthcare space.
At the time, Andrei realized that his wife Emelia, a “back office pharmacist” for a health insurance company, was spending a lot of time manually reviewing customer’s requests asking the insurance to pay for their treatment.
Alex, being a technologist, had the idea to use an LLM to solve this problem. It worked like magic. This is how Alex & his co-founder decided to double down on this problem with his co-founder.
I loved this story because it shows that niche problems — with huge market sizes nonetheless :) — are everywhere.
Hidden in plain sight.
Waiting for the right person to discover and solve them.
This could be you. What are you waiting for?
I’m feeling generous, so I’m sharing lists of problems at the end of the article ⬇️
If I had to start an AI Wrapper from scratch, here’s how I’d do it:
Find a Problem in a Paying Niche: Ideally one I know well. More on that below.
Build It With AI Tools: You can literally build a full app (web/mobile) from scratch in a matter of hours with very little knowledge of code:
Build with AI assistants:
Depending on the type of content I’m trying to generate, I’d use the APIs of:
Create a Tailored Interface: I’d make it relevant to the user’s workflow.
Monetize Day 1
Distribute: I’d distribute the product on the relevant online communities (subreddits, discord servers, facebook groups) and, if B2C, heavily through Tiktok (UGC content creators, influencers deals & paid ads)
Exit or Defend:
While each of these points deserves a full article, I won’t pretend I have a magical recipe 😅. If you want to dive deeper into these topics, check out the further readings at the end of my article. I also strongly encourage you to read & watch content by the founders of the successful wrappers I shared. They’re very generous with their advice and often build in public.
The best problem to pick is one you’re facing yourself — scratch your own itch. Otherwise, browse some of these resources for ideas:
Elon Musk dropped out in the 90s to launch a startup because the Internet wave was too big to ignore.
Today, GenAI is undeniable—will you ignore it?
Hey guys, thanks for reading through my rants.
I’m Kamil. I’ve been building in AI for 5 years. I’m a 2x founder and currently Product Manager in a GenAI company: Poolday.ai lets mobile app marketers generate performing video ads in seconds.
I live in San Francisco & my favorite thing is to meet curious, ambitious, and contagiously enthusiastic people.
PS: my next article will be on how to mitigate non-deterministic outputs to build successful GenAI products — ping me if you’re interested about this topic!
[1] These figures are self-reported by founders. True or not, they’re directionally accurate.