DEV Community: Spencer Claydon

Paid Ads for Startups: How to Spend Your First $1,000

Spencer Claydon — Thu, 24 Sep 2026 15:08:28 +0000

Paid Ads for Startups: How to Spend Your First $1,000

Every first-time founder hits the same moment. The product works, a few people are using it, and organic growth is moving at the speed of a glacier. So you open Google Ads, put in a credit card, and tell yourself you'll "just test it."

Two weeks later, $800 is gone. You got 140 clicks, 3 signups, and zero paying customers. And you have no idea whether ads don't work for your business or you just did them wrong.

Here's the thing about paid ads for startups: they're one of the best learning tools you have and one of the worst growth engines you can bet on early. Used as an experiment with a fixed budget and a clear question, $1,000 can tell you more about your market than three months of posting on LinkedIn. Used as a hope-and-pray acquisition channel, it's a very efficient way to set money on fire.

This guide covers when to start, what things actually cost in 2026, which platform fits which kind of startup, and a week-by-week plan for spending your first $1,000.

Should an early-stage startup run paid ads at all?

Yes, but only after you can convert the traffic you already have. If your landing page doesn't turn organic visitors into signups, paid traffic won't either. It'll just fail faster and cost more.

The rough bar I'd use before spending a dollar:

At least 10 to 20 people have signed up or paid through channels you didn't pay for
You can explain in one sentence who the product is for and what it replaces
Your landing page converts cold visitors at something like 2% or better
You know roughly what a customer is worth to you over 12 months

That last one matters more than people think. Without a rough customer lifetime value, you have no way to say whether $60 per signup is a bargain or a disaster. If you haven't done the math yet, start with how to calculate customer lifetime value and then how to calculate customer acquisition cost.

There's one exception. You can run paid ads before you have a product if the goal is validation. A small smoke test, where you send $200 of traffic to a landing page and measure how many people try to sign up or pay, is one of the cheapest ways to find out if anyone cares. We cover that approach in detail in how to run a smoke test for your startup idea.

How much do paid ads cost for startups in 2026?

Paid ads cost more than most founders expect. Across industries, Google search clicks average about $5.42 in 2026, Meta traffic clicks average around $0.78, and LinkedIn clicks usually land between $5 and $10. Your real cost depends heavily on your category.

Here's a working snapshot from current benchmark data:

Platform	Typical cost per click	Minimum daily budget	Practical daily floor
Google Search	~$5.42 average (B2B software often much higher)	None	$20 to $50
Meta (Facebook, Instagram)	~$0.78 for traffic, ~$1.70 blended across objectives	$1	$20 to $30
LinkedIn	$5 to $10, spiking higher in Q3 and Q4	$10	$50 to $100
Reddit	$1.25 to $1.85 median	$5	$30 to $50

Meta CPMs (the cost to show your ad 1,000 times) rose about 20% year over year, from roughly $11.82 to $14.19. The cheap-attention era on Facebook is over.

LinkedIn costs swing with the calendar. Some advertisers report Q3 click costs running around 50% higher than Q1, because that's when every enterprise marketing team is burning through its annual budget.

The good news: WordStream's 2026 Google Ads data found average cost per lead dropped for the first time in five years, to about $66.69. Conversion rates also went up in 87% of industries. So clicks aren't cheap, but they're converting a bit better.

Now do the math on a $1,000 budget. At Google's average CPC, that buys roughly 184 clicks. If your landing page converts at 3%, that's 5 or 6 signups. Five signups isn't a growth channel. But it might be enough of a signal to tell you whether to keep going.

Which ad platform should a startup start with?

Pick the platform that matches how your customer already searches for or discovers solutions. If they know the problem and go looking, start with Google Search. If they don't know they need you yet, start with Meta or Reddit. Only start with LinkedIn if you sell to companies and your contract value can absorb $8 clicks.

Google Search: when people already know what they want

Search ads catch intent. Someone typing "invoice software for freelancers" has a problem right now. That's why Google clicks cost more: they're worth more.

It's the right first bet if your product fits into an existing category with search volume. It's a bad bet if you're creating a new category, because nobody is searching for something they don't know exists.

One early warning worth heeding: Dropbox's Drew Houston famously shared that paid search was costing them somewhere between $233 and $388 to acquire a customer for a $99 product. They stopped. The referral program that replaced it became one of the most studied growth loops in startup history. Search ads can be great. They can also be wildly unprofitable if your price point is low.

Meta: when you need to create demand

Facebook and Instagram are interruption channels. People aren't looking for you, so your creative has to stop the scroll and explain the problem in about two seconds.

Meta works well for consumer products, prosumer tools, and anything visual. Its targeting has gotten more automated over the years, which actually helps small advertisers (the algorithm finds buyers better than your hand-picked interest list will). The catch is that the algorithm needs data. Meta's delivery system generally wants around 50 conversions per ad set per week to exit its "learning phase" and stabilize. On a $30/day budget, you probably won't get there, so optimize for a cheaper upstream event like a landing page view or email signup.

Reddit: underrated for niche B2B and developer tools

Reddit is where a lot of first-time founders should start and almost none do. You can target specific subreddits, clicks are cheaper than Google or LinkedIn, and the audiences are extremely self-selected. A tool for Shopify store owners can run ads directly in r/shopify.

The tradeoff: Reddit users are allergic to anything that smells like marketing. Ads that read like a normal post from a founder ("I built this because X annoyed me, would love feedback") tend to beat polished brand creative.

LinkedIn: only if the math supports it

LinkedIn has the best B2B targeting on the internet. Job title, company size, industry, seniority. It also has some of the most expensive clicks. If your product costs $29/month, LinkedIn probably isn't for you yet. If you're selling a $10,000/year contract to heads of finance, a $9 click is a rounding error.

How should a startup spend its first $1,000 on ads?

Spend it as a four-week experiment with one platform, one audience, and one question you're trying to answer. Don't split $1,000 across four platforms. You'll end up with $250 of noise on each and learn nothing.

Here's a plan that works for most early-stage founders:

Week 1 ($150): Set up and sanity check. Install conversion tracking (Google Tag or the Meta Pixel) and confirm it's actually firing. Write 3 to 5 ad variations that each test a different angle: one leads with the pain, one with the outcome, one with a specific number. Launch with a small daily budget and watch for broken tracking, disapproved ads, or a landing page that loads slowly on mobile.

Week 2 ($300): Find the message that works. Let the ads run. Don't touch them for at least 3 or 4 days, no matter how tempting it is. By the end of the week, one or two angles will usually be pulling clearly ahead on click-through rate. Kill the bottom half.

Week 3 ($350): Test the landing page. Now that you know which message gets clicks, check whether that message carries through. Does your landing page headline match the ad that got someone there? Mismatched promises are the single biggest leak I see. If the ad says "Close your books in 10 minutes" and the page says "The all-in-one finance platform," you'll lose people instantly. Our guide on how to write a landing page that converts goes deeper on this.

Week 4 ($200): Measure and decide. Pull your numbers: cost per click, landing page conversion rate, cost per signup, and if you have them, cost per paying customer. Compare that cost to what a customer is worth over a year.

At the end, you should be able to answer one of three things:

The channel works, and it's worth spending more to confirm it at a higher budget
The channel could work, but the landing page or offer is the bottleneck
The channel doesn't work for this product at this price point, at least not yet

What metrics matter when a startup runs paid ads?

The metric that matters most is cost per paying customer compared against customer value. Everything else (clicks, impressions, click-through rate) is a diagnostic that helps you find where the funnel breaks.

Work backward through the funnel:

Cost per paying customer (CAC): The only number your bank account cares about.
Signup to paid conversion: If people sign up but don't pay, that's a product or onboarding problem, not an ad problem.
Landing page conversion rate: If people click but don't sign up, the page or offer is off.
Click-through rate: If people see the ad but don't click, the creative or targeting is off.
Cost per click: Mostly outside your control. Useful for planning, not for diagnosing.

A useful rule for SaaS: aim to earn back what you spent to acquire a customer within 12 months or less. So if your product is $39/month and a customer sticks around for a year, you can afford to spend meaningfully less than $468 to acquire them, once you account for your margins and churn. The exact target depends on your cash position, which is why CAC payback period is worth calculating before you scale anything.

What are the most common paid ad mistakes first-time founders make?

The most common mistake is running ads before the rest of the funnel works. The second most common is changing everything every day. Ad platforms need time and data to optimize, and founders rarely give them either.

A few others that come up constantly:

Using broad match keywords on Google. Broad match lets Google show your ad for anything it thinks is related. For a small budget, this usually means paying for irrelevant searches. Start with phrase or exact match and check the search terms report weekly.

Sending traffic to the homepage. Your homepage tries to speak to everyone. Your ad should land people on a page built for that ad's specific promise.

Optimizing for the wrong event. If you tell Meta to get you clicks, it will find people who click on everything. If you tell it to get signups, it will find people who sign up. Pick the event closest to revenue that you can realistically get enough volume on.

Not setting a hard cap. Set a lifetime budget or a daily cap before you launch. Platforms are very good at spending money, and "I'll keep an eye on it" isn't a budget.

When should a startup scale paid ads?

Scale when you've hit a cost per customer that works at your current budget for at least 3 or 4 consecutive weeks. Then raise the budget by 20 to 30% at a time, not by 5x overnight.

Why slow? Your first few hundred dollars reach the most interested people in your audience. Spend more and you reach less interested people, so costs climb. Doubling your budget rarely doubles your customers.

It also helps to plan where paid fits into your overall channel mix before you pour money into it. A lot of the startups I've seen do this well sketch out their channels, budgets, and targets in one place first. You can do that in a spreadsheet, Notion, or a planning tool like Foundra that has a go-to-market module for mapping channels against your numbers. The tool matters less than doing it before you're committed.

And if paid isn't working yet, that's fine. Plenty of great companies grew almost entirely without it. Organic channels like free tools, content, and communities often compound better at the early stage, and you can always come back to ads once you have more data and a tighter offer.

Key takeaways

Paid ads for startups are best used as a fixed-budget experiment, not a growth plan, until your landing page and offer convert on organic traffic.
2026 benchmarks: Google Search averages about $5.42 per click, Meta around $0.78 for traffic, LinkedIn $5 to $10, and Reddit roughly $1.25 to $1.85.
Pick one platform based on how your customer finds solutions. Search for existing demand, Meta or Reddit for creating it, LinkedIn only for high-value B2B.
Spend your first $1,000 over four weeks with one audience and one question.
Judge success by cost per paying customer compared to customer value, not by clicks or impressions.
Scale slowly, 20 to 30% at a time, once the numbers hold for several weeks.

FAQ

How much should a startup spend on paid ads?

Start with a fixed test budget of $500 to $1,500 over four weeks on a single platform. That's enough to get directional data without risking runway. Only increase spend once your cost per paying customer is clearly below what a customer is worth to you.

Are Google Ads worth it for startups?

Google Ads are worth it when people already search for your category and your price point can cover $5+ clicks. They're usually not worth it for brand new categories with no search volume, or for low-priced products where acquisition costs would outrun revenue.

Are Facebook ads good for B2B startups?

They can be, especially for small business and prosumer audiences who spend time on Instagram and Facebook. For enterprise buyers, LinkedIn or Google Search usually performs better. Meta's B2B click costs tend to run $2.50 or more, well above its consumer averages.

Should I run ads before launching my product?

Only for validation. A small landing page test with $100 to $300 of ad spend can show whether people will sign up or pre-order. Don't run ads to build hype for a product that isn't ready to convert visitors into users.

What's a good cost per acquisition for a startup?

A good CAC is one you can earn back within roughly 12 months from that customer's gross profit. For a $39/month SaaS product, that means staying comfortably under a few hundred dollars per paying customer. For a $500/month product, you have much more room.

Email Marketing for Startups: A Founder's Playbook

Spencer Claydon — Wed, 23 Sep 2026 15:08:36 +0000

Email Marketing for Startups: A Founder's Playbook

Most founders treat email as the thing they'll get to after the product is done. Then they launch, get 200 signups from a Product Hunt spike, and realize they have no way to reach any of them again.

That's the actual problem email solves. Every other channel is rented. Your X reach depends on an algorithm that changed last Tuesday. Your Google rankings depend on a core update nobody warned you about. Your email list is the only audience you own outright, and it's the only one that still works when a platform decides you're less interesting this quarter.

Here's the part nobody tells first-time founders: email marketing for startups looks almost nothing like email marketing for established companies. You don't need a newsletter. You don't need a content calendar. You need about four emails that do specific jobs, and a list that isn't full of people who will never buy.

What is email marketing for startups actually for?

For an early-stage startup, email does three jobs: it turns anonymous visitors into people you can contact, it converts trial users into paying ones, and it keeps churned or cold users from disappearing forever. Newsletters are optional. Those three jobs are not.

Think about where email sits in your funnel. Someone lands on your site from a blog post. They're interested but not ready. Without email, that's the end of the relationship. With email, you've got a second, third, and fifteenth chance.

The numbers back this up in a way that's hard to argue with. Flow-based emails, meaning the automated ones triggered by something a user did, pull roughly 3x the click rate of broadcast campaigns (around 5.6% versus 1.7%). Welcome emails specifically hit open rates north of 50% on average, sometimes far higher, compared to the 21-27% you'd see on a standard campaign.

So the email work that pays off most for a startup is almost entirely automated and almost entirely triggered. Which is good news, because you don't have time to write a weekly newsletter.

How do you build an email list from zero?

You build a list by giving people a specific reason to hand over their address, not by putting a "subscribe to our newsletter" box in the footer. Nobody subscribes to newsletters from companies they've never heard of.

The mechanics that actually work for early-stage startups:

Gate something useful. Build a free tool, calculator, template, or teardown that solves a narrow problem, then show partial results for free and email-gate the full output. This works because the person has already gotten value before you ask. We covered this pattern in depth in our piece on free tools as a distribution channel, and it's how a lot of small startups build their first thousand subscribers without paid spend.

Offer a real lead magnet. Not an ebook. A checklist, a spreadsheet model, a Notion template, a swipe file. Something a founder would actually open twice. Ours is a 10-page starter kit, and the rule we use is simple: if you wouldn't pay $20 for it, don't ask for an email address for it.

Ask at the end of your best content. If someone read 2,000 words of your article, they're warm. That's the moment to offer something related, not a generic signup box.

Waitlists, carefully. A waitlist gets you addresses fast, but it's not validation. People will join a list for free and never pay you a cent. We wrote about that trap in why a waitlist isn't validation. Collect the emails, sure. Just don't confuse the number with demand.

One thing to avoid completely: buying a list, scraping one, or importing your LinkedIn connections. Beyond the legal issues in most jurisdictions, it torches your sender reputation before you've built one. More on that below.

What should your welcome sequence say?

Your welcome sequence should do one thing: get the new subscriber to take the single most valuable action in your product, as fast as possible. That's it. Not tell your founding story. Not explain your values.

A four-email sequence that works for most early startups:

Email 1, sent immediately. Deliver whatever they signed up for. Lead magnet link, tool output, trial login. Add one sentence explaining what the next email will cover. Nothing else. This email will get opened by half your list or more, so don't waste it on a manifesto.

Email 2, day two. Show the outcome, not the feature. If your product builds financial models, don't explain the model builder. Show a founder who walked into an investor meeting with numbers that held up. One concrete story beats a feature list every time.

Email 3, day four. Handle the biggest objection. For most first-time-founder products, that objection is "I don't have time for this." Answer it directly with a smaller ask: the 15-minute version, the one-section version, the free version.

Email 4, day seven. Ask for a reply. Not a purchase. A reply. "What are you stuck on right now?" Replies do two things: they tell you what your positioning is missing, and they signal to inbox providers that your mail is wanted, which helps everything you send afterwards.

Write these as plain text from a real person at a real name, not noreply@. Plain-text-looking emails from a founder consistently outperform designed templates in early-stage B2B. Partly deliverability, mostly because they don't feel like marketing.

How often should a startup send emails?

