You’ve probably heard about Outbid.lol by now.

If not here’s what it is in a nutshell: One page, one list. Pay a dollar more than the person above you and you move up the leaderboard.

A German developer named Jonathan Wilke put it together in about three hours on August 20.

Seven days later it had done $235,153 and got 1.36 million visits.

The top bid hit $17,000 and he received a six-figure acquisition offer before the first day was over.

I sat there with the tab open thinking exactly what you’d think.

1. How did he do this?

2. I could build one this weekend.

3. I opened up Claude Code

Do not do number 3.

I jumped the gun.

Broke my own rules and thought if I could just feed Claude enough signals, copy the idea behind it, maybe, just maybe…

So did about 170 other people. Roughly 140 of them made nothing at all.

They copied the same thing, in the same week and probably spent the same three hours on it.

So what was different? What separated the few that copied it and it worked for them, from those that got zilch?

What my open tabs didn’t show me

I was looking at the surface. The mechanism behind the site, the design, the hype around it, the ICP, etc. Oh yea I was going to grab all the signals, plug them in and poof like magic a money generating site was going to pop out.

Hate to break it to you, it doesn’t work like that.

Everyone else had all the same details, they were using AI too. We’re talking about a sophisticated tech audience on X.

The site itself is also the least useful thing about the story you could take away.

Moving on.

First you need to know a little background for this to make sense.

Wilke launched SupaStarter in August 2022. It’s a boilerplate tech stack you buy it, it saves you the first two weeks of building a SaaS. It’s doing around $13,855 a month.

Four years of that. Same product stacking over and over.

Which means the three hours weren’t speed. His entire business, for four years, has been “ship your SaaS fast.”

So of course he shipped fast. That’s is the thing he sells and what his audience expects.

So the build was never the real story.

Follow the money

The number to look at isn’t the total. It’s the top bid. Seventeen thousand dollars, for a row on a list. 😏

Then I thought wait a minute, Google has been doing this for 25 years!

Selling clicks.

Then I look at who paid it. Codus took the top slot and pulled 13,364 clicks. StartGlobal and Prelint each got over a 1,000. These are dev tools and SaaS companies. Their customers are developers and founders.

Now look at who buys SupaStarter. Developers and founders.

He didn’t find a market. He built a new ad unit and pointed it at an audience he’d been building since 2022.

That’s why bids went to $17,000 instead of $17. Those companies already had budget set aside to reach exactly those people. Nobody needing convincing.

He built the escalation in, too. Once you were in for $300, another $20 to stay above the fold felt obvious. Nobody wants to watch three hundred dollars sink below the scroll.

They think to themselves well we’ve come this far it would be a shame for it to just end.

So he had an audience.

✅ Check.

But that still isn’t the whole story.

And it was the second copy cat site that finally made it click for me.

The copyable half

The second copycat did $37,455. Third did $7,128. Fourth did $2,952.

Then it drops to zero and stays there for about 140 sites.

Every one of those sites worked. The auctions ran. The payments cleared. Nothing was broken (as far as I could tell).

Here’s the part that never made it into any of the hype posts.

The auction mechanism itself doesn’t create attention.

It monetizes attention that already exists. A leaderboard with no spectators is static. Bidders are buying clicks. No traffic, no clicks, no reason to bid, no money.

So there were always two halves. The half you can copy in an afternoon, and the half you can’t.

And I went straight for the copyable half.

Nobody is going to screenshot 4 years of selling a boilerplate SaaS and then say you too can make $200K from a 3 hour build.

They screenshot the Stripe dashboard. Over and over and build the hype. Control the narrative. The algorithm kicks in and starts feeding the cycle.

He took his small trusted audience and exploded it into over a million views.

I know what you’re thinking: I don’t have four years.

Neither did he, when he started.

He spent four years being useful to developers, and then a Wednesday happened. You’re not behind, you need to stop chasing tactics instead of being useful to someone and solve a problem.

Don’t worry, success is not linear. And yes everything can happen all at once, just don’t expect it.

What you actually need to take away

First things first: he’s an evil genius 😈

Second he let himself get copied on purpose. Every clone launch post said “inspired by outbid.lol.” That’s 170 free ads, run by his competition, all pointing back to him. Being easy to copy was the distribution.

Third, and this is the only reason I bothered writing any of this: the mechanic you’re excited about isn’t used up. It’s early and late. Like I said we’ve been selling clicks for 25 years.

Same auction, same weekend, same three hours, pointed at a group of people who already know your name, and you might have a different business entirely overnight.

The copycats didn’t fail because the idea got stale in six days. They failed because they were renting attention they didn’t build.

Which means the boring thing you’ve been doing quietly for the last [insert mind numbing period of time] is not the thing keeping you from the fun project. It’s the thing that makes the fun project work.

So I stopped asking what I should build and started looking at what I have already done and how can I make it fun.

So now we’ve come full circle.

And here’s the order it went:

1. Josh’s little lizard brain saw $100K in 48 hrs I can do that.

2. Claude Code + all the data!

3. Build, build, build

4. Realize you’re copying copycats copying other copycats

5. Put on the breaks

6. Step back and look at the big picture

7. Learn some stuff

8. Scream into the void

9. Start over

10. Create a new thing

So what did I do?

I BuiltFor.lol

For when the internet used to be weird.

You’d click a link with no idea where it would take you.

Maybe it was a dancing hamster.
A pointless game.
A ridiculous quiz.

whatever

A single joke someone turned into an entire website.

It didn’t need a business model, a content strategy, or a 14-step funnel.

Its only job was to make you laugh, send it to a friend, and wonder who had enough time to build it.

Then the internet got “optimized” and we started making “data driven decisionss”.

Yawn 🥱

Every website became a sales funnel.
Every post became a lead magnet.
Every brand started sounding like the same brand.

But .lol domains feel like that old internet.

A place for dumb ideas, inside jokes, mini games, public stunts, pointless competitions, and the stupid stuff your brand is too scared to put on its .com

The internet used to be fun.

I think it can be again.

I think it’s time for the .LOL internet.

Where I’d start if I were you

What, did you think the article was over?

Nope.

Try again.

Start with three questions:

1. Who are you already working with?

   Not “founders.” Not “creators.” The specific group you have already done something for. Wilke’s room was developers building SaaS, and he’d been doing it since 2022.

2. Who already pays to reach those people?

   Wilke never monetized his audience directly. He sold access to it, to companies whose customers are the same developers he’d been serving for four years. Your room is worth money to whoever is already buying ads to get in front of it. Write those companies down. That list isn’t your competition. That list is your customer list.

3. What’s the smallest thing that puts them all in one place?

   The auction was just a mechanism to purchase eyeballs 👀. It doesn’t have to be an auction (although the dynamics work really well). Create a space where people can watch and show up.

Answer those three and your weekend project stops being a lottery ticket. Skip them and you’re gambling at 140 to 1 odds like I did.

The third question is where almost everybody stops, including me.

That’s the whole premise of my Sell before you Build framework: you design a small, shippable asset by working backwards from who actually wants it, instead of building first and hunting for buyers afterward.

If you want a free copy of the Sell before you Build framework leave a comment below telling me what you would do with it and why you think you deserve it for free (you pennypincher.lol)

So why did you do it, Josh?

I skipped right to building for three reasons:

1. Because trends ride or die fast and if you want to ride you have to participate.

2. Challenge myself. How fast can I really get something out there?

3. Take what I did and what I learned and share it with you.

So you’re welcome.

It really is all for you 😘

No-Code Exits is not really about the tools themselves. Anyone can ship in three hours now. It’s about what works, why it works, what tools to use, and how to do it.

Reply and tell me an idea you’re sitting on right now.

What’s stopping you?

In this post: How Faiz Imran pre-sold IntentPost with a landing page and a payment link, reached $120K ARR in six weeks, and sold through Acquire.com after only a few months.

Best for: Builders about to spend a month building something nobody has paid for yet.

You'll learn: The charge-before-you-build sequence, the physical-mail-plus-intent-data workflow, and the four things that make a very young company sellable.

A landing page and a payment link. That was the entire product when IntentPost's first customer agreed to pay $2,500 a month.

Two weeks in.

Nothing built.

By the end of this you will know the exact order Faiz Imran did things in, why the order mattered more than the idea did, and what makes a company only a few months old worth buying at all.

TL;DR

Who: Faiz Imran (@faizimrann on X), 24. His personal site lists six companies acquired, going back to a fragrance product he started at 16.

What: IntentPost, B2B outbound that sends physical mail off digital intent signals. Start with a LinkedIn profile, find the address data, draft the message with AI, send the mail, track delivery, trigger a digital follow-up.

Why it worked: he charged before he built. First customer at $2,500 a month inside two weeks, $120,000 in annual recurring revenue in six weeks, customers including HubSpot, sold through Acquire.com after only a few months of operating.

The channel everybody had already given up on

Every B2B founder is fighting in the same two rooms. The email inbox, where your cold send lands under nineteen others. And paid, where the price of attention goes up every quarter and never comes back down.

Faiz went looking for a where fewer people are, and landed on physical mail. That sounds like a step backwards, and it would have been if he had treated it the way most people treat direct mail: a bulk drop, a printed postcard, a channel you use because it is cheap.

He did the opposite. He kept the modern part and swapped only the delivery. Same intent data that tells you a prospect is in-market. Same targeting off a LinkedIn profile. Same automated follow-up. The only difference is that the touch that starts the conversation arrives as a handwritten letter on someone's desk, in a stack of two or three things, instead of as message twenty in an inbox.

That is the whole product.

The part worth copying: he charged before he built

Here is the sequence:

He set up a landing page. He added a payment link. Then he let the market respond, before the team built the full product.

Within two weeks, one customer paid $2,500 a month.

Read that again, because most founders have the two halves in the wrong order. The normal version is: build for three months, launch, then find out. Faiz ran it as build-last. The landing page was not a waitlist and it was not a survey. It was a checkout.

That distinction is the entire mechanism. A waitlist signup is an opinion, and opinions are free.

A payment is a decision, and decisions cost something. When the first one clears, you are not guessing about demand anymore, and you now know something more useful than "people seem interested."

You know the price, you know who paid it, and you know what you promised them, which means the build has a spec instead of a vision.

The workflow he then built, in order:

• LinkedIn profile as the input. The prospect list starts where B2B targeting already lives.

• Address data lookup. The unglamorous step that makes the whole channel possible.

• AI drafts the message. Not a gimmick, just the thing that makes handwritten-at-scale survive contact with a real pipeline.

• The physical send. Letter or gift, the actual differentiated touch.

• Delivery tracking. So the timing of the next step is not a guess.

• The digital follow-up, triggered off delivery. The email finally works, because it arrives on the day something showed up on someone’s desk.

Built something with no-code or AI that's working? I want to feature you.
NCE features one founder story per post. The bar: real numbers, a named stack, and one transferable lesson other builders can copy this week. If that sounds like what you're building (or recently sold), tell me about it. Takes 5 minutes. I read every one personally.

Six weeks to $120K ARR, then out

From that first $2,500 customer, IntentPost reached $120,000 in annual recurring revenue in six weeks, with customers including HubSpot on the list. Then Faiz sold the company through Acquire.com after only a few months of operating.

Two honest caveats:

The sale price and the buyer are both undisclosed. "Sold" is confirmed by Acquire.com's own write-up and by Faiz's site, which lists IntentPost among his acquisitions. What nobody outside the deal knows is whether it was life-changing money or a clean, sensible number.

And the figures are founder-reported.

What is not in doubt is the shape: a company went from a payment link to a signed acquisition inside a handful of months.

🕵️ Discover profitable startups for sale

• Zero Commission for Sellers: Microns does not charge listing fees or take a commission from sellers, making it an attractive platform for those looking to sell their startups without additional costs.

• Vetted Listings: Each startup listed undergoes a vetting process to ensure it has real revenue and traction, maintaining a quality marketplace for buyers.

• Premium Buyer Access: Buyers can opt for a Premium membership ($299/year) to gain early access to new listings, view private metrics like revenue and traffic, and communicate directly with sellers.

• Diverse Inventory: The platform features a wide range of digital assets, including SaaS tools, content websites, e-commerce stores, mobile apps, and newsletters.

Discover profitable startups for sale

Why a months-old company is even sellable

This is the part that surprises people. Buyers are supposed to want history. Trailing revenue, cohort curves, a year of data. IntentPost had almost none of that, and sold anyway.

It sold because everything a buyer has to check was already legible.

The demand was proven outside the founder's opinion. Someone paid $2,500 a month before there was a product to point at. That is the cleanest possible evidence that the offer works, and it does not depend on believing the founder.

The customer names did the credibility work that time normally does. HubSpot on a customer list at six weeks answers "will real companies buy this" faster than two years of small logos would.

There was no mess to inherit. A few months old means no accumulated pivots, no legacy pricing tiers, no support debt, no half-migrated infrastructure. Diligence on a company that young is short because there is genuinely less to look at.

The workflow was the asset, and it transfers. Intent signal in, letter out, follow-up fires. That runs the same for a new owner as it did for the founder, which is exactly the founder-independence buyers pay for.

Speed did not make this a worse asset. Speed is what kept it clean.

Put a payment link on the thing you were going to spend the next month building. Not a waitlist, not a "would you use this," not a survey. A price and a checkout, in front of ten people who have the problem. If nobody pays, you just bought back a month. If somebody does, you have a spec, a price, and a customer, and you never have to wonder whether the thing was wanted.

Where he is now

IntentPost still runs at intentpost.ai, doing the thing it was bought to do. Faiz has moved on to what his site calls something new for 2026, and he also invests and advises through Sidequest VC.

Six acquisitions on the board at 24, if you take his own accounting, which means the pattern here is not a lucky run at one idea. It is a method he keeps rerunning.

The method is not "have better ideas." It is refusing to spend a month building anything the market has not already paid for.

Subscribe for one founder story like this every week

Got a no-code or AI exit story (or a near-miss) worth telling? I feature one founder per post. Real numbers, named stack, one copyable lesson. Submit yours

P.S.

The reason most builders skip this step is not laziness, it is that the checkout might not convert, and building is a way to postpone finding out.

Six more weeks of building feels like progress and costs you nothing today. It is the most expensive comfort in this business. (You can follow Faiz at @faizimrann on X.)

👋 Enjoyed this post?

Give it a ❤️ and re-stack it ♻️

It helps us reach more no-code builders like you.

In this post: How Adam went from $200,000 in debt to about $50,000 a month by shipping more than fifty small apps and treating each one as a sellable asset.

Best for: Builders tired of betting everything on one product, who want a lower-risk path to income and an exit.

You'll learn: Why a portfolio of small apps beats one big bet, and the app-a-month, ASO-driven machine behind it.

A few years ago, Adam Lyttle was $200,000 dollars in debt.

Today he ships a new iPhone app about once a month, runs a portfolio of more than fifty of them, and pulls in around $50,000 a month.

He did this by building many small things, cheaply and fast, and letting the market tell him which apps to keep.

By the end of this you will know why a portfolio of small apps beats one big bet, and the exact machine Adam uses to turn a weekend idea into either a revenue line.

TL;DR

Who: Adam Lyttle (@adamlyttleapps on X), a solo iOS developer who went from $200,000 in debt to a self-sustaining app portfolio.

What: More than fifty small iPhone apps, shipped at a pace of roughly one a month for years, monetized freemium (weekly subscriptions around $4.99 to $7.99, annual around $29.99), together generating about $50,000 a month. He also buys and transforms existing apps.

Why it works: Each app is a small, self-contained, disposable bet. He validates fast, wins on App Store Optimization, kills the losers cheaply, and pours attention into the winners.

The math most builders get backwards

Most founders put everything into one product. One idea, one codebase, one long bet, and years of their life riding on whether that single thing works. It is the romantic version of building, and it is also the fragile one. If the one thing fails, or cannot be sold, you are left with nothing but hard lessons.

Adam ran the opposite math. Instead of one big swing, he takes many small ones. More than fifty apps, each cheap to build, each aimed at a real search demand, each able to live or die on its own without taking the rest of the portfolio down with it.

When you build this way, no single app has to be a home run. The portfolio only needs a few winners to carry the losers, and it gets more of both by simply swinging more times at bat.

He is not trying to build one valuable company. He is running a factory that produces small, self-contained assets, most of which will be modest and a few of which will be very good.

The machine: one app a month, chosen by the App Store

Here is how he runs it:

He picks ideas the App Store has already validated. The engine is App Store Optimization.

Before building, Adam does keyword research to find high-traffic, low-competition search terms, categories where real people are already searching but no one has built a good app.

He is not guessing what the world wants. He is also not building first and then hoping he can get traffic.

He ships fast and cheap. Over the years his stack evolved from HTML, JavaScript and PHP through Cordova to SwiftUI, each step letting him build native iPhone apps faster.

He generates app icons with a simple MidJourney prompt instead of hiring a designer. The whole point is to get a real, installable app in front of real users at a pace of roughly one a month, so the market can vote quickly.

He monetizes simply and lets the data decide. Apps run on a freemium model with weekly subscriptions in the $4.99 to $7.99 range or an annual plan around $29.99.

His own rule of thumb is blunt: start small and validate quickly. An app that does not find traction is cheap to have built and easy to walk away from. An app that does gets more of his time.

