NewNVIDIA Inception Program

Mantis Ai is now part of NVIDIA Inceptionthe program for startups building with AI

Read more
Client Acquisition

Built With AI, No Users? Start With 20 Named Accounts

AI shipped your MVP. Your LinkedIn network already saw the build posts and didn't buy. Here is the loop I replace 'post more' with: one line of ICP, 20 named accounts that fit it, one visible signal per account, one specific opener.

first userssaasaioutboundnamed accountsicp

Last week an indie founder put it like this, building two products with AI: "I can build the product with AI. Getting the first users is harder."

He's right, and he's not alone. With Brainy and MoneyBrain, he writes, "getting the first users and growing monthly recurring revenue has been harder than building the software." The failure mode he names is the one I see every week: "A post about my AI workflow and a post explaining why someone should use an application ask for different kinds of attention." His LinkedIn feed loved the build. It did not buy the product.

I'm Tarun, founder of Mantis. This is the loop I'd replace "post more" with: one line of ICP, 20 named accounts that fit it, one visible signal per account, one specific opener. Recruit the first users manually, the way Paul Graham described it twenty years ago: "the most common unscalable thing founders have to do at the start is to recruit users manually."

Why "post more on LinkedIn" stops working after launch

The LinkedIn-feed loop rewards the people who already follow you for the thing you're already good at. It gave this founder a crowd watching him build. It did not give him buyers. His own line — "where to reach people who need the product, and why they would try it, return, and eventually pay" — is still an open question in his post, and that's not his failure. That's the format's.

The 2026 version of this pain is worse than it was. "Getting first 100 users for your AI Startup is not easy, it's a battlefield," one YC-adjacent playbook puts it. "Market is too flooded. Everyone's selling the next big AI SaaS." More posts. More AI tool launches per week. The noise floor rose, and feed-based "lazy content" rose with it.

Replacing it costs nothing — except specificity. That's the trade.

The ICP box: one buyer, one signal, one opener

Before any account goes on the list, write three lines.

Who buys

One sentence. Not a persona deck. The template I use on our [leads-without-buying-lists guide](/resources/how-to-get-leads-without-buying-lists) is "the buyer and two signals: Who buys, and what visible fact shows they need it now."

One visible signal

A fact anyone could check from the outside — a job post, a broken feature, a review complaint, an SDK import, a dead integration page, a specific tech-stack combo. If the signal is invisible, drop it.

One opener

20 to 40 words. Reads like a person who already knows their business, not a template.

A worked example from our own guide reads: "companies with roughly 20 to 200 staff that are growing fast enough to outgrow spreadsheets and an informal HR function." That is specific enough that you can tell, in ten seconds, whether a name on your list belongs on it or not. That's the bar.

Why 20 accounts, not 100

Account-tiering is older than the AI-MVP crowd. A clear primer puts it this way: "Tier 1 accounts are your best-fit, highest-value targets, usually 5-15% of a list." The research budget by tier is the giveaway: "Tier 1: 20-30 minutes per account… Tier 2: 5-10 minutes per account… Tier 3: 1-3 minutes per account, largely automated." And explicitly on the number: "Some teams add a tier 0 for named strategic accounts, a small handful, sometimes fewer than 20."

Twenty is not arbitrary. Twenty is what one founder can carry in their head for a week — read the site, read the LinkedIn, read the last release notes, write the opener, send it, remember what happened. A hundred collapses into a mail-merge within three days. Thirty well-chosen leads a week is "a realistic pace for one person doing it part-time," I've written before. Twenty is tighter than that on purpose.

How to build the list of 20

I keep it in a table. Nothing else.

ColumnWhat goes in itSource
CompanyLegal name as it appears on their siteTheir site
Fit (one line)Why they match the ICP sentenceTheir site / About
Visible signalThe specific, dated factJob post, review, changelog, tweet
Reachable personA name, a title, a public channelLinkedIn, team page, a podcast
Opener (first line)20 to 40 words, mentions the signalYou — don't outsource this
Statuspending → sent → replied → meetingYou, updated as you go

Twenty rows. One page. Three hours the first time, under an hour by week three.

The move most AI-MVP founders skip is the signal column. "The feature I built works best on X" is a feature, not a signal. "They posted a job for a sales intern and their careers page still shows 2024" is a signal. "They complained about Tool Y twice in a review" is a signal. If you can't put a signal in that column, the row is not ready.