Send as often as you have something specific to say, with a hard floor of once a month so people don't forget who you are. For most pre-revenue and early-revenue startups, that lands somewhere between two and four broadcast emails a month, on top of your automated sequences.

The failure mode isn't sending too much. It's sending on a schedule with nothing to say. A weekly newsletter you dread writing becomes a weekly newsletter nobody reads, and dead weight on your list drags down deliverability for everything else.

Better model: batch your sends around real events. You shipped something. You learned something from 20 customer interviews. You published a piece of research worth reading. Three useful emails a quarter beat twelve filler ones.

And if you go quiet for two months, don't pretend you didn't. Open with "it's been a while" and get on with it. Founders overestimate how much anyone noticed.

What email metrics actually matter in 2026?

Click-to-open rate, reply rate, and unsubscribe rate matter. Raw open rate mostly doesn't anymore, because Apple's Mail Privacy Protection pre-loads tracking pixels and inflates the number for anyone using Apple Mail.

This trips up a lot of founders. You'll see average open rates quoted anywhere from 21% to 44% depending on whose data you read, and the spread exists largely because of how each provider handles MPP-inflated opens. Treating a 40% open rate as a win when a chunk of it is machine-opened is how you end up optimizing subject lines that aren't broken.

What to watch instead:

Metric	What it tells you	Rough B2B SaaS range
Click-to-open rate	Whether the email delivered on the subject line	8-15%
Click-through rate	Overall message effectiveness	2-4%
Reply rate (1:1 and sequences)	Real engagement, best early signal	3-8%
Unsubscribe rate	Whether you're sending too much or to the wrong people	Under 0.5%
Spam complaint rate	Deliverability risk	Under 0.1%

Reply rate is the one most founders ignore and shouldn't. At fewer than 500 subscribers, a reply is worth more than a hundred opens. It's a customer discovery interview that started itself.

Track these against your own baseline, not against industry averages. Your list of 300 people who downloaded a startup planning template is a different animal from a 50,000-person ecommerce list, and the benchmarks won't transfer cleanly.

How do you stay out of the spam folder?

You stay out of spam by authenticating your domain, keeping complaint rates under 0.3%, and only emailing people who asked. As of 2026 this isn't optional advice, it's enforced policy at Gmail, Yahoo, Microsoft, and Apple.

The requirements, in plain terms:

Set up SPF, DKIM, and DMARC on your sending domain. Google now requires DKIM specifically; having SPF and DMARC without it still fails the check. Your email provider will walk you through the DNS records. Budget an hour.
Keep spam complaints below 0.3%. Google's actual guidance is to stay under 0.1% and never touch 0.3%. Once you cross it, deliverability degrades and recovers slowly.
One-click unsubscribe (RFC 8058) on every marketing email. Required by Google, Yahoo, and Apple.
Valid reverse DNS and TLS. Handled by your provider in almost every case.
Warm up gradually. Don't go from zero to 5,000 sends in a day on a fresh domain.

Google and Microsoft now issue permanent 550 rejections for non-compliant bulk mail, so the old "we'll fix deliverability later" approach doesn't survive first contact with a real list.

One more thing: prune aggressively. If someone hasn't opened anything in six months, run a single re-engagement email, then remove them. A smaller list that engages beats a bigger one that doesn't, and inbox providers are watching engagement to decide where your mail lands.

What tools should a startup use?

Pick based on where you are, and expect to switch once. Nobody's first email tool is their last one.

Under 1,000 subscribers, content-led: Kit (formerly ConvertKit), Buttondown, or Beehiiv. Cheap or free, good automation, built for creators and small teams.
Product-led SaaS with in-app behavior: Loops, Customer.io, or Resend paired with your own triggers. You need to send based on what users do inside the product, not just what list they're on.
Transactional only: Postmark or Resend. Keep transactional and marketing mail on separate subdomains so a bad campaign never risks your password reset emails.
Ecommerce: Klaviyo, and it isn't close.

Don't start with HubSpot or Marketo. The cost of the tool isn't the problem, the cost of your time configuring it is.

Whichever you pick, the email tool is one piece of a broader acquisition plan, and it's worth mapping the whole thing before you optimize any single channel. You can do that in a spreadsheet, in Notion, or in a planning tool like Foundra that walks first-time founders through channel strategy section by section. The format matters less than actually doing it.

What are the most common email mistakes founders make?

The most common mistake is writing to a list instead of to a person. The second is building the list before knowing what you'd say to it.

Others worth naming:

Designing when you should be writing. A template with a hero image and three columns looks professional and converts worse than three paragraphs from a founder.
Asking for the sale in email one. You haven't earned it yet.
Sending from noreply@. You're explicitly telling people you don't want to hear from them, then wondering why nobody replies.
Confusing list size with pipeline. 5,000 subscribers who joined for a free template are not 5,000 prospects. Segment by what they did, not just when they joined.
Ignoring the data you're sitting on. Every reply, every click, every unsubscribe is signal about your positioning. Most founders never read it.
Starting a newsletter out of obligation. If you don't have something to say this week, don't send. Nobody is waiting.

Key takeaways

Email is the only audience channel you own. Everything else is rented from a platform that can change the terms.
For early startups, automated triggered emails matter far more than broadcasts. Flows out-click campaigns roughly 3 to 1.
Build your list by gating something specifically useful, not with a footer signup box.
A four-email welcome sequence that drives one key action beats a 12-part drip nobody finishes.
Ignore raw open rate. Watch click-to-open, reply rate, and unsubscribes.
Set up SPF, DKIM, and DMARC before your first real send. Gmail, Yahoo, Microsoft, and Apple now enforce it with hard rejections.
Keep complaint rates under 0.3%, ideally under 0.1%, and prune inactive subscribers without sentiment.

FAQ

How many subscribers does a startup need before email is worth doing?
About 100. Below that, you're better off sending individual emails by hand, which will teach you more about your customers than any automation. Above 100, set up a welcome sequence. The automation pays for itself in time saved.

Should my startup start a newsletter?
Only if you have a genuine content angle and the discipline to sustain it for six months. For most early startups, a lifecycle sequence plus occasional product updates delivers more revenue per hour spent than a newsletter does.

What's a good email open rate for a startup in 2026?
Somewhere between 21% and 44%, depending on whose benchmark you use and how much Apple Mail traffic you have. That range is wide enough to be nearly useless, which is why click-to-open rate (8-15% for B2B SaaS) is the better number to optimize against.

Can I email people who signed up for my waitlist?
Yes, if they opted in knowingly. What you can't do is treat waitlist signups as qualified demand. Waitlist joins are free; purchases aren't. Test willingness to pay separately before you build around the number.

Do I need DMARC if I'm only sending 200 emails a week?
Technically the bulk sender rules kick in at 5,000 messages per day to Gmail addresses, so a small list isn't strictly covered. Set it up anyway. It takes an hour, it improves inbox placement immediately, and you won't have to scramble when volume grows.

How do I write subject lines that get opened?
Be specific and slightly incomplete. "The pricing mistake that cost us 40% of revenue" beats "Our latest update." Avoid clickbait you can't pay off in the first sentence, because a subject line that oversells trains people to stop opening.

How to Calculate CAC Payback Period (2026 Benchmarks)

Spencer Claydon — Tue, 22 Sep 2026 20:14:51 +0000

You spent $900 on ads last month and got three customers. Each pays you $60 a month. So you're fine, right?

Not yet. You're $900 in the hole and earning $180 a month against it. Five months from now you break even. And that's before you subtract what it costs to actually serve those people.

That gap, between the day you spend the money and the day you get it back, is your CAC payback period. It's the single most useful number a bootstrapped or early-stage founder can track, and most first-time founders either don't calculate it or calculate it wrong. Here's how to do it properly.

What is CAC payback period?

CAC payback period is the number of months it takes for a customer's gross profit to cover what you spent acquiring them. If you spend $300 to land a customer who generates $50 of gross profit a month, your payback period is six months.

Think of it as the speed at which your marketing dollar recycles. A short payback means the same $10,000 can be spent again and again in a year. A long payback means that money is locked up, and you need outside cash to keep growing.

This is different from LTV:CAC ratio, which we'll get to. LTV:CAC tells you whether acquiring a customer is profitable eventually. Payback period tells you when. When you're small, when matters more.

How do you calculate CAC payback period?

The formula is:

CAC Payback Period = CAC ÷ (Monthly Revenue per Customer × Gross Margin)

Three inputs. Let's take them one at a time.

CAC (customer acquisition cost). Total sales and marketing spend in a period, divided by new customers acquired in that period. Include ad spend, content costs, tools, agency fees, commissions, and the fully loaded cost of anyone whose job is getting customers. If you're a solo founder doing your own marketing, most people exclude their own salary. That's a defensible choice, but know that it flatters the number.

Monthly revenue per customer. Usually your ARPA (average revenue per account). For a $39/month product, that's $39. If you sell annual plans at $390, divide by 12 to get $32.50.

Gross margin. Revenue minus cost of goods sold, expressed as a percentage. For software, COGS means hosting, third-party API calls, payment processing fees, and support costs. Not your rent. Not your dev salaries.

Here's a worked example. Say you run a B2B tool at $150/month. Last quarter you spent $36,000 on sales and marketing and signed 40 customers.

CAC = $36,000 ÷ 40 = $900
Monthly revenue per customer = $150
Gross margin = 78%, so gross profit per customer per month = $150 × 0.78 = $117
CAC payback = $900 ÷ $117 = 7.7 months

Just under eight months. That's a healthy number, and we'll see why in a moment.

Why does gross margin matter so much?

Because skipping it can make your payback look twice as good as it really is, and founders skip it constantly.

Run the same example without gross margin: $900 ÷ $150 = 6 months. That's a 22% understatement. Not catastrophic at 78% margin. But try it on a business with thinner economics.

An AI product burning real inference costs might run at 45% gross margin. Same $900 CAC, same $150 price. Gross profit per month is $67.50, not $150. Payback is 13.3 months, not 6. You'd be planning your hiring around a number that's off by more than a year.

This is why AI-native startups are quietly having a harder time than the 2015 SaaS cohort did. Classic software had 80% margins because serving one more user cost nearly nothing. When every query costs you money, margin becomes a first-class variable in your model, not a footnote. If you haven't built margin into your projections yet, that's the fix to make before anything else.

For a deeper walk through the surrounding metrics, see our pieces on customer acquisition cost and unit economics for startups.

What's a good CAC payback period in 2026?

The median B2B SaaS company takes about 16 months to pay back CAC. Top-quartile companies do it in six months or less. Bottom quartile takes 24 months or more.

But the median hides a lot. Payback scales with deal size, because bigger deals require salespeople, and salespeople are expensive.

Segment	Typical ACV	CAC payback
Self-serve / SMB	Under $5,000	8 to 12 months
Mid-market	$15,000 to $100,000	14 to 18 months
Enterprise	$100,000+	18 to 24 months

One encouraging data point: median payback improved about 11% between 2024 and 2025, from roughly 18 months down to 16. That wasn't caused by companies spending more. It came from go-to-market discipline, cutting channels that never worked and doubling down on the ones that did.

So what should you aim for? If you're pre-revenue or under $500k ARR and bootstrapping, treat 12 months as your ceiling. Anything longer and you're funding growth from savings, which is a race against your own runway. A venture-backed company can carry a 20-month payback because the money's already in the bank. You probably can't.

Quick sanity check on your own number: if your CAC payback is longer than your average customer's lifetime, you're not building a business. You're buying customers at a loss and hoping volume fixes it. It won't.

Why CAC payback beats LTV:CAC for early-stage founders

LTV:CAC is the metric everyone quotes. The famous rule is 3:1. And for a company with three years of cohort data, it's a fine measure.

For a startup that's nine months old, it's mostly fiction.

LTV depends on churn. Churn depends on retention over time. If your oldest customer signed up in February, you don't have retention data. You have a guess dressed up as a number. I've seen founders build a $40M revenue projection on an assumed 2% monthly churn rate they pulled from a blog post, and the whole model collapsed when real churn came in at 7%.

CAC payback uses only things you can observe today: what you spent, what customers pay, what it costs to serve them. No forecasting required. That makes it harder to fool yourself with.

It also maps to the question you actually care about, which is cash. A 3:1 LTV:CAC ratio that takes four years to materialise doesn't help you make payroll in March.

Use payback period to run the business month to month. Bring LTV:CAC out once you have twelve months of cohort data and are talking to investors. Both belong in your financial model; they just answer different questions. You can build this in a spreadsheet, in Causal, or in a planning tool like Foundra that walks first-time founders through the projection section step by step.

How do you shorten your CAC payback period?

Four levers, roughly in order of how quickly they move.

1. Raise prices. The fastest lever, and the one founders resist hardest. A 20% price increase on a $150 product drops an eight-month payback to about 6.5 months, and it costs you nothing to implement. Most early-stage products are underpriced because the founder is pricing against their own discomfort rather than the value delivered. If less than 20% of your prospects push back on price, you're too cheap.

2. Push annual billing. If a customer prepays twelve months upfront, your payback period on that customer is effectively day one. Even a 15% annual discount is usually worth it, because you've converted a twelve-month cash drag into immediate working capital. Offer it at checkout, not as an afterthought in a renewal email.

3. Fix your gross margin. Audit what each customer actually costs you. For AI products, this means caching aggressive, routing cheap queries to smaller models, and killing the free tier that's eating your inference budget. Ten margin points is often sitting there in infrastructure choices nobody's revisited since launch.

4. Kill your worst channel. Blended CAC hides bad spend. Break CAC out by channel and you'll usually find one that's two or three times worse than the average. Cut it. That alone moves the blended number without any new work.

And one more that's slower but compounds: build acquisition that doesn't cost per customer. Free tools, content that ranks, a community, word of mouth. These have real upfront cost and near-zero marginal cost, which means CAC falls over time instead of rising. We wrote about this in free tools as a distribution channel.

When does CAC payback period mislead you?

Three situations where the number looks better than reality.

Blended CAC with a big organic base. If 70% of your signups come from a Hacker News post you wrote once, your blended CAC is tiny and your paid channels might be terrible. Always calculate paid CAC separately. That's the number that tells you whether you can buy growth.

Ignoring churn during the payback window. A twelve-month payback assumes the customer is still there in month twelve. At 8% monthly churn, only about 37% of a cohort survives that long. Your effective payback across the cohort is far worse than your per-customer math suggests. Check your payback period against your median customer lifetime, not your best customer.

Counting bookings instead of cash. A customer who signs a $1,200 annual contract billed quarterly hasn't given you $1,200. Model the cash as it arrives, especially if runway is tight.

There's also a less obvious failure: optimising payback too hard. You can get payback down to two months by only chasing customers who convert instantly, and end up with a business that has no room to grow. Efficiency is not the goal. Efficiency that funds growth is.

Key takeaways

CAC payback period = CAC ÷ (monthly revenue per customer × gross margin). Leave out gross margin and you'll overstate your health, badly if margins are thin.
Median B2B SaaS payback is about 16 months in 2026. Top quartile is under six. Self-serve should target 8 to 12; enterprise motions run 18 to 24.
If you're bootstrapping, treat 12 months as a hard ceiling. Longer than that and growth comes out of your savings.
Payback period beats LTV:CAC in your first year because it uses observed data instead of guessed churn.
The fastest ways to shorten it: raise prices, sell annual plans, fix gross margin, cut your worst channel.
Always check payback against real customer lifetime. A ten-month payback on a customer who leaves in month seven is a loss, not a metric.

Frequently asked questions

What is a good CAC payback period for an early-stage startup?
Under 12 months if you're bootstrapped, since you're funding acquisition from your own cash. Venture-backed companies can tolerate 18 to 24 months. Top-quartile SaaS companies recover CAC in six months or less.

Should I include my own salary in CAC?
Most founders exclude it while they're pre-revenue, which is reasonable. Just be consistent, and note the exclusion when you show the number to an investor. The moment you hire someone to do marketing, their fully loaded cost goes in.