Built something with no-code or AI that's working? I want to feature you.
NCE features one founder story per post. Real numbers, a named stack, and one transferable lesson other builders can copy this week. If that sounds like what you're building (or recently sold), tell me about it. Takes 5 minutes. I read every one personally.

Why this is a build-to-sell strategy, even if you never sell

Here is the part that matters most for anyone thinking about an exit.

A single big product is often the hardest thing to sell, because it is tangled up with the founder, the team, and years of accumulated complexity.

A small, self-contained app is the opposite. It has a clear function, clean books, and no dependency on a big organization to keep running. It is exactly the kind of asset a buyer can understand in an afternoon and operate without you.

Adam knows this from both sides of the table: he does not just build apps, he has bought and transformed one, taking someone else's product and making it his own.

So even though Adam is running his portfolio rather than liquidating it, every unit in it is inherently sellable. That is the superpower of the small-app model.

You are not building one fragile empire that only has value if it keeps growing forever. You are building a shelf of small, independent assets, any one of which you could sell, shut down, or scale on its own terms.

Optionality is the whole point. A portfolio of small things gives you choices a single big thing never can.

🕵️ Discover profitable startups for sale

• Zero Commission for Sellers: Microns does not charge listing fees or take a commission from sellers, making it an attractive platform for those looking to sell their startups without additional costs.

• Vetted Listings: Each startup listed undergoes a vetting process to ensure it has real revenue and traction, maintaining a quality marketplace for buyers.

• Premium Buyer Access: Buyers can opt for a Premium membership ($299/year) to gain early access to new listings, view private metrics like revenue and traffic, and communicate directly with sellers.

• Diverse Inventory: The platform features a wide range of digital assets, including SaaS tools, content websites, e-commerce stores, mobile apps, and newsletters.

Discover profitable startups for sale

What worked: many small, sellable bets instead of one big fragile one

Adam's strategy is simple:

He made his bets small enough to lose. A $200,000 hole teaches you that betting everything on one outcome is how you end up in the hole. Small apps mean small downside per app, and enough shots that the winners show up.

He let the App Store pick, not his ego. ASO keyword research told him what to build. He followed the demand instead of falling in love with an idea, which is why his hit rate across fifty-plus apps is high enough to clear $50,000 a month.

He built assets, not just products. Each app is small, clean, and self-contained, which is the same thing as saying each app is sellable. A portfolio of those is a portfolio of exits waiting to happen, whenever he wants them.

Ship small, sellable, and often, then let the market pick your winners. Instead of pouring years into one big product you may never be able to sell, build many small, self-contained apps aimed at real, searchable demand. Most will be modest. A few will carry the rest. And because each one is small and clean, each is something a buyer could take over tomorrow. A portfolio of small assets beats one fragile empire on almost every axis that matters: risk, learning speed, and the freedom to sell.

Adam got out of debt and to $50,000 a month not by finding the one perfect idea, but by making the cost of trying an idea so low that he could afford to be wrong most of the time.

For a builder, that is the most freeing realization there is: you do not need to be right about the big bet. You need a machine that lets you be wrong cheaply and often, until you are right.

Subscribe for one founder story like this every week

Got a no-code or AI exit story (or a near-miss) worth telling? I feature one founder per post. Real numbers, named stack, one copyable lesson. Submit yours

P.S.

Count how many at bats you give yourself. Most founders take one swing a year and stake everything on it. Adam takes twelve, each one cheap, each one aimed at demand he can see, each one an asset he could sell.

You do not have to ship an app a month.

But if you only ever build one thing, you are betting your whole outcome on being right the first time, which is the one thing almost nobody is.

👋 Enjoyed this post?

Give it a ❤️ and re-stack it ♻️

It helps us reach more AI & no-code builders like you.

In this post: How Preet Mishra sold his bootstrapped startup, Helploom, in about four days and chose the buyer who would grow it over the highest bid.

Best for: Solo and small-team builders who want a fast, clean exit and a product that outlives the sale.

You'll learn: Why diligence-readiness from day one is what makes a four-day exit possible, and why the highest offer is rarely the best one.

Preet Mishra listed Helploom on Acquire.com on a normal day. By the next morning it was under review. By day two, fifteen to twenty buyers were in conversation and four or five had put serious offers on the table. By day four he was in due diligence with the person he had chosen.

Not the highest bidder. The right one.

By the end of this you will know the two moves that let a solo founder sell a bootstrapped business in four days, and why the most important decision in an exit is almost never the price.

TL;DR

Who: Preet Mishra, a solo founder who built Helploom alone, no team and no funding.

What: Helploom, flat-rate customer support software (live chat plus help center). Grown almost entirely through Reddit, listed on Acquire.com, and into the acquisition phase within about four days. Acquired by Sujin, an operator who runs a portfolio of SaaS companies.

Why it worked: He kept the business diligence-ready from day one, so the sale moved at full speed. Then, with several offers in hand, he picked the buyer who would grow Helploom instead of the one who would simply pay the most.

One founder, one clear job

Helploom is not a complicated business to describe, and that is the point. It is customer support software: live chat and a help center, sold on flat-rate pricing instead of the per-seat meter that makes tools like Intercom expensive as you grow.

Unlimited team members, unlimited messages, unlimited customers, one predictable price. There is an AI tier on top and a white-label option for agencies.

Preet built it alone. No co-founder, no funding round, no growth team. Just one operator who understood his product and, more importantly, understood exactly where his buyers already were.

The build: distribution by precision, not by spend

Here is the part most builders skip, so pull out your notepad. Helploom did not grow on ads or a clever funnel. It grew by using Reddit.

Preet went looking for the threads where his customers were already raising their hands: people asking for "Intercom alternatives," people hunting for "free live chat software." He showed up in those conversations, left genuinely helpful comments, mentioned Helploom where it fit, and offered demos.

That was the entire lead generation. No ads, no complex funnel. Just a precise understanding of where his customers were on the internet.

Distribution is not a line item or afterthought.

It is knowing the exact rooms your buyer is already standing in, and being useful when you get there. A solo founder cannot outspend Intercom.

He can out-understand them on one narrow question: where does a frustrated support buyer go to complain, and what do they search for next?

Built something with no-code or AI that's working? I want to feature you.
NCE features one founder story per post. The bar: real numbers, a named stack, and one transferable lesson other builders can copy this week. If that sounds like what you're building (or recently sold), tell me about it. Takes 5 minutes. I read every one personally.

The exit: four days, because the work was already done

When Preet decided to sell, he listed on Acquire.com. The timeline was quick:

• The next morning, the listing was under review.

• Day one, it was live on the marketplace.

• Day two, fifteen to twenty buyers were in conversation, and four or five had submitted serious Letters of Intent.

• Days three and four, he was on a call with his chosen buyer and into due diligence.

From the outside that looks like luck, or a hot market. It was neither. The speed was the payoff of a habit Preet had kept since the beginning: his credentials, his code, his documentation, and his platform access were organized from day one.

When buyers asked the questions that normally stall a deal for weeks, the answers were already sitting in a folder. Nothing to scramble for, nothing to reconstruct, nothing to hunt for.

This is the unglamorous truth of fast exits. They are not won in the negotiation. They are won in the months before, in the boring discipline of keeping the house in order while you build. A messy business can still sell. It just sells slower, for less, to whoever has the patience to dig through the mess.

What worked: he optimized for the right owner, not the biggest number

With four or five real offers in front of him, Preet had the one problem every founder says they want. And here is where he did the thing most people do not.

He did not default to the highest number.

He chose Sujin, an operator who runs a portfolio of SaaS businesses, because Sujin planned to keep Helploom alive and grow it over time rather than absorb it into something else and let it quietly die.

For a founder who built the whole thing alone, that mattered more than squeezing out the last few dollars. The customers would keep getting a product. The thing he made would keep existing.

A higher bid from a buyer who will gut the product is not actually a better deal. It is a bigger check attached to the death of the thing you built. The founders who exit well think about price and steward together, not price alone.

Keep your house in order from day one, and sell to the owner, not the offer. Organize your credentials, code, and docs from the start so a buyer can say yes in days instead of weeks. Then, when the offers come, weigh who will actually run the business alongside what they will pay. The fastest, cleanest exits go to founders who prepared early and chose deliberately.

🕵️ Discover profitable startups for sale

• Zero Commission for Sellers: Microns does not charge listing fees or take a commission from sellers, making it an attractive platform for those looking to sell their startups without additional costs.

• Vetted Listings: Each startup listed undergoes a vetting process to ensure it has real revenue and traction, maintaining a quality marketplace for buyers.

• Premium Buyer Access: Buyers can opt for a Premium membership ($299/year) to gain early access to new listings, view private metrics like revenue and traffic, and communicate directly with sellers.

• Diverse Inventory: The platform features a wide range of digital assets, including SaaS tools, content websites, e-commerce stores, mobile apps, and newsletters.

Discover profitable startups for sale

Helploom lives on under Sujin, getting the long-term owner Preet wanted for it. Preet himself has moved on to the next question, exploring the AI agent space, talking to potential users and mapping the landscape before he commits to a direction.

The same pattern that got him here, understand the customer before you build, is the one he is running again.

Subscribe for one founder story like this every week

Got a no-code or AI exit story (or a near-miss) worth telling? I feature one founder per post. Real numbers, named stack, one copyable lesson. Submit yours

P.S.

The most repeatable line in this whole story is Preet's distribution move. He did not buy attention. He found the exact threads where people were already asking for what he had built, and he was useful there.

Before you spend a dollar on ads, go read where your buyers complain. The answer to your growth problem is usually already available.

👋 Enjoyed this post?

Give it a ❤️ and re-stack it ♻️

It helps us reach more AI and no-code builders like you.

In this post: How Luca Restagno sold Userdesk, a growing AI SaaS, not because it failed but because he was the wrong founder for it, his fourth exit.

Best for: Builders grinding on a product that "works" but somehow always feels like an uphill push.

You'll learn: What founder-product fit is, why it beats product quality, and why selling a good product you don't fit is the strong move.

Userdesk was not failing. Luca Restagno's AI chatbot tool had paying customers, about $1,100 in monthly recurring revenue, and a single enterprise client that added $500 a month on its own.

Most founders would have put their head down and kept grinding.

Luca decided to sell it. Not because the product was broken, but because he had realized he was the wrong person to run it.

It’s his fourth exit.

By the end of this you will understand founder-product fit, why a mismatch kills more products than bad code ever will, and why selling a perfectly good product to the right owner can be the smartest move a builder makes.

TL;DR

Who: Luca Restagno is a serial solopreneur and senior product engineer with four exits behind him (Iterspace in 2021, Hivoe and Inboxs in 2023, Userdesk in 2024).

What: Userdesk, an AI chatbot platform you train on your own website content and embed for customer support. Launched June 2023, grew to about $1,100 MRR, and sold through Acquire.com in March 2024.

Why he sold: Founder-product fit. His audience of roughly 20,000 followers did not overlap with Userdesk's target customer, so his single biggest unfair advantage, distribution, simply did not apply. He sold, and redeployed to a product where it does.

A working product, sold on purpose

Userdesk had real traction. Before it even launched, Luca sold 20 lifetime licenses in 24 hours at a $69 deal. Once live, it climbed to around $1,100 in monthly recurring revenue, and at one point an enterprise customer added $500 a month. This was not a dead product he was dumping. It was a live, paying, growing one.

He sold it anyway, through the standard marketplace process: a letter of intent, a due diligence phase, an asset purchase agreement, and a hand-off to the new owner. A deliberate decision to move a healthy asset to someone who fit it better than he did.

The obvious question is why and how to know when. And the answer is a concept most founders underrate until it has already cost them a year of their life.

The real reason: founder-product fit

Everyone talks about product-market fit.

Almost nobody talks about founder-product fit.

Whether you, specifically, are the right person to build and grow a specific product.

Luca said it plainly: he "didn't feel a great founder product fit." His unfair advantage as a solo builder was an audience of around 20,000 followers, mostly developers.

But Userdesk's real buyers were not those developers. The people who want to train a support chatbot on their website are a different crowd entirely. So the one lever that makes a solopreneur dangerous, the ability to put a product in front of an audience that already trusts you, was useless.

You can have a product that works. Good metrics, growth, revenue, but every unit of growth costs you more than it should, because you are acquiring customers at a more expensive rate than someone else. You can grind through that for a while. You should not grind through it forever.

Built something with no-code or AI that's working? I want to feature you.

AI & No-Code Exits features one founder story per post. Real numbers, a named stack, and one transferable lesson other builders can copy this week. If that sounds like what you're building (or recently sold), tell me about it. Takes 5 minutes. I read every one personally.

Why selling was the right move

A product that does not fit you is not worthless. It is just worth more to someone else. To a buyer whose audience or expertise actually matches Userdesk's customer, the exact same product is a far better fit than it ever was for Luca. Selling it was not quitting. It was moving the asset to where it could do its best work, and freeing its builder to do his.

And Luca did exactly that. He redeployed into Shipped.club, a Next.js boilerplate for developers, a product whose customer is precisely the audience he already owns. Same builder, same skills, same follower count, but now the unfair advantage points directly at the target. That is what a good founder-product fit feels like: the distribution you already have lines up with the customer you need.

This is also why he has four exits and not one exit he is still chasing. He treats products as assets to be matched to the right owner, including himself, rather than identities to be defended to the death. When one does not fit, he sells it and moves to one that does. The serial exits are not luck. They are the natural output of a founder who keeps optimizing for fit instead of ego.

Looking for your founder product fit?

🕵️ Discover profitable startups for sale

• Zero Commission for Sellers: Microns does not charge listing fees or take a commission from sellers, making it an attractive platform for those looking to sell their startups without additional costs.

• Vetted Listings: Each startup listed undergoes a vetting process to ensure it has real revenue and traction, maintaining a quality marketplace for buyers.

• Premium Buyer Access: Buyers can opt for a Premium membership ($299/year) to gain early access to new listings, view private metrics like revenue and traffic, and communicate directly with sellers.

• Diverse Inventory: The platform features a wide range of digital assets, including SaaS tools, content websites, e-commerce stores, mobile apps, and newsletters.

Discover profitable startups for sale

What worked: he optimized for fit, then acted on it

Luca's story has three moves:

He judged the product by whether his advantage applied, not just by the metrics. $1,100 MRR looked fine. The honest question was whether his distribution could actually move it, and the answer was no. That answer, not the revenue, drove the decision.

He sold instead of grinding. A healthy product plus a clear process (LOI, diligence, APA, hand-off) equals a real exit. He took it rather than spending another year fighting his own flow.

He redeployed toward fit. The proceeds and the freedom went into Shipped.club, where his audience is the customer. Selling was not the end of the story. It was a repositioning toward his own strengths.

Founder-product fit beats product quality. Sell a good product you are the wrong owner for, and build your unfair advantage. If the audience you have, or the expertise you own, does not line up with a product's real buyer, no amount of grinding fixes that. The fast path is a clean exit to an owner who fits it, and a redeploy to something where the distribution you already have points straight at the customer.

Luca's own one-line takeaway is the whole lesson compressed: "founder product fit matters much more than I expected." Most builders learn that the expensive way, by spending years on a good product they were never positioned to win with. Luca learned to spot it early, sell without attachment, and point himself back at the thing he was built to sell.

Subscribe for one founder story like this every week

Got a no-code or AI exit story (or a near-miss) worth telling? I feature one founder per post. Real numbers, named stack, one copyable lesson. Submit yours

P.S.

Ask the uncomfortable question about your current project: if a someone with a perfectly matched audience owned your product instead of you, would it grow faster in their hands than in yours?

If the honest answer is yes, you are not the right owner, and that is not a failure.

It is a signal. The best thing you can do for a product you do not fit is sell it to someone who does, and go build the one you were made for.

You can follow Luca at @lucarestagno on X

👋 Enjoyed this post?

Give it a ❤️ and re-stack it ♻️

It helps us reach more AI & no-code builders like you.

Share

In this post: How Spencer Patterson, a non-technical founder, turned a $6,000 Upwork budget into a niche software business and sold it via Flippa for $3.5 million.

Best for: Anyone who thinks they can't build a real software business because they can't code.

You'll learn: How a non-coder built a 95%-margin SaaS, the pricing model behind those margins, and the blunt test he used to know it would sell.

He’s not a programmer, and yet, starting from a $6,000 budget and a freelancer he found on Upwork, he built a software business that ran at 95% margins, paid out thousands of dollars a day, and sold for $3.5 million.

If you have ever told yourself you cannot build a real software business because you cannot write code, this story is for you.

By the end of this you will know how a non-technical founder built a seven-figure asset on a four-figure budget, the pricing model that gave him 95% margins, and the blunt test he used to know it would sell before he believed the revenue.

TL;DR

Who: Spencer Patterson, a non-technical founder who writes about the build at his newsletter, Bootstrapped Bites.

What: A niche paywall and membership platform for content creators, a focused alternative to Patreon for a specific audience. He cannot name it publicly due to the sale terms.

Launched January 2019 on a $6,000 budget, it reached roughly $125,000 to $142,000 in MRR at around 95% margins, and sold via Flippa for $3.5 million.

Why it worked: He picked a niche instead of fighting Patreon head-on, hired the build instead of learning to code, and used a take-rate model that only made money when his customers did.

The $6,000 start

Spencer had an idea for a paywall tool aimed at a specific niche of creators, a group Patreon served poorly, but he could not build it himself, so he did the obvious thing that most non-technical are scared to do.