We built Mantis to populate the first three columns when the signal exists in public — map listings, open web, hiring pages, review platforms, public registries. It's "an Apollo alternative for leads Apollo was never built to see", because bought databases miss the businesses the signal actually points to — in India, for example, 41.2% of Indian businesses checked have no website at all. But the signal column is yours to write. Nobody else will do it for a company you don't know yet.

For why self-built lists beat bought ones even when you ignore price, see bought database vs live search — "a self-built list tends to be better than a bought one, for a reason that has nothing to do with price: you know why every business is on it."

The one-line opener

The opener is not a sales email. It's the first turn of a conversation a stranger did not know you were waiting to have. Three rules:

✓
Name the signal in sentence one: Not the product. Not you. The thing you noticed about them. If you can't do this in one line, you don't have a signal; you have a guess.
✓
Ask one specific, low-friction question: Not "quick call?" The question earns the reply; the call earns itself later.
✓
Offer to do the unscalable thing: This is the Stripe move Paul Graham tells on himself: "When anyone agreed to try Stripe they'd say 'Right then, give me your laptop' and set them up on the spot." Not scalable. Exactly the point. You won't be setting up 10,000 users like this. You'll be setting up the first 20.

What opener-writing is not: GPT dropping your product name into a Loom template. The opener lives or dies on the signal, and the signal is proof you read their business. Any shortcut on that side of the equation shows on the other side as "no reply."

The weekly loop

1

Monday — refresh the ICP sentence

If last week's replies taught you something, edit the sentence. Otherwise leave it.

2

Tuesday — pick the 20

By your own search or by a tool; what matters is each one fits the sentence and each has a visible signal.

3

Wednesday-Thursday — write 20 openers

One hour each is too much. Fifteen minutes each is the right order of magnitude. The signal does most of the work.

4

Friday — send

One at a time, from your own address. No sequence tool yet; you're not warm enough for that to help.

5

Monday — read replies

Promote the three strongest signals from the week's replies into the next week's ICP sentence. The loop gets sharper by the week.

This is one week. It replaces every "post more on LinkedIn" cycle you were running. The only thing it needs you to defend is the signal column. Everything else is just doing it.

Paul Graham again, because he was right the first time: "A lot of would-be founders believe that startups either take off or don't. You build something, make it available, and if you've made a better mousetrap, people beat a path to your door." They don't. "Startups take off because the founders make them take off."

Try Mantis for the first three columns

Describe your buyer in one line — "funded SaaS startups in Bangalore hiring their first SDR", or "MSMEs in Ludhiana running on spreadsheets" — and Mantis pulls the named accounts, the visible signal and a reachable person from map listings, the open web and public registries. We won't write your opener. We'll give you the twenty names and the reason each is on the list.

500 free credits once at signup, no card.

Find your 20 named accounts

500 free credits once at signup, no card.

Start free

Frequently asked questions

Why 20 accounts and not 50 or 100?

Because one founder can hold 20 companies in their head for a week — research, opener, send, remember what happened. A hundred collapses into a mail-merge within three days. A standard account-tiering primer puts the strategic tier at "sometimes fewer than 20."

Doesn't this scale badly?

It's supposed to. The founder who shipped two AI products can't recruit the first twenty users by launching on ten more Reddit threads. He needs twenty buyers, each read, each written to by name. Paul Graham called this "the most common unscalable thing founders have to do at the start." It stops being your job at a few hundred users — not before.

What if my product has no visible buying signal?

Then the ICP line is wrong, not the account list. Rewrite the sentence so that a signal exists. "Who buys and what visible fact shows they need it now" is the test — if there is no visible fact, there is no row.

Where does Mantis fit in this?

Mantis fills the first three columns of the table — company, fit, visible signal — from live sources rather than a bought list. Every search scans multiple live sources across Google Maps, business websites, social profiles and the open web. You still write the opener.

I have a technical product; my buyers aren't on Google Maps.

Then your signals are on GitHub, in changelogs, in job posts, in docs 404s. Change the source, not the loop. The ICP box, the 20, and the opener are the same.

Start finding clients today

Your next clients are
already nearby.

Find high-intent local businesses and grow your agency with confidence.

Get Free Access →Partner with us ›