What's the difference between CAC payback period and LTV:CAC?
Payback period measures how fast you recover acquisition cost, in months. LTV:CAC measures whether the customer is profitable over their whole lifetime, as a ratio. Payback is a cash-flow question; LTV:CAC is a profitability question. Early on, cash flow is the one that can kill you.

How does annual billing change CAC payback?
Dramatically. A prepaid annual plan covers your CAC immediately in most cases, turning a twelve-month cash drag into same-day recovery. This is why so many SaaS companies discount annual plans 15 to 20%: they're buying working capital.

Can CAC payback period be too short?
Yes, in the sense that a very short payback often means you're underinvesting in growth. If you're recovering CAC in two months and growing 5% annually, you have room to spend more aggressively. Efficiency only matters if it's funding expansion.

How often should I recalculate it?
Monthly if you're spending on paid channels, quarterly if you're mostly organic. Recalculate immediately after any price change or major channel shift, because both reset the math.

How to Test Willingness to Pay Before You Build

Spencer Claydon — Mon, 21 Sep 2026 15:08:57 +0000

Every founder I talk to has a number in their head. Twenty-nine a month. Ninety-nine a seat. Five grand for the pilot. Ask where the number came from and you get some version of "it felt about right" or "that's what the competitor charges."

That's not pricing. That's a guess wearing a dollar sign.

Willingness to pay is the amount a specific customer will actually hand over for a specific outcome, and it's the one validation signal that can't be talked around. Someone can love your demo, forward it to a colleague, join your waitlist, and still never pay you a cent. The gap between enthusiasm and payment is where most first-time founders lose six months. So let's close it before you write the code.

What does willingness to pay actually mean before you have a product?

Willingness to pay is the highest price a buyer would accept before they walk away, measured by behaviour rather than opinion. Pre-launch, you're not measuring a number. You're measuring whether a number exists at all.

There's a distinction that matters here and almost nobody makes it. There are two separate questions hiding inside "will they pay?":

Will anyone pay anything? (Does the problem hurt enough to open a wallet?)
How much will they pay? (Where does the number land?)

Question one is a validation question. Question two is a pricing question. If you try to answer both with the same test, you get a muddy result and usually an optimistic one. Answer question one first. A founder who knows eleven people will pay something has a business. A founder who knows the theoretically optimal price for a product nobody wants has a spreadsheet.

Why do price surveys give you the wrong number?

Because people are bad at predicting their own future spending, and worse at disappointing you to your face. Hypothetical questions produce hypothetical answers, and hypothetical answers skew high on interest and low on price.

Ask "would you pay $40 a month for this?" and you're asking two things at once: do you like me, and is $40 reasonable in the abstract. Most respondents answer the first question. Research on the Van Westendorp method, which I'll get to in a second, is explicit about this: results are biased by the hypothetical framing and by the method's focus on the point of minimum customer resistance rather than maximum revenue.

That doesn't make surveys useless. It makes them a range-finder, not a decision. Here's the hierarchy I'd use, weakest signal at the top:

Signal	What it proves	Strength
"Yes, I'd pay for that"	They're being polite	Near zero
Waitlist signup	Mild curiosity, zero cost to them	Weak
Survey price ranges (Van Westendorp)	Rough price corridor	Directional
Pricing page click to checkout	Interest survives a real number	Moderate
Refundable deposit	Money moved	Strong
Signed LOI or paid pilot	Budget owner committed	Strongest

Notice the pattern. Signal strength tracks exactly with how much it costs the respondent to say yes. Free yes, worthless. Costly yes, meaningful. That's the whole framework, and if you remember nothing else from this article, remember that line.

We wrote a longer piece on why waitlists specifically fail this test, and the short version is that a waitlist measures curiosity at a price of zero, which tells you almost nothing about behaviour at a price above zero.

How do you run a Van Westendorp price sensitivity test?

You ask four questions about price after showing a clear product description, then plot the answers to find the range where most people think price and value line up. It takes about 40 respondents to be useful and about 200 to be stable.

The four questions, in this exact order:

At what price would this be so expensive you wouldn't consider it?
At what price would this be expensive, but still worth considering?
At what price would this feel like a bargain?
At what price would this be so cheap you'd question the quality?

Plot the cumulative curves and you get two useful intersections. The point where "too cheap" crosses "too expensive" is the price of indifference. The range between the other two crossings is your acceptable corridor. Tools like Conjointly, Qualtrics, and SurveyMonkey will draw the chart for you, or you can do it in a spreadsheet in twenty minutes.

Three rules for making it worth the effort:

Describe the outcome, not the features. "A tool that cuts your monthly close from five days to one" gets you a real answer. "An AI-powered financial workspace" gets you noise.

Recruit the actual buyer. Twelve responses from people who have the problem and the budget beat 300 from a general audience. If you're B2B, the person who'll sign the invoice is the only respondent who counts.

Treat the output as a corridor, not a price. Van Westendorp tells you where the walls are. It does not tell you where to stand.

What's the strongest signal you can get before you build?

A payment. Failing that, a signed commitment from someone with budget authority. In B2B, a paid pilot or a signed letter of intent is the strongest demand signal that exists, and it's the one investors actually weigh.

The ladder, from easiest to run to most convincing:

Refundable deposit. Ask for $20 or $50 against a future subscription, fully refundable, no questions. You're not raising money. You're buying information. The friction of entering a card is the test, and a deposit conversion rate above roughly 1.5% of qualified traffic is a real proceed signal.

Pre-order at a founding price. Charge for annual access at a discount before launch, with a hard refund promise and a delivery date you'll actually hit. Fieldboom famously got 100 paying customers before writing a line of code. That's an outlier, but the mechanic is boring and repeatable.

Paid pilot. B2B only. You charge a real fee, usually a few thousand, for a scoped engagement that you may deliver semi-manually. If a company pays for a pilot, the problem has a budget line. Three to five signed pilots or LOIs is roughly the bar most seed investors treat as convincing.

Letter of intent. Non-binding, but it forces a named person to put the commitment in writing, which surfaces every hidden approval step in their org. The LOI that dies in procurement taught you something valuable and cost you a week.

One warning on pre-selling. Take money and you've made a promise. Set a date you can defend, write the refund terms in plain English, and refund without argument if you slip. A founder who refunds cleanly keeps the relationship. A founder who goes quiet burns the only twenty people who believed them early.

How do you test willingness to pay with a pricing page?

Put up a real pricing page with real numbers and a real checkout button, drive qualified traffic to it, and measure how many people click through to pay. This is a smoke test, and it's the cheapest quantitative read you'll get.

The setup takes an afternoon:

One landing page that describes the outcome, with three price tiers.
A checkout button that leads to either a real payment flow or an honest "we're onboarding in batches, leave your email and a deposit to hold your spot."
Traffic from somewhere qualified: a niche subreddit, a LinkedIn post to your own network, a small paid test, a relevant newsletter.
Enough volume to mean something. Under 200 qualified visitors, you're reading tea leaves.

Then run the same page at two different price points. Split traffic, or run price A for a week and price B the next. What you're looking for isn't just which converts better. It's whether the conversion rate moves at all. If doubling the price barely dents conversion, you're underpriced and you've learned something worth more than the test cost. If halving it doesn't lift conversion, price isn't your problem. The product promise is.

Be careful with the fake-door version of this. Taking someone to a dead end feels clever and costs you trust. An honest pre-launch checkout with a deposit gets you a stronger signal and leaves the relationship intact.

What numbers count as a pass?

There's no universal threshold, but there are ranges that experienced founders use as a gut check. Here's what I'd treat as a proceed signal at pre-launch scale:

Test	Weak	Worth continuing	Strong
Pricing page visit to checkout click	Under 2%	3 to 5%	Over 8%
Qualified traffic to paid deposit	Under 0.5%	1.5%	Over 3%
Customer conversations to paid pilot (B2B)	1 in 40	1 in 15	1 in 8
Pre-orders from your own network of 100	Under 3	6 to 10	Over 15

Two caveats. These assume qualified traffic, meaning people with the problem, not your Twitter followers being supportive. And the B2B numbers assume you're talking to budget holders, not enthusiastic managers who then need to ask someone.

If you land in the weak column, that isn't a failure. It's a finding, delivered three months before you'd have got it the expensive way. The usual next move is to narrow the audience rather than drop the price. Weak willingness to pay across a broad group often hides strong willingness to pay inside a narrow one.

How do you turn a tested number into an actual price?

Combine the corridor from your survey with the behaviour from your paid tests, then set the launch price near the top of what behaviour supports, not the middle of what the survey suggested. You can raise prices later, but the first hundred customers anchor your positioning for years.

A worked example. Say your Van Westendorp corridor lands between $19 and $65, with a price of indifference around $34. Your pricing page test shows $29 and $49 converting within a point of each other. Your five paid pilots came in at $2,000 each without a negotiation. What that pattern says: buyers aren't price sensitive in this band, and $34 was the survey being polite. Launch at $49, and watch churn and objections for the first sixty days.

This is the point where the numbers need to live somewhere other than your head. You've got a price corridor, conversion data at two points, pilot revenue, and a cost base that determines whether any of it works. Most founders keep this in four different places and lose the thread. A spreadsheet is fine. Notion is fine. A planning tool like Foundra walks first-time founders through the pricing and unit economics sections in one place if a blank sheet is the thing stopping you. The tool matters less than the discipline of writing the assumptions down where you can check them against reality in ninety days.

What mistakes kill these tests?

Four show up again and again:

Testing on friends. Your network will pre-order out of affection. Weight those sales at roughly a tenth of a stranger's.

Asking about price before establishing the problem. If the respondent doesn't feel the pain, every price is too high, and your data is about them, not your product.

Running one test and calling it validated. One signal is an anecdote. A survey corridor plus a pricing page test plus three paid commitments is a case.

Confusing "no" with "not yet." Timing kills more deals than price. When someone declines, ask what would have to be true for this to be worth paying for. The answer is usually your roadmap.

Refusing to test high. Almost every first-time founder underprices. Test a number that makes you slightly uncomfortable to say out loud. Worst case, nobody clicks and you've bought that information for the cost of a landing page.

Key takeaways

Willingness to pay is measured by behaviour, not opinion. The strength of any signal equals what it cost the person to give it.
Answer "will anyone pay anything?" before "how much?" They're different questions and mixing them produces mush.
Van Westendorp gives you a corridor in an afternoon, but its results skew low and hypothetical. Use it to frame tests, not to set price.
Refundable deposits, pre-orders, paid pilots, and signed LOIs are the signals that hold up. Three to five paid pilots or LOIs is the rough bar for B2B credibility.
Run a pricing page smoke test at two price points. If conversion barely moves when you double the price, you're underpriced.
Launch near the top of what behaviour supports. Your first hundred customers anchor your positioning.

FAQ

How many people do I need for a willingness to pay test?
For a Van Westendorp survey, 40 qualified respondents gives you a usable shape and 200 gives you a stable one. For behavioural tests, you need around 200 qualified visitors to read a conversion rate, or 5 to 10 real sales conversations for B2B.

Can I test willingness to pay without a product?
Yes. A landing page with a clear outcome promise, real prices, and a deposit or pre-order flow tests it without any product existing. That's the entire point of running the test before you build.

Is it ethical to charge before the product exists?
It is, if you're honest about the delivery date, offer a clean refund, and actually refund when you slip. Pre-orders are a normal commercial arrangement. Silence after taking money is not.

What if people say yes but never pay?
That's the expected result and the reason you're testing. Verbal yes converts to payment at a low single-digit rate for most pre-launch products. Stop counting verbal commitments as pipeline and the picture gets clear quickly.

Should I test price or product first?
Together. Price is part of the offer, and an offer tested at zero cost tells you nothing about the offer at $49. Put the number on the page from the first test.

What if my willingness to pay comes back too low to build a business?
Narrow the audience before you drop the price. A segment with acute pain and budget will often pay five times what a general audience will for the same product. If no segment clears your cost base, you've saved yourself a year, and that's a win worth taking.

The Saturation Test: AI Startup Ideas to Avoid in 2026

Spencer Claydon — Sun, 20 Sep 2026 15:09:34 +0000

You had the idea in the shower. An AI tool that does the boring part of your old job. You checked, and nothing quite like it exists, at least not the way you'd build it. So you opened a repo.

Stop for twenty minutes.

The question that kills most AI startups in 2026 isn't "can I build this." Of course you can. Everybody can. The question is whether the category you're walking into still has room for a new entrant, or whether it closed sometime in the last eighteen months while nobody sent out a memo. Around 14,000 AI startups launched globally in 2024. By early 2026, roughly 40% of that cohort had shut down, and various analysts put the eventual failure rate at 80% or higher. Those aren't bad founders. A lot of them are smart people who picked a category that was already full.

This is a test for figuring out which one you're in before you spend six months finding out.

What makes an AI startup category saturated?

A category is saturated when the gap between what your product costs to run and what a customer will pay for it has collapsed to nothing. That's the whole definition. Competitor count is a symptom, not the disease.

Here's the thing about AI specifically. Inference cost per million tokens dropped roughly 80% between 2023 and 2025. If your only advantage was the spread between what OpenAI charged you and what you charged your customer, that spread got squeezed from both ends: the model got cheaper for everyone, including your competitors, and the customer figured out they could paste the prompt in themselves.

Saturation shows up in four places at once. Pricing drifts toward free. Customer acquisition cost climbs because every channel is full of people selling the same thing. Churn rises because switching costs are near zero. And the frontier labs start shipping your feature natively, which is the one that actually ends companies.

That last one has a name now. Founders call it getting Sherlocked, after Apple's habit of absorbing third-party Mac apps into the OS. By one count, OpenAI's product releases in 2024 alone cannibalized something like 200 funded GPT wrapper startups. Not outcompeted. Absorbed.

Which AI startup ideas are already saturated in 2026?

Five categories are effectively closed to new entrants without an unusual angle: AI writing assistants, AI customer support chatbots, AI meeting summarizers, AI logo and design generators, and AI resume builders. Each has 50 to 100+ funded competitors and a native equivalent shipped by a major platform.

Look at what happened to the flagships. Jasper AI, once valued at $125M as the category-defining AI writing tool, got sold for parts. Copy.ai merged with a competitor after raising $80M. Character.AI ended up as an acqui-hire at Google. Descript killed Overdub outright. These weren't underfunded companies with bad execution. They were the winners of their categories, and the categories stopped being worth winning.

A few more that are further along than founders realize:

Generic AI chat interfaces for a specific document type. Chat with your PDF, chat with your CSV, chat with your codebase. All three now exist as a checkbox inside ChatGPT, Claude, Notion, and about forty other products you already pay for.
AI social media post generators. The output is commodity, the buyer is price-sensitive, and Canva and Buffer both ship it free.
AI email writers. Gmail and Outlook have it built in. You're asking someone to pay $19/mo for a worse version of a button they already have.
AI transcription and note-taking. Otter, Fireflies, Granola, Zoom, Teams, Google Meet, and your phone's OS. The floor price is zero.
General-purpose "AI agent that does anything." The hardest seed round to raise in 2026. Investors have seen four hundred of these decks.

None of this means these products are bad. It means the market has already decided who wins them, and it isn't the person starting this week.

How do you run the saturation test on your own idea?

Four questions. If you answer yes to two or more, your category is closed and you should either find a sharper angle or pick something else.

1. The paste test. Can a reasonably capable user get 80% of your product's value by pasting your prompt into ChatGPT? If yes, you don't have a product. You have a prompt with a login screen. This is the single fastest disqualifier and most founders skip it because the answer is uncomfortable.

2. The roadmap test. Is what you're building a plausible feature on OpenAI's, Anthropic's, Google's, or Microsoft's next-quarter roadmap? Read their last four release notes. If your entire product appears as a bullet point in any of them, you're building on a runway that's being shortened while you taxi.

3. The free-tier test. Search your category plus the word "free." If page one returns five tools with generous free tiers backed by companies that make money elsewhere, your pricing power is already gone. You'll spend your whole existence explaining why you cost money.

4. The distinctness test. Write your one-line pitch. Now find five competitors and write theirs. If a stranger couldn't sort the six lines into the right buckets, you don't have positioning, you have a synonym.