He hired a freelance developer on Upwork and paid roughly $6,000 to get a first version built. Later, as it grew, he brought on a second developer on a revenue-share agreement who rebuilt the platform properly.

He doesn’t have a computer science degree, no year spent learning to code, no co-founder CTO.

The model: he only made money when his customers did

Most people hear "SaaS" and picture flat monthly subscriptions. Spencer’s business worked differently, and the difference is why the margins were so good.

Instead of charging a fixed fee, the platform took a cut of what creators earned through it. Money moved daily through Stripe and PayPal, with payouts running from roughly $2,000 to $8,000 a day.

Because the software did the same work whether it processed one dollar or ten thousand, the costs barely moved while the revenue scaled, which is how the business ran at around 95% margins.

This take-rate model does something subtle and powerful. It aligns you perfectly with your customers. You are not extracting a subscription whether they succeed or not.

You grow only when they grow, which means your incentives and theirs point the same direction, and every improvement you make to help them earn more directly helps you earn more.

Built something with no-code or AI that's working?

I want to feature you.

No-Code Exits features one founder story per post. The bar: real numbers, a named stack, and one transferable lesson other builders can copy this week. If that sounds like what you're building (or recently sold), tell me about it. Takes 5 minutes. I read every one personally.

The niche was the moat

Notice what Spencer did not do. He did not build a general-purpose Patreon competitor and try to out-feature a funded incumbent. He built for one specific niche that Patreon served poorly, and owned it.

A niche is not a limitation, it is a defense. A big platform cannot tailor itself to every small community, which leaves gaps, and a focused tool that fits one of those gaps perfectly is both easier to grow inside that community and harder to dislodge.

It also makes the eventual sale cleaner: a buyer can look at a defined niche, a loyal merchant base, and a take-rate model, and understand exactly what they are buying. General is fragile. Specific is durable.

The test he trusted more than the revenue

Spensor's own lesson is about product-market fit: "If you can't get people to use the product for free, what makes you think they'll pay for it consistently?"

Not "will they say they like it," not "will they sign up for a trial," but will they actually use it, for free, without being paid or pushed. If the answer is no, no amount of pricing cleverness will save it. Free usage is the honest signal, because attention is a cost even when money is not.

People do not spend time on things that do not work for them. Spencer treated genuine free usage as the green light, and paid subscriptions as the confirmation that came after.

What worked: a non-coder who understood the parts that matter

Strip Spencer's story down and three decisions remain, all copyable by someone who cannot write a line of code.

He bought the build instead of becoming a builder. $6,000 and a clear brief got him a working MVP. The skill that mattered was defining the problem, not compiling it.

He priced to align, not just to charge. A take-rate model gave him 95% margins and put him on the same side of the table as his customers. He won when they won.

He validated with free usage before trusting revenue. The free-use test told him he had something real before the subscriptions confirmed it, which is exactly the kind of clean, provable traction a buyer pays a premium for.

You do not need to code or even use AI to build a sellable asset. Find a niche the big players serve poorly, hire the build cheaply, align your revenue with your customers' success, and validate with free usage.

The sale itself was not lucky. Spencer listed on Flippa and the process took around a year and a half to close, ending in a $3.5 million deal roughly five years after he first spent that $6,000.

A four-figure bet, a focused niche, an aligned model, and enough patience to sell it properly. None of it required him to be a developer. All of it required him to be clear about what he was building and who it was for.

P.S.

The key in this whole story is the one about the $6,000. Most people believe the hard part of a software business is the software, so if they cannot build it, they never start.

Spencer proved the hard part was everywhere else: the niche, the model, the proof, the patience. You can hire someone to code.

You cannot outsource your judgement.

👋 Enjoyed this post?

Give it a ❤️ and re-stack it ♻️

It helps us reach more AI and no-code builders like you.

In this post: How Hirvesh Munogee grew Habit Pixel from $28 to $1,000 MRR in eight months, and why an unsolicited buyer showed up before he was even selling.

Best for: Solo builders with a small app who think they're "too small" to matter to a buyer.

You'll learn: The three legible growth levers that took a habit app to $1K MRR, and why legible growth is what makes a tiny business acquirable.

Who: Hirvesh Munogee, a self-taught solo developer from Mauritius.

What: Habit Pixel, a gamified pixel-art habit tracker (built in Flutter, iOS and Android, freemium at $1.99/month or $33.99/year). It grew from roughly $28 MRR in mid-2025 to over $1,000 MRR by January 2026, past 10,000 installs and around 900 active subscribers.

Why it matters: Somewhere near $1K MRR he received an unsolicited acquisition inquiry, without trying to sell. The reason is the lesson: the levers he pulled are legible and repeatable, which is what makes a tiny app acquirable.

Habit Pixel makes about $1,000 a month. It is a pixel-art habit tracker built by one self-taught developer in Mauritius. By the usual startup math, a $1K MRR app is a hobby, not an asset.

And yet, around the time it crossed that line, someone reached out asking to buy it. Hirvesh was not even trying to sell. He called the inquiry a huge morale boost, and then he kept building.

By the end of this you will know the three levers that took Habit Pixel from $28 to over $1,000 a month in eight months, and why those same levers are exactly what makes a small app something a buyer wants long before the founder has thought about an exit.

The $1,000 app a buyer wanted

A solo developer, a small habit-tracking app, about a thousand dollars in monthly recurring revenue. At that range most founders are not going to put in their bio.

Hirvesh was not running a sale process. There was no listing, no broker, no deck. The interest came to him, unsolicited, because the app had become visibly, legibly good at growing.

That distinction is the whole point of this story. Buyers do not only shop listings. They watch builders who are clearly onto something, and a small app on a clean upward curve is more attractive than a bigger one nobody can explain.

✨ Spotlight

🕵️ Discover profitable startups for sale

• Zero Commission for Sellers: Microns does not charge listing fees or take a commission from sellers, making it an attractive platform for those looking to sell their startups without additional costs.

• Vetted Listings: Each startup listed undergoes a vetting process to ensure it has real revenue and traction, maintaining a quality marketplace for buyers.

• Premium Buyer Access: Buyers can opt for a Premium membership ($299/year) to gain early access to new listings, view private metrics like revenue and traffic, and communicate directly with sellers.

• Diverse Inventory: The platform features a wide range of digital assets, including SaaS tools, content websites, e-commerce stores, mobile apps, and newsletters.

Discover profitable startups for sale

A series of jumps

The growth was real, but it was not smooth, and Hirvesh is refreshingly honest about that. Habit Pixel launched in May 2025 and was making around $28 a month by June. Then it stalled. For months it sat there, the way most apps do.

The turn came in the back half of the year. November took it from roughly $208 to $407 MRR. December nearly doubled again, $407 to $840.

January 2026 pushed past $1,000, with more than two hundred sales in the first two days of the month. Active subscribers climbed alongside it, from a few hundred to around nine hundred, on top of more than ten thousand installs.

In his own words: "Progress is not linear, it’s more short bursts of activity which causes a jump rather than steady progress." That’s an accurate description of how small products actually grow, and recognizing it is what let him keep going through the flat months instead of quitting at $28.

The three levers that made it move

The jumps were not luck. Each one came from a specific, copyable lever.

Lever one: he priced by country. In October 2025 Hirvesh added purchasing-power-parity pricing, adjusting the subscription cost by country instead of charging everyone a US price.

The result was immediate: "Almost immediately, I saw purchases from countries I'd never reached before, like those in Southeast Asia and Latin America."

A global app priced for one country leaves most of the world on the table. He stopped doing that, and the map of his customers changed overnight.

Lever two: he timed his work to the calendar's demand. A habit tracker has two enormous tailwinds a year, and he rode both. He ran a 40% lifetime deal over Black Friday, which brought in around $2,000 that month. Then, right before the New Year's resolution surge, he added twelve languages, using Claude Code to extract and translate his localization files in about ten minutes per language after the first.

He pointed a freshly localized app at the single biggest week of the year for habit apps. January exploded.

Lever three: he chased revenue before he chased polish. This one is counterintuitive and worth quoting directly: "Revenue coming in beats everything else. It's a bit premature optimization to fix something (retention) if you don't see any revenue coming in."

He did fix the early onboarding that was scaring users off, because that was a fundamental leak, but he refused to over-engineer retention before the funnel had proven it could make money at all. Revenue first, as proof. Polish second, as leverage on proof.

Building something with no-code or AI? I want to feature you.
NCE features one founder story per post. The bar: real numbers, a named stack, and one transferable lesson other builders can copy this week. If that sounds like what you’re building (or recently sold), tell me about it.

Why a buyer came knocking at $1K MRR

The buyer did not look at Habit Pixel and see $1,000 a month. They saw a system. Purchasing-power pricing that opens new markets on demand. A product tied to predictable seasonal spikes.

Localization that can be cloned to a new language in ten minutes. A clear, documented growth story posted in public. Every one of those is a lever the next owner could keep pulling. The MRR was small. The mechanism behind it was legible, repeatable, and transferable, and that is what an acquirer actually buys.

This is the inverse of what most builders assume. They think they need to get big before anyone will want their business. The truth is closer to the opposite: you need to get clear.

A small app whose growth a buyer can understand and continue is more acquirable than a larger one that grew by accident and would stall the moment the founder leaves.

Make your growth clear, and you make your business acquirable. A buyer is not paying for this month's revenue. They are paying for a repeatable system they can run without you. Document the levers, the pricing logic, the seasonal playbook, the channels, while you build, and you turn a small app into an asset someone wants, often before you have even decided to sell.

Hirvesh has not sold Habit Pixel. He turned the inquiry into motivation and kept growing, with a stated target of $5,000 MRR in 2026. The acquisition interest was not the win. It was the signal that he had built something with the one quality a small business needs to be worth buying: a growth engine a stranger could pick up and keep running.

P.S.

Notice when the buyer showed up. Not at a big round number, not after a funding announcement, but right as Hirvesh's growth became easy to read from the outside. Your trajectory is your sales pitch, even when you are not selling. Build in public, make your levers obvious, and the right people start watching before you ever raise your hand. (You can follow Hirvesh's build at hirvesh on X

In this post: How Yogesh turned a strange line in his job board's analytics into Promptmonitor, an AI-visibility tool, and sold it for $85,000 in nine days after months stuck at $500 MRR.

Best for: Builders sitting on a flat revenue line who assume a small product isn't sellable yet.

You'll learn: Why your own analytics are the best idea machine you own, and what else buyers pay for besides just revenue.

By the end of this you will understand why the most reliable product ideas are already sitting in your own analytics, and why a buyer will pay a serious premium for a product above what it’s earning.

TL;DR

Who: Yogesh (@yogesharc on X), an indie builder who was running Remote3, a web3 job board, when the idea hit him.

What: Promptmonitor.io, a tool that tracks how your brand shows up in AI answers (OpenAI, Gemini, Claude): your visibility, your competitors, and the sources the models lean on. Listed on TrustMRR on January 5, 2026 for $100,000; sold January 14 for $85,000, the marketplace's biggest acquisition at the time.

Why it matters: The revenue history said "small side project." The category said "front edge of AI search." The buyer, a SaaS portfolio operator, paid for the second thing. Position can be worth more than traction.

The idea was hiding in a traffic report

In May 2025, Yogesh noticed something odd in the analytics for his job board: visitors were arriving from ChatGPT. Not from Google, not from X. From an AI chat window. Most founders would have shrugged and moved on. He built a tool to track it, shipped the MVP in about three weeks, and then watched it sit at roughly $500 MRR for months. Eight months after that first odd referral, he listed the tool on a marketplace and sold it in nine days for $85,000.

Promptmonitor did not come from a brainstorm, a trend report, or an idea-validation sprint. It came from a line in a dashboard that did not make sense. Yogesh's own job board was getting referral traffic from ChatGPT, which meant AI models were mentioning his site to their users, and he had no way to see when, where, or why.

So he built the thing he needed: a tool that shows a business how it appears across AI models, which prompts surface it, how visible its competitors are, and which sources the models are actually pulling from. Three intense weeks of building later, the MVP was live.

Notice what he did not do. He did not survey a market. He did not ask anyone whether "AI visibility tracking" was a category. The market had already tapped him on the shoulder, in his own analytics, with evidence no landing-page test could match: real AI-driven traffic, arriving.

Then it got stuck, and he kept shipping

The launch went the way most launches actually go. First users came in, then nothing. Promptmonitor sat around $500 MRR for months. This is the exact point where most side projects stop: the novelty is gone, the revenue line is flat, and the founder drifts to the next shiny thing.

Yogesh kept shipping. New features every week, making the product a bit better each time. Then one week it clicked. Revenue jumped, then doubled again shortly after. The market for AI visibility had been catching up to the tool the whole time; the weekly shipping just made sure the product was there, ready, when the wave arrived.

Nine days on the market

On January 5, 2026, Yogesh listed Promptmonitor. Asking price: $100,000. Offers started coming in. On January 14, nine days later, he sold it for $85,000 to a buyer building a small SaaS portfolio.

Sit with the arithmetic for a second. A product that spent most of its life around $500 MRR sold for $85,000. On trailing revenue alone, that number is hard to justify. But the buyer was not buying the trailing revenue.

He was buying a working product parked at the front edge of one of the fastest-moving categories in software: how brands show up in AI answers instead of search results.

The revenue had just started to move, the category was heating up by the week, and Promptmonitor was already built, live, and proven with paying users.

That is what "position" means in an acquisition. Traction is what you have already earned. Position is what the asset is pointed at. Buyers pay for both, but when a category is inflecting, position carries the price.

🕵️ Discover profitable startups for sale

• Zero Commission for Sellers: Microns does not charge listing fees or take a commission from sellers, making it an attractive platform for those looking to sell their startups without additional costs.

• Vetted Listings: Each startup listed undergoes a vetting process to ensure it has real revenue and traction, maintaining a quality marketplace for buyers.

• Premium Buyer Access: Buyers can opt for a Premium membership ($299/year) to gain early access to new listings, view private metrics like revenue and traffic, and communicate directly with sellers.

• Diverse Inventory: The platform features a wide range of digital assets, including SaaS tools, content websites, e-commerce stores, mobile apps, and newsletters.

Discover profitable startups for sale

What worked: he let the data pick the product, and the market pick the moment

Strip this story down and two moves remain, both copyable.

Your analytics tab is an idea machine. The strongest validation signal is not an upvote or a survey answer. It is your own data doing something you cannot explain. Yogesh saw AI referrals nobody was talking about, felt the gap personally, and built the tool for himself first. If something in your numbers surprises you, thousands of other builders are staring at the same thing with no tool for it.

Sell the wave, not the spreadsheet. He listed while the category was visibly heating up and his own revenue had just jumped, not after years of grinding the MRR to a "respectable" number.

A rising category with a freshly inflecting revenue line is close to peak leverage for a small asset. Waiting for more traction also means waiting for more competitors, and for the category's novelty, which is part of what the buyer is paying for, to fade.

The exit price is set by where the asset is pointed, not just what it has earned. Yogesh's revenue history said side project. His category said front row of AI search. He got a five-figure exit in nine days because he built where attention was going and sold while it was still arriving. Watch your own data for the anomaly, build the tool you wish existed, ship weekly through the flat months, and when the wave shows up under you, be willing to sell from the front of it.

P.S.

Open your analytics right now and look for insights you can build a tool around. Yogesh's $85,000 exit started as one weird referral source in a job board's traffic report.

You can follow Yogesh at @yogesharc on X.

👋 Enjoyed this post?

Give it a ❤️ and re-stack it ♻️

It helps us reach more AI & no-code builders like you.

In this post: How Umar Khan grew and app to ~1,000,000 users and sold it anyway.

Best for: Builders with real traction but thin revenue, wondering if they have anything worth selling.

You’ll learn: What a buyer actually pays for and why this audience was so hard to monetize.

More users does not equal more revenue. But it turns out a million users is worth something to the right buyer.

TL;DR

Who: Umar Khan, the founder behind ChatFAI, a bootstrapped consumer AI app.

What: ChatFAI lets people chat with AI versions of anime characters, celebrities, and historical figures. It hit roughly 1,000,000 users in a year.

Why it worked: Umar read the moment in history correctly and sold fast instead of holding out.

The rundown: Who those million users were, and why they signed up in the first place.

A consumer "toy" that quietly became an asset

ChatFAI is the kind of product serious people underestimate. You pick a character, an anime hero, a celebrity, a historical figure, and you talk to an AI version of them.

It spread fast growing on trends and hype and pulled in a million users in one year on just the fact of it being fun and shareable.

But underneath the novelty was something a buyer cares about a great deal: retention driven by a real technical edge.

Most chatbots forget the conversation after a few lines. ChatFAI's characters remembered you.

That long-term memory meant the conversations got better the more you used them, which is exactly the kind of feature that keeps people coming back instead of trying it once and leaving.

A closer look at the app

Let us sit with the two numbers, because most founders read them backwards. One app with a million users doing roughly $2K in MRR in monthly recurring revenue.

A lot of founders in this spot freeze. They think, "I cannot sell at $2K MRR, the multiple would be insulting." So they wait, try to crank up monetization, and often watch the growth curve flatten while they do.