Answer them straight. The temptation is to argue with each one, and every founder can construct a story for why their case is different. Write the answers down instead of debating them in your head, ideally in whatever you're using to plan the business. Some people use a spreadsheet. Some use Notion. Some use a planning tool like Foundra that walks first-time founders through validation before they get attached to the build. The tool matters less than the fact that the answers exist somewhere you can't quietly revise later.

Why did the wrapper model stop working?

The wrapper model worked in 2023 because the models were hard to access and most people hadn't tried them. Both of those facts expired. Distribution, not the model, is now the entire game, and wrappers have no distribution advantage by construction.

The numbers on wrappers are grim and fairly consistent across sources: somewhere between 80% and 95% fail, 60% to 70% never produce revenue at all, and only 3% to 5% clear $10K MRR. Treat those as directional rather than precise, since nobody has a clean census of a category this messy. The direction is clear enough.

But "wrapper" has become lazy shorthand, and it's worth being careful. Cursor is a wrapper in the narrow technical sense. It calls somebody else's models. Its annualized revenue passed $2 billion in early 2026. So the model isn't what determines survival.

What determines survival is whether anything accumulates. Cursor accumulates context about your codebase, workflow habits, and team conventions. Every week a developer uses it, leaving costs a little more. That's the difference between a wrapper and a product: a product gets better for the specific user over time in a way a fresh ChatGPT session can't replicate.

Ask yourself what's accumulating in your product. If the answer is "nothing, each session starts clean," you've got a feature.

What kinds of AI startups are still winning?

Vertical AI with deep domain access. The pattern is consistent enough by now to be boring: pick one industry, learn its actual workflow in painful detail, and build something a generalist tool can't approximate.

The proof is in the revenue curves. Harvey went from $50M ARR to $195M to around $350M by July 2026, all inside legal. Abridge crossed $100M ARR turning clinician conversations into notes and doubled its valuation to $5.3B in four months, with 250+ health systems deployed. Sierra passed $150M in customer support. Avoca hit unicorn status doing voice AI for HVAC and plumbing companies, which is not a sentence anyone would have written in 2022.

The funding data backs the same read. Horizontal SaaS funding fell about 35% in the twelve months to Q1 2026 while vertical SaaS stayed roughly flat. Seed deal count dropped 31% year over year even as seed dollars rose 30%, meaning fewer bets, bigger checks, and a much higher bar for anything that looks generic.

Three characteristics show up in nearly every survivor:

Proprietary data or access the model can't get on its own. Harvey has law firm document sets. Abridge has health system integrations that took years of compliance work.
A workflow so specific that a generalist tool produces confidently wrong answers. Regulated industries are good hunting here for exactly this reason.
A buyer with a measurable cost to eliminate. "Saves time" loses. "Replaces 3.5 FTEs of chart review" wins.

Can you still build in a saturated category?

Yes, but only with an unfair advantage that has nothing to do with the model. Being better at prompting isn't one. Being faster to ship isn't one either, not anymore.

The ones that work: an existing audience you built before the product, a distribution channel competitors can't buy into, a regulatory or compliance position that took years to earn, or a specific customer segment everyone else finds too small or too annoying to serve well.

That last one is underrated. "AI writing assistant" is closed. "AI writing assistant for FDA submission documents at mid-size medtech companies" might be wide open, because the generalists can't afford the domain work and the incumbents in medtech can't build software. Narrowing isn't giving up on a big market. It's picking a beachhead you can actually take.

The honest version: if you're starting today with no audience, no domain access, and no unusual distribution, a saturated category is a coin flip you'll lose. Pick a different one. There are plenty. The 2026 shift toward physical AI, agent infrastructure, and deep domain problems is happening because the easy categories filled up, not because anyone declared them fashionable.

How do you pick a category that's still open?

Start from a workflow you personally understand rather than from a technology you find exciting. Founders who came out of an industry consistently beat founders who came out of a model release.

A practical sequence:

List the five most tedious things you did in your last job. Not the ones that were hard. The ones that were dumb, repetitive, and expensive.
For each, find out who currently gets paid to do it. If there's a line item, there's a budget. If there's no line item, you're creating a category, which is a much longer game.
Run the saturation test on each. Most will fail question one or two. That's fine, it's a filter, not a verdict on you.
For the survivors, go find ten people who do that job and ask what they use today. Not whether they'd use your thing. What they use, what it costs, and what makes them swear at it.
Check whether the frontier labs can reach it. If the workflow needs data sitting behind a firewall, a compliance regime, or a physical process, they probably can't, at least not soon.

This takes a week or two and it will save you a year. If you want more structure around steps three through five, there are free tools at foundra.ai/tools/ for market sizing and competitive analysis, and the same questions work fine on paper.

Key takeaways

Saturation isn't about competitor count, it's about the collapse of the gap between your cost and your price.
Five categories are effectively closed: writing assistants, support chatbots, meeting summarizers, logo generators, resume builders.
Run the four-question test: the paste test, the roadmap test, the free-tier test, the distinctness test. Two yeses means find another idea.
"Wrapper" isn't a death sentence. Not accumulating anything is. Cursor calls somebody else's models and passed $2B annualized.
Vertical AI with proprietary data access is where the durable revenue is. Harvey, Abridge, Sierra, Avoca all followed the same shape.
If you must enter a crowded category, bring an unfair advantage that isn't technical: audience, distribution, compliance position, or a segment nobody else wants.

FAQ

Is it too late to start an AI company in 2026?
No, but it's too late to start a generic one. The categories that filled up are the ones where the product is a thin layer over a public model. Vertical applications with domain-specific data and workflow depth are still early, and most industries haven't been touched.

How many competitors is too many?
There's no fixed number. Ten well-funded competitors in a market with real switching costs can be fine. Three competitors in a market where the frontier labs will ship the feature next quarter is fatal. Judge by pricing power and defensibility, not by the length of the list.

What's the difference between an AI wrapper and a real AI product?
Accumulation. A wrapper gives every user the same output a fresh model session would. A product builds up context, data, or workflow integration that makes it better for that specific user over time and costly to leave.

Should I avoid a category if a big company already offers the feature?
Usually yes, if their version is free and good enough. The exception is when the incumbent's version is a neglected checkbox and your buyer cares enough to pay for a real one. Test this by talking to people who use the free version, not by assuming they're unhappy.

How do I know if my idea passes the paste test?
Actually do it. Open ChatGPT, paste in your core prompt with realistic inputs, and compare the output to what your product would produce. Show both to someone in your target market without telling them which is which. If they can't tell or don't care, you have your answer.

What if I've already built something in a saturated category?
Don't throw it away. Narrow it. Find the segment of your existing users who get the most value, learn why, and rebuild the positioning and the product around that slice. Most successful pivots are compressions, not restarts.

Your Waitlist Is Not Validation. Run the Money Test.

Spencer Claydon — Sat, 19 Sep 2026 15:08:35 +0000

You launched a landing page. You posted it on X, dropped it in three Slack groups, and 1,400 people gave you their email address. It felt like the ground moved.

Here's the uncomfortable part. You've learned almost nothing about whether anyone will pay you.

A waitlist signup costs a person six seconds and zero dollars. That's the entire problem. You built a test where the cost of a "yes" is roughly the same as the cost of a "no," and then you read the results as if they meant something. They don't. Waitlist validation is the most popular self-deception in early-stage startups right now, and 2026 is the year founders started saying so out loud.

The fix isn't complicated. It's just harder. You have to make saying yes cost something.

Why doesn't a waitlist prove anyone wants your product?

A waitlist proves people are curious. It doesn't prove they have a problem, that the problem hurts enough to pay for, or that they'll change what they currently do. Curiosity and demand feel identical on a dashboard and behave nothing alike in a checkout flow.

Think about what you're actually asking someone to do. You're asking them to type an email they already use for newsletters into a box, in exchange for the possibility of something interesting later. There is no downside for them. There is no decision. Most people who join a waitlist aren't evaluating your product, they're bookmarking a vibe.

That's why the numbers look so good and convert so badly. Industry benchmarks put landing-page-to-waitlist conversion around 3.4% for SaaS, 4.1% for consumer apps, and 4.6% for AI tools, and the median waitlist turns about 11% of its page visitors into signups. Those are healthy top-of-funnel numbers. But waitlist-to-paying-customer sits somewhere between 5% and 25%, averaging near 20% only if you convert people within a month, and dropping under 10% once you make them wait longer than three months.

Run that math on your 1,400. If you take three months to launch, which you will, you're looking at maybe 100 paying customers in the best case and 70 in the realistic one. If your price is $20/month, that's a business doing $1,700 MRR at peak hype. Worth knowing before you spend eight months building.

And that's the optimistic version, where everyone on the list is a real prospect. Some of them are your friends. Some are competitors. Some are founders who joined to study your onboarding email.

What is the money test?

The money test is a single question: did this person give up something scarce to say yes? Money is the cleanest version of scarce, but time, reputation and access count too. If the answer is no, you have interest. If the answer is yes, you have evidence.

One founder building a Stripe failed-payment recovery tool wrote a postmortem that puts it better than any framework: he'd written a 50-page product spec and shipped a landing page before talking to a single customer, and got zero signups in five days. His conclusion: "Validation is a person handing you money."

That's the bar. Not a survey response. Not a "this is sick, ship it" reply on X. Not a signup. A transfer of something the other person can't get back.

The useful thing about this framing is that it scales down. You don't need a product to run it. You need an ask that has teeth.

What signals actually count as validation?

Rank every piece of evidence you have by what it cost the other person. Anything free sits at the bottom and should never drive a build decision. Here's the ladder, weakest to strongest:

Tier 1: free and anonymous. Page views, social likes, poll votes, "would you use this" survey answers. Cost: nothing. Use: traffic testing only. Never quote these numbers to yourself or an investor as demand.

Tier 2: free and identified. Waitlist signups, newsletter subscribes, fake-door clicks, replies to a cold email. Cost: a few seconds and an email address they may not check. Use: testing which message lands, not whether the product should exist.

Tier 3: time and access. A 30-minute discovery call they showed up to on time. An intro to their boss. Sending you their actual spreadsheet. Cost: real, because calendar time is finite. Use: problem confirmation. This is where you learn whether the pain is real.

Tier 4: reputation and commitment. A signed letter of intent, a referral to a peer, agreeing to be a named design partner. Cost: their credibility is now attached to your thing. Use: strong B2B signal, especially at higher price points.

Tier 5: money. A pre-order, a deposit, a paid pilot, a subscription that starts before the product is finished. Cost: obvious. Use: this is validation. Everything else is a step on the way here.

Most founders live in tiers 1 and 2 for months and call it traction. The jump from tier 2 to tier 5 is where you find out if you have a company.

And when you do move money into the equation, the behavior on the other side changes immediately. Deposit-based waitlists have been reported converting 3x to 5x better than free lists, with email open rates in the 60% to 80% range versus 15% to 25% for free signups. Same people, same product, different filter. Paying $10 turns a stranger into someone who remembers your name.

How do you run a money test without a product?

You pre-sell. The mechanics depend on your model, but the principle is identical: describe the thing precisely enough that someone can decide, then ask for the transaction before the thing exists.

Waseem Daher, a three-time YC founder, did this before Pilot wrote a line of code. He went to small business owners and got them to commit to paying for the accounting service once it launched. Those commitments were the validation. The product came after.

Five versions that work depending on what you're building:

The deposit. $20 to $100, refundable, holds your spot in the first cohort. Works for consumer and prosumer products. Stripe Payment Links take about ten minutes to set up and you don't need an app to accept them.
The pre-order. Full price, charged now or on launch, usually at a discount. Works when the value is obvious and the product is concrete. This is the whole Kickstarter model compressed into a landing page.
The paid pilot. For B2B: charge $500 to $5,000 for a scoped, time-boxed engagement you deliver manually. You get paid to learn. The customer gets the outcome. You get a case study and a reference before you've written any software.
The letter of intent. When procurement makes a real payment impossible, get a document stating they intend to buy at a stated price on a stated timeline. It's weaker than cash and much stronger than enthusiasm.
The concierge. Do the job by hand for one paying customer. Notion, spreadsheets, and your own labor. If nobody will pay you to solve the problem manually, they won't pay software to solve it either.

The hardest part of all five isn't the setup. It's that you have to ask, and asking is where founders discover their idea was a hypothesis. That discomfort is the test working correctly.

Keep the results somewhere structured rather than in your head. You want the ask, the response, the objection, and the amount, per person, so you can see patterns instead of remembering the two conversations that went well. A spreadsheet is fine. So is Notion, or a planning tool like Foundra that walks first-time founders through validation before the build phase. The tool matters far less than writing down the nos.

How many paid commitments do you need before you build?

Enough that the pattern can't be luck, which for most early products means somewhere between 5 and 20 paying commitments from strangers. The word doing the work in that sentence is strangers.

Three signals that mean you're clear to build:

Five or more paid commitments from people you didn't already know. Friends and former colleagues buy out of loyalty. Their money is real and their signal isn't.
A close rate above roughly 20% on qualified conversations. If you're pitching 50 people to get one deposit, the problem is either the problem or the price, and you should find out which before scaling the pitch.
At least one unprompted referral. Someone paid, then told a peer without you asking. That's the earliest form of the growth loop you'll live on later.

There's a companion heuristic worth keeping: if you can't find ten strangers who describe the problem in their own words without you prompting them, you don't have demand yet. You have a hypothesis with a nice landing page.

What if nobody pays?

Then you've saved yourself the eight months, which is the entire point. A failed money test is the cheapest useful outcome available to a founder. But before you kill the idea, separate the three things it might be telling you.

It might be the ask. You buried the price, apologized for it, or made the commitment vague. "Would you pay for this?" is not an ask. "It's $49, here's the link, first cohort starts October 6" is an ask.

It might be the audience. You pitched people who have the problem mildly to people who have it severely. Severity is what opens wallets. Go find the ones who've already built a broken workaround for this, because a workaround is proof of pain.

It might be the idea. Sometimes people are polite, interested, and completely unwilling to pay. That's a real answer. Take it.

The order matters. Most founders conclude "the idea is dead" when they actually ran a bad ask at a soft audience, and most of the rest conclude "I just need better messaging" when the idea is dead. Test the ask twice with a sharper audience before you decide.

How do you turn a waitlist you already have into a real signal?

Email it with a paid offer. Today. You're sitting on the cheapest test available to you and it takes one message.

Send the list a note that says the first cohort is opening, it costs X, and there are a limited number of spots. Include a payment link. Then read three numbers: how many opened, how many clicked, how many paid. That third number is your actual validation, and you'll have it by Friday.

Expect it to be brutal. A 1,400-person list that produces four purchases is telling you something clear, and it's better to hear it now than after the build. A 1,400-person list that produces sixty is a business.

If you can't bring yourself to charge yet, run the intermediate version: ask for a 20-minute call. Count how many book it and show up. Time is tier 3, which is weaker than money but far stronger than the signup you already have.

One more thing worth doing regardless of the result: ask the people who don't buy what would have to be true for them to say yes. The non-buyers explain your pricing, your positioning, and your roadmap better than the buyers do.

Key takeaways

Waitlist signups measure curiosity. They cost the signer nothing, so they predict almost nothing about revenue.
Waitlist-to-paid conversion runs 5% to 25%, and falls below 10% if you make people wait more than three months.
Rank every signal by what it cost the other person. Free and anonymous is worthless, money is validation, and time and reputation sit in between.
You can run a money test without a product using a deposit, a pre-order, a paid pilot, an LOI, or a manual concierge offer.
Five to twenty paid commitments from strangers, a close rate above 20%, and one unprompted referral is a reasonable bar to start building.
If nobody pays, check the ask and the audience before you blame the idea.
If you already have a waitlist, email it a real paid offer this week. That one message is worth more than the last six months of signups.

FAQ

Is a waitlist ever useful?
Yes, for distribution and messaging. A waitlist gives you a list to launch to and a cheap way to test which headline pulls. Treat it as a marketing asset, not as evidence that your product should exist.