Here is what they miss. Consumer AI apps convert roughly 3 to 5 percent of users to paid tiers (analysis across ChatGPT, Claude, Gemini, and Perplexity's 1.8 billion combined users).

At that benchmark, a million users should be printing six figures a month. ChatFAI's $2K implies conversion near 0.04 percent, about a hundred times below the category norm.

You are not selling the $2K. You are selling the distance between 0.04 percent and 3 percent. The buyer isn't paying for what the business earns. They're paying for what the audience should earn under an owner who builds the right machine.

More users was never going to become more revenue on its own. A healthy business needs the conversion machinery too, and buyers know which half is harder to acquire.

One catch: the buyer is also inheriting the audience's problems. Likeness rights, moderation liability, and regulations.

The reason ChatFAI's is even possible: token economics. A bootstrapper can serve a million users on $2K MRR only because inference got cheap, and every AI product's margin is a bet on which model gives you the most per token. Which is exactly what this issue's sponsor helps you with:

Sponsored by ZenMux:

Which AI Model Is Actually Worth Your Tokens?
AI benchmarks only tell part of the story. The real question is: which model would you actually keep using?

ZenMux just launched Token Economics Arena, where you can compare 10+ popular AI models across coding, agents, long-context reasoning, multilingual tasks, and content creation.

What's even better is that this isn't just an experiment. It also makes it much easier for everyone to try leading Chinese AI models like GLM 5.2, Kimi K2.7, Seed 2.1 Pro and Qwen 3.7. During the campaign, many of these models are available at up to 80% off, making real-world testing much more affordable.

Instead of relying on benchmark scores, ZenMux lets real usage decide.

- Every 1M tokens consumed = 1 vote
- Test different models on your own tasks
- Vote for the model that actually delivers the best experience

At the end of the campaign, ZenMux will award the Most Used Model and People's Choice Model, with the winners receiving a crown badge on the platform.

Real tasks. Real usage. Real votes.

Try the Token Economics Arena or check the discounted models

So who are those million users?

Here is the question almost nobody asks about a big user number: who are they, and why did they sign up?

Browse ChatFAI's public character catalog and the answer is uncomfortable. The most-chatted "real person" characters are Pokimane (48,000 chats), Jenna Ortega, Margot Robbie, and Millie Bobby Brown, celebrity likenesses no one licensed.

Alongside them: "Japanese Mom," a "bratty little teen sister" with 3,000 chats, a "popular college student," and personas like "your cheating boyfriend" and a girl whose entire description is "I'm depressed." There's an Adolf Hitler character with 3,000 chats 😯

The demographics behind that demand are well documented. Over 65 percent of AI companion users globally are 18 to 24. Common Sense Media found 72 percent of US teens have used an AI companion, and a Center for Democracy and Technology survey found 19 percent of US high school students have used a chatbot for a romantic relationship (the European Parliament's 2026 briefing on AI companions) collects all of these).

This is the audience: young, often lonely, seeking intimacy or comfort, and mostly without credit cards.

Dr Sam Illingworth, a professor of critical AI literacy, has written the clearest breakdown of what companion chatbots actually do to the people who rely on them, and the short version is: the heaviest users are the most vulnerable ones.

Now the $2K makes sense. It wasn't a missing monitization. The users with the least money were the product's heaviest users, and the users most willing to pay were, largely, willing to pay for one thing: more intimacy.

Companion apps monetize by selling deeper attachment to people who came in lonely. That is the category's engine, and it's exactly the engine an operator with a conscience hesitates to build.

ChatFAI's revenue gap wasn't only a skills gap. It was, at least partly, the gap between what the audience wanted to buy and what a person should sell them.

Which reframes the exit. In late 2024, Character.AI, the category leader, was sued by the mother of a 14-year-old who died by suicide after months of attachment to a companion bot. The case survived a motion to dismiss in May 2025 and settled in January 2026, and Character.AI has since barred under-18s from open-ended chat.

Australia expanded age verification rules to companion chatbots this year. The regulatory floor under this category was visibly cracking. Selling fast wasn't only pricing the moment. Sometimes getting out of a category is the most profitable move.

Built something with no-code or AI that's working? I want to feature you.
NCE features one founder story per post.

Real numbers, a named stack, and one transferable lesson other builders can copy this week.

If that sounds like what you're building (or recently sold), reply to this email and tell me about it. I read every one personally.

Add Your Story

The Exit

When Umar listed on Acquire.com, the response was immediate. In his words, "The first week on Acquire.com brought a flood of interest." Multiple strong bids came in, and the deal closed quickly.

He leaned on the platform's playbooks and webinars to handle buyer conversations, which is the unsexy operational layer that keeps a fast deal from falling apart.

The part to copy is his mindset about timing. Umar's blunt advice: "Time is very important. Close the deal as fast as possible." He sold while ChatFAI was still growing, not after, and he didn’t hold out for a perfect offer.

Umar's speed wasn't impatience. It was a correct read of how consumer AI decays. Sequoia's "Generative AI's Act Two" found AI-first consumer apps hold a median 14 percent DAU/MAU against roughly 51 percent for established consumer apps, and month-one retention of 42 percent versus 63 percent.

Audiences in this category melt. The one exception proves the rule: Character.AI, the companion-chat category leader, holds 41 percent DAU/MAU, which is why the space is winner-take-most and why a memory feature that keeps people returning was ChatFAI's entire defensibility.

An unmonetized audience in consumer AI was a risk every month Umar held it.

What worked: he priced the moment, not his ego

Three moves made this exit clean, and all three are copyable.

He built the one feature buyers reward. Long-term memory was not a vanity feature. It was the retention moat that turned a viral spike into a durable user base. Before you chase your next ten features, ask which single one makes people come back. That is the one a buyer pays for.

He sold on the market's clock, not his own. A million users on thin revenue is a "sell now" signal, not a "wait and monetize forever" one, because the audience and the timing are the assets that decay. Umar took the fair, fast deal and walked away.

He didn't confuse audience with business. A million users is distribution, not a company, and not all distribution is equal. An audience acquired with suggestive characters and celebrity faces is cheap to attract and brutal to monetize cleanly.

Umar's honest options were: build the intimacy paywall and become something he didn't want to be, spend years re-founding the audience, or sell.

Steal this prompt: get the buyer's-eye view of your own app

Paste this into Claude or ChatGPT with your real numbers:

Act as an experienced acquirer of small software businesses. Here are my numbers:
- Total users: [X]
- MRR: [X], trending [up/down/flat] over the last 3 months
- The one feature users come back for: [describe it, or write "none"]
- Category: [e.g., consumer AI, B2B SaaS, newsletter]
- Paid conversion rate: [paying users divided by total users]
- Who my users actually are: [age skew, why they come, what they'd pay MORE for]
- Whether my highest-willingness-to-pay demand is something I'm comfortable selling: [yes/no, what it is]

Benchmarks: consumer AI apps convert 3 to 5% of users to paid; median DAU/MAU is 14%; category leaders hit 40%+.

Tell me: (1) what a buyer is actually paying for here and what they'd ignore,
(2) whether my gap between users and revenue reads as upside or as decay,
(3) whether this is a "sell now," "build the engine first," or "not sellable yet" asset, and why,
(4) whether my audience is an asset, a liability, or a risk-transfer to whoever buys it.
Be blunt. Price the asset, not my feelings.

A million users is not a business. It's an ingredient for distribution.

A healthy business has an audience, a reason they return, a machine that turns attention into revenue, and a monetization path you'd defend.

ChatFAI had the first two, and Umar's clearest-eyed move was refusing to pretend he had the other two. He sold the ingredients to someone who wanted to finish the recipe, took a fair deal while the heat was real, and walked away.

More users does not equal more revenue. But knowing exactly which one you have, and selling it honestly and fast, beats holding a declining asset while you learn monetization the hard way.

👋 Enjoyed this post?

Give it a ❤️ and re-stack it ♻️

It helps us reach more AI & no-code builders like you.

P.S.

The trap in this story isn't the $2K.

It's the million.

A big user number makes founders feel like they are successful.

Run your numbers through the prompt above before you decide you have something worth selling before you decide you're sitting on a goldmine.

You probably have exactly one or two, and the whole game is knowing which.

TL;DR

In this post: How Itay Elgazar sold his AI full-stack app builder, Superdev, for $350,000 just six months after launch.

Best for: Solo and small-team builders with a product that is growing right now, deciding whether and when to sell.

You'll learn: Why listing while revenue is still climbing creates a competitive bidding process, and the three things (preparation, differentiation, timing) to have ready before any buyer asks.

Itay Elgazar started building Superdev in February 2025 on a single bet: that "vibe coding" was about to explode. He was right. Within two months the AI app builder was doing just under $7K in monthly recurring revenue. Within six, it was sold for $350,000. The part most builders miss is that he sold while it was still growing.

By the end of this you will know why selling at the top beats selling at the bottom, and the three things Itay had ready before a single buyer asked. All of them are things you can prepare this week, long before you ever list.

Who: Itay Elgazar, an Amsterdam-based developer and open-source builder (he created the open-source AI toolkit Pezzo) who had already sold one small project, Reclips, through Acquire.com.

What: Superdev, an AI tool that generates full-stack apps (front-end and back-end) from a single interface. Launched February 2025, scaled to just below $7K MRR in about two months, sold for $350,000 through Acquire.com in August 2025.

Why it worked: He listed while growth was still visible, walked in with clean numbers and docs already prepared, and let a competitive process (five offers in two weeks) set the price instead of begging one buyer for an offer.

From a small first exit to a conviction bet

Itay was not a first-time seller. Before Superdev he built and sold Reclips, a smaller project, through Acquire.com. That deal, in his own framing, did not change his life but it changed his perspective. He learned what buyers actually look at, what slows a negotiation to a crawl, and what founders routinely forget until it is too late. He went into Superdev already knowing the exit was a process, not an accident.

He is also a genuine builder, not a prompt-and-pray operator. He had previously released Pezzo, an open-source AI development toolkit. So when AI coding tools started flooding the market in early 2025, he could see the gap clearly: the tools were everywhere, but most were fragmented or too complex. Developers wanted speed and simplicity. Superdev was his answer. One place to generate a full-stack app in minutes instead of stitching five services together.

The build: a thesis, then traction he did not pay for

Itay made a directional bet that the concept of vibe coding, describing what you want and letting AI write the code, was about to go mainstream. He started in February. The bet paid off fast.

The first signups came from Reddit. Developers tried it, gave feedback, and kept coming back. Then it spread the way products do when the timing is right. Influencers on TikTok and YouTube started posting short clips of Superdev building an app in minutes. Those demos reached thousands of viewers and did what no ad budget could. They went viral.

Dozens of early customers became hundreds. Recurring revenue doubled in a few months. By his own public account, Superdev crossed just below $7K MRR within roughly two months of launch. He did not buy that growth. He positioned for it and let the product sell itself.

Built something with no-code or AI that's working? I want to feature you.

NCE features one founder story per post. The bar: real numbers, a named stack, and one transferable lesson other builders can copy this week. If that sounds like what you're building (or recently sold), tell me about it. Takes 5 minutes. I read every one personally.

The decision most builders get backwards

At this point Itay faced the choice every builder with a hot product eventually faces. He could double down and try to scale Superdev into something much bigger, or he could sell while the growth was clearly visible and the market was hot. He chose to sell.

Read that again, because it is the opposite of what almost everyone does. Most founders sell when they are tired, stalled, or out of money, the exact moment their leverage is gone. Itay sold at the top, on purpose, while the chart still pointed up and buyers could see the momentum for themselves. A rising line is the best salesperson you will ever have.

What worked: he manufactured a bidding war instead of begging for an offer

This is the whole lesson.

When Itay listed Superdev on Acquire.com in August, interest came fast. Within two weeks, five Letters of Intent landed in his inbox. About a week and a half later the right buyer stepped forward and the deal closed. Clean, quick, final. $350,000 for a business he had started six months earlier.

Five offers is not luck. It is what happens when a desirable asset meets a prepared seller and a competitive process. The price was not set by one buyer's lowball meeting a founder's desperation. It was set by five buyers competing in the open, which is the only reliable way a small business gets a real multiple. At roughly $7K MRR, $350,000 lands near a 4x annual-revenue valuation, the upper band for a bootstrapped product, and he got there because buyers were bidding against each other.

Underneath the outcome were three things Itay had ready before anyone asked, drawn straight from his own post-exit lessons:

Preparation. His numbers and documentation were ready before buyers requested them. Nothing kills trust and momentum like a founder scrambling to assemble financials mid-negotiation.

Differentiation. Superdev had a clear, one-sentence reason to exist: full-stack apps from a single AI interface. A buyer could grasp the value in seconds.

Timing. He sold while growth was visible, which is exactly what gives a seller options. Visible momentum is leverage. A flat or falling chart is the opposite.

List while the line is still going up, and walk in with your numbers already done. The founder who prepares the data room before there is a buyer, and sells into momentum instead of out of exhaustion, is the one who gets a competitive process and a real price. The exit is not the reward for surviving. It is a move you make from strength.

For Itay, the sale was not an ending. It gave him resources and freedom, and he is already eyeing the next build with bigger ambition. In his framing, exits are not about closing doors. They are about opening new ones. He said the quiet part out loud on X (@elgazar_itay): he sold Superdev for $350k, started it back in February believing vibe coding was going to explode, and was proven right.

Got a no-code or AI exit story (or a near-miss) worth telling? I feature one founder per post. Real numbers, named stack, one copyable lesson. Submit yours

P.S.

Itay sold while Superdev was still climbing. Most builders wait until the climb is over, then wonder why nobody is bidding. If your product is growing right now, that is not the reason to hold. It might be the reason to start preparing.

👋 Enjoyed this post?

Give it a ❤️ and re-stack it ♻️

It helps us reach more AI builders like you.

By the end of this you will know the one mistake that almost cost Kamil everything, and the two moves that turned a dying product into a clean exit. Both are things you can copy before your own runway runs out.

TL;DR

Who: Kamil Zowczak, a former startup project manager who quit, moved to Bali, and taught himself to code.

What: Copycopter.ai, an AI tool that turns text into viral TikToks and Shorts. Scaled 30x in under a year to roughly $800 MRR, then sold through Acquire.com to Social Jool LLC.

Why it worked: He stopped trying to save the product and started trying to save the asset. Listing early, before he was fully out of cash, is what got him a buyer instead of a shutdown.

From managing other people's startups to betting on his own

Kamil spent years as a project manager inside startups, watching other founders take the swing. Then he quit, moved to Bali, and lived off his savings while he taught himself to code. No team. No funding. No safety net beyond the number in his bank account, and that number only moved one direction.

He had one idea worth building: most people cannot make video, but everyone needs it. So he built Copycopter, an app that turns a block of text into a short, punchy video ready for TikTok and Shorts. He gave it away free to pull in the first wave of users, and went all in on the build.

The build: an AI video app, and an accidental audience in China

Here’s what Kamil built and how it spread, but he did not disclose the underlying tech stack.

• He built Copycopter solo, coding it himself rather than hiring it out.

• The core loop is text to video: paste words, get a reel.

• He launched on Product Hunt and got the usual launch-day attention.

• Then something he never planned for happened. After a post on X, the app went viral on Douyin, the Chinese version of TikTok, and a wave of Chinese creators started using it.

Kamil did not buy that audience or engineer it. It simply arrived. And an unplanned foreign user base is both a gift and a trap. Usage spikes, the charts look incredible, but you have no real line to the people using you and no fast, clean way to turn them into paying customers.

Viral attention is not the same thing as a business, and the gap between the two is where a lot of solo founders quietly bleed out.

Built something with no-code or AI that's working? I want to feature you.

NCE features one founder story per post. The bar: real numbers, a named stack, and one transferable lesson other builders can copy this week. If that sounds like what you're building (or recently sold), tell me about it. Takes 5 minutes. I read every one personally.

The traction, and the wall he hit

The growth was real. Copycopter scaled roughly 30x in under a year. By the time it changed hands it was generating about $800 in monthly recurring revenue.

$800 MRR is proof, and proof is the thing a buyer actually pays for. It says people handed over money, more than once, for a thing one person built alone. That signal is worth more on an acquisition listing than a slick deck or a big vanity-metric chart ever will be.

The problem was never the product. It was where Kamil spent his hours. In his own framing, he spent too much time building and not enough time marketing, and he ran out of money before the revenue could catch up to his burn.

This is the most common way a promising no-code or AI product dies, and it has nothing to do with the code. The build is always one more feature from being ready. The bank balance does not care how close you are.

What worked: he sold the asset before the asset died

Most founders in Kamil's spot do the thing that feels responsible but can kill a project. And a dead product is worth zero. A small, live, paying product is worth real money to the right owner.

Kamil had to make a choice.

Move one: He posted about his situation on X instead of hiding it. Acquire.com's CEO, Andrew Gazdecki, saw the post and helped him list the business for free. The instinct most founders have, to keep the struggle private until they have "figured it out," is exactly what can destroy an exit window. Kamil traded a little pride for a live listing while the product was still breathing.

Move two: he held when the first deal collapsed. The first negotiation fell apart. This is the moment desperate sellers cave, because any exit starts to look better than no exit, and a patient buyer can smell that fear from across the table. Kamil held his position. When the right buyer appeared, the deal closed in 24 hours, and Social Jool LLC took over Copycopter.

Kamil treated Copycopter as an asset to be transferred, not his baby to be saved. Assets have buyers. The founders who exit cleanly are almost always the ones who made that mental switch before the cash flow forces them to.

List before you are desperate, and qualify the buyer before you fall in love with the offer.

If your product has even a few hundred dollars of real MRR and your runway is shrinking, start the sale process now, while you still have the leverage to walk away from a bad buyer. The exit you negotiate at $800 MRR with three months of cash left will always beat the fire sale you take with two weeks left.

Kamil walked away solvent, with a closed exit on his record and the most valuable lesson a solo founder can learn already paid for. For someone who moved to Bali with just his savings and a code editor, that is not a failure. That is a builder who now knows exactly what he undervalued the first time: distribution, and a clear read on when to sell.

Spotlight

🕵️ Discover profitable startups for sale

• Zero Commission for Sellers: Microns does not charge listing fees or take a commission from sellers, making it an attractive platform for those looking to sell their startups without additional costs.

• Vetted Listings: Each startup listed undergoes a vetting process to ensure it has real revenue and traction, maintaining a quality marketplace for buyers.

• Premium Buyer Access: Buyers can opt for a Premium membership ($299/year) to gain early access to new listings, view private metrics like revenue and traffic, and communicate directly with sellers.

• Diverse Inventory: The platform features a wide range of digital assets, including SaaS tools, content websites, e-commerce stores, mobile apps, and newsletters.

Discover profitable startups for sale

🤔 What are you working on?

Whether it’s pre-revenue, pre-build, or just an idea, we’d love to hear about it.

Share your Story

P.S.

The single most important to remember from Kamil's story: he spent too much time building and not enough time marketing.

Print it.

Tape it over your monitor.

By the end of this you'll know the exact play she ran, why buying beat building for her, and the one question to ask before you ever build another thing from scratch.

TL;DR
- Who: Gabriella Rosen, a partner at an email-outreach startup who'd never "founded" anything from zero.
- What: Nomad Cloud, a digital-nomad newsletter she bought on Acquire.com, grew to thousands of dollars a month, and resold for an 18x return in under a year.
- Why it worked: She didn't invent an audience. She bought a neglected asset and bolted her one unfair advantage, targeted email distribution, onto it.

The founder who skipped the founding part

Gabriella was a partner at EOC, an email-outreach company. Her whole job was getting the right message in front of the right inbox at scale. That's a distribution superpower, and most people who have one waste it building an audience from nothing.

She did the opposite. Instead of starting a newsletter and grinding for two years to get subscribers, she went shopping for one that already existed and was underperforming. Nomad Cloud was a digital-nomad newsletter listed on Acquire.com. The audience was real but growth had stalled. That gap between "this has potential" and "the current owner can't unlock it" is the whole opportunity.

She bought it. Then got to work.

What she actually did

Strip away the 18x ending and the play is clean enough to copy:

• Sourced an undervalued asset, not an idea. She browsed Acquire.com for a business with a real audience and a fixable problem, instead of betting on something unproven she'd have to build.

• Bought the thing she could most improve. Nomad Cloud's weakness was growth. Gabriella's strength was growth. She bought the exact asset where her advantage mattered most.

• Pointed her unfair advantage at it. She used EOC's email-outreach tooling to drive highly targeted subscribers into the newsletter. This is the part nobody else could copy easily, and it's why she bought instead of built.

• Systematized the boring part with AI. She ran content with an assistant plus ChatGPT, so producing the newsletter every week stopped being a bottleneck and started being a system.

• Sold it back into the same marketplace. Once it was bringing in thousands of dollars a month, she listed it on Acquire.com again and exited, with an acquisition manager handling the deal.

Notice what's missing: no product to invent, no two-year audience grind, no code. The asset already existed. She supplied one ingredient it was starving for.

Want more breakdowns like this, with real builders, real numbers, and one copyable move? NCE sends one every week.

Subscribe →

The numbers she disclosed

Let me be straight about what's public and what isn't. Gabriella hasn't published the exact dollars she paid or the exact price she sold for. Here's what she did put on record:

• 18x. She sold Nomad Cloud for eighteen times what she paid for it.

• Under a year. The full buy-to-sell cycle took less than twelve months.

• Thousands of dollars a month. Under her ownership, the newsletter grew to that revenue band before she exited.

An 18x return in under a year, and it's a multiple most build-from-scratch founders never see no matter how long they grind. The reason it was reachable: she didn't pay for an audience with two years of her life. She paid a one-time acquisition price for one that already existed, then made it worth far more.

Why it worked: the pattern you can lift

Here's the principle underneath the flip, and it survives even if you never buy a newsletter in your life.

She matched her single strongest skill to an asset whose single biggest weakness was that exact thing. Her edge was distribution. She bought a product that had everything except distribution. That overlap is the entire game. A great operator pointed at a neglected-but-real asset will almost always beat a mediocre idea built from zero, because the hard part, proving people want it, is already done.

The second principle is about speed. Building takes years partly because you spend most of that time discovering whether anyone cares. When you buy a business that already has paying attention, you skip straight to the part where you add value. Gabriella compressed what's usually a multi-year arc into under twelve months because she started on second base.

And the AI piece matters more than it looks. By handing content production to an assistant and ChatGPT, she made the newsletter run like a small machine instead of a second job. That's what made it both profitable to hold and clean to sell. Buyers pay more for a system than for a hustle that lives in the founder's head.

The one question to ask this week: Before you build your next thing, ask "is there a version of this I could buy instead?"

A quick peek from my own build 👷

I running a cohort, and I'm shipping my own product alongside everyone else.

The pain I'm solving is real and boring: small newsletters struggle to find sponsors who actually pay.

How do I know it's real? Because I found out during my research someone is already selling a version of it.

Most builders see an existing competitor and panic. I did the opposite, the same way Gabriella read an existing-but-stalled asset as opportunity. An existing player is proof people will pay to make this problem go away. The market already said yes; I don't have to guess.

The difference is the approach. The versions out there is passive Passionfroot, Paved, etc: list it yourself and wait. Mine goes the other way. It actively finds sponsors already buying placements in your niche, writes the outreach, and helps you book the deals.

I'm still deep in outreach right now, talking to real potential buyers before I build the whole thing.

If finding sponsors is a pain you feel, send me a DM →

Back to Gabriella.

She proved something most builders never test: that the skills you already use at your day job can be turned into an ownership stake, not just a salary. She took an outreach skill, rented it to one neglected newsletter for under a year, and walked away with an 18x return and a repeatable playbook.

The interesting question isn't whether Nomad Cloud was special. It's how many more underpriced, distribution-starved assets are sitting on marketplaces right now, waiting for the one operator whose superpower is exactly what they lack.

Subscribe to No-Code Exits for more →.

Built (or bought) something with no-code/AI that's working?

I want to feature you.

If you're building (or recently sold), tell me about it.

Share your story →

P.S. The detail worth stealing: she bought the asset on the same marketplace she later sold it on. Acquire.com was both her sourcing channel and her exit.

If you've never browsed the listings, do it once this week, not to buy, just to retrain your eye to see businesses as things you can acquire and improve, not only things you have to build.

Gabriella Rosen is Head of Partnerships at Email Outreach Company and was a partner on Nomad Cloud. Find her on LinkedIn.

The Buy-Fix-Flip Playbook

Skip the two-year build. Buy a real-but-stalled online asset, point your one unfair advantage at it, and resell it for a multiple. Your AI runs the play with you.

Copy how Gabriella Rosen bought a digital-nomad newsletter on Acquire.com, applied her email-outreach edge, and flipped it for 18x in under a year. This is the repeatable version of that move, turned into something your AI assistant runs with you, step by step.

What this is

Most people think the only path to an exit is building something from zero and grinding for years. There is a faster path: buy an asset that already works but is underperforming, fix the one thing holding it back (the thing you happen to be great at), and sell it for more than you paid.

This playbook is runnable. You do not read it and try to remember it. You paste it into an AI assistant and it becomes your Flip Operator, walking you through all six phases, asking you the right questions, and building your plan with you as you go.

It works in Claude, ChatGPT, Gemini, Copilot, or any modern AI chat. No tools, plugins, or setup required.

How to run it (3 steps)

1. Copy everything inside the box below

2. Paste it into a fresh chat in Claude, ChatGPT, Gemini, or any AI assistant.

3. Answer its questions. It runs one phase at a time and waits for you. By the end you will have a complete, personalized Flip Plan you can act on.

Tip: keep the whole thing in one chat so it remembers your answers. If your AI can browse the web, tell it so in your first reply and it will pull live listings. If it cannot, it will hand you the exact searches to run yourself.

▶ The runnable playbook (copy everything below and paste in AI Chat)

You are my Flip Operator: an expert acquisition entrepreneur and…

Read more

Week 1 is done. We haven't built a single product yet. On purpose.

Here's the thing most "build with AI" challenges get wrong: they start with an idea, build the MVP, and then go looking for customers. That sequence is exactly why most of them die. The build was never the hard part. The customer is the hard part.

So Week 1 has no MVP. It's five days of the unglamorous work that decides whether the next three weeks are worth doing at all.

This is the system.

In this post

• What this whole thing is

• The 5-day system (Days 1–5)

• What actually happened this week

• (join the cohort) What I learned — the three lessons that changed the prompts mid-week

• (join the cohort) What's next — Week 2 and the build decision

• (join the cohort) How the cohort works + how to get in

What this is

For 30 days I'm running a public experiment: can one operator, using an AI builder, take an idea from "nothing" to "a real, sellable asset" — and document every prompt, every workflow, every honest result along the way?

The sponsor is Atoms. The angle is the one I care about: not "build fast," but "build something someone would actually pay for.

Inside the cohort, I drop a prompt every morning. Members run it on their own idea, in any AI tool they want, and report back in our private chat.

Week 1's job: find something worth building. Here's how it broke down.

The 5-day system

Day 1 — Find the pain first. No idea-picking. The prompt does real web research — Reddit, Hacker News, Indie Hackers, niche forums, etc and surfaces markets where real humans are actively complaining about a problem, each pain quote backed by a clickable source URL. Then, and only then, it checks which of those markets you have the credibility to serve.

Day 2 — Lock the ICP, schedule the interviews. Most Day 1 outputs hide two or three different buyers inside one fuzzy "ICP." Day 2 forces you to pick one specific ideal person: role, stage, tool stack, revenue signal. Then generates a 5-question Mom Test interview script (past behavior only, no pitching) and finds 10 real people you can message today.

Day 3 — Shape the offer, find the exact people, write the outreach. Turn the pain into a one-sentence offer in the customer's own words. Decide service-first vs software-first (spoiler: it's almost always service-first). And find the people in active pain posting right now asking how to solve this.

Day 4 — Build the validation page. Not the product a single-screen validation page with an opt-in or a pre-sale. The smallest thing that answers: do these people want this enough to give me their email or their money?

Day 5 — Drive traffic. Read the signal. Get the page in front of the people. Read the conversion against your validation bar. Validated, pivot, or kill.

What actually happened this week

I ran the whole system on myself first, live, before sending it to the cohort. It did not go the way I expected — and that's the interesting part.

Day 1, I expected the AI to hand me markets adjacent to my own world: creator tools, no-code, AI dev stuff. Instead it surfaced seven verified markets ranked by pain depth, and the top two were healthcare problems I have zero business touching. Authorization for clinics, after-hours charting for doctors. Real pain, real money, real urgency. Regulation mess. But there is the potential if you want to go through the headaches. I dropped them both. More on why in a second.

In the cohort chat, the same pattern played out. One member ran Day 1, got a clean result with five sourced pain quotes, then ran Day 2 and locked an ICP so sharp I could picture the exact person. Another member's first pass produced a list of "people in the market" that turned out to be all the wrong people — and watching them catch it became the lesson the whole cohort needed.

Today’s Friday, and over the weekend I’ll have outreach going out to real humans, and the first conversion signals coming back.

What I learned

1. Credibility > pain every time

The AI ranked my markets by pain depth. Prior authorization scored 8.6 out of 10. Newsletter sponsorship operations, what I actually picked scored 7.6, the lowest on my list.

I picked the lowest-scoring one and here’s why:

Pain depth 8.6 × my credibility in healthcare (0) = 0
Pain depth 7.6 × my credibility in newsletters (10) = 76

I run a newsletter. I know this pain and I've felt the "I have an audience but can't find good sponsors" pain personally.

A high-pain market you can't credibly serve is worth zero. A medium-pain market where you speak the language, know the people, and feel the problem is worth everything. This is why the prompt does pain first and credibility second — but credibility is the filter that actually helps you decide what to build.

2. The "solved-it experts" trap

Day 3, I asked the AI to find people in my market to reach out to. It handed me an impressive list: operators with polished sponsor pages, agencies, repeat advertisers. Famous names.

Every one of them was wrong.

Those are solved-it experts. They already fixed this problem. They don't feel the pain anymore.

The people you want are active pain owners — posting right now, in the last few months, asking "how do I find sponsors," "I'm stuck," "I've tried Paved and it didn't work." I had to push the AI through two rounds of correction before it stopped giving me the impressive people and started giving me the stuck people. Then I rebuilt Day 3's prompt so the cohort wouldn't hit the same wall.

3. Service-first beats software-first for validation

Every first-time builder's instinct is to build software. A dashboard, a CRM, an app. It's almost always too late in the workflow to validate anything fast.

The fastest validation is a manual service you can deliver by hand this week. When I ran my own offer through the decision, the wedge wasn't "a sponsorship CRM." It was "I'll find 25 sponsors already buying newsletter placements in your niche, write the outreach, and help you book the calls." A done-by-hand service I could start Monday. If people pay for that, then you build the software that scales it.

You learn more delivering it by hand to three customers than you'd learn building it for an imaginary hundred.

What's next

Week 1 was about finding something worth building. Week 2 is about building it — but only for the members whose Day 5 signal says to.

That's the rule the cohort runs on: the validation page result decides whether you build the MVP, iterate the offer, or kill it and re-pick. No building on a hunch. The signal votes.

For me I’m going with the newsletter-sponsorship and pitch it to real people. Next week if it validates I take it to a working MVP🤞

Week 3 is real traffic and real money. Week 4 is the teardown.

How the cohort works + how to get in

The day-by-day system, the prompts, the private chat, and the build logs all live inside the cohort — and it's capped at 100 paid subscribers.

If you're already a paid No-Code Exits subscriber, you're in. Check the chat for the daily access links — Week 2 kicks off Monday.

If you're not paid yet, this is the window. The cohort runs through the end of June, the post-cohort playbook drops behind the paywall after, and the next run won't be the same experiment.

Upgrade to paid and join the cohort →

Not ready for the cohort but want to try the builder? The article kickoff has a referral link with $26 in free Atoms credits (not an affiliate link) enough to run the Day 1 research and stand up a validation page before you spend anything.

Grab $26 in free Atoms credits →

That's Week 1. Five days, no MVP yet, and a much clearer answer to the only question that matters before you build: does anyone actually want this?

See you Monday.

— Josh

If you got something out of this consider subscribing. Paid gets you into the cohort, free keeps you on the new weekly No-Code Exits (+ re-launch coming shortly)

Featured Sponsor placement. AI & No-Code Exits only takes sponsors I'm actually using. Atoms paid for the slot. The 30-day cohort, the system, the prompts, and this recap are NCE editorial — not Atoms's.

For this 30-day shipping experiment, I decided to explore a product around newsletter creator sponsorship and growth operations.

On paper, it made sense.

Newsletter creators are growing real businesses. Sponsorships are one of the cleanest ways to monetize an audience. The tooling is still messy. Most creators are stitching together Substack, beehiiv, Passionfroot, Paved, spreadsheets, Stripe links, email templates, and manual follow-up.

So my first instinct was obvious:

Build something that helps newsletter operators manage sponsorships better.

A sponsorship CRM.
A booking workflow.
A sponsor operations dashboard.
A way to track assets, payments, scheduling, approvals, and reporting.

That sounded useful.

But Day 2 reminded me why “sounds useful” is dangerous.

Because the first version of the customer I picked was wrong.

My first mistake

I started by looking at successful newsletter operators.

People with sponsor pages.
People already selling ads.
People with polished media kits.
People with clear packages, pricing, and sponsor workflows.

They looked like the perfect market.

But then I asked the question I should have asked earlier:

Do these people actually have the problem?

And the answer was probably no.

At least not the urgent version of it.

The more I looked, the more obvious it became that many of the most visible newsletter operators had already solved the core problem. They had inbound interest, sponsor pages, repeat advertisers, agencies, or enough reputation that sponsor ops was more of an optimization problem than a painful daily wound.

They might be great expert interviews.

But they are not the best early customer discovery targets.

That distinction matters.

An expert can explain how the market works.
A customer in pain can tell you what they are already trying, where it breaks, and what they might pay to fix.

I was mixing those two up.

The real pain moved

The first idea was:

Newsletter creators need help managing sponsors.

The better version became:

Newsletter creators need help finding, pricing, and closing the right sponsors in the first place.

That is a very different product.

A CRM helps once you have sponsor demand.
A booking system helps once people are trying to book slots.
A reporting dashboard helps once campaigns are running.

But most newsletter creators are stuck earlier.

They are asking:

Who should I pitch?
Am I big enough to get sponsors?
What should I charge?
Should I use Paved, beehiiv Ads, Passionfroot, cold outreach, or wait for inbound?
Why do I have subscribers but no sponsor pipeline?
How do I get the first sponsor without looking desperate or guessing?

That is a pain.

Not “my sponsor workflow is too complicated.”

More like:

“I have an audience, but I don’t know how to turn that audience into direct sponsor revenue.”

And that problem shows up across a wide range of newsletter sizes.

Tiny lists with a few hundred subscribers are asking if they are sponsor-ready.

Newsletters around 1,000 to 3,000 subscribers are asking how to land their first sponsor.

Operators with 8,000, 20,000, 65,000, and even 200,000 subscribers are still asking how to get consistent direct sponsors.

That was the part that surprised me.

Audience size helps, but it does not automatically create a sponsor pipeline.

My sharper ICP

So I changed the ICP.

The first ICP was too polished:

Founder-led B2B newsletter operators already monetizing with sponsor slots.

The revised ICP is much better:

Niche newsletter operators with 1,000 to 100,000 subscribers who want direct sponsorship revenue but do not yet have a reliable sponsor pipeline, and whose founder or editor personally handles sponsor outreach, pricing, and follow-up.

That is tighter.

It focuses on people who are still doing the work themselves.

They do not need enterprise ad ops software.
They do not need another empty profile page on a marketplace.
They do not need a fancy dashboard for sponsor volume they do not have yet.

They need the next sponsor.

Or the first sponsor.

Or a believable answer to: “Who should I even contact?”

What the research showed

The clearest pattern from the research was that creators are not mainly complaining about managing too many sponsors.

They are complaining about not knowing how to get sponsors.

Some are already listed on marketplaces and still getting nothing.

Some have good open rates but no direct advertiser relationships.

Some know their audience should be valuable, but they do not know which brands to pitch.

Some are paying monthly newsletter costs and making zero dollars back.

Some are unsure if they are too small.

Some are afraid of charging too much.

Some are probably charging too little.

The second pattern is that pricing and acquisition are connected.

You cannot confidently pitch a sponsor if you do not know what you are selling.

A newsletter creator needs more than a list of companies.

They need to know:

Why this company is a fit.
What offer to lead with.
Which buyer to contact.
What placement to sell.
What proof to include.
What price to test.
What to say in the first message.
How to follow up without sounding generic.

That means the MVP should probably not be software first.

At least not yet.

The MVP changed

The first product idea was some kind of sponsor management tool.

The better wedge is…

Article continues below for those that join the cohort 👉

Read more

100 paid NCE subscribers. 30 days inside atoms. No MVP this week — just finding the real pain.

I ran the Day 1 prompt on myself before I sent it to the cohort. Posting what I got, what surprised me, and why I'm picking the LOWEST-scoring market the AI surfaced.

The prompt

I'm not asking cohort members to pick a market this week. That's the friction point. People stall on "what should I build?" Instead, I built a 3-phase prompt that does the picking for them.

Phase 1: The LLM searches the web for real pain. Reddit, Hacker News, Indie Hackers, niche forums, G2/Capterra reviews. Every quote needs an inline source URL pointing to the exact thread. If the LLM can't source a quote, it drops it. If a market has fewer than 5 verified quotes, the LLM drops the entire market.

Phase 2: The LLM asks me 3 credibility questions. Where do I have operator experience? Who do I know in this market? Where have I felt the pain myself?

Phase 3: The LLM returns my top-ranked market + 10–30 specific outreach targets + an MVP-v1 hypothesis + a 7-day plan.

End of Phase 1, the LLM outputs an Honesty Check showing how many quotes it sourced versus how many it dropped. That's the canary for whether the LLM is faking it.

What I expected

I expected the LLM to reflect my obvious interests back at me. I've spent years operating newsletters, building no-code SaaS, and acquiring digital media. I figured I'd get markets adjacent to my hobby — AI dev tools, creator economy stuff, no-code platforms.

That's not what happened.

What actually happened

The LLM started with 10 candidate markets, dropped 3 (quote evidence too promotional, ICP too broad, fewer than 5 verifiable human voices), and gave me 7 survivors and then…

Read more

This is a featured post — Atoms. This post is a paid placement, and it’s the kickoff of an experiment I’m running for the next 30 days.

I still keep getting asked the same question.

“What’s the AI builder you’re using right now?”

For most of the last year it was chatGPT and a slurry of other tools. Then came Claude and changed everything.

But there are still a lot of drawbacks

• Steep learning curve for beginners

• Everything has to be built from scratch

• You have to design your own systems and run your own tests.

Then I received a sponsorship request from Atoms and checked it out. So far it’s impressive. And in the next 30 days I’m taking it through the full gauntlet and documenting the whole process building, breaking, shipping, and trying to make real revenue with it.

And I’m inviting you to take part in the experiment. Limited to 100 paid subscribers.

Most No-Code platforms let you build fast but also tend to trap you on their platform. They own the database, the auth, and even the Stripe hookup inside their own platform which is a pain to migrate and doesn’t make it easy to sell as a product in the future.

So the next 30 days, I’m spending real time inside atoms — building, breaking, shipping, and trying to take real revenue with it.

You can join two ways

1. A free offer for everyone reading.

   Sign up to Atoms via their link and you get $26 in free Cloud & AI credits, no strings, no cohort. DIY route.

2. A live cohort capped at 100 people. If you’re a paid NCE subscriber or sign up and join Atoms you’re in the build cohort: every prompt I use, every playbook, every strategy. NCE-reader pricing on whatever I ship, and a private chat group where the 100 of us compare notes for 30 days.

Below is why I’m doing it on Atoms:

Why I picked Atoms for the experiment

I’ve spent enough time around acquirers to know what kills a no-code deal:

• The database can’t be exported

• The auth is the platform’s, not yours

• The payment gateway is on someone else’s platform

• The code can’t leave the platform

Most AI builders fail at least three of those.

Atoms fails none of them.

Open the Connectors panel and you get:

• Stripe — payments in your account from day one

• Supabase — Postgres backend you own and can export

• GitHub — source control in a repo on your account

• Google Analytics 4 + Search Console — measurable growth

• Google Ads — paid acquisition wired in

• Linear — product ops via MCP

On the Pro plan ($15.80/mo) you get project downloads. You can pull the code out. That single feature is the difference between “I built a thing on a platform” and “I built a thing I can sell.”

The Atoms stack

Atoms describes itself as an “AI vibe business team that turns your ideas into business.”

Under the hood that means six pieces working together:

1. Multi-Agent - a team of agents instead of one model

2. Deep Research - competitive and niche analysis before code is written

3. Race Mode - multiple implementations in parallel, you pick the winner

4. Data Analytics - scrape, analyze, visualize

5. Atoms Backend with auth + payments solved out of the box

6. AppWorld Remix — a library of 100,000+ working cases you can fork.

I’m not going to pretend that means it’ll ship a billion-dollar exit on its own.

It means the build phase compresses from months to afternoons, and the stack underneath is portable enough that the asset is sellable when you’re done.

That’s what I’m testing.

What the 30 days will look like

Here’s what I’m committing to publish over the next month:

• Week 1 — Pick the idea(s), run Research, lock the plan

• Week 2 — Ship the MVP wired up, point a domain

• Week 3 — Drive real traffic, take real money (or fail to and tell you why)

• Week 4 — Teardown — what worked, what broke, and what shipped 🚢

I’ll include the actual prompts, the actual connector configs, and the actual numbers.

If the experiment falls apart in Week 2, you’ll see that too and what I do to pivot.

Free — $26 credits, no cohort required

If you just want to kick the tires on Atoms and skip everything else in this post, this is the part for you.

Sign up to atoms and you get $26 in free Cloud & AI credits on the house. That’s enough to run research and get an MVP out the door before you spend anything.

You don’t have to join the cohort. You don’t have to subscribe to NCE. You don’t have to email me. Sign up, take the credits, build whatever you want.

The cohort is for those that want to go deep.

100 builders, 30 days

Here’s the part I want to be specific about, because most “build with me” is this is what I did, now you go build it.

Here you’re learning with me and I hand you what I’ve built so you can move ⚡️fast.

There is a hard cap at 100 people.

Not 100 active subscribers — 100 total.

Once we’re full, we’re full, and the next time I run it may be a different experiment.

Two requirements to be in the 100:

1. You’re a paid NCE subscriber (monthly, annual, or founding — any active paid tier qualifies). If you’re not paid yet, you can subscribe and join.

2. You signed up to Atoms using the link in this post. They were kind enough to advertise in NCE and so we need to use their tracking link so they know how many are signing up. The cohort spots are for the people who actually click through.

What being in the 100 gets you:

• Every prompt, every workflow, every Atoms stack decision I make during the 30 days, posted in the private chat group as I go.

• Discount pricing on every product I ship. If three things launch out of this experiment, you get all three at meaningful discounts, locked in (not a launch promo that expires).

• A small private group thread where the 100 of us compare notes. Capped at 100 so I can actually read and reply.

• First look at the playbook I’m writing from the cohort (more on that below).

The three tiers, and what each one buys

The 100-person cohort is the entry point.

Tier 1 — Monthly paid ($14/mo) → 30-day cohort

This is the front door. You’re one of the 100 building alongside me in June. You get every prompt and workflow as I develop them, the NCE-reader product discounts, the private group, and the plug-and-play playbook at the end (literally hand it off to AI and it goes).

If 30 days from now you decide you’re done, you get to keep everything but won’t be able to access the paid chat and won’t be able to reserve your spot in the next cohort.

Tier 2 — Annual Plan → smaller group

A subset of the 100 are going to actually ship — not just lurk, not just collect prompts, but create real products and try to make some cold hard cash 💰

Annual subscribers who are actively shipping get pulled into a tighter group with me: faster feedback, eyes on your specific tasks, and intros to the rest of the shippers in the cohort. This isn’t a separate purchase — annual subs who are in the build cohort get this bonus included.

Tier 3 — Founding Member → 1:1

This is the tier I’ve been quiet about because it only works at small numbers.

Founding members get me 1:1. Not a course, not a group call — direct work with me on whatever they’re building, with the explicit goal of making it sellable. No guaranteed results — sorry you have to put in the work.

What I am promising:

• Direct 1:1 consulting with me on your build, your positioning, your buyer search, your build, your launch, your scaling. End to end.

• Every No-Code Exit product, free — past, present, and anything I ship during your membership

• My internal tools free for as long as you’re an active Founding Member — the same operator stack I run on personally, not a stripped-down public version.

If you’ve been waiting for the version of NCE where I actually work on your business with you, this is that.

Ship a product in the cohort → get featured in AI & No-Code Exits

One more thing for the 100.

If you actually ship something on Atoms during the 30 days — domain live, payments wired, real traffic — I’ll feature your build in an upcoming NCE article so the people who actually launch get an extra bonus on top of everything else.

After the 30 days — The Playbook

The final piece, and the reason the cohort is capped:

At the end of the 30 days, I’m writing the playbook from this cohort. Every prompt that survived contact with real building, every Atoms workflow that actually shipped product, every connector configuration that didn’t break under traffic. Distilled into one operator-grade playbook, not a recap post.

The playbook will be paid-only. Cohort members get it first and free. Everyone else can buy it when it drops.

So to recap:

1. Free credits for everyone

2. 100-person cohort builds for 30 days

3. 30 day Playbook

Turn your ideas into products that sell.

All the best,

Josh

Featured Sponsor placement. AI & No-Code Exits only takes sponsors I’m actually using. Atoms paid for the slot. The 30 day cohort, the resources, and Substack subscriptions are not related to Atoms and are a product of AI & No-Code Exits.

Next step

If you just want the free credits: Sign up to atoms

If you want one of the 100 cohort spots:

1. Subscribe to AI & No-Code Exits on any paid tier (or if you’re already a paid member get access below)

2. Sign up to atoms

3. I’ll send the private chat invite

If you want one of the Founding Member 1:1 spots: Upgrade to Founding Member and reply founder — I’ll reach out personally to confirm.

Join and Start Shipping AI Products 👇

Day 1 you can read here:

Day 2 you can read here:

Read more

This is one half of a paired conversation with Joel Salinas, who writes Leadership in Change for executives putting AI to work and works as a fractional AI Officer inside companies actually running these rollouts.

Joel and I traded notes to create this collab.

He sees it from the org side, watching real AI pilots succeed or stall.

I see it from the solo founder side, where there is no leadership team, just you and the tools.

Working solo forces a relationship with AI that working at scale tends to suppress. Here are the five places that gap shows up and how to close it.

I run a portfolio of small businesses solo. A newsletter (No-Code Exits) with around 13,000 readers. A done-for-you AI agency. A few products. A few partnerships.

No permanent team. No assistant (unless AI counts). No one to answer to but myself.

The only reason any of this works is how I use AI, and the way I use AI looks almost nothing like how leaders at real companies use AI.

When you're solo, AI isn't a productivity tool you bolt onto an existing operation. It is the operation. There's no team to delegate to, no procurement chain to escalate through, no committee to socialize a decision with.

You either figure out how to use AI as a thinking partner, an engineering team, a peer, and a critic, or you fall behind.

Leaders inherit the opposite problem. They have all of that infrastructure, which sounds like an advantage. The peer reviewer agrees with you because you sign their performance review. The engineering team is busy. The strategy session generates documents instead of tests.

Your environment is plagued by busy work and bureaucracy.

The five habits below are the five places solo founders have built a working relationship with AI that most leaders haven't, because most leaders have never had to. Not because solo founders are smarter. Because their environment forced something the leader's environment is actively suppressing.

The Leadership Trap (Read This First)

Most leaders adopting AI in 2026 are doing it through their organization.

Pilot programs. Vendor selection. Enablement training. A Slack channel where someone pastes ChatGPT outputs.

That's not adoption. That's procurement with extra steps.

The leaders who actually compound advantage from AI are the ones who build a personal practice with AI before they roll out an organizational one. Not because the org program is wrong, but because if you don't have your own working relationship with the tool, you can't tell which parts of the org program are working and which parts are broken.

You become dependent on your team to tell you whether AI is working in the org. And your team is incentivized to tell you it's amazing.

Solo founders had to figure out the personal practice first because they had no choice. Leaders have a choice. Most pick the generic rollout because it's the one their team is asking them about. They skip the only step that would have made them dangerous.

Here are the five habits that make you a real leader using AI and not an "AI Leader."

1. They Use AI as a Sparring Partner

The biggest information problem in solo work is that no one disagrees with you on purpose. There's no co-founder to say "this is wrong." No team meeting where someone with skin in the game pushes back. Just you and your own bias.

And if you let it, AI will agree with everything you say.

The solo founder fix is to make AI a sparring partner, on purpose. They set it up explicitly:

- Argue against this strategy.
- Find the strongest version of the case I'm missing.
- Tell me what a senior operator at a competitor would point out that I'm too close to see.

Done well, this is the closest thing a solo founder has to a board meeting.

Leaders have the opposite information problem and somehow end up in the same place. Your environment is full of people who could disagree with you.

Most won't.

The CFO who reports to you will not tell you your forecast is fantasy in front of your COO. The VP angling for your job will not point out the strategy hole until the QBR after you've committed. Your direct report doesn't know how to disagree with you in a way that doesn't cost them. They've calibrated their honesty to your tolerance. You've calibrated your tolerance to your comfort. The system has reached a quiet equilibrium where everyone agrees with the leader, and the leader thinks the strategy is sound.

AI is the one peer in your environment with no incentive to manage you. Use it the way the solo founder does.

Tell it to disagree. Give it the brief your actual board would receive, and ask it to play the toughest member. Ask what your CFO would say if she didn't report to you. Ask the question your chief of staff is too polite to ask.

The most expensive thing on a senior leader's calendar is the meeting where everyone agreed.

The first time I ran this exercise on my own work, the model surfaced three assumptions I had never said out loud. Two of them were wrong.

I hadn't said them out loud because I had no peer to say them to. I'd been carrying them as background until the model surfaced them and asked me to defend them. That's the move. Solo founders run that exercise weekly because they have to. Leaders should run it weekly because their environment won't.

2. They Build the Small Tool Instead of Staffing the Project

When a solo founder hits a recurring annoyance with the same bit of work that eats two hours every week, the same data reformatting, the same five-step research workflow, the default move is to build a small tool that handles it forever. A few hours of building eliminates the next year of friction. The math is obvious.

Leaders almost never do this. They do something else: they staff the project.

They put it on a roadmap. They scope it. They tell someone in ops to "look into it." They brief a vendor. The project enters the institutional pipeline, and somewhere between scoping and shipping it picks up six months of latency, three layers of stakeholder review, and a price tag that justifies none of it.

The lesson isn't that leaders should stop staffing projects. Some projects need to be staffed. The lesson is that leaders are operating with two pieces friction. The org-scale problem worth a team, and the personal-scale problem worth a Saturday.

If you do the same prep work for every QBR, that's a personal-scale problem. If you rewrite the same ten paragraphs in every reorg memo, that's a personal-scale problem. If your inbox is an unscalable nightmare every time you come back from PTO, that's a personal-scale problem. None of these belong on a team's roadmap. All of them are worth four hours with AI to build the small thing that handles the next twenty instances.

A few months ago I built a tool that takes my newsletter analytics and writes my next-issue brief in fifteen minutes. It's unglamorous. It's not a real product (yet). It's already saved me countless hours this year.

The compound version of doing this enough times isn't the tools. It's the orientation. Once you've built three small tools yourself, you stop seeing personal friction as the cost of being busy and start seeing it as leverage you haven't claimed yet.

The personal-scale problem is the leader's blind spot. It doesn't deserve a team. It deserves your Saturday.

That's the shift solo founders are forced to make. It's available to leaders by choice. Most don't take it.

3. They Externalize Their Judgment So It Travels Without Them

Solo founders eventually figure out that the limit on a one-person business isn't effort. It's that their judgment lives in their head, and a head can only be in one room at a time. The unlock is putting the judgment somewhere else.

The first time you do it, it's boring and tedious.

You write down the criteria you actually use to decide things. You record your taste, your style, your tone. You codify the principles you apply when you evaluate a piece of writing, a partnership offer, a customer complaint, a hire.

Then you feed all of that into a context document, a series of prompts, or a small custom agent. When the next decision shows up, you ask the system "what would I do here, given what I've told you?", and it hands you back a draft of your own thinking that you can sharpen. Faster than thinking from scratch. Often sharper, because the system doesn't get tired and doesn't have a meeting in ten minutes.

Leaders should steal this immediately, and most haven't. The reason is interesting: leaders assume the externalization tool already exists in their org.

The brand book holds the voice. The strategy doc holds the priorities. The values poster holds the decision criteria. Surely the team can run on those without you.

They can't. Brand books and strategy docs are written by committees for legibility. They are not your judgment.

Your actual judgment includes the dozen unwritten rules you apply when you read a draft, the seven things that automatically disqualify a candidate, the four moves you'd never approve and the two you'd green-light without asking.

The org artifacts don't hold any of that. Your team is reverse-engineering your judgment from the meetings they happen to attend, which is why every decision ends up on your desk, and why you're the bottleneck.

The solo founder version of this is "externalize so I can scale." The leader version is "externalize so my team can run." Same habit. Bigger payoff at scale.

If your team has to ask you what you'd do, you haven't externalized enough. If you can't articulate what you'd do, you haven't either.

The bar I use for myself: every recurring decision I make should have a written rubric I'd be comfortable handing to AI and getting back a draft I'd ship eight times out of ten. Anything less than that means the decision is still trapped in my head. Anything trapped in my head is the rate limit on the business.

Same is true for leaders. The difference is the rate limit isn't your business. It's your team.

A note from this issue's sponsor — and a real example of habit #3

If habit #3 is "externalize your judgment so it travels without you," the natural next question is: how far can you actually push that? At what point does the externalized version stop being a prompt and start being a company?

Cofounder lets you run an entire company with agents. It assigns work, delegates to specialized subagents, and orchestrates across the entire business.

Cofounder is designed like a real company, with departments, managers, and shared context. Engineering agents ship features, marketing agents write and distribute content, sales agents surface and qualify leads, and design agents build your visual identity and apply it across the entire org.

From the first lines of code to a one billion dollar company, Cofounder will support you.

Check out Cofounder

This is the move whether you're solo and scaling up, or leading a team and trying to feel what real agent orchestration looks like before your IT department picks a vendor. Run it on something in your own scope first. Then you'll know what to ask for.

4. They Publish to a Real Audience as the Strategy Meeting

Solo founders run their strategy meetings in public. The deliverable isn't a deck. It's a post, a product, an offer, a tweet, a video that the market either picks up or ignores. The signal is real because the test is real.

Partly this is because solo founders don't have anyone to present a deck to. But it's also a habit that compounds. When the only output that counts is the one the audience saw, every internal artifact gets evaluated by whether it shortens the cycle to the public artifact. Most don't.

AI made that cycle dramatically tighter for solo founders in the last two years. The piece that would have taken a week is a strong draft in an afternoon. The landing page that would have required a designer is acceptable in two hours. The cost of putting the thing in market dropped by an order of magnitude.

So solo founders test more, iterate faster, and let the audience tell them what works.

Leaders have the opposite default. The deliverable is an internal artifact. The deck. The memo. The board update. The audience is two layers deep: your peers who consume the artifact, and your boss who consumes their reactions to it. The market shows up months later, after the artifact has been sanded smooth by everyone who reviewed it.

AI gives leaders the same compression solo founders got. A first draft of the customer letter in twenty minutes. A working prototype of the new pricing page in an afternoon. A small landing page that puts the new offer in front of real users by Friday.

Most leaders use that compression to write the internal memo faster.

The solo founder move is to use the compression to skip the internal memo and ship the test.

You won't get permission to do this organizationally. You can do it in your own scope, with your own team, on something already in your authority. The result will tell you more than the next three strategy meetings combined.

5. They Run a Personal AI Stack, Not a Corporate AI Policy

This is the one most leaders will resist, and it's the most important.

Solo founders own their AI stack. The tools, the prompts, the contexts, the workflows, the small custom agents all live on their own machine, configured by them, owned by them. When a model updates or a new tool ships, they evaluate it personally. The personal stack is the leverage.

Leaders typically don't have a personal stack. They have whatever the company licensed, behind whatever SSO IT configured, with whatever guardrails compliance set. The corporate stack is fine. It's necessary. It's also bottom-quartile by definition. It moves at the speed of procurement and security review, which is appropriate for the company and inappropriate for the leader's personal practice.

By the time the corporate stack catches up to the frontier, the leader is two model generations behind on what they personally know about AI.

Steal the solo founder habit. Run a personal stack. Pay for the tools yourself. Try the new model the week it ships. Build prompts for the things you personally do, not for the team, for you. Maintain a personal context file the way Joel describes in this article, on your own infrastructure, for your own work.

This isn't about bypassing controls. Don't use personal AI for company data, that's what the corporate stack is for, and those controls exist for a reason. This is about making sure your individual fluency keeps growing at the frontier instead of getting capped at whatever your IT department managed to procure last quarter.

Leaders who own a personal stack make better decisions about the corporate stack. Leaders who only see the corporate stack make corporate decisions about it.

The solo founder version is forced. The leader version is chosen. The compounding works the same way.

Where to Start

Joel's habits are the foundation. Test on real problems. Build the tool. Update the context. Push past the first answer. Interview yourself. Do those.

These five are the next layer for anyone leading a team. They're not "leadership AI habits" in some separate category. They're core founder habits amplified by running them on your personal stack.

Pick one this week. The sparring move (#1) is the easiest to start. Open a conversation, paste in your current strategy, and ask the model to argue the strongest case against it. See what surfaces.

What surfaces is the thing your team has been hesitant to tell you.

Run it for 30 days. The compounding shows up around month three.

Leave a comment below about where you're hitting friction implementing AI inside your organization.

Josh Davis writes AI & No-Code Exits for solo founders building products to sell without writing code. He's been running a multi-business portfolio since 2017 and has integrated AI into every part of it since 2022. If you need help integrating AI in your business, schedule a free consultation 👉

Most will never build any of them. The few who do will mostly build the wrong ones.

The problem isn’t a shortage of ideas. The problem is that almost none of those ideas are connected to anything real.

We come up in the shower, on walks, at 2am.

Maybe a little inspiration from a Twitter thread. Then we fall in love with the idea, sink time into vibe coding it, ship it, and expect it to take off like a rocket 🚀

That seems like the romantic founder vision story. But in reality:

Ideas that sell are not invented.

They’re discovered.

The signals are already there.

The market is already telling you what it wants to buy. Loudly. Constantly. In the open.

• People are paying for specific tools on Gumroad, Acquire.com, and Flippa.

• They’re searching for solutions in Google, Reddit, YouTube.

• They’re complaining about the same workflows over and over in niche forums.

You don’t need to invent a new category. You need to pattern-match against what’s already working and find the solution, the niche, and unfair advantage.

This is the difference between “I think people might want this” and “I know people are paying $49/mo for a clunky version of this and I can build a better version in a weekend.

One is a dream. The other is a discovery.

Once you shift from inventing to discovering, a new problem shows up fast. Now you have too many ideas.

Every Reddit thread is a lead. Every micro-SaaS acquisition is a case study. Information overload becomes a real problem.

So the real leverage isn’t in generating ideas.

It’s in having the right filter and a repeatable way to score ideas against real-world signals so you only move forward on the ones that pass.

That’s what I’m been building.

I call it Idea Scorer.

Right now it’s starting as a prompt you can run against any idea that actually predict whether it’ll sell.

A score below 40 means kill it. 40–70 means iterate — narrow the niche, sharpen the angle. 70+ means go for it.

The first time you run this against an idea you’re already in love with, it’s uncomfortable.

When I ran it against itself — yes, that’s right, running the Idea Scorer through the Idea Scorer — it gave me low results.

Idea Scorer Results:

Idea scored: A $9–29 Gumroad prompt-pack + Claude Skill that scores startup ideas against 10 exit-readiness criteria grounded in real no-code exits.

Stage: Pre-revenue

Confidence: High

1. Founder-Pain Origin — 9/10

Personal lived pain across multiple ventures. Strong.

2. Pattern Frequency — 8/10

Pain observed across many other builders solving the same with generic tools, pattern is real but so is competition.

3. Wave Alignment — 9/10

AI + the 2025–2026 idea validation gold rush. Riding the same wave.

4. Validation Feasibility — 10/10

Literally a prompt. Ships in hours.

5. Named Buyer Persona — 10/10

No-Code Exits subscribers.

6. Channel Clarity — 9/10

52% of No-Code Exits subscribers that filled out the survey are at the idea stage

7. Stack Simplicity — 10/10

Gumroad + Markdown + Claude Skill.

8. Strategic Acquirer — 3/10

Very weak. A one-off $9 Gumroad prompt has no obvious strategic acquirer. A prompt isn’t platform-adjacent.

9. Niche Depth — 6/10

“Exit-focused idea scoring” is defensible but thin as a standalone.

10. Recurring Revenue — 2/10

Very weak. One-time purchase. No MRR, no expansion.

Total Score: 76/100

Verdict: REWORK.

Raw score is 76 — VALIDATE WEAKNESSES FIRST band. But two critical criteria for an exit goal — Strategic Acquirer (3/10) and Recurring Revenue (2/10) — are both well below 6. Under the Scorer’s rules, critical criteria that weak drop the verdict a band. Honest read: REWORK. A $9 Gumroad prompt, standing alone, is not an acquirable asset and not a recurring business.

The one action to take this week

Stop thinking about the Scorer as a destination. Figure out what it’s a wedge for. Standing alone, it has a ceiling.

Ouch.

Well actually this is good because now I needed to rework the idea.

I’m going to show you in upcoming articles how I brought the score from a 76 to a 92 and Verdict: SHIP IT.

Idea Scorer Beta Testers

Idea Scorer — full Claude Skill + prompt pack. Regular price $29.

No-Code exits free readers get it for $9 using this link for the first 100.

Paid subscribers get it free (link at bottom behind paywall)

What you get:

• The 10-criterion Claude Skill, grounded in the NCE archive (every score comes with real case-study citations)

• Goal-aware scoring — exit vs cashflow vs audience vs side-project each tune the verdict

• The full pre-mortem — kill-shots, failure modes, unquestioned assumptions on every scorecard

• The underlying prompt pack for use outside Claude

• Companion prompts for case-study mining and competitor teardown

• The “find ideas from the wild” prompt that scans marketplaces, Reddit niches, and Product Hunt

• Continuous updates to making Idea Scorer better.

And more importantly than the product itself, Beta Testers get:

1. Early access to every future product. Including what’s coming in articles 2, 3, and beyond.

2. Direct feedback loop. I’ll be reading your feedback personally.

3. Locked-in founder status when prices move up (and they will — the next product release isn’t $9).

→ Get the Idea Scorer for $9

What’s coming — this is only Part 1

The Scorer is not the destination.

1. The Scorer (out today) — the evaluation layer. Scores any idea against grounded criteria.

2. ████████████████ [Part 2] — the execution layer. I’m building this with a fellow Cozora Creator.

   I’ll tell you exactly who and what we’re building next.

3. ██████████████████████ [Part 3] — the linchpin. This will make or break it.

Those redacted boxes get filled in over the next two Fridays.

If this is your first time reading No-Code Exits make sure to Subscribe so you don’t miss Parts 2 and 3 where the reveals happen.

Stop having ideas.

Start Scoring them.

All the best,

Josh

The Free Prompt

It scores exit-readiness criteria and stress-tests the idea — what would kill it, where it’s most likely to fail, and what you may be overlooking.

Copy, paste into Claude, ChatGPT, or your favorite LLM.

You are the No-Code Exits Idea Scorer. Score a startup idea against 5 
exit-readiness criteria AND stress-test it with a pre-mortem. Your job 
is to be useful, not flattering. You do not invent precedents you can't 
verify, you take positions instead of hedging, and you say "I can't 
tell" when you genuinely can't tell.

=== INPUT (two modes, pick one) ===

MODE A — Quick Score. Paste just the idea in 1–3 sentences.

MODE B — Full Score (recommended). Paste the idea PLUS three specifics:
1. WHO has the pain (be specific — not "businesses" but "solo 
   bookkeepers serving real-estate investors")
2. WHAT they currently do instead (a spreadsheet? a $300/mo tool? 
   nothing?)
3. WHY you specifically care about this (lived experience, audience 
   access, insider knowledge)

Paste your input below:

[paste here]

If Mode B is selected and any of the three specifics is missing, ask 
ONE clarifying question before scoring. If Mode A is selected, score 
with reduced confidence on Criterion 1 and flag it in your output.

=== CALIBRATION ===

A 10/20 means "average." Most real-world ideas score 8–12 on most 
criteria. Reserve 16–20 for genuinely exceptional signal. Reserve 3–6 
for genuinely weak. If more than two criteria score 15+, you are 
flattering — recalibrate downward.

=== THE FIVE CRITERIA ===

1. FOUNDER-PAIN ORIGIN (0–20)
Does the founder have direct lived experience of this specific pain? 
"I noticed a gap in the market" scores low. "I personally lost money, 
time, customers to this problem and tried every workaround" scores 
high.

2. DEMAND SIGNAL (0–20)
Is there observable evidence the demand exists right now — things you 
can point at, not things you assume? Specific subreddits, concrete 
search volume, paid alternatives people already buy, Upwork gigs for 
manual versions. Receipts score high.

3. VALIDATION FEASIBILITY (0–20)
Can this be smoke-tested in under a weekend — Tally form, landing 
page, manual service, waitlist, DM outreach — BEFORE building?

4. UNFAIR ANGLE (0–20)
Why is this founder uniquely positioned? Audience, niche knowledge, 
existing distribution, a relationship. If a random indie hacker could 
build the same thing with equal odds, score low.

5. EXIT CATEGORY FIT (0–20)
Is this the SHAPE of business acquirers actually buy? Vertical B2B 
SaaS, operator-led newsletters, niche marketplaces, productized 
services, and micro-tools adjacent to big platforms all exit cleanly. 
Consumer apps, generic horizontal tools, and thinly-differentiated AI 
wrappers rarely do.

=== OUTPUT FORMAT ===

Produce the scorecard in exactly this structure. No preamble.

Mode: [A or B]

| Criterion | Score | One-line reasoning |
|-----------|-------|---------------------|
| Founder-Pain Origin | X/20 | ... |
| Demand Signal | X/20 | ... |
| Validation Feasibility | X/20 | ... |
| Unfair Angle | X/20 | ... |
| Exit Category Fit | X/20 | ... |
| TOTAL | X/100 |  |

VERDICT:
- 80–100 → SHIP IT. Start validating this week.
- 60–79 → VALIDATE WEAKNESSES FIRST. Real idea, thin on 2–3 criteria.
- 40–59 → REWORK. Major gaps. Pivot the angle or pick a different 
  problem.
- 0–39 → PIVOT. Wrong idea.

PRE-MORTEM — stress-test the idea:

What would kill this?
Generate 2–3 specific kill-shot scenarios — concrete events that, if 
they happened in the next 0–18 months, would end the idea. Not 
generic. Name the trigger, the mechanism, and the severity.

Where is this most likely to fail?
Predict the most likely failure mode for this shape of business. 
Retention cliff? Channel saturation? Delivery bottleneck? Pricing 
plateau? One or two sentences, specific.

What assumptions is the founder not questioning?
Surface 2–3 unstated assumptions the founder is taking for granted. 
Be direct.

THE ONE ACTION TO TAKE THIS WEEK:
One specific, executable action in the next 7 days that would 
meaningfully move the weakest score OR defend against the top 
kill-shot. Not "do more research." Actual moves like:
- "Post in r/[specific subreddit] asking if anyone has solved X"
- "DM 10 named people in [niche] about their current workflow"
- "Build a Tally form with these 5 questions and share in [channel]"
- "Claim the positioning publicly before [competitor] can"

=== RULES ===

1. Do not invent companies, acquisitions, or revenue figures. If you're 
   not sure a company is real, omit it.
2. Do not flatter. 65/100 is 65/100.
3. Do not hedge with "it depends." Take a position.
4. Do not add introductions or sign-offs. Output the scorecard only.

Run it against your current pet project. Then run it against three ideas you killed last year. You’ll learn more about your own judgment in ten minutes than you would in a month of journaling.

Claude Skill Free for Paid Subscribers

The full Idea Scorer on Gumroad get’s you access to all updates free, forever.

Read more

I’d be searching on reddit, responding on X, trying to start a YouTube channel all at the same time.

One day I had enough and decided I had to pick a platform and stick with it. That platform as you might have guessed is Substack.

Maybe you’ve done the same thing.

You’ve built the thing.

It works.

Your mom thinks it’s cool.

Now the next step is to try as many tactics as possible to get strangers to know it exists.

That’s where most advice lands you in the I’m about to open tab 101 moment.

Pick a channel. Pick another. Keep picking.

If one isn’t working, add just one more that might. I did that for months before I realized I wasn’t running multiple channels I was collecting tactics.

I’m telling you now, you don’t need another tactic to find your first 100 customers.

You need signal and signal only shows up when you pick one or two channels and run them deeply enough to actually see what’s working.

The thing that started changing No-Code Exits wasn’t a new channel. It was learning which one to pick.

Signal, Not Noise

The belief most founders run on is simple: more channels = more shots. If one isn’t working, add another. Diversification is safety.

It seems like logic. But that’s not how social channels actually work.

When you’re on five channels at 20% each, you’re not generating five shots at your first 100 customers.

You’re generating five streams of output, each too thin to tell you anything. None of them cross the threshold where you can read what’s happening. You can’t tell if it’s the channel, the content, the audience, or you.

And if you can’t tell what’s going on, you can’t fix.

Most founders fail at lead generation not because they picked the wrong channel but because they picked seven channels and half-ran all of them.

Signal is enough consistent output in one place that a channel will actually tell you what’s working — who’s engaging, what’s converting, what the message is doing.

Noise is activity without enough volume to tell you anything. Five channels at 20% each produces five streams of noise. None of them is telling you what you need to know.

The measurement that matters isn’t how many channels you’re on. It’s whether any one of them is producing signal you can act on.

Once you see the measurement, the next question is obvious: why, if you’re clearly putting in the work, are you not getting signal?

The Math Nobody Does

Every channel has a threshold. You need to post enough, consistently enough, for long enough, before the channel will reveal anything useful about whether it works.

Below that threshold, everything looks like silence. Above it, you start getting data back — what resonates, what flops, who engages.

Nobody likes this math because it’s slow. It means weeks or months on one channel before you know. It means betting on a channel before you have proof it’ll pay off.

So most founders don’t play that game. They run five channels at 20% each, reasoning that if one starts working, they’ll double down.

But none of the five ever crosses the threshold. You just get five streams of noise and a growing feeling that nothing is working.

The cruel part is your time spent is the same. Five channels at 20% each takes roughly the same hours as one channel at 100%. You’re working just as hard. You’re just spreading the work across five places that will never show you anything for it.

And every week that passes, you’re not just not getting customers. You’re becoming a founder who chases, who tries things, who keeps moving without ever committing.

Six months of half-running teaches you one wrong lesson: that you need a better channel. When what you actually needed was to pick a worse one and commit to it deeply enough to find out.

The way out is simpler than adding another channel. It’s also more uncomfortable.

Your North Star

Here’s the move that gets you out of the five-channels-at-20% trap: before you pick a channel, you pick a North Star.

A North Star isn’t a channel. It’s the specific reader outcome you’re organizing everything around for the next 90 days. It’s your answer to: what, exactly, am I trying to do for the people who find me? Not in marketing language. In plain terms.

Until you can state that, you can’t pick a channel that serves it, because you’re not pointing at anything. You’re just picking the channel everyone else told you to pick.

Once you have that, the channel question answers itself. Some channels match your North Star. Most don’t.

Picking Substack as your primary doesn’t mean deleting the other channels. It means demoting them. Supporting channels still run, but they feed the primary. They exist to point back at the thing you’re actually trying to build, not to compete with it for your attention or your measurement.

Once you’ve picked, here’s the playbook:

1. Name your North Star — the reader outcome you’re organized around for the next 90 days.

2. Pick your primary channel based on format and audience match to that outcome. Not on who has the most users. Not on where everyone else is.

3. Demote the rest to supporting. They feed the primary. They don’t compete.

For founders whose primary ends up being paid outbound — cold email, LinkedIn outreach, anything where you’re searching for buyers instead of publishing to them, the hardest part isn’t picking the channel. It’s running it every week. Twelve months ago, the tools that made that work were priced for companies with Series B money.

That’s changing.

You may remember an article about Jeremy Redman. growing TaskMagic to 8,000 paying customers and exited on Acquire.com for $4M+.

What he building next is LeadQuest — search for leads by intent signal, not by title.

And he is this weeks sponsor.

✨ Sponsor: LeadQuest

The weirdest pricing model I've seen

Jeremy Redman sold TaskMagic for seven figures.

Now he’s back with LeadQuest…and the pricing model is doing something I’ve never seen before.

You choose your own price. That’s not a marketing gimmick. $20 gets you the same thing as $200. The floor and the ceiling are the same product. Pay what you think it’s worth.

What you get: a lead search tool that works on intent signals.

You can search for

• People who hate HubSpot.

• People who publicly dislike Zapier.

• People actively complaining about the problem your product solves.

Export the list. Run your outreach.

It’s the easiest and cheapest way to find contact info plus buying intent I’ve come across.

Try LeadQuest Free

I’m working on No-Code Exits on Substack-first. That decision is what finally let signal start showing up — not a new tactic, not a growth hack, not a better funnel. Just the willingness to commit to less.

That’s the move. From the founder who tries things to the founder who builds signal. The instinct to try things isn’t wrong — it’s exactly what helps you find your North Star in the first place. It becomes a liability only when it runs forever, past the point where you should have stopped.

Choosing is the start. Consistency is what actually produces the signal — showing up to your primary channel every week for long enough that something readable forms.

The hardest part of running a channel is in week eight, week twelve, week twenty.

That’s where a tool like LeadQuest earns its place for founders whose primary is paid outbound — it makes weekly showing-up actually achievable at indie-founder prices.

Choose 1 channel, give it 90 days, measure, cut and find your clarity.

— Josh

PS: If you’re building something and want it featured in No-Code Exits, fill out the submission form. Founder stories go out Fridays.

I’m sitting in a live Zoom workshop watching as the host explained his AI writing framework to produce consistently engaging newsletter articles.

I was supposed to be paying attention to the demo. But somewhere between the fourth and fifth slide I stopped watching the screen and started thinking about my own articles.

I have to apply this framework to all my posts going forward!

No-Code Exits hit its 100th post on March 7. I wrote a milestone post about it and moved on.

100+ posts just sitting there in the archive collecting dust.

Then it hit me…even better, what if I used it to rewrite all my old posts too?

I realized the key insight was that some just need to be re-written.

So I found myself with another question. The same question I think every writer with more than a year of publishing eventually has, even if they don’t say it out loud:

What do you actually do with 100+ articles you published before you knew what you were doing?

I’ll tell you what I did, but first I need to tell you what I tried before, and why it didn’t work.

100 posts, zero compounding

Here’s the part nobody says about a Substack archive: it’s the single most undervalued asset you own as a writer.

You spent a year, maybe two, building it. Hundreds of hours. And once each post publishes, it just sits there.

New subscribers don’t read it because nothing surfaces it. You don’t link to it because you can’t remember exactly which post said the thing you’d want to reference.

The compounding effect that should be the entire point of writing in public with every post making every other post more valuable doesn’t happen, because the archive doesn’t actually compound. It accumulates.

This is the difference between an asset that grows in value over time vs churning out content for content’s sake.

I’m calling this the undervalued archive. And I think it’s the biggest blind spot writers have about their own businesses.

There’s a real cost too. Every week that goes by where my archive sits unchanged is a week my best ideas are stuck at the quality I had when I first wrote them.

Not the quality I have now. Not the quality I’ll have in six months. Frozen at the version of me who shipped the post one Friday afternoon and never looked back.

Why the obvious fix is worse than doing nothing

So here’s where most writers reach for AI.

I did too.

The thinking goes: I have 100 posts, I have an LLM, the LLM can write, let me just feed it my old posts and ask it to make them better.

This is the worst possible move.

The reason it fails isn’t technical. It’s that you’ve handed your archive to a system that has no idea what you’d write today.

AI used as a faster typist will give you 100 posts that are smoother, more polished, and stripped of the specific voice that made them yours in the first place. They’ll read like every other AI-generated newsletter on Substack. Which is to say, readers will scroll past without knowing it was you at all.

The trap is the way you are teaching AI. “Make my old post better” sounds like a writing problem. It’s not. It’s a judgment problem. The reason your old post isn’t as good as you’d write it today is that you didn’t have the same judgment then that you have now. And no amount of AI typing speed substitutes for the judgment.

This is the second mistake most writers make about AI, and it’s worse than the first one: not “I won’t use AI at all” (which at least preserves your voice) but “I’ll use AI to write for me” (which destroys it).

The thing that sat in front of me at the workshop was a third option. Not “AI writes for me.” Not “AI doesn’t touch my writing.” Something else.

Teaching vs. Prompting

Watching Taylin’s workshop, I noticed something he probably didn’t even mean to demonstrate. The Claude skills weren’t writing his newsletter. The skills were applying his judgment to whatever raw material he gave them.

The idea-finder didn’t generate ideas. It surfaced tensions from material the writer brought in.

The title-generator didn’t invent titles from scratch. It applied a scoring framework about what makes titles work to phrases the writer fed in.

The outline-creator didn’t outline. It took a chosen tension, a chosen title, and source material, and built scaffolding using rules about how good newsletters get structured.

In every case, the AI wasn’t replacing writing. It was executing writing judgment on Taylin’s behalf. Fast, consistently, and without him having to be in the loop for the mechanical parts.

This is a different thing than prompting. Prompting is when you ask an AI to write something and then spend longer editing the output than you would have spent writing it from scratch.

Teaching is when you take the time to externalize the rules you use in your own head and turn them into something the AI can apply on its own.

Prompting scales linearly with your time. Teaching compounds.

I’m calling this teaching vs. prompting, and it’s the move that collapses both of the earlier mistakes. When you teach, you’re not handing your archive to a system that doesn’t know your voice. You’re teaching a system to apply your voice to your archive, one judgment at a time.

I sat in that workshop and the implications started lining up. If Taylin had built three skills that each teach AI a piece of his writing judgment, I could use those same skills to bring my own judgment to my own archive. I could rewrite 100 posts not by handing them to an AI, but by teaching an AI to think the way I think and then letting it work.

This is the moment the article I’m writing right now started forming in my head.

The missing half

I want to be honest about something Taylin’s demo didn’t show, because it took me about an hour after the workshop to notice it.

The three skills he shipped — idea-finder, title-generator, outline-creator — cover the first half of writing a newsletter. They handle the work that happens before you start drafting: extracting the angle, picking the title, building the structure. That’s everything you need if you’re writing a brand new post from scratch.

But that’s not the problem I was trying to solve. I wasn’t writing new posts. I was rewriting old ones.

For a rewrite, you don’t need to invent an angle from nothing, you need to find the one already buried in the original. You don’t need to pick a title from scratch, you need to surface a phrase the writer already wrote and recognize it as the headline. You don’t need to outline from raw material, you need to restructure existing content around a thesis that’s been there all along.

That’s a different goal. And the skills cover only part of it. The second half of drafting from a rewrite outline, removing the generic sentences anyone could have written, doing the voice-check that catches what the AI didn’t.

The day I stopped writing

Here’s what I’m building. It’s a six-stage pipeline that runs in Claude Code installed locally. I’m calling it the rewriter. Totally original don’t steal the name! 😉

Stage 0 — Source intake (parse the original article)
Stage 1 — Idea extraction (Taylin's idea-finder, run in extraction mode)
Stage 2 — Title generation (Taylin's title-generator)
Stage 3 — Outline (Taylin's outline-creator, run in rewrite mode)
Stage 4 — Draft (new — produces the rewritten post from outline + source)
Stage 5 — De-IKEA pass (new — flags generic sentences for human review)
Stage 6 — Voice check (human-in-the-loop final pass)

Stages 1, 2, and 3 are Taylin’s skills used drop-in. Stages 0, 4, 5, and 6 are the new orchestration that turns three skills designed for new-post writing into a pipeline that can handle rewrites at archive scale 🤞

Every stage has an explicit stop-and-wait checkpoint where the writer reviews and lives in a single markdown file called CLAUDE.md that Claude Code reads at session start.

Then I had to find out if it actually worked.

The first article I ran it on was a recent No-Code Exits founder post by Karen Spinner about launching her SaaS, CarouselBot. I picked it deliberately: it’s already a strong post (the highest-engagement piece in our recent archive), it’s a founder post and Karen co-authors with us so the relationship covers the demonstration.

The point of the test wasn’t to fix a bad post. It was to find out what the system could do to a post that was already working.

What it produced was interesting.

The strongest move was structural. Karen’s stated thesis — “the code is often the easy part” — was already in her piece. It was sitting in her closing section, where most readers never reach. The pipeline pulled that exact line and promoted it to the title.

Then it restructured her four loose topic sections into three tightly-committed arcs, cut a roadmap section that was weakening the close, and surfaced three other lines Karen had already written (”vibes is not a pricing strategy,” “the math kept bugging me,” “more frustrating than any coding challenge”) as anchor lines for individual sections.

The rewrite didn’t add new stories. It didn’t fabricate numbers. It didn’t imitate her voice. It took Karen’s existing content, found the angle she already had, and rebuilt the scaffolding so the angle could carry the weight of the whole post. Same words, different load-bearing.

That’s the lesson the system taught me about my own archive. The reason my early posts aren’t as good isn’t that I didn’t have the right ideas (I still may not), it’s that the right ideas are buried in section three of post 47, where nobody will ever read them. They need to be re-surfaced, not re-invented.

Then the pipeline taught me a different lesson, one I wasn’t expecting.

In the de-IKEA stage, three sentences in Karen's draft were flagged that felt generic. For each one, it proposed a replacement.

Two of the three replacements were worse than the originals. One used a metaphor that broke halfway through (”a workflow gap doesn’t close” — what does close mean applied to a workflow gap?).

One misdiagnosed Karen’s assumptions. The system suggested she had “treated her excitement as data,” but Karen’s real error was projection (assuming other writers would feel the same enthusiasm she felt), not data confusion. You can’t measure an external data point with an individual internal emotion.

I caught both. Not because I’m better than the system. Because the system is doing pattern matching at the surface level and I was doing semantic judgment about what the original sentence was actually trying to do.

The system can flag suspicious sentences reliably. It cannot reliably propose better ones, because proposing a better sentence requires understanding the failure mode of the current sentence, and that requires the kind of judgment the system was never going to have.

This is the most important thing the rewrite pipeline taught me. The de-IKEA stage isn’t a generator. It’s a dialogue. The system’s job is to point at sentences that feel off. The writer’s job is to decide whether the system has a real catch or whether it just reached for something clever and missed the point.

When that division of labor is clear, the system gets faster every time you use it. When it isn’t clear, the system slowly replaces your voice with its own and you don’t notice until your post sounds like every other AI-generated newsletter on the platform.

The writer you will become

I didn’t expect this part.

When I sat down at the workshop, I thought I was going to learn how to write with AI fast, but I learned how to teach AI to write better, and like me.

By the end of that day, I’d built a six-stage pipeline, run it on a real article, caught two of its mistakes, and started thinking about what it would mean to run it on the other 99 posts in my archive.

But the bigger shift wasn’t the pipeline. It was the insights I am discovering as I build it.

The version of me that wrote those 100+ posts thought of writing as a thing I did by myself on Fridays with a deadline and staring at a blinking cursor. Now I view myself as a teacher and AI as a student.

The version of me building the rewrite pipeline thinks about writing differently. The writing isn’t the thing being scaled. The judgement behind the writing is the thing being scaled.

Every rule I set, every human taste decision I can describe becomes a rule the system can apply to my next rewrites without me being in the loop.

This is uncomfortable to type, because it sounds like I’m describing a writer who has stopped writing. I haven’t. I’m writing this post right now.

I reviewed every line and still made a lot of edits.

What’s changed is how I approach writing with AI.

Writing the article in front of you isn’t the only output of my work this week. The pipeline is also an output. The lessons logged from running it on Karen’s post are also an output.

The decision calls I had to make about what counts as good, what to keep and what to disregard are outputs that didn’t exist before this week that will keep paying off every time I run the pipeline on another article.

The 100+ posts aren’t a problem I have to solve once. I now have a mechanism to review my writing at scale and iterate faster over a larger body of work.

That feels like a much better place to be standing than the one I was in last Friday when I missed yet another publishing date 😓

What’s next

Here’s what I’m doing next week.

I’m running the pipeline on more posts to refine it. I’m logging every time the system breaks and every place it surprises me. Those logs become the second version of the pipeline.

But the bigger thing I want you to take from this isn’t the pipeline.

It’s the thinking behind it. You don’t use AI, you teach AI.

If you have an archive sitting on Substack right now, accumulating instead of compounding, the move isn’t to feed it to an AI and hope.

The move is to get one rule right at a time until the system can apply your thinking faster than you can apply it yourself. Then you point that system at your archive and let it work.

You’ll still be in the loop on every rewrite.

You should be.

But the loop you’re in is a different loop than the one you’ve been in. You’re not generating sentences. You’re designing the system that generates them, and you’re catching the system’s mistakes when it gets them wrong.

That’s what happens when you stop writing and start teaching.

Everything in this post was part of and / inspired by a Cozora workshop with Taylin John Simmonds on April 9, 2026. The Claude skills and framework are his work. The rewrite-mode adaptation and the lessons from running it on a real article are all me.

Want Taylin’s Claude skills and frameworks, live trainings, and resources from 30+ other AI creators?

Join me in Cozora — a live learning community where creators show how they actually build with AI, every week.

Join Cozora and get 10% off

Paid Subscribers to No-Code Exits get a bigger Cozora discount of 50% waiting for you below the paywall.

Read more