What's the difference between a smoke test and a pre-sale?
A smoke test measures intent: someone clicks a button for a product that isn't built. A pre-sale measures commitment: someone enters a card. Both are useful, but only one of them survives contact with an investor's questions.

How much should I charge for a pre-order or deposit?
Charge something close to your intended price. A $1 deposit filters out nobody and teaches you nothing. Most consumer and prosumer products land between $20 and $100 for a refundable deposit, and B2B pilots start around $500.

Is it dishonest to sell something I haven't built?
Not if you're clear. Say plainly that it doesn't exist yet, give a date, and offer a full refund if you miss it. Founders get into trouble by implying the product is ready, not by pre-selling.

What if my product is free or ad-supported?
Substitute a different scarce resource. Ask for 30 minutes of their time, a piece of their data, or an invite to three friends. The test isn't money specifically, it's cost.

How long should a money test take?
Two to three weeks. If you need longer, you're building instead of testing. Set a date, make the ask to a defined list of people, and read the result on the date.

How to Run a Product-Market Fit Survey (Step by Step)

Spencer Claydon — Fri, 18 Sep 2026 17:00:19 +0000

Most founders talk about product-market fit like it's weather. It arrives or it doesn't. You feel it or you don't. That framing is useless when you're trying to decide what to build next quarter.

There's a better option. A product-market fit survey turns a vague feeling into a number you can track, segment, and improve. It takes about a day to set up and it costs nothing. And the output isn't just a score. It's a ranked list of what to build, who to build it for, and who to stop listening to.

Here's how to run one properly.

What is a product-market fit survey?

A product-market fit survey asks your existing users one core question: how would you feel if you could no longer use this product? The percentage who answer "very disappointed" is your PMF score. Above 40% is the widely used benchmark for having found fit.

The test comes from Sean Ellis, who ran early growth at Dropbox, LogMeIn, and Eventbrite. He surveyed close to 100 startups and noticed a pattern. Companies that couldn't find durable growth almost always scored under 40%. Companies with real traction almost always cleared it. It's not a law of physics, but as leading indicators go it's better than almost anything else you can measure in a week.

The reason it works is that it measures dependency, not enthusiasm. People will tell you they love your product to be polite. Very few people will claim they'd be devastated to lose something they barely use.

Who should you survey (and who should you exclude)?

Survey people who have actually experienced your core product, and nobody else. Signups who never activated will drag your score toward zero and tell you nothing useful about the product you actually shipped.

Sean Ellis's original screening rule is a good default. Include users who:

Used the product at least twice
Used it within the last two weeks
Completed the core action, whatever that is for you (sent an email, published a page, ran a report)

If you've got fewer than 40 people who clear that bar, don't run the survey yet. You'll get a number that swings 15 points depending on who happened to answer. Go do customer interviews instead, then come back when you have a real base.

Practical target: 100 to 200 responses. That gives you enough to segment. Under 40 responses, treat the score as directional at best.

One more thing. Don't survey the people you personally onboarded and text every week. They'll answer for the relationship, not the product. If those users are a big chunk of your base, tag them and look at their responses separately.

What questions should the survey include?

Four questions. The first gives you the score, the next three give you the roadmap. Anything beyond that and your completion rate falls off a cliff.

Question 1: How would you feel if you could no longer use [product]?

Very disappointed
Somewhat disappointed
Not disappointed (it isn't that useful)
N/A, I no longer use it

Question 2: What type of people do you think would most benefit from [product]?

Open text. This is the one everyone skips, and it's the most valuable question in the survey. Your users will describe your ideal customer profile in their own words, better than any positioning workshop you could run.

Question 3: What is the main benefit you receive from [product]?

Open text. The answers become your homepage copy. Not the benefit you think you deliver, the one people actually cite when nobody's selling to them.

Question 4: How can we improve [product] for you?

Open text. Critical: you'll segment these answers by the response to question 1, which is where most of the value lives.

Keep it to these four. Rahul Vohra's team at Superhuman ran essentially this set, and the whole thing takes a user about 90 seconds. Resist the urge to bolt on NPS, a satisfaction scale, and three demographic dropdowns. Every extra field costs you responses, and responses are the whole point.

How do you actually send it?

In-app is best, email is fine, and a link on Twitter is worthless. You want responses from your real users, not from whoever's bored on a Tuesday.

The mechanics matter less than people think. Typeform, Google Forms, a simple embedded widget: all fine. What matters:

Timing. Trigger it after a user completes the core action, not on login. Someone who just got value from you is in a position to give you a real answer. Someone who just opened the app is thinking about something else.

Subject line, if you're emailing. "Quick question about [product]" outperforms anything that sounds like a marketing campaign. Send it from a real person, ideally the founder.

Length signal. Tell them it's four questions. People will start a survey they believe has an end.

Follow-up. One reminder, four days later, to non-responders only. That single reminder usually adds 30 to 50% more responses. Two reminders start to annoy people.

Typical response rates for in-app prompts to active users run 10 to 25%. Email to active users runs 5 to 15%. Plan your base size accordingly: if you want 150 responses from email, you need somewhere around 1,500 qualified users on the list.

What does your PMF score actually mean?

Above 40% means you have fit and your problem is growth. Between 25 and 40% means you have something real but it isn't sharp enough yet. Below 25% means the product or the audience is wrong, and shipping more features won't fix it.

Here's the part that gets lost. A low score isn't a verdict. Superhuman's first score was 22%. Rahul Vohra didn't shut the company down. He segmented the data, rebuilt the roadmap around two specific insights, and the score reached 58% within about three quarters. That's the actual point of the survey: it's a diagnostic, not a grade.

A few things to watch out for when you read your number:

Situation	What it usually means
Score above 40% but flat growth	You have fit with a segment too small or too hard to reach
Score 25-40% with one loud segment at 60%+	You're serving two audiences, pick one
Score below 25% across all segments	Wrong problem, wrong audience, or the product doesn't work yet
Score jumped 15 points with no product changes	Your sample changed, check who answered

Track the score quarterly, not monthly. It moves slower than you want it to, and measuring it too often just creates noise you'll be tempted to react to.

How do you turn the answers into a roadmap?

Segment every open-text answer by how that person answered question 1. Then build for one group and ignore another. That single move is what separates a useful survey from a slide in a board deck.

Three buckets, three different jobs:

The "very disappointed" group. Read their answers to question 3 and find the common benefit. That's your product's real value proposition. Read their answers to question 2 and you've got your ICP in customer language. Now read their answers to question 4 and treat every request as high priority, because these are the people who already love you and you want to keep them.

The "somewhat disappointed" group. This is where the growth is. These people see something in the product but something's blocking them. Sort their question 4 responses into two piles: requests that would move them toward what the "very disappointed" group already values, and requests that would pull the product in some other direction. Build the first pile. Skip the second. Superhuman's version of this was to focus only on the somewhat-disappointed users who also cited the same main benefit as the very-disappointed group, which cut out a lot of noise.

The "not disappointed" group. Ignore them. This feels wrong and it isn't. They told you the product isn't for them. Building for them will make the product worse for the people who love it, and it almost never converts them anyway.

If you're mapping this against your broader positioning and go-to-market plan, it helps to have the whole picture in one place. A spreadsheet works, Notion works, and a planning tool like Foundra walks first-time founders through connecting customer research to the positioning and GTM sections it feeds. Whatever you use, the rule is the same: survey insights should change your roadmap document, or you wasted everyone's time.

When should you run your first one?

Run it once you have 40+ users who've hit your core action twice in the last two weeks. Before that, the number is noise and interviews will teach you more.

Rough timing by stage:

Pre-launch or under 40 active users. Don't survey. Do 10 to 15 customer discovery interviews instead. You need texture, not statistics.
40 to 100 active users. Run it, but treat the score as a rough baseline. Focus on the open-text answers, which are useful at any sample size.
100+ active users. Run it properly, segment it, and set a quarterly cadence.
After a major pivot or repositioning. Run it again eight to twelve weeks after the change, once people have had time to use the new thing.

One caveat worth naming: this survey works best for products people use repeatedly. If you sell something transactional, a wedding planning tool, say, or tax software, "how would you feel if you could no longer use it" doesn't map cleanly onto the buying behavior. You'll get better signal from repurchase rate and referral behavior. Know when the tool fits.

Key takeaways

The PMF survey measures dependency, not enthusiasm. That's why it beats NPS as an early-stage signal.
40% "very disappointed" is the benchmark, but a low score is a starting point, not a death sentence. Superhuman went from 22% to 58%.
Only survey users who've experienced the core product. Screening is what makes the number mean anything.
Four questions, no more. The three open-text ones are where the roadmap comes from.
Segment every answer by the question 1 response. Build for the somewhat-disappointed, protect the very-disappointed, ignore the rest.
Run it quarterly, not monthly. And don't run it at all under 40 qualified users.

If you want more on the validation side of this, the Foundra key reads library has walkthroughs on customer discovery interviews and smoke tests that pair well with this survey.

FAQ

What is a good product-market fit survey score?

Above 40% of respondents answering "very disappointed" is the standard benchmark, based on Sean Ellis's survey of roughly 100 startups. Between 25 and 40% suggests partial fit with a specific segment. Below 25% usually means the product, the audience, or the problem needs to change.

How many responses do I need for a PMF survey?

Aim for 100 to 200 responses so you can segment meaningfully. You can get directional signal from 40, but below that the score swings too much to be useful. Prioritize response quality over volume: 50 responses from truly active users beat 300 from cold signups.

How is a PMF survey different from NPS?

NPS asks whether someone would recommend you, which measures social willingness. The PMF survey asks how they'd feel losing the product, which measures dependency. Early-stage users will recommend a product they don't really use. Very few will claim they'd be devastated to lose it.

How often should I run a product-market fit survey?

Quarterly is right for most startups. The score moves slowly, and measuring monthly produces noise you'll be tempted to overreact to. Also run one eight to twelve weeks after any major pivot, repositioning, or pricing change.

Can I run a PMF survey before launching?

No. The survey depends on people having used the product, so there's nothing to measure pre-launch. Use customer discovery interviews, landing page smoke tests, and waitlist conversion rates instead, then run the survey once you have 40+ users hitting your core action.

What if my score is under 25%?

Read the open-text answers before touching the roadmap. Look for any segment scoring meaningfully higher than the average: a job title, a company size, a use case. If one exists, that's your beachhead and the fix is narrowing your focus. If no segment clears 40%, the problem is more fundamental and you're looking at a pivot, not a feature sprint.

How to Raise Prices Without Losing Customers

Spencer Claydon — Thu, 17 Sep 2026 19:00:47 +0000

You picked a price a year ago. You picked it in about eleven minutes, probably while staring at a competitor's pricing page. Since then you've shipped forty features, hired a support person, and watched your infrastructure bill triple. The price hasn't moved.

Here's the thing. Most first-time founders are underpriced, and they know it. What stops them isn't the math. It's the mental image of forty angry emails and a Slack channel full of cancellations. So the price stays frozen, margins get thinner, and the business slowly becomes harder to run than it needs to be.

That fear is mostly wrong, but not entirely. Price increases do cause churn. They just cause a lot less of it than you think, and almost all of the damage comes from how you execute rather than from the number itself. This is the part nobody teaches you, so let's walk through it.

Why does raising prices feel so much riskier than it is?

Because you're modeling the worst case and ignoring the base rate. Founders imagine a mass exodus, when the actual pattern is a short churn spike that decays back to normal within a couple of months.

Netflix is the cleanest public example. When they raised prices across every U.S. plan in January 2025, Antenna measured monthly churn climbing from 1.8% in December to 2.5% in January. By February it was 2.3%. By May it was 2.0%. The spike lasted about eight weeks and then the business went back to normal, while JPMorgan pegged the annualized revenue lift at roughly $1.7 billion.

Now, you are not Netflix. You don't have their catalog or their switching costs. But the shape of the curve is the same at every scale: a bump, then a return to baseline. What changes is the size of the bump, and that's the part you control.

There's also a quieter risk on the other side that nobody puts in a spreadsheet. Underpricing attracts the customers who are hardest to serve. Cheap plans pull in people who want everything, complain the most, and churn anyway. Raise the price and your support load often goes down, not up.

How do you know it's actually time to raise prices?

You're ready when the evidence is behavioral, not emotional. Look for signals in how people buy and use the product, not for a feeling that you deserve more money.

The signals worth acting on:

Nobody flinches. If fewer than one in five prospects mentions price during a sales conversation or a trial, you're leaving money on the table. Some friction is healthy.
Your close rate is suspiciously high. Converting 40%+ of qualified trials usually means the price is a no-brainer, and no-brainer is another word for underpriced.
Your cheapest plan is your busiest support queue. Classic sign of a mismatch between what you charge and what you deliver.
You've shipped real things. Not a redesign. Integrations, capabilities, or time savings customers would name unprompted.
Costs moved structurally. AI inference, infrastructure, a support hire. These don't reverse.
Customers tell you. When someone says "I can't believe this is only $29," that's data.

Two of these and you should be planning an increase. Four and you're late.

And if none of them are true? Then your problem isn't pricing. It's the product, and a higher number won't fix it.

How much should you raise prices?

Smaller increases are safer, but they're also less useful. The range that tends to work for early-stage software is 20% to 40% on new customers, with existing customers handled separately.

Here's why going too small backfires. A 10% increase creates nearly all the awkwardness of a 30% increase, since you still have to write the email, still have to face the replies, still burn the goodwill. But it barely changes the business. On $8,000 in monthly recurring revenue, 10% is $800. That's not a hire, or a longer runway, or anything that changes what you can do. You spent your one increase of the year on a rounding error.

A useful frame: price for the customer you want next year, not the one you signed last year. If you're moving upmarket, your price needs to move with you or you'll keep attracting the wrong buyer.

One more piece of the mechanics that founders miss. You don't have to raise everything at once. Raising the middle tier while leaving the entry tier alone pushes new buyers upward and gives price-sensitive customers somewhere to land instead of somewhere to leave. Adding a higher tier is often better than repricing the existing ones, because the people who need more will self-select into it and nobody feels punished.

Should you grandfather existing customers?

Usually yes, but with an expiry date. Permanent grandfathering feels generous in month one and becomes a liability by year three, when you're supporting three pricing schemes and can't run a clean promotion without confusing half your base.

The pattern that works: new pricing applies immediately to new signups, existing customers keep their current rate for 6 to 12 months, then move to the new price with plenty of warning.

This buys you three things. New revenue starts flowing right away, existing customers feel protected rather than punished, and you get real market data on whether the new price actually converts before you ever touch your loyal base.

Pricing practitioners who've run this repeatedly report grandfathered transitions landing in the low single digits for churn, versus the 10% to 15% spikes that show up when a price change lands on existing customers with no warning. Treat those figures as directional rather than gospel, because they come from vendor blogs rather than peer-reviewed work. The mechanism, though, is hard to argue with: people accept a price change they saw coming and resent one they didn't.

The exception is when your current price is so far below cost that carrying it for another year is a real problem. In that case, shorten the window to 90 days and be direct about why.

How much notice should you give before a price increase?

Thirty days minimum, 60 is better, 90 is ideal for annual contracts. The pattern people report is roughly linear: each extra month of notice meaningfully reduces the churn that follows.

Notice works because it converts a shock into a decision. Someone who gets 60 days has time to check whether switching is worth it, discovers that migrating their data and retraining their team is a two-week project, and stays. Someone who finds out from a surprise invoice has a different reaction entirely, and it isn't about the money.

Sequence it like this:

Day 0: Email from the founder, not from "The Team." Explain the change, the date, the new number, and what's improved.
Day 7: Reply personally to everyone who wrote back. All of them.
Day 21: Short in-app notice for anyone who missed the email.
Day 30 to 60: One reminder a week before it takes effect.
Billing day: New price applies. No surprises, because everyone has now heard it four times.

The single worst thing you can do is bury the announcement in a changelog or a terms-of-service update. Customers find out anyway, and now they're angry about two things.

What should the price increase email actually say?

Short, specific, signed by a human, and led with value rather than apology. The structure that works is four paragraphs and no more.

Open with what changed in the product. Not a feature list, two or three concrete things people asked for. Then state the new price plainly, including the exact date and what they'll pay. Then explain the grandfathering window if there is one. Then close with a direct line to reply.

What to leave out: the phrase "due to rising costs" (nobody cares about your costs), long apologies (they signal you don't believe in the price), and corporate throat-clearing about your commitment to excellence.

A version that works:

Hi Sarah,

Over the last eight months we shipped the Slack integration, cut export times from four minutes to under ten seconds, and added the audit log a lot of you asked for.

Starting November 1, our Pro plan moves from $49 to $69 per month for new customers. Your account stays at $49 through June 2027. After that you'll move to the new rate, and I'll remind you 60 days before.

If this doesn't work for you, reply and tell me. I read every one of these.

Spencer

That's it. Ninety words. The founders who write two pages are usually arguing with themselves.

How do you model the impact before you commit?

Run the break-even churn number first. It's one line of arithmetic and it usually ends the debate.

If you raise prices by X percent, you can afford to lose roughly X divided by (100 plus X) of your revenue before you're worse off than you started. A 30% increase means you break even at about 23% revenue churn. Since realistic churn from a well-executed increase lands in the low single digits, the margin for error is enormous.

Work a real example. You have 120 customers at $49, so $5,880 in MRR. You move to $69 and lose 8% of the base over three months. You're left with 110 customers at $69, which is $7,590. That's a 29% revenue lift while serving ten fewer accounts. Your support load dropped and your margins improved at the same time.

Build a second version of that model where churn comes in at 20%, which is the pessimistic case. You're at 96 customers and $6,624, still ahead. If even your pessimistic case wins, the decision is made.

You can do this in a spreadsheet in fifteen minutes. If you'd rather not start from a blank grid, a runway or break-even calculator (there are free ones at foundra.ai/tools/, and plenty elsewhere) will get you to the same numbers faster. The tool matters less than actually running the scenarios before you send the email.

What do you do when customers push back?

Expect pushback from 5% to 10% of your base, and treat it as a retention conversation rather than a negotiation. Most people who complain aren't leaving. They want to be heard and they want to know you thought about it.

Reply personally within a day. Ask what they'd need to see for the new price to feel fair. Sometimes the answer is a feature you're already building, and telling them that ends the conversation.

For the ones truly at their budget ceiling, you have options that don't involve caving: extend their grandfathered window by six months, offer annual prepay at the old rate, or move them to a lower tier that fits their actual usage. What you shouldn't do is quietly give a discount to everyone who complains loudly. That teaches your base that complaining works, and you'll pay for it at every future change.

Some customers will leave. That's the cost of the transaction, and it's already priced into the math you ran. A customer who leaves over a $20 increase was going to leave over something else within six months.

Key takeaways

Price increases cause a churn spike that decays within roughly two months. Netflix went 1.8% to 2.5% and back to 2.0% within five months of a 2025 increase across all U.S. plans.
Raise 20% to 40%, not 10%. A small increase costs the same goodwill and changes nothing.
Apply new pricing to new customers immediately. Grandfather existing ones for 6 to 12 months with a firm end date.
Give 30 to 60 days of notice, minimum. Surprise invoices cause more churn than the price itself.
Send a four-paragraph email from a named person, leading with what you shipped, not with your costs.
Run the break-even churn math first. At a 30% increase you can lose 23% of revenue and still come out even.
Handle pushback individually. Never blanket-discount the people who complain hardest.

FAQ

How often should a startup raise prices?

Once a year is a reasonable cadence for early-stage software, usually tied to a meaningful release. More often than that and you erode trust. Less often and you fall behind your own product. Many companies bake a small annual adjustment into their terms so it stops being an event.

Will raising prices increase my churn permanently?

No. The data pattern across both consumer and B2B subscriptions shows a temporary spike that returns to baseline within one to three months. Permanent elevation usually means the product wasn't delivering enough value at the old price either.

Should I raise prices before or after product market fit?

After. Before you've proven people will pay and stay, price changes just add noise to signals you can't read yet. Once you have consistent retention and customers describing real value, you're ready.

What if a competitor is much cheaper than me?

Being cheaper is the easiest position to attack and the hardest to defend. Compete on outcome, specificity, or service instead. Customers who pick purely on price churn to the next cheap option anyway.

Can I raise prices during a customer's annual contract?

No. Honor existing terms through the end of the contract period, then apply the new rate at renewal with notice beforehand. Changing mid-term is a fast way to lose both the customer and the referral.

Do I need to explain why I'm raising prices?

Briefly, and framed around value delivered rather than costs incurred. "We shipped X, Y, and Z" works. "Our expenses went up" invites the reply that your expenses are not the customer's problem.

How to Build a Unit Economics Model for an AI Product

Spencer Claydon — Wed, 16 Sep 2026 15:10:58 +0000

Cursor was running a negative 23 percent gross margin in the quarter ending January 2026, at roughly $2 billion in annualized revenue. Read that again. A company most founders would kill to be was losing money on every single dollar customers handed over, because the models underneath cost more than the subscriptions on top.

That's not a Cursor problem. It's an arithmetic problem, and it shows up in almost every AI product built by someone who learned software economics from the SaaS era. A unit economics model for an AI product has to answer one question that classic SaaS never had to take seriously: what does it cost me, in cash, every time somebody uses this thing?

Most first-time founders skip the model entirely and find out the answer from their credit card statement. Let's do it the other way round.

What is a unit economics model for an AI product?

A unit economics model for an AI product is a per-customer profit and loss statement: revenue from one customer, minus everything it costs to acquire and serve that one customer, over the time they stay. The difference from SaaS is that "serve" now includes a variable cost that scales with usage rather than a fixed cost that scales with headcount.

In traditional SaaS, cost of goods sold ran 15 to 25 percent of revenue and barely moved when a customer got enthusiastic. Hosting was mostly paid for either way. In AI-first companies, COGS commonly lands at 40 to 50 percent of revenue once you count model hosting, inference, and data. Inference alone eats about 23 percent of revenue at scaling-stage AI B2B companies.

So the model isn't optional bookkeeping. It's the thing that tells you whether growth makes you richer or poorer.

What counts as a "unit" when usage varies wildly?

Your unit is one paying customer, but you can only model it with any accuracy if you first model one action: one query, one agent run, one generated document, one resolved ticket. Cost per action times actions per customer gives you cost per customer. Trying to skip to the customer level is where the model goes wrong.

Here's the thing nobody warns you about. You need three versions of "actions per customer," not one. The median user, the 95th percentile user, and the blended average. Modeling only the average is how founders end up with a spreadsheet that says 70 percent margin while the finance reality says 40.

Write down these numbers before you touch a formula:

Actions per customer per month at the median
Actions per customer per month at the 95th percentile
Input tokens per action, including system prompt, retrieved context, and conversation history
Output tokens per action
Retries and failed runs as a percentage (most teams forget this one entirely, and it's rarely under 5 percent)
Non-model costs per action, like web search calls, vector database reads, or third-party APIs

If you don't have real usage data yet, estimate by running the workload yourself fifty times and logging what happened. Fifty real runs beat any assumption you could reason your way to.

How do you calculate cost to serve one AI customer?

Multiply tokens per action by your model's per-token price, add every non-model variable cost, multiply by actions per month, then add the per-customer allocated costs like storage, observability, support, and payment processing. That total is your cost to serve.

Let's work a real example instead of waving at one.

Say you're building a research agent that finds prospect information and drafts outreach. You charge $99 a month and include 500 prospects. Each prospect run makes roughly eight model calls, burning about 25,000 input tokens (mostly web page content getting stuffed into context) and producing about 3,000 output tokens.

On a mid-tier model at $2 per million input tokens and $10 per million output:

Input: 25,000 / 1,000,000 x $2 = $0.050
Output: 3,000 / 1,000,000 x $10 = $0.030
Model cost per run: $0.080
Web search API at five searches per run: $0.020
Run total: $0.10

Now the monthly customer:

Line item	Cost per customer per month
Inference, 500 runs x $0.08	$40.00
Web search, 500 runs x $0.02	$10.00
Storage, vector DB, observability	$3.00
Payment processing (2.9% + $0.30)	$3.17
Total cost to serve	$56.17
Revenue	$99.00
Gross profit	$42.83
Gross margin	43.3%

Forty-three percent. Not a disaster, but below the 50 to 70 percent band AI-native companies are expected to hit in 2026, and a long way from the 80 percent number that lives rent free in every founder's head.

Now change one variable. Run the identical product on a flagship model at $5 input and $25 output, and your cost per run goes from $0.08 to $0.20. Five hundred runs becomes $100 of inference against $99 of revenue. You are underwater before you've paid for anything else. Move up to a top-tier model at $10 and $50 and it's $200 of inference on $99 of revenue.

The output price gap between the cheapest usable models and the frontier ones is roughly one hundred to one right now, from about $0.50 to about $50 per million tokens. Model choice is almost always the single biggest lever in the whole model. Test whether the cheap one is good enough before you assume it isn't.

What gross margin should your model produce?

Target 60 percent or better, accept 50 percent, and treat anything below 40 percent as a design flaw rather than a phase you'll grow out of. The average AI product gross margin in 2026 sits around 52 percent, against the 70 to 90 percent that mature SaaS delivers.

Two things to keep straight. First, put inference in COGS, not in operating expenses. Plenty of AI startups park model spend in R&D because it started life as an experiment, which makes gross margin look beautiful and makes the number useless. Investors unpick this in about four minutes.

Second, margin should improve with scale, and you should be able to say exactly why. Committed spend discounts, caching, smaller fine-tuned models for the common path, batching. If your model shows margin improving because "we'll optimize," that's not a model, it's a wish.

You can build this in a spreadsheet, in Notion, or in a planning tool like Foundra that walks first-time founders through cost structure and financial projections section by section. The format matters much less than whether the assumptions underneath are written down where someone can argue with them.

How do CAC and payback change when delivery costs real money?

CAC barely changes, but payback period nearly doubles, because payback is calculated on gross profit rather than revenue. This is the part of AI unit economics that catches founders completely off guard.

Back to the research agent. Median B2B SaaS customer acquisition cost in 2026 runs $500 to $2,000, with self-serve product-led motions coming in under $700. Take $700.

At 43 percent margin: $42.83 gross profit per month. Payback = 16.3 months.
At classic 80 percent SaaS margin: $79.20 per month. Payback = 8.8 months.

Same product, same price, same CAC. The token bill added seven and a half months to how long your cash is tied up. Median SaaS payback in 2026 is 15 to 18 months, so 16.3 isn't alarming on its own. What's alarming is the lifetime value math.

At 4 percent monthly churn, average customer lifetime is 25 months. Lifetime gross profit is 25 x $42.83 = $1,071. Against $700 CAC, that's an LTV to CAC ratio of 1.5 to 1. Investors want 3 to 1. To get there you'd need CAC down near $355, or churn cut roughly in half, or margin up around 60 percent. Probably some of each.

Run this calculation before you spend a dollar on paid acquisition. The median SaaS company now spends $2.00 to acquire $1 of new ARR. On AI margins, that math gets tight fast.

How do you model the free tier without lying to yourself?

Add free tier inference cost into your cost to serve, allocated across paying users. This is the single most common omission in AI unit economics models, and it's the one that quietly kills companies.

The arithmetic is unforgiving. If 3 percent of your users convert to paid, every paying customer is carrying the AI bill for about 33 free users. Give those free users a generous allowance and you can wipe out your entire gross profit without a single line item looking wrong.

Take the research agent again. Suppose the free tier allows 10 runs a month, costing $0.80 of inference. Thirty-three free users at $0.80 is $26.40 of cost sitting against $42.83 of gross profit from the one paying customer. You're left with $16.43. Alive, but thin. Now imagine the free tier allowed 50 runs. That's $132 of free-user cost against $42.83 of gross profit, and the business is structurally dead no matter how fast it grows.

So cap the free tier by cost, not by feature. Decide what you're willing to spend acquiring one trial user, convert that into a number of actions, and set the limit there. Then watch the free-to-paid rate. Below 2 to 3 percent and you're funding a very expensive hobby.

The same logic applies to paid tiers. Set your included allowance so 70 to 80 percent of users stay comfortably under it, and meter or throttle above that. Caps are not hostile to users. They're what lets you keep the price low for the majority.

What happens to your model when token prices fall?

Assume nothing. Model at today's prices and treat any price decline as upside, not as a plan. Token prices dropped roughly 80 percent year over year for equivalent capability, and total AI spend still grew 320 percent over the same period, because cheaper tokens mean people use more of them.

That's the trap. Founders look at the a16z observation that inference cost for a given performance level falls about tenfold per year and conclude their margin problem solves itself. It doesn't, for two reasons. Your competitors get the same price cut, so it lands in the customer's pocket through price competition rather than yours. And cheaper tokens change user behavior: features you'd have rationed become features you ship, and consumption per customer climbs.

Build the model with a usage growth assumption alongside the price decline assumption. If price per token falls 50 percent and usage per customer rises 60 percent, your cost per customer went up.

What are the most common AI unit economics mistakes?

The big five, in the order they show up:

Modeling the average user only. Your median user might be 82 percent margin while your top 5 percent are negative. Blended averages hide this until the heavy users churn in and the light ones churn out.
Forgetting retries, evals, and internal usage. Failed runs cost the same as successful ones. So do your own team's testing, your eval suites, and every demo you give.
Filing inference under R&D. It's COGS. Putting it anywhere else produces a gross margin number that means nothing.
Ignoring the free tier. Covered above, and worth repeating because it's the most expensive mistake on this list.
Assuming optimization later. Caching, smaller models, and prompt compression are real levers worth 30 to 60 percent. But "we'll optimize" without a named technique and an estimated saving is not a financial assumption.

One more, and it's the one that separates the founders who make it. Don't build this model once. Rebuild it monthly against actual spend. Your token bill is the only honest auditor you have.

Key takeaways

Build the model bottom up: cost per action, then actions per customer, then cost to serve.
Model three usage profiles, median, 95th percentile, and blended. Never just the average.
Target 60 percent gross margin, accept 50, treat below 40 as a design problem.
Model choice is usually your biggest lever. The price gap between cheap and frontier models is about 100 to 1 on output tokens.
Calculate CAC payback on gross profit, not revenue. AI margins can nearly double your payback period at identical CAC.
Cap free tiers by cost, not features. At 3 percent conversion, every paying user funds about 33 free ones.
Model at today's token prices. Cheaper tokens historically lead to more usage, not lower bills.

If you want the surrounding pieces, the free calculators at foundra.ai/tools/ cover burn rate, runway, and startup costs, which feed the same financial model this sits inside.

FAQ

What gross margin do investors expect from an AI startup in 2026?
Between 50 and 70 percent, with 60 percent generally treated as the floor for a credible Series A story. The 2026 average across AI products is about 52 percent. Below 40 percent you'll be asked to explain your path to improvement in detail.

Should inference costs go in COGS or operating expenses?
COGS. Inference scales with usage and is a direct cost of delivering your product. Classifying it as R&D inflates gross margin and is the first thing a diligence process corrects.

How do I estimate cost per action before I have users?
Run the workload yourself fifty times and log token counts from your provider's API response. Every major provider returns input and output token counts per call. Fifty runs gives you a usable median and a rough spread.

What's a healthy LTV to CAC ratio for an AI product?
The same 3 to 1 that applies to SaaS, but it's harder to hit because the gross profit side of LTV is smaller. If your ratio is under 2 to 1, fix margin or churn before spending on acquisition.

Do I need a different model if I self-host instead of using an API?
The structure is identical, but your costs shift from variable to fixed, which means idle GPU time becomes the thing to watch. For most products spending under about $5 million a year on inference, hosted APIs come out cheaper once you price in the operations work.

How often should I update my unit economics model?
Monthly, against actual provider invoices. Assumptions drift fast when model prices, usage patterns, and your own prompt lengths all change quarter to quarter.

How to Price an AI Product Without Killing Your Margin

Spencer Claydon — Tue, 15 Sep 2026 15:11:05 +0000

Every time someone uses your AI product, you pay. That one sentence breaks most of what founders learned about pricing software.

Classic SaaS pricing worked because the marginal cost of one more user was close to zero. Server capacity was already paid for. A customer who logged in fifty times a day cost you roughly the same as one who logged in twice a month. That assumption is dead for AI products. Every call to a model burns real compute, and that compute shows up in cost of goods sold rather than in a fixed engineering budget. So the question of how to price an AI product isn't a marketing exercise. It's a survival calculation.

Here's the part most first-time founders miss. You can grow revenue fast, celebrate, and still be losing money on your best customers. Let's look at what the numbers actually say in 2026, and then at what to do about them.

Why is pricing an AI product different from pricing SaaS?

Because your costs scale with usage, and traditional SaaS pricing was built on the assumption that they don't. In SaaS, cost of goods sold typically runs 10 to 25 percent of revenue. At scaling-stage AI B2B companies, inference alone averages about 23 percent of revenue. That means for every million dollars of AI product revenue, roughly $230,000 disappears into model calls before you've paid for hosting, support, or anything else.

Stack the rest of COGS on top and the picture gets uncomfortable. AI-native companies are running total COGS around 40 to 50 percent, which leaves gross margins of 50 to 60 percent. Mature SaaS sits at 70 to 90 percent. One 2026 projection puts the AI-native average at about 52 percent, which is real improvement from 41 percent in 2024, but still nowhere near what investors and founders were trained to expect.

If you're a SaaS company bolting AI features onto an existing product, the typical hit is 12 to 17 points of gross margin depending on how hard you've optimized. That's not a rounding error. That's the difference between a company that can afford a sales team and one that can't.

What gross margin should an AI product actually target?

Aim for 60 percent or better, and treat anything under 50 percent as a problem you need a written plan to fix. Not a vague intention. A plan with dates.

The useful mental model is to stop thinking of your AI feature as software and start thinking of it as a service with a cost per unit delivered, the way a manufacturer thinks about cost per widget. Pick the unit that matters in your product: a resolved support ticket, a generated report, a document reviewed, a call transcribed. Then work out what that unit costs you at current model prices, at realistic usage, including the retries and the failed attempts that nobody puts in the spreadsheet.

Do that math before you pick a price, not after. I've watched founders set a price by copying a competitor, then discover four months later that the competitor is running a different model at a tenth of the cost. Their price was never the right price for your cost structure.

What are the AI pricing models founders choose from in 2026?

There are four real options, and most companies end up blending two of them.

Per seat. Flat fee per user per month. Predictable for the buyer, dangerous for you, because a single heavy user can consume twenty times what an average one does at exactly the same price. Per seat is also losing ground fast: its share of SaaS pricing fell from 21 percent to 15 percent in twelve months. A Cruxy survey of 300 SaaS CEOs in April 2026 found 97 percent planning to retire seat-based pricing within two years.

Usage based. Customers pay for what they consume, usually metered in credits, tokens, or actions. Roughly 80 percent of customers say usage-based pricing lines up better with the value they get. The catch is budget volatility. Even as token prices fell about 80 percent year over year, total AI spending grew 320 percent, which tells you exactly how buyers behave when a meter is running and the product is good.

Outcome based. Customers pay per result delivered. Intercom's Fin charges $0.99 per billable outcome, HubSpot dropped its Customer Agent to $0.50 per resolved conversation in April 2026, Zendesk's AI agents run roughly $1.20 to $1.50 per verified resolution, and Salesforce Agentforce launched at $2.00 per conversation. This is the cleanest value story you can tell a buyer. It's also the hardest to define, because you and your customer have to agree on what counts as a resolution.

Hybrid. A predictable base fee plus metered charges for AI work. This has quietly become the most common model in 2026, and for good reason. It gives you recurring revenue you can forecast and a variable component that covers your variable cost. Intercom does exactly this: seats at $29 to $139 per agent per month, plus $0.99 per outcome, plus a 50-outcome monthly minimum.

How do you price an AI product when you have zero customers?

Build the cost model first, then pick a price that clears your target margin at your worst realistic usage, not your average one.

Concretely, four steps:

Define your billable unit and measure what it costs. Run 50 real tasks end to end and record actual token spend, including failures and retries.
Multiply by your expected monthly volume per customer, then multiply that by three. Heavy users are not an edge case, they are your most engaged customers and they will find you.
Set the price so that even at 3x expected usage you still clear 60 percent margin.
Put a usage ceiling in the plan from day one. Adding one later feels like a price increase. Having one from the start is just how the product works.

This is the moment where the cost model belongs next to the rest of your financial planning, not in a separate file nobody opens. A spreadsheet works. So does Notion, or a planning tool like Foundra that walks first-time founders through the projection alongside the rest of the business model. What matters is that your pricing page and your financial model are looking at the same numbers.

One more thing on early pricing. Charge something from the first customer. Free tiers on AI products are a direct transfer from your bank account to a model provider, and the usage data you get from people who pay nothing tells you almost nothing about willingness to pay.

Should you charge per seat, per usage, or per outcome?

Match the model to how variable your costs are and how measurable your value is.

Your situation	Model that fits
Light AI features, usage roughly even across users	Per seat, watch the outliers
Usage varies wildly between customers	Hybrid: base fee plus metered overage
You can point at a countable result the customer cares about	Outcome based
Developer tool or API	Pure usage based
Enterprise buyer who needs budget certainty	Committed contract with a usage pool

The honest test for outcome pricing is whether you could write the definition of a successful outcome on one line and have your customer agree to it without negotiation. "Ticket resolved without human escalation" passes. "Improved productivity" does not. Zendesk's May 2026 move to bill only for LLM-verified resolutions is a sign of where this goes: buyers stopped accepting vendor claims about what counted, so the definition had to get tighter.

How do you keep one heavy user from bankrupting you?

Cap it, meter it, and make the limit visible in the product before the customer hits it.

The specific controls worth building early:

A hard usage ceiling per plan, with a clear upgrade path when someone reaches it
A live usage meter in the app, so nobody is surprised at the end of the month
Per-account alerts on your side when a customer crosses a margin threshold
Model routing, so cheap requests go to a cheap model and only the hard ones hit a flagship

That last one is where the real money is. The price gap between model tiers is enormous right now. Google's Gemini 3.1 Flash runs $0.10 per million input tokens and $0.40 per million output, while flagship models sit at $5 to $30 per million. If 70 percent of your requests are simple and you're sending all of them to a frontier model, you're burning margin on purpose.

And the ground keeps shifting in your favor. Frontier-class pricing per million tokens is roughly a fifth of what it was two years ago. Andreessen Horowitz's analysis found the cost for an LLM of equivalent performance dropping about 10x per year, faster than compute during the PC era or bandwidth during the dotcom boom. Your margin problem this quarter may partly solve itself next year. Partly. Don't build a business that depends on it.

What pricing mistakes are AI founders making right now?

The expensive ones are all variations on the same theme: changing the meter without preparing the customer.

Cursor is the case study everyone in this category should read. In mid-2025 the company moved Pro users from request-based billing to monthly usage credits, and described the change using the phrase "rate limits," which almost nobody understood. Users started reporting unexpected charges of $10 to $20 a day. One team burned through a $7,000 annual plan in a single day. The CEO apologized, refunds went out, spending controls and usage visibility got better, but the old plan never came back. Cursor survived it because the product is loved. A seed-stage company with 40 customers does not get that grace.

The other recurring mistakes:

Inventing a credit currency nobody can price. If a customer can't answer "what will this cost me next month" in under ten seconds, your pricing page has failed.
Pricing against a competitor's cost structure instead of your own. They may be running a distilled model on their own hardware.
Forgetting retries and failures in the cost model. These are frequently 20 to 30 percent of real token spend.
Giving unlimited usage to land a logo. The logo is worth less than the bill.
Treating the AI feature as free marketing inside an existing SaaS plan. That's the 12 to 17 point margin hit, and it usually arrives without anyone noticing for two quarters.

How often should you change your pricing?

Review the cost side monthly, and revisit the price itself every six to twelve months in the first two years.

Monthly review is not about changing the price. It's about watching cost per unit and margin per account so you catch a problem while it's small. Model prices move, usage patterns drift, and a feature you shipped in March can quietly double your inference bill by June.

When you do change the price, give existing customers notice and grandfather the early ones for a defined window. Early customers took a risk on an unproven product. Protecting them costs you very little and buys you the references you'll need later.

Key takeaways

AI products run 50 to 60 percent gross margins, not the 70 to 90 percent of mature SaaS. Plan around that number, don't fight it.
Inference alone averages about 23 percent of revenue at scaling-stage AI companies. Model your cost per unit before you pick a price.
Hybrid pricing, a predictable base plus a meter, is the most common 2026 model because it matches recurring revenue to recurring cost.
Outcome pricing tells the best value story but only works when the outcome is countable and both sides agree on the definition.
Build usage caps, live meters, and model routing before you need them. Retrofitting a limit reads as a price increase.
Token costs are falling roughly 10x a year for equivalent performance. That helps, but never build a plan that requires it.

FAQ

What is a good gross margin for an AI startup?

Sixty percent or better is a reasonable target for an AI-native product in 2026. The category average is around 52 percent. Below 50 percent you're in territory where growth makes the cash problem worse rather than better.

Should I use usage-based or subscription pricing for my AI product?

Most companies land on both. A base subscription covers your fixed costs and gives you forecastable revenue, while a usage or outcome component covers the compute that scales with each customer. Pure subscription only works if usage is close to uniform across your customers.

How much does it cost to run an AI product?

It depends entirely on the model tier and request volume. Cheap models run about $0.10 per million input tokens, flagship models $5 to $30. The practical answer is to measure your own cost per billable unit across 50 real tasks rather than estimating from published rates.

What is outcome-based pricing?

Charging per result delivered rather than per user or per unit of consumption. Intercom's Fin charges $0.99 per resolved conversation, HubSpot $0.50, Salesforce Agentforce $2.00. It aligns your revenue with customer value, but it requires a definition of "outcome" that survives a procurement conversation.

Can I raise prices after launch?

Yes, and most AI companies will have to. Give notice, explain what changed, and grandfather existing customers for a set period. What damages trust isn't the increase, it's changing how the meter works without making the new math easy to understand.

Do I need to charge from day one?

Charge early. Every free user of an AI product costs you real money, and free-tier usage data tells you nothing about what someone will actually pay. A small price from your first customer is better research than a thousand free signups.

Startup Distribution Strategy: Why Building Isn't Enough

Spencer Claydon — Mon, 14 Sep 2026 15:09:18 +0000

You shipped. The thing works. You posted about it, and the counter went to 40 views, three of which were you refreshing the page.

This is the most common founder experience of 2026, and almost nobody warned you about it. The advice you absorbed for years was "just build something people want." That advice was written when building was the hard part. It isn't anymore. A startup distribution strategy used to be the thing you figured out after product-market fit. Now it's the thing that decides whether you ever get close.

Here's the uncomfortable math. On Product Hunt alone, there were 44,744 launches between May 24 and July 25, 2026. That's roughly 711 products a day, every day, on one platform. Product Hunt's daily traffic is still somewhere around 150,000 to 250,000 unique visitors. Divide one by the other and you'll see why "we launched and nothing happened" isn't a story about your product being bad.

Why is distribution harder now than it was three years ago?

Distribution is harder because the cost of building collapsed and the supply of attention didn't move. AI compressed the build step from months to days. It did nothing to the number of hours a potential customer has in their week, or how many pitches they'll tolerate before they tune out.

Think about what actually changed. In 2022, if you wanted a working SaaS product, you needed either engineering skill or $40,000. That requirement was a filter. It kept the number of competing products low, which meant a decent product with mediocre marketing could still get noticed. The filter is gone. What's left is a much bigger pile of decent products all pointed at the same finite audience.

And there's a second-order effect people miss. Because building is cheap, the marginal product in any category is now much better than it used to be. Your competition isn't three companies with clunky onboarding. It's forty companies, half of which shipped last quarter, all with clean UIs because the tooling makes clean UIs nearly free.

So the advantage moved. It used to sit in the product. It sits in distribution now.

What is a startup distribution strategy, actually?

A startup distribution strategy is a written answer to one question: what specific, repeatable path brings a stranger from not knowing you exist to using your product? Not a list of channels. A path, with a sequence and a mechanism.

Most founders confuse the two. "We'll do content, social, and some Reddit" is a list of channels. It's not a strategy, because it doesn't say how any one of those things turns into a user, or why that particular stranger would care.

A real one looks more like this:

First-time founders search "how to calculate startup runway" when their accountant asks for projections. They land on our guide. The guide contains a free calculator. The calculator gives partial output free, full output for an email. The email sequence shows them three other things they haven't planned for. Two of those three are the paid product.

That's a mechanism. You can measure every step, find the leaky one, and fix it. You can't fix "we'll do content."

The test I use: can you draw it on a napkin as boxes and arrows, with a number on each arrow? If not, it's a wish list.

Which distribution channels still work in 2026?

The channels that still work are the ones where you're answering a question someone already asked, rather than interrupting them. Search, communities, and owned audience. Everything else is either expensive or closing.

Let me be specific about each.

Search, including AI search. Still the best channel for most B2B tools, with a caveat. Ranking on Google and getting cited by ChatGPT or Perplexity are not the same job anymore. AI answer engines pull from sources that often sit well outside the first page of traditional results, which means a page that ranks 30th can still end up quoted in an answer. If your category has people typing questions into something, this channel is worth the year it takes to compound.

Communities, carefully. Reddit hasn't banned self-promotion. It's banned bad self-promotion. The working norm is still roughly 90/10: ninety percent participation, ten percent or less talking about your thing. What's changed is the tolerance level. In 2026, r/programming banned LLM-related content outright, and plenty of smaller subs have tightened up because they were drowning in launch posts. The launch-friendly rooms have shifted to places like r/SideProject, r/microsaas, r/buildinpublic, and r/Solopreneur. Smaller, but they'll actually let you talk.

Owned audience. The slowest to build and the only one nobody can turn off. A founder with a few thousand people who trust them has more reliable distribution than a company burning $50,000 a month on ads, because the ads stop the day the card declines.

Partnerships and integrations. Underrated by first-time founders. If another company already has your customers and doesn't compete with you, a integration listing or a co-written guide can outperform six months of cold outreach.

Paid acquisition. Fine as an accelerant, terrible as a discovery mechanism. If you don't know your payback period, paid ads are a way to learn expensive lessons quickly.

Why do good products launch to silence?

Good products launch to silence because the founder built in private for four months and then tried to create demand in a single day. Launch day doesn't generate attention. It converts attention you already gathered.

I've watched this play out over and over. A founder disappears, builds something legitimately useful, posts it on a Tuesday, and gets eleven upvotes and one comment asking if it's open source. They conclude the product failed. The product didn't fail. The product never got evaluated.

The founders who get traction on launch day did the unglamorous thing: they spent the build period talking in public about the problem. Not teasing the product. Talking about the problem, in the rooms where people have it. By the time they shipped, there were forty people who'd already told them "let me know when it's ready," and those forty people are what a launch is made of.

There's a related failure that's harder to see. A lot of what founders call validation is just politeness. Friends saying "that's cool," a survey where 60 people said they'd pay. Neither predicts anything. The only signal that has ever meant much is someone doing something inconvenient: giving you money, giving you their calendar time, or giving you a real email address in exchange for something they want. If your validation didn't cost anyone anything, you didn't validate.

How much time should you spend on distribution versus building?

Most founders should spend at least as much time on distribution as on the product, and the ones who are stuck should probably spend more. The common ratio is something like 40 hours a week building and 4 hours trying to find customers, which is roughly backwards for anything past a working prototype.

The specific number matters less than the habit. Here's a schedule that works for a solo founder or a two-person team:

Week	Build	Distribution
Pre-launch, weeks 1 to 8	60%	40% (audience, waitlist, conversations)
Launch month	30%	70%
Post-launch, first 6 months	50%	50%

The pre-launch 40% is the one everybody skips, and it's the one that determines whether launch month does anything at all.

One more thing worth saying plainly: distribution work feels worse than building. Building gives you a clean feedback loop. You write code, something appears, you feel competent. Distribution gives you silence for weeks, then one reply. That asymmetry is exactly why the advantage is available. Most people can't tolerate it, so the people who can face less competition than the raw product numbers suggest.

How do you pick your first channel?

Pick the one channel where your specific customer already goes when they have the problem you solve, and commit to it for 90 days before judging it. One channel, done properly, beats five done at 20%.

Here's how to narrow it:

Write down the trigger moment. What happens in your customer's week, right before they'd need you? An investor asks for projections. A cofounder quits. The trial of a competing tool expires.
Ask where they go in that moment. Google? A specific Slack group? Their accountant? LinkedIn?
Go there and read for a week without posting anything. You'll learn the vocabulary, which is most of the work.
Show up as a person who helps, not a person who sells. For a month.
Then, and only then, mention what you built, once, in a thread where it's the actual answer.

That's slow. It's also the version that works, and the compressed version is what gets people banned.

If you're structuring this alongside your positioning and target market work, it helps to have it written down somewhere other than your head. A spreadsheet is fine. Notion is fine. A planning tool like Foundra walks first-time founders through the go-to-market section specifically, and there's a growing set of free calculators and templates at foundra.ai/tools if you'd rather just grab the piece you need. The format matters much less than the fact that it exists in writing and you revisit it monthly.

What does distribution look like when it's working?

Distribution is working when new users arrive on days you did nothing. That's the only test. Traffic from a single post is an event. Traffic that shows up next Tuesday without your involvement is a channel.

Three markers to watch for:

Compounding baseline. Your worst day this month is better than your worst day last month.
Inbound language shift. People start describing your product back to you using words you wrote, which means your positioning traveled without you.
Referral without a program. Someone mentions you in a thread you weren't in.

If none of those are happening after 90 days of real effort on one channel, the channel is probably wrong, or the positioning is. Usually the positioning. Switching channels when the message is the problem is how founders burn two years.

Key takeaways

Building is no longer the bottleneck. Roughly 711 products launch on Product Hunt daily, and the audience didn't grow to match.
A distribution strategy is a mechanism with measurable steps, not a list of channels.
Search, communities, owned audience, and partnerships still work. Interruption-based tactics mostly don't.
Launch day converts attention you already built. It doesn't create it.
Spend 40% of pre-launch time on distribution, and more than that during launch month.
Pick one channel, give it 90 days, and judge it on whether users arrive on days you did nothing.

FAQ

How long does it take for a distribution channel to work?
Plan for 90 days minimum to see early signal and six to twelve months for search or owned audience to compound. Communities can produce results in weeks, but only after you've built standing there. Anything promising results in two weeks is either paid or not real.

Should I build an audience before I build the product?
Not necessarily before, but definitely during. Talking publicly about the problem while you build costs you a few hours a week and means launch day has an audience. The mistake is sequencing them: four months of silence, then a launch.

Is paid advertising worth it for an early-stage startup?
Only after you know your conversion rate and roughly what a customer is worth over time. Paid ads amplify whatever's already happening. If your landing page converts at 0.5%, ads will buy you expensive proof of that.

What if my product is for a niche nobody discusses online?
Then your channel is probably partnerships or direct outreach, not content. Find the companies, consultants, or associations that already serve that niche and work through them. Small markets reward relationships over reach.

How do I know if the problem is distribution or the product?
Look at what happens after people arrive. If visitors sign up and stay, you have a distribution problem. If they arrive and bounce, or sign up and never return, it's the product or the positioning. Fixing distribution first when the product leaks is how you waste a budget.

Can I outsource distribution to an agency?
Rarely, at the early stage. Agencies execute channels; they can't discover which channel fits a product nobody understands yet. Once you've found something repeatable, handing off execution makes sense. Before that, you're paying someone to guess.

How to Get on G2 and Capterra as a New Startup

Spencer Claydon — Sun, 13 Sep 2026 15:11:19 +0000

Somewhere in the last year, "get on G2 and Capterra" became the standard advice for any software company that wants to show up in AI answers. It's half right. The half that's wrong will cost you three months chasing a review count that doesn't do what you think it does.

The short version: getting listed is close to mandatory, because almost every tool an AI assistant names has a profile on both. Getting more reviews past the listing minimum does almost nothing for how AI ranks you, and the review sites themselves are almost never the page that gets cited. Clear the gate cheaply, then spend your real effort elsewhere. This piece covers both halves.

Do G2 and Capterra still matter for a startup with no customers?

Yes, but as an entry ticket rather than a growth channel. In a 2026 study of B2B SaaS recommendations, 100% of the tools ChatGPT named had a Capterra profile and 99% had G2 reviews. A product with zero presence on either almost never got named at all. That's a strong signal, and it's cheap to act on, which is why it belongs on your list.

What it isn't is proof that reviews caused the recommendations. Established tools tend to have both review profiles and piles of third-party coverage, so presence may just mark a company that's been around long enough to accumulate everything else. Treat it as a credibility check you want to pass, not a lever you can pull.

The practical read for an early-stage startup: claim the profiles now, while it costs you an afternoon. Do it before you have ten customers, so that when you do, the machinery for asking them already exists.

G2 now owns Capterra, and that changes where you start

This is the fact most 2025-era advice misses. G2 acquired Capterra, GetApp, and Software Advice from Gartner, and the deal closed on February 5, 2026. The three former Gartner properties are now grouped under "G2 Digital Markets."

Same parent company, two entirely separate systems. As of mid-2026 there are two vendor logins, two billing relationships, two category taxonomies, and critically, two separate review pools. A review you collect on G2.com does not appear on Capterra. A review collected on Capterra does not appear on G2. Syndication between them is the obvious next integration and it has not shipped.

What follows from that is a real strategic choice, and the answer is not "do both." Splitting ten reviews across two ecosystems gives you two profiles that clear nothing. Concentrate on one:

Start with Capterra (and therefore G2 Digital Markets) if you sell to small businesses or your buyers find software by browsing category pages. One review submitted to Capterra, GetApp, or Software Advice appears on all three automatically. One effort, three surfaces.
Start with G2 if you sell to technically fluent or mid-market buyers. G2 reviews syndicate out to AWS Marketplace, Azure, and other procurement surfaces, which matters if your buyer evaluates software through a cloud marketplace.

If you already have momentum on one, stay there. Switching forfeits everything you've collected.

How to get listed on G2, step by step

The submission is free and takes about twenty minutes. Go to the G2 profile creation form at sell.g2.com, and pay attention to three things most people get wrong.

Check the admin box. The form asks whether you'd like to serve as admin for the profile. Say yes. Otherwise your profile gets approved and you then have to file a separate claim to control it.

Use a work email. Gmail addresses get rejected. If you're a solo founder running off a personal address, set up the domain email first.

Expect three to five business days. A human reviews it. They open your site, check your LinkedIn company page, and look up the domain WHOIS. A thin landing page with no company entity behind it is the usual reason for rejection, so ship a real site first.

Once live, the free plan lets you hold a profile and collect reviews. Responding to reviews publicly, displaying G2 badges, and accessing analytics sit behind a paid plan. Capterra's equivalent badges are free to display with attribution, which is a real difference for a bootstrapped company. Don't buy a G2 plan until you have ten reviews and a reason.

How to get listed on Capterra, GetApp, and Software Advice

Register once with G2 Digital Markets, then claim each of the three sites separately from inside that dashboard. They share a login and a billing relationship but they are three distinct listings, and each can carry its own description and screenshots.

The payoff for that extra clicking is the best effort-to-surface ratio in the category: one review lands on all three sites at once. GetApp skews more European and more technical, Software Advice routes buyers through phone-qualified advisor introductions, and Capterra is the broad small-business front door that ranks for "best [category] software" in Google.

One piece of housekeeping that confuses everyone: you will still get emails branded "Gartner Digital Markets" for password resets and support. The rebrand is rolling out in stages. It's not phishing.

The review thresholds that actually exist

Every number worth knowing is published by the platforms themselves. Everything else you read is someone's guess.

What it unlocks	Platform	Requirement	Window
Plotted on a category Grid report	G2	10 reviews in that category	Rolling
Live Grid shown on a category page	G2	Category needs 3+ products with 10+ reviews	Updated daily
Category qualifies for a Grid report	G2	6+ products with 10+ reviews, 150+ reviews total	Rolling
Eligible for the Shortlist	Capterra	20 unique reviews	Trailing 24 months

Ten. Not fifty. You'll see "you need at least 50 reviews on G2 to appear in Grid Reports" repeated in a lot of agency blog posts, including ones published this month. G2's own documentation says ten in the relevant category. If you're budgeting effort, budget for ten.

Two details hide in that table. First, G2 counts reviews by category, so a review filed under the wrong category does nothing for the Grid you actually compete in. Check which category your reviewer selected. Second, Capterra's window is the trailing 24 months, which means Shortlist eligibility decays. A burst of twenty reviews in 2024 does not keep you qualified in 2026. A slow trickle beats a one-time push.

How to get your first ten reviews without breaking the rules

Ten reviews from a customer base of thirty is not a marketing campaign, it's about forty personal emails. Plan it that way. A well-run program converts roughly 15 to 30 percent of invitations into published reviews, so to land ten you should be asking forty to sixty people.

The sequence that works:

Pick people who've hit a win. Someone three to six months in who just finished onboarding, closed out a good support ticket, or told you something nice in a call. Value has to be fresh.
Send a direct link. Not "we're on G2." A one-click URL to your review page. Every extra step drops your conversion.
Ask once, remind once. First ask within a day of the positive signal, one nudge a week later, then stop.
Route unhappy customers somewhere else. If someone is frustrated, that's a customer success conversation, not a public profile. This isn't about hiding criticism, it's about not manufacturing it.

On incentives, the rules are clearer than founders assume. Both platforms let you offer a thank-you for the act of writing a review. G2 caps incentive value at $100 and tags incentivized reviews as such; $10 to $25 is the normal amount. What's prohibited is conditioning the reward on sentiment. You cannot pay for a good review, and you cannot withhold payment for a bad one. Offer it to everyone who submits, disclose it, and you're fine.

Reply to every negative review once you can. Buyers read the response more carefully than the complaint.

Why more reviews won't get you recommended by ChatGPT

Here's the part that should change how you spend the next quarter. Once you clear the listing minimums, review volume stops predicting anything about AI visibility, and the data is unusually blunt about it.

A 2026 analysis measured review count against where ChatGPT ranked tools in its answers. The correlation was weakly negative: Capterra at -0.21, G2 at -0.16. Average rating was effectively noise (Capterra +0.02, G2 -0.11). Asked for Notion alternatives, ChatGPT put Coda at number three on 97 Capterra reviews and ClickUp at number four on roughly 4,490. A 46x difference in review count bought a worse position.

Then it gets stranger. DerivateX ran 40 B2B SaaS categories through ChatGPT with web search enabled, ten times each, and logged all 233 recommendations and every source credited. Review aggregators accounted for 0.9% of all citations. G2 and Capterra each got exactly zero. Independent and niche blogs plus vendor-owned content took 81.9%. Reddit was the single most-cited domain in the whole study.

So the review profile does quiet background work: it signals you're a real company so the engine is willing to name you. The visible citation, the link a buyer actually clicks, comes from somewhere else entirely. If you want the mechanics of how citation and ranking came apart, we covered that in how to get your startup cited by ChatGPT.

One caveat worth stating: that study measured one engine on one query type at one point in time. Treat the direction as solid and the exact percentages as a snapshot.

What to do instead once you've cleared the gates

Publish the definitive list for your own category, on your own domain, and be fair to your competitors in it.

The DerivateX study found that the vendors winning citations were frequently the ones who'd written the ranked roundup of their own market. Procurify runs a "Best Procurement Software" post on its blog that ranks Procurify well and lists competitors accurately. ChatGPT used that one page as the cited source for five different brand recommendations inside a single procurement answer. Zapier, Mercury, and Front are all running the same play in their categories.

The format matters as much as the content. Of the cited pages the study retrieved and analyzed: 100% used list structure, 78% carried the current year in the title, 68% included a comparison table, and 56% had an FAQ section. Domain authority was not the differentiator. Small, narrowly focused sites outperformed household names, which is the entire opening for a startup with a two-year-old domain.

That's the whole strategy, and it's cheaper than a G2 Enterprise plan:

Claim your profiles and get to ten or twenty reviews. Stop there.
Write the "best [your category] tools in 2026" page yourself. Include competitors, with real pricing and real trade-offs. A roundup that only flatters you gets read as marketing and cited by nobody.
Add a comparison table and an FAQ. Put the year in the title. Refresh it monthly.
Answer questions in the communities where your category gets discussed, because Reddit threads are getting cited more than every review site combined.
Build things people link to on their own. We've written about free tools as a distribution channel, and Foundra's own free tools exist as much for that reason as for the signups.

Scope it to one category at a time. In that same study, 94% of the 219 tools analyzed appeared in only a single category. There's no such thing as brand-wide AI visibility. There's only winning the specific question your buyer types.

Key takeaways

Presence on G2 and Capterra is close to mandatory: 100% of ChatGPT-recommended tools in a 2026 study had a Capterra profile, 99% had G2 reviews.
G2 bought Capterra, GetApp, and Software Advice from Gartner on February 5, 2026. Two separate cabinets, two separate review pools, no syndication yet. Pick one ecosystem and concentrate.
The real thresholds are 10 category reviews for a G2 Grid and 20 reviews in 24 months for a Capterra Shortlist. The "you need 50" claim is wrong.
Incentives are allowed for the act of reviewing, capped at $100 on G2, never conditioned on sentiment.
Past the minimums, review volume correlates weakly negatively with ChatGPT ranking (-0.21 Capterra, -0.16 G2).
Review sites supplied 0.9% of citations across 233 software recommendations. G2 and Capterra each got zero.
The highest-leverage move is publishing the current, fair, well-structured ranked list of your own category. One such page earned citations for five different brands in a single answer.

FAQ

How many reviews do I need to show up on a G2 category page?

Ten reviews in that specific category gets your product plotted on the category Grid. G2 displays a live Grid on a category page once at least three products each have ten or more reviews, and a category qualifies for a formal Grid report when six or more products have ten-plus reviews and the category has 150 or more reviews total. Reviews filed under a different category don't count toward the Grid you care about.

Is Capterra still owned by Gartner?

No. G2 acquired Capterra, GetApp, and Software Advice from Gartner in a deal that closed February 5, 2026. They now operate as G2 Digital Markets. The vendor dashboard is still separate from G2.com's, with its own login, its own billing, and its own review pool, and some support emails still carry Gartner branding while the rebrand rolls out.

Will my G2 reviews show up on Capterra now that they're the same company?

Not yet, and there's no announced date. Reviews collected on G2 stay on G2. Reviews collected on any one of Capterra, GetApp, or Software Advice appear on all three of those automatically. This is the main reason to concentrate your review collection on one ecosystem rather than splitting it.

Can I offer a gift card for a G2 review?

Yes, within limits. G2 caps incentive value at $100 and automatically labels reviews that came through an incentivized campaign. The reward has to be for submitting a review, not for submitting a positive one, and you have to honor it regardless of what the review says. Ten to twenty-five dollars is the typical amount, and conditioning the reward on a good rating violates the community guidelines on both platforms.

If reviews don't drive AI recommendations, why collect them at all?

Because absence is disqualifying even though abundance isn't rewarded. Nearly every tool AI names has review profiles, and products with none rarely appear. Reviews also convert human buyers, who read them far more carefully than any model does. Collect enough to clear the listing floors, keep them fresh, and then put the next hundred hours into the comparison content that actually earns the citation. More of our thinking on early distribution is in the Foundra key reads library.