<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://dealpuffin.com/blog/general/</id>
    <title>Dealpuffin Blog</title>
    <updated>2026-11-15T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://dealpuffin.com/blog/general/"/>
    <subtitle>Dealpuffin Blog</subtitle>
    <icon>https://dealpuffin.com/img/mark.svg</icon>
    <entry>
        <title type="html"><![CDATA[How to run customer interviews as a solo founder: a 15-minute method]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/"/>
        <updated>2026-11-15T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Run customer interviews as a solo founder without pitching. Five questions, a note template, and rules from Y Combinator's guidance on talking to users, with a worked example.]]></summary>
        <content type="html"><![CDATA[<p>To run a customer interview as a solo founder, spend 10 to 15 minutes asking a person about a specific time they hit the problem, and say almost nothing about your product. Ask what they did about it, what they disliked about that fix, and write down their exact words. You are collecting facts about their past.</p>
<p>This method follows Y Combinator partner Eric Migicovsky's talk <a href="https://www.youtube.com/watch?v=MT4Ig2uqjTc" target="_blank" rel="noopener noreferrer" class="">How to Talk to Users</a> (YC Startup School, July 2019), summarized in <a href="https://www.ycombinator.com/blog/startup-school-week-1-recap-kevin-hale-and-eric-migicovsky/" target="_blank" rel="noopener noreferrer" class="">YC's Startup School recap</a>. Where a step is our own suggestion, it says so. We read both on 15 November 2026.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-three-rules">The three rules<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#the-three-rules" class="hash-link" aria-label="Direct link to The three rules" title="Direct link to The three rules" translate="no">​</a></h2>
<p>Migicovsky's talk reduces interviewing to three rules.</p>
<ol>
<li class="">Talk about their life, not your idea. Founders love pitching, and he says a user interview is not the time to pitch. The goal is to extract information that helps you improve the product, your marketing or your positioning.</li>
<li class="">Talk about specifics, not hypotheticals. Instead of asking whether they would use or pay for a feature, ask about things that already happened. In his words, that gives you stronger information for decisions.</li>
<li class="">Listen. Founders spend their days pitching investors and candidates, so restrain the urge to talk and take notes.</li>
</ol>
<p>He frames the stakes simply: YC's core teaching is that you must build your product and talk to users.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-five-questions">The five questions<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#the-five-questions" class="hash-link" aria-label="Direct link to The five questions" title="Direct link to The five questions" translate="no">​</a></h2>
<p>The talk lists five questions anyone can use in early interviews. Here they are, with a note on what each one is for.</p>
<ol>
<li class="">What is the hardest part about [doing this thing]? It tests whether the problem is a real pain point for them. Fill in the bracket with their job.</li>
<li class="">When was the last time you ran into this problem? This pulls out a concrete incident and its context, which you can later compare your solution against.</li>
<li class="">Why was that hard? The answer tells you how to explain the value in their words.</li>
<li class="">What, if anything, have you done to solve this problem? That is your real competition, including spreadsheets and doing nothing.</li>
<li class="">What don't you love about the solution you already tried? The gaps here are the start of your feature list.</li>
</ol>
<p>Migicovsky also says users are not good at naming the next feature they want, so do not ask them to design your roadmap. Our suggestion is to treat their answer to question 5 as a problem statement and design the fix yourself.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="how-to-run-one-step-by-step">How to run one, step by step<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#how-to-run-one-step-by-step" class="hash-link" aria-label="Direct link to How to run one, step by step" title="Direct link to How to run one, step by step" translate="no">​</a></h2>
<ol>
<li class="">Practice on yourself. Migicovsky suggests testing your interview strategy on yourself by walking through a time you hit the problem.</li>
<li class="">Start with warm contacts. He recommends friends, coworkers and warm introductions for the first interviews, and says you do not need to talk to thousands of people. Our caution: friends tend to be kind, so ask them about the problem and skip "is my idea good?".</li>
<li class="">Keep it short. He says a 10 to 15 minute first interview can give you the best information, and that you should be mindful of the other person's time.</li>
<li class="">Record or take notes. Alone, you cannot do both well. He suggests bringing a friend or cofounder, or asking permission to record. As a solo founder, ask permission and use a recorder, then review the audio within a day.</li>
<li class="">Do five before you judge. He says you learn a lot from the first five or ten interviews and your process improves. Start with one, then three, then five.</li>
<li class="">Steer away from hypotheticals. When the person drifts into "I would probably...", he says to bring them back to what actually happened.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-note-template">A note template<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#a-note-template" class="hash-link" aria-label="Direct link to A note template" title="Direct link to A note template" translate="no">​</a></h2>
<p>Use one row per interview. The columns are our suggestion.</p>
<table><thead><tr><th>Date</th><th>Who and role</th><th>Last time it happened</th><th>What they did</th><th>What they disliked</th><th>Exact quote</th><th>Follow-up</th></tr></thead><tbody><tr><td>11-15</td><td>Freelance designer</td><td>Last Tuesday, invoice paid 3 weeks late</td><td>Chased by email, then a reminder in Notion</td><td>Felt awkward and kept forgetting</td><td>"I just avoid sending the second reminder"</td><td>Ask about how many late invoices per month</td></tr></tbody></table>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-worked-example">A worked example<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#a-worked-example" class="hash-link" aria-label="Direct link to A worked example" title="Direct link to A worked example" translate="no">​</a></h2>
<p>Imagine you are building invoicing software for freelancers. This is a made-up scenario to show the method.</p>
<p>A bad interview: "I'm building a tool that sends automatic payment reminders. Would you use it?" Almost everyone says yes, and you learn nothing.</p>
<p>A good interview starts with question 1: "What's the hardest part of getting paid as a freelancer?" She mentions late payments. You ask question 2: "When did that last happen?" She describes a specific invoice, three weeks late. Questions 3 to 5 reveal that she chases by email, finds it awkward, and has tried a calendar reminder that she ignores. Now you have a specific problem, her workaround and its flaw. You never mentioned your product.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="use-the-data">Use the data<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#use-the-data" class="hash-link" aria-label="Direct link to Use the data" title="Direct link to Use the data" translate="no">​</a></h2>
<p>Migicovsky describes a way to find your best first customers from interviews. His criteria include people who hit the problem frequently, and people who have the ability to act, because an operator may feel the pain daily but lack the budget. You can add these as columns to your notes.</p>
<p>When you have users, he points to the Superhuman CEO's survey, which asks how users would feel if the product went away. Migicovsky relays the analysis that 40% or more answering "very disappointed" is a signal of product-market fit. For small user counts, he says even 30 or 40 users is enough to ask.</p>
<p>He also suggests testing demand with action instead of opinion: rather than asking whether users would want a feature, show an upgrade flow that asks for a card. See <a class="" href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/">how to price a SaaS product early stage</a> before you do that, and tell testers what is real.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="where-interviews-fit-in-your-launch">Where interviews fit in your launch<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#where-interviews-fit-in-your-launch" class="hash-link" aria-label="Direct link to Where interviews fit in your launch" title="Direct link to Where interviews fit in your launch" translate="no">​</a></h2>
<p>Interviews feed your positioning and your list of first prospects. They pair well with <a class="" href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/">how to get your first 10 paying customers</a> and with <a class="" href="https://dealpuffin.com/blog/general/how-to-get-your-first-100-users-for-a-saas/">how to get your first 100 users for a SaaS</a>. Ask each person at the end whether they know anyone else who has the problem. Our suggestion: ask for one introduction per interview.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-many-customer-interviews-should-i-do">How many customer interviews should I do?<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#how-many-customer-interviews-should-i-do" class="hash-link" aria-label="Direct link to How many customer interviews should I do?" title="Direct link to How many customer interviews should I do?" translate="no">​</a></h3>
<p>Start with one, then three, then five. Migicovsky says the first five or ten teach you the most and improve your process. Keep going until the answers repeat.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-long-should-a-customer-interview-be">How long should a customer interview be?<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#how-long-should-a-customer-interview-be" class="hash-link" aria-label="Direct link to How long should a customer interview be?" title="Direct link to How long should a customer interview be?" translate="no">​</a></h3>
<p>Aim for 10 to 15 minutes for a first interview. Migicovsky says that length can produce the best information, and a short slot is easier to get from a busy person.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-i-pitch-my-product-during-the-interview">Should I pitch my product during the interview?<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#should-i-pitch-my-product-during-the-interview" class="hash-link" aria-label="Direct link to Should I pitch my product during the interview?" title="Direct link to Should I pitch my product during the interview?" translate="no">​</a></h3>
<p>No. The talk says the goal is to extract information, not to sell them on using your product. If they ask, answer briefly and return to their experience.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-interview-friends-and-family">Can I interview friends and family?<a href="https://dealpuffin.com/blog/general/how-to-run-customer-interviews-as-a-solo-founder/#can-i-interview-friends-and-family" class="hash-link" aria-label="Direct link to Can I interview friends and family?" title="Direct link to Can I interview friends and family?" translate="no">​</a></h3>
<p>You can start there, and the talk suggests warm contacts. They tend to be supportive, so ask about concrete past events rather than whether they like your idea.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="go-to-market" term="go-to-market"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
        <category label="validation" term="validation"/>
        <category label="howto" term="howto"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to set up error monitoring for an indie SaaS (4 tools compared)]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/"/>
        <updated>2026-11-15T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Set up error monitoring for a small SaaS in one sitting. Compares Sentry, GlitchTip, PostHog and BugSnag free tiers and limits, with a setup checklist and a decision rule.]]></summary>
        <content type="html"><![CDATA[<p>To set up error monitoring for an indie SaaS, pick one tool with a free tier, install its SDK in both your browser code and your server code, upload source maps so stack traces are readable, and send alerts to one channel you actually check. Sentry, GlitchTip, PostHog and BugSnag all have free plans, and the main differences are how many users, events and days of history you get.</p>
<p>Limits and prices below come from each vendor's pricing page, read on 15 November 2026. They change often, so check the page before you commit.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-error-monitoring-does-for-a-small-product">What error monitoring does for a small product<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#what-error-monitoring-does-for-a-small-product" class="hash-link" aria-label="Direct link to What error monitoring does for a small product" title="Direct link to What error monitoring does for a small product" translate="no">​</a></h2>
<p>Without it, you learn about a crash when a customer emails you, and many customers never do. An error monitor catches uncaught exceptions in your app, groups repeats into one issue, and shows the stack trace and context. PostHog describes the same job as turning exceptions into issues you can prioritize, assign and resolve.</p>
<p>This is different from <a class="" href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/">uptime monitoring</a>, which only tells you whether a URL answers. A page can return 200 and still fail for every user whose card is declined, and only an error monitor will show you that.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-four-tools-at-a-glance">The four tools at a glance<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#the-four-tools-at-a-glance" class="hash-link" aria-label="Direct link to The four tools at a glance" title="Direct link to The four tools at a glance" translate="no">​</a></h2>
<table><thead><tr><th>Tool</th><th>Free plan</th><th>Paid entry point</th><th>What happens past the limit</th></tr></thead><tbody><tr><td>Sentry</td><td>Developer: $0, 1 user, 5k errors, 30-day lookback</td><td>Team: $26/mo billed annually, 50k errors, unlimited users</td><td>Pay-as-you-go rates above quota</td></tr><tr><td>GlitchTip</td><td>1,000 events/mo, 30 days retention</td><td>Small: $15/mo, up to 100k events, 90 days</td><td>Throttles by default; optional on-demand billing with a spend cap</td></tr><tr><td>PostHog</td><td>100K exceptions/mo free, 1 project, 1-year retention</td><td>Pay-as-you-go, usage-based</td><td>Free plan drops extra events; billing limit stops spend</td></tr><tr><td>BugSnag</td><td>Free: 1 user, 7.5K events/mo, 7 days retention</td><td>Select from $20/mo (50k events)</td><td>Covered in their quota FAQ; check it before relying on the plan</td></tr></tbody></table>
<p>Sources: <a href="https://sentry.io/pricing/" target="_blank" rel="noopener noreferrer" class="">Sentry pricing</a>, <a href="https://glitchtip.com/pricing" target="_blank" rel="noopener noreferrer" class="">GlitchTip pricing</a>, <a href="https://posthog.com/pricing" target="_blank" rel="noopener noreferrer" class="">PostHog pricing</a>, <a href="https://www.bugsnag.com/pricing" target="_blank" rel="noopener noreferrer" class="">BugSnag pricing</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="sentry">Sentry<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#sentry" class="hash-link" aria-label="Direct link to Sentry" title="Direct link to Sentry" translate="no">​</a></h2>
<p>Sentry's Developer plan is free and limited to one user, with 5k errors a month and a 30-day lookback. The Team plan is $26 a month when billed annually with default pre-paid data, adds unlimited users and includes 50k errors. Above the quota you pay per error, starting at $0.0003625 per error between 50K and 100K on Team.</p>
<p>For a Next.js app, the docs give one command, <code>npx @sentry/wizard@latest -i nextjs</code>, which installs the SDK and creates separate init files for the browser, the Node.js runtime and the Edge runtime. It also wraps your Next.js config so source maps upload at build time.</p>
<p>The catch for a two-person team is the single user on the free plan. The moment a cofounder needs a login, you are on a paid plan.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="glitchtip">GlitchTip<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#glitchtip" class="hash-link" aria-label="Direct link to GlitchTip" title="Direct link to GlitchTip" translate="no">​</a></h2>
<p>GlitchTip calls itself an open source, Sentry API compatible error tracking platform, and it offers a hosted version and a self-hosted one. The hosted free plan covers 1,000 events a month, where each error and each performance transaction counts as one event. That is small, so it suits a very early product or a side project.</p>
<p>The Small plan is $15 a month for up to 100k events, with unlimited projects and team members. If you go past your limit, GlitchTip throttles by default, starting at dropping about 10% of events and blocking fully at twice your limit. You can turn on on-demand billing at $0.17 per 1,000 events for the first million over, with a monthly spend cap you set.</p>
<p>Because it is Sentry API compatible, it is also the tool to try if you want your data in the EU. GlitchTip lists hosting in Germany as available on all plans.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="posthog">PostHog<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#posthog" class="hash-link" aria-label="Direct link to PostHog" title="Direct link to PostHog" translate="no">​</a></h2>
<p>If you already use PostHog for product analytics, error tracking is the lowest-effort option. The free tier includes 100K exceptions a month, unlimited team members, one project and one year of retention. The practical benefit is context: PostHog says each issue comes with the affected user's session replay, events and properties attached.</p>
<p>Two limits matter. Billing is organization-wide, so extra projects share one free allowance. And on the free plan, usage above the limit is permanently dropped, so a bad deploy that throws a million exceptions will cost you visibility for the rest of the month. Add a card and set a billing limit if you want to keep capturing.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="bugsnag">BugSnag<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#bugsnag" class="hash-link" aria-label="Direct link to BugSnag" title="Direct link to BugSnag" translate="no">​</a></h2>
<p>BugSnag's free plan covers one user with 7.5K events and 1M spans a month, and its pricing page notes the free tier keeps 7 days of data. The paid Select plan starts at $20 a month, with event packs starting at 50k monthly events. Its feature list leans toward stability tracking, such as release health and stability scores. That helps once you ship mobile apps or have several releases in the field. For a single web app it is more than you need on day one.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-decision-rule">A decision rule<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#a-decision-rule" class="hash-link" aria-label="Direct link to A decision rule" title="Direct link to A decision rule" translate="no">​</a></h2>
<p>Answer these in order and stop at the first yes.</p>
<ol>
<li class="">Do you already run PostHog for analytics? Use its error tracking. One SDK and one bill is worth more than a feature gap at this stage.</li>
<li class="">Do you need a second person to log in today? Skip Sentry's free plan and compare GlitchTip Small at $15 a month against Sentry Team at $26 a month.</li>
<li class="">Do you need to self-host or keep data in the EU? Look at GlitchTip first.</li>
<li class="">Otherwise start with Sentry's free plan. You can move later, because GlitchTip says it is compatible with the Sentry API.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-worked-example">A worked example<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#a-worked-example" class="hash-link" aria-label="Direct link to A worked example" title="Direct link to A worked example" translate="no">​</a></h2>
<p>Say you run a Next.js app and expect a few hundred errors a month while you have under a hundred users. That fits inside the Sentry Developer plan's 5k errors, inside PostHog's 100K exceptions, and inside BugSnag's 7.5K events. It can overflow GlitchTip's free 1,000 events if you also send performance transactions, because those count as events too. Your real constraint is how fast a bug loop can burn quota. One retry loop that logs an error every second produces 86,400 events a day. Rate-limit or sample your reporting before that happens, and see <a class="" href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/">how to cap AI API costs in a SaaS</a> for the same idea applied to spend.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="setup-checklist">Setup checklist<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#setup-checklist" class="hash-link" aria-label="Direct link to Setup checklist" title="Direct link to Setup checklist" translate="no">​</a></h2>
<ol>
<li class="">Create the project and install the SDK for both client and server code.</li>
<li class="">Add the framework hook that catches server render errors. For Next.js, Sentry's guide uses <code>instrumentation.ts</code> with an <code>onRequestError</code> export and a <code>global-error.tsx</code> for React rendering errors.</li>
<li class="">Upload source maps in your build. In CI, set <code>SENTRY_AUTH_TOKEN</code> in your build system instead of committing it. If you <a class="" href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/">deploy Next.js on a single VM with Docker</a>, pass it as a build argument or build secret.</li>
<li class="">Throw a test error from a button and confirm it appears. Sentry's guide notes that errors triggered from the browser console are sandboxed and will not show up.</li>
<li class="">Set one alert, sent to the place you already read. A loud channel you mute is worse than none.</li>
<li class="">Tag each error with the release, so you can tell whether a deploy caused it.</li>
<li class="">Review what the SDK sends. Sentry's docs say it can include IP address, user ID and request data by default and lets you turn categories off, which matters for privacy policies.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="which-error-monitoring-tool-is-best-for-a-solo-founder">Which error monitoring tool is best for a solo founder?<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#which-error-monitoring-tool-is-best-for-a-solo-founder" class="hash-link" aria-label="Direct link to Which error monitoring tool is best for a solo founder?" title="Direct link to Which error monitoring tool is best for a solo founder?" translate="no">​</a></h3>
<p>Sentry's free Developer plan is a common starting point and has a one-command setup for Next.js. If you already use PostHog, its error tracking avoids adding another vendor. Both are free for one person at small volume.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="is-sentry-free">Is Sentry free?<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#is-sentry-free" class="hash-link" aria-label="Direct link to Is Sentry free?" title="Direct link to Is Sentry free?" translate="no">​</a></h3>
<p>Sentry has a free Developer plan limited to one user, with 5k errors a month and a 30-day lookback. Paid plans start at $26 a month on the Team plan when billed annually.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-i-need-error-monitoring-before-i-have-users">Do I need error monitoring before I have users?<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#do-i-need-error-monitoring-before-i-have-users" class="hash-link" aria-label="Direct link to Do I need error monitoring before I have users?" title="Direct link to Do I need error monitoring before I have users?" translate="no">​</a></h3>
<p>You need it as soon as a stranger can use your app, because they will not report bugs for you. Install it before launch so the first crash is already recorded.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-happens-if-i-go-over-my-free-error-limit">What happens if I go over my free error limit?<a href="https://dealpuffin.com/blog/general/how-to-set-up-error-monitoring-for-an-indie-saas/#what-happens-if-i-go-over-my-free-error-limit" class="hash-link" aria-label="Direct link to What happens if I go over my free error limit?" title="Direct link to What happens if I go over my free error limit?" translate="no">​</a></h3>
<p>It depends on the tool. PostHog's free plan drops events above the limit, GlitchTip throttles by default, and Sentry bills pay-as-you-go rates on paid plans. Check the overage rule before you rely on a plan.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="devtools" term="devtools"/>
        <category label="saas" term="saas"/>
        <category label="listicle" term="listicle"/>
        <category label="early-founders" term="early-founders"/>
        <category label="monitoring" term="monitoring"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to write docs for a SaaS API: a four-part structure that works]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/"/>
        <updated>2026-11-15T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Write SaaS API docs in four parts: a generated reference, a quickstart, task-based how-to guides and explanations. Uses Diátaxis and OpenAPI, with a launch-week checklist.]]></summary>
        <content type="html"><![CDATA[<p>To write docs for a SaaS API, split them into four parts: a reference generated from an OpenAPI file, a quickstart that gets a first call working, a handful of how-to guides for real tasks, and a short explanation page for concepts such as auth and rate limits. Keep each part to one job. Most weak API docs fail because one page tries to be all four.</p>
<p>This post uses two primary sources, the <a href="https://diataxis.fr/" target="_blank" rel="noopener noreferrer" class="">Diátaxis documentation framework</a> and the <a href="https://learn.openapis.org/introduction.html" target="_blank" rel="noopener noreferrer" class="">OpenAPI Initiative's introduction</a>, both read on 15 November 2026. Suggestions that come from us rather than those sources are marked.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="why-four-parts-instead-of-one-long-page">Why four parts instead of one long page<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#why-four-parts-instead-of-one-long-page" class="hash-link" aria-label="Direct link to Why four parts instead of one long page" title="Direct link to Why four parts instead of one long page" translate="no">​</a></h2>
<p>Diátaxis identifies four needs and four matching forms of documentation: tutorials, how-to guides, technical reference and explanation. Its point is that these serve different readers in different moments, so mixing them hurts all of them.</p>
<p>For an API this maps cleanly:</p>
<table><thead><tr><th>Reader's question</th><th>Diátaxis form</th><th>What it looks like for your API</th></tr></thead><tbody><tr><td>"Can I make this work at all?"</td><td>Tutorial</td><td>A quickstart ending in a first successful call</td></tr><tr><td>"How do I do X?"</td><td>How-to guide</td><td>"How to issue a refund", "How to paginate results"</td></tr><tr><td>"What exactly does this endpoint accept?"</td><td>Reference</td><td>Endpoint, parameter and error listings</td></tr><tr><td>"Why does it work this way?"</td><td>Explanation</td><td>Auth model, idempotency, rate limits</td></tr></tbody></table>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-1-write-an-openapi-description-first">Step 1: Write an OpenAPI description first<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#step-1-write-an-openapi-description-first" class="hash-link" aria-label="Direct link to Step 1: Write an OpenAPI description first" title="Direct link to Step 1: Write an OpenAPI description first" translate="no">​</a></h2>
<p>An OpenAPI Description is a machine-readable specification of an HTTP API. The OpenAPI introduction says reference documentation can be generated from it as a step in the build process, which prevents out-of-sync docs. It adds that the same file can drive generated client code and mock servers built from the examples you include. The specification is vendor-neutral and maintained by the OpenAPI Initiative under the Linux Foundation.</p>
<p>A minimal file looks like this:</p>
<div class="language-yaml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-yaml codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token key atrule">openapi</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> 3.1.0</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token key atrule">info</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token key atrule">title</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> Example API</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token key atrule">version</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> </span><span class="token datetime number">2026-11-15</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token key atrule">paths</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  /invoices/</span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain">id</span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token key atrule">get</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token key atrule">summary</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> Retrieve an invoice</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token key atrule">parameters</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        </span><span class="token punctuation" style="color:rgb(248, 248, 242)">-</span><span class="token plain"> </span><span class="token key atrule">name</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> id</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">          </span><span class="token key atrule">in</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> path</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">          </span><span class="token key atrule">required</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> </span><span class="token boolean important">true</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">          </span><span class="token key atrule">schema</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">            </span><span class="token key atrule">type</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> string</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token key atrule">responses</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        </span><span class="token key atrule">"200"</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">          </span><span class="token key atrule">description</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> The invoice</span><br></div></code></pre></div></div>
<p>If your framework can generate the file from your code, use that. If it cannot, write it by hand and add a CI check that your tests exercise every path in it. Our suggestion: treat a mismatch between the file and the live API as a failing build.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-2-generate-the-reference-and-keep-it-austere">Step 2: Generate the reference, and keep it austere<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#step-2-generate-the-reference-and-keep-it-austere" class="hash-link" aria-label="Direct link to Step 2: Generate the reference, and keep it austere" title="Direct link to Step 2: Generate the reference, and keep it austere" translate="no">​</a></h2>
<p>Diátaxis says the only purpose of reference is to describe as succinctly and orderly as possible, and that it should be neutral. It also notes that API documentation can be generated from the software it describes, which keeps it accurate to the code.</p>
<p>So do not hand-edit reference pages. Put your effort into the fields the generator cannot invent: a one-line summary per endpoint, a description for each parameter, a realistic example request and response, and every error code with its cause. Link out to how-to guides instead of explaining inside the reference.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-3-write-one-quickstart">Step 3: Write one quickstart<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#step-3-write-one-quickstart" class="hash-link" aria-label="Direct link to Step 3: Write one quickstart" title="Direct link to Step 3: Write one quickstart" translate="no">​</a></h2>
<p>A quickstart is the tutorial. It should take a new developer from nothing to one working call, and nothing more. Our suggested shape:</p>
<ol>
<li class="">How to get an API key, in one paragraph.</li>
<li class="">One copy-paste request with the key in an environment variable.</li>
<li class="">The response the reader should see, shown in full.</li>
<li class="">Three links: the reference, your top how-to guides and the explanation page on auth.</li>
</ol>
<p>Test it by giving the page to someone who has never seen your product and watching where they stall. Stalls show you what the page is missing. This is the same logic as running a <a class="" href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/">beta program for a new SaaS</a>: you learn more from watching one person than from guessing.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-4-add-how-to-guides-from-real-questions">Step 4: Add how-to guides from real questions<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#step-4-add-how-to-guides-from-real-questions" class="hash-link" aria-label="Direct link to Step 4: Add how-to guides from real questions" title="Direct link to Step 4: Add how-to guides from real questions" translate="no">​</a></h2>
<p>Diátaxis describes how-to guides as goal-oriented directions that must be written from the perspective of the user, not the machinery. Its naming advice is practical: titles should say exactly what the guide shows, so "How to integrate application performance monitoring" is better than "Application performance monitoring". It adds that search engines appreciate good titles as much as people do.</p>
<p>Our suggestion is to pick topics from evidence: start with the five questions your support inbox gets most often. For a billing API that might be "how to retry a failed charge", "how to verify a webhook" and "how to filter by date range". For a worked example of a task-first guide, see <a class="" href="https://dealpuffin.com/blog/general/how-to-test-stripe-webhooks-locally/">how to test Stripe webhooks locally</a>.</p>
<p>Keep each guide to one goal. Diátaxis warns against polluting a how-to with every possible thing related to the topic, and says to link to reference instead.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-5-write-one-explanation-page">Step 5: Write one explanation page<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#step-5-write-one-explanation-page" class="hash-link" aria-label="Direct link to Step 5: Write one explanation page" title="Direct link to Step 5: Write one explanation page" translate="no">​</a></h2>
<p>Explanation answers "why". Cover the choices a developer cannot see from the endpoints: how authentication works, whether requests can be retried safely, what your rate limits are and what happens when someone hits them, and how you version the API. Only state limits you have verified in your own code or config.</p>
<p>If you also publish an MCP server, say how it relates to the REST API, because developers will ask. <a class="" href="https://dealpuffin.com/blog/general/mcp-server-vs-rest-api-for-a-saas/">MCP server vs REST API for a SaaS</a> covers that choice.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-6-publish-changes-and-deprecations">Step 6: Publish changes and deprecations<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#step-6-publish-changes-and-deprecations" class="hash-link" aria-label="Direct link to Step 6: Publish changes and deprecations" title="Direct link to Step 6: Publish changes and deprecations" translate="no">​</a></h2>
<p>Docs are accurate only on the day you publish them. Add a changelog and put deprecations in it with dates. <a class="" href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/">Setting up a changelog</a> takes an afternoon and gives integrators somewhere to look before something breaks.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-launch-week-checklist">A launch-week checklist<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#a-launch-week-checklist" class="hash-link" aria-label="Direct link to A launch-week checklist" title="Direct link to A launch-week checklist" translate="no">​</a></h2>
<ul>
<li class="">The OpenAPI file validates and is the source of the reference.</li>
<li class="">Every endpoint has a summary, parameter descriptions, an example and its error codes.</li>
<li class="">A new developer can make a first call from the quickstart in one sitting.</li>
<li class="">At least three how-to guides exist, titled by the task.</li>
<li class="">Auth, retries, rate limits and versioning are on one explanation page.</li>
<li class="">A changelog exists, even if it has one entry.</li>
<li class="">Every page has a visible way to report a mistake, such as an email address or an issue link.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-i-need-openapi-to-document-an-api">Do I need OpenAPI to document an API?<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#do-i-need-openapi-to-document-an-api" class="hash-link" aria-label="Direct link to Do I need OpenAPI to document an API?" title="Direct link to Do I need OpenAPI to document an API?" translate="no">​</a></h3>
<p>No, but it helps. The OpenAPI introduction says a machine-readable description lets you generate reference docs, client code and mock servers, and it reduces drift between docs and behavior. You can still write docs by hand for a very small API.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-should-an-api-quickstart-include">What should an API quickstart include?<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#what-should-an-api-quickstart-include" class="hash-link" aria-label="Direct link to What should an API quickstart include?" title="Direct link to What should an API quickstart include?" translate="no">​</a></h3>
<p>A way to get credentials, one working request, the expected response and links to what comes next. Keep it to a single path from nothing to a first successful call.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-long-should-api-docs-be">How long should API docs be?<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#how-long-should-api-docs-be" class="hash-link" aria-label="Direct link to How long should API docs be?" title="Direct link to How long should API docs be?" translate="no">​</a></h3>
<p>As long as each page's single job needs. Diátaxis suggests separating tutorials, how-to guides, reference and explanation instead of capping length, so a reference page can be long while a how-to guide stays short.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-i-write-docs-before-or-after-the-api">Should I write docs before or after the API?<a href="https://dealpuffin.com/blog/general/how-to-write-docs-for-a-saas-api/#should-i-write-docs-before-or-after-the-api" class="hash-link" aria-label="Direct link to Should I write docs before or after the API?" title="Direct link to Should I write docs before or after the API?" translate="no">​</a></h3>
<p>Writing the OpenAPI description first is a cheap way to review the design before building it, and the introduction notes that examples in the file can power mock servers for early testing.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="devtools" term="devtools"/>
        <category label="saas" term="saas"/>
        <category label="howto" term="howto"/>
        <category label="early-founders" term="early-founders"/>
        <category label="documentation" term="documentation"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to collect testimonials for a new SaaS without breaking FTC rules]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/"/>
        <updated>2026-11-14T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Ask real customers for specific quotes, get written permission, and never pay for positive ones. Covers the FTC's 2024 rule on fake and incentivized testimonials.]]></summary>
        <content type="html"><![CDATA[<p>To collect testimonials for a new SaaS, ask real customers at the moment they get a result, give them two or three specific questions to answer, get written permission to publish their words and name, and never pay for or script a positive quote. A short, specific quote from a named customer is worth more than a vague line of praise.</p>
<p>This guide covers a collection routine and the legal floor in the United States. The legal parts quote the FTC's rule at <a href="https://www.ecfr.gov/current/title-16/part-465" target="_blank" rel="noopener noreferrer" class="">16 CFR Part 465</a> and its <a href="https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255" target="_blank" rel="noopener noreferrer" class="">Endorsement Guides</a>, read on 14 November 2026. We are not lawyers, and this is not legal advice.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="why-early-testimonials-are-hard">Why early testimonials are hard<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#why-early-testimonials-are-hard" class="hash-link" aria-label="Direct link to Why early testimonials are hard" title="Direct link to Why early testimonials are hard" translate="no">​</a></h2>
<p>With zero or few customers, you have little to show. The temptation is to write a quote yourself, borrow one from a friend, or offer a discount for a five-star review. The first three customers you get usually come from conversations, as covered in <a class="" href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/">how to get your first 10 paying customers</a>, so you already know them well enough to ask.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-routine-that-works-with-ten-customers">A routine that works with ten customers<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#a-routine-that-works-with-ten-customers" class="hash-link" aria-label="Direct link to A routine that works with ten customers" title="Direct link to A routine that works with ten customers" translate="no">​</a></h2>
<ol>
<li class="">Pick the moment. Ask right after something good happens: the first report generated, the first invoice sent, a support issue closed. People write better when the result is fresh.</li>
<li class="">Ask by email or in person, one customer at a time. Do not use a form letter for the first ten.</li>
<li class="">Give them prompts instead of a blank page. Our three: What were you doing before? What changed after you started using the product? What would you tell someone in the same position?</li>
<li class="">Let them write in their own words. Light edits for typos are fine if they approve the final text. Do not change the meaning.</li>
<li class="">Ask for written permission to publish the quote with their name, role and company, or agree on a label like "founder of a two-person analytics tool" if they prefer to stay unnamed.</li>
<li class="">Save the evidence: the original message, the date, and the permission. If anyone asks later whether the person exists and said this, you can show it.</li>
<li class="">Publish the quote near the claim it supports, such as next to the pricing table or the feature description.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-the-ftc-rule-says-in-plain-terms">What the FTC rule says in plain terms<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#what-the-ftc-rule-says-in-plain-terms" class="hash-link" aria-label="Direct link to What the FTC rule says in plain terms" title="Direct link to What the FTC rule says in plain terms" translate="no">​</a></h2>
<p>The FTC's Trade Regulation Rule on the Use of Consumer Reviews and Testimonials took effect on 21 October 2024, according to the eCFR's timeline for Part 465. Several provisions are relevant to a founder:</p>
<ul>
<li class="">Section 465.2 makes it a violation for a business to write, create or sell a consumer review or consumer testimonial that materially misrepresents that the reviewer exists, that they used the product, or what their experience was. Disseminating one that the business knew or should have known was false is also covered.</li>
<li class="">Section 465.4 prohibits giving compensation or other incentives in exchange for reviews expressing a particular sentiment, positive or negative. The rule's definition of buying a review includes discounts, coupons, products and services.</li>
<li class="">Section 465.5 requires officers and managers to disclose their material relationship to the business when they write a review or testimonial, unless the relationship is already clear. A founder's quote on their own site is the obvious case.</li>
<li class="">Section 465.7 covers review suppression. A business may not misrepresent that the reviews it shows are most or all of the reviews when it hides them based on rating or negative sentiment.</li>
</ul>
<p>The rule also says that general requests are fine. Sections 465.2 and 465.5 exempt reviews or testimonials that resulted from generalized solicitations to purchasers to post about their experiences. So an email to every customer that says "we would value an honest review" is not the same as handing out a free year for five stars.</p>
<p>One caveat: the rule's definitions speak about consumers. Whether a given B2B quote counts is a question for a lawyer, and the safe approach is to follow the same practices anyway.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="results-claims-need-care">Results claims need care<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#results-claims-need-care" class="hash-link" aria-label="Direct link to Results claims need care" title="Direct link to Results claims need care" translate="no">​</a></h2>
<p>The Endorsement Guides in 16 CFR 255 address testimonials that describe unusual results. The text says a disclaimer such as "Results not typical" is not enough to avoid deception in the heat pump example it gives, because consumers still read the ad as representative. If a customer says "we cut churn by 60%," and most customers do not, the claim can mislead. Our practical rule: only publish a number if you can show that it is typical, or describe it as one customer's case with the context (their size, their starting point, how long it took).</p>
<p>The guides also require disclosure of material connections that the audience would not expect, such as payment or free product. Ask whether a connection exists and say so next to the quote.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="use-evidence-that-is-not-a-quote">Use evidence that is not a quote<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#use-evidence-that-is-not-a-quote" class="hash-link" aria-label="Direct link to Use evidence that is not a quote" title="Direct link to Use evidence that is not a quote" translate="no">​</a></h2>
<p>Readers can doubt a quote, so pair them with facts a reader can check: a public changelog, a status page, a case study with the customer's permission. On Dealpuffin, founders can attach proof points such as MRR or uptime read from a provider and choose whether the public sees an exact value, a band, or nothing. That is one option among several, and <a class="" href="https://dealpuffin.com/docs/publishing/go-to-market/">Dealpuffin's listing docs</a> explain how it works.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="where-to-put-them">Where to put them<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#where-to-put-them" class="hash-link" aria-label="Direct link to Where to put them" title="Direct link to Where to put them" translate="no">​</a></h2>
<p>Place two or three short quotes on the home page, one near the price, and one on the onboarding or sign-up screen. A long testimonials page is less useful at this stage than quotes next to the decision they support. If you are comparing launch channels, <a class="" href="https://dealpuffin.com/blog/general/show-hn-vs-product-hunt-for-early-saas/">Show HN vs Product Hunt</a> notes what each audience looks for in a new product.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-offer-a-discount-in-exchange-for-a-testimonial">Can I offer a discount in exchange for a testimonial?<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#can-i-offer-a-discount-in-exchange-for-a-testimonial" class="hash-link" aria-label="Direct link to Can I offer a discount in exchange for a testimonial?" title="Direct link to Can I offer a discount in exchange for a testimonial?" translate="no">​</a></h3>
<p>Be careful. Section 465.4 prohibits compensation or incentives given in exchange for reviews expressing a particular sentiment, and its definition of buying a review lists discounts and coupons. A general request to all customers, with no reward tied to a positive opinion, is treated differently under the exemptions.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-write-a-testimonial-myself-or-use-a-friends-quote">Can I write a testimonial myself or use a friend's quote?<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#can-i-write-a-testimonial-myself-or-use-a-friends-quote" class="hash-link" aria-label="Direct link to Can I write a testimonial myself or use a friend's quote?" title="Direct link to Can I write a testimonial myself or use a friend's quote?" translate="no">​</a></h3>
<p>You can write about your own product in your own voice, labeled as yours. Section 465.5 requires officers and managers to disclose their relationship when they write a consumer testimonial about the business, unless it is already clear. Inventing a customer or an experience that did not happen is what section 465.2 targets.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-i-need-written-permission-to-publish-a-customers-name">Do I need written permission to publish a customer's name?<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#do-i-need-written-permission-to-publish-a-customers-name" class="hash-link" aria-label="Direct link to Do I need written permission to publish a customer's name?" title="Direct link to Do I need written permission to publish a customer's name?" translate="no">​</a></h3>
<p>It is a good practice, and we recommend it. The FTC rule does not use the word permission in the sections above, but publishing a person's name and words without agreement can damage the relationship with the customer. Keep the message that shows they agreed.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-if-a-customer-gives-me-a-negative-review">What if a customer gives me a negative review?<a href="https://dealpuffin.com/blog/general/how-to-collect-testimonials-as-a-new-saas/#what-if-a-customer-gives-me-a-negative-review" class="hash-link" aria-label="Direct link to What if a customer gives me a negative review?" title="Direct link to What if a customer gives me a negative review?" translate="no">​</a></h3>
<p>Do not hide it only because it is negative. Section 465.7(b) is about misrepresenting that the reviews you display are most or all of the reviews when you are suppressing them for sentiment. Reply, fix the problem, and ask whether they would update their view.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="go-to-market" term="go-to-market"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
        <category label="launch" term="launch"/>
        <category label="howto" term="howto"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to run a beta program for a new SaaS, step by step]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/"/>
        <updated>2026-11-14T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Run a SaaS beta with 10 to 30 hand-picked users: set one goal, gate access with a feature flag, ask the same three questions each week, and decide when to end it.]]></summary>
        <content type="html"><![CDATA[<p>To run a beta program for a new SaaS, invite a small group of people who have the problem today, give them access behind a feature flag or an allow-list, ask the same few questions every week, and set an end condition before you start. Ten to thirty testers is plenty to find the biggest problems. The beta comes before the public launch and has its own end date.</p>
<p>This guide covers seven steps, from picking a goal to closing the beta. The facts about tools come from PostHog's and Apple's documentation and Paul Graham's essay on early users, all read on 14 November 2026. The numbers and rules of thumb are ours and are marked as such.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-a-beta-is-for">What a beta is for<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#what-a-beta-is-for" class="hash-link" aria-label="Direct link to What a beta is for" title="Direct link to What a beta is for" translate="no">​</a></h2>
<p>A beta answers one question you can state in a sentence. Examples: "Can a new user connect Stripe and see their first report without help?" or "Do people come back in the second week?" If you cannot write the question down, you will collect opinions instead of evidence.</p>
<p>Paul Graham's essay <a href="https://paulgraham.com/ds.html" target="_blank" rel="noopener noreferrer" class="">Do Things that Don't Scale</a> makes the case for recruiting early users by hand. He writes that you cannot wait for users to come to you, and he describes the "Collison installation": when someone agreed to try Stripe, the founders asked for their laptop and set it up on the spot. Graham contrasts that with founders who ask "Will you try our beta?" and then say "we'll send you a link." Only the first approach guarantees that you watch someone use the product.</p>
<p>If you have not found those first people yet, <a class="" href="https://dealpuffin.com/blog/general/how-to-get-your-first-100-users-for-a-saas/">how to get your first 100 users</a> covers where to look.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-seven-steps">The seven steps<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#the-seven-steps" class="hash-link" aria-label="Direct link to The seven steps" title="Direct link to The seven steps" translate="no">​</a></h2>
<ol>
<li class="">Write the beta question and an end condition. Our suggestion: pick a date or a number, such as "four weeks, or when 15 testers have finished onboarding, whichever comes first."</li>
<li class="">Choose who to invite. Take people who already work around the problem. Graham notes that for B2B products the best early adopters are usually other startups, because they have not made all their tool choices yet.</li>
<li class="">Gate access. Use a feature flag, an allow-list of emails, or an invite code. You want to be able to turn one person on or off without a deploy.</li>
<li class="">Onboard each tester personally. Book 20 minutes, watch them sign up, and say nothing unless they are stuck for a minute or more. Write down every place they hesitate.</li>
<li class="">Ask the same three questions weekly. Our set: What did you try to do? What got in the way? What would you miss if it disappeared?</li>
<li class="">Fix the top item between check-ins and tell the testers you did. Testers who see their feedback acted on tend to keep replying (our experience, not a measured figure).</li>
<li class="">End on your condition. Decide who graduates to paid, what you cut, and what the launch message will say.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="gate-access-with-a-feature-flag">Gate access with a feature flag<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#gate-access-with-a-feature-flag" class="hash-link" aria-label="Direct link to Gate access with a feature flag" title="Direct link to Gate access with a feature flag" translate="no">​</a></h2>
<p>For a web product, the simplest gate is a feature flag with an opt-in list. PostHog's <a href="https://posthog.com/docs/feature-flags/early-access-feature-management" target="_blank" rel="noopener noreferrer" class="">early access feature management</a> is one example. Its documentation says you can run beta programs and waitlists with it, and that each feature moves through five stages: Draft, Concept, Alpha, Beta and General availability. Users opted in at the Alpha, Beta and General availability stages have the linked flag enabled. At the Concept stage a user can register interest, but the flag stays off, which makes it a cheap way to measure demand before you build.</p>
<p>Two details from that page are worth knowing. Opting in or out is an overriding condition on the flag, so it beats any other release rule. And when you promote a feature to General availability, there is a checkbox to include users who previously opted out, so decide in advance whether you want that. The page also notes that early access management works with the JavaScript Web SDK and does not support Groups, which matters if your accounts are organizations rather than individual users.</p>
<p>You can do the same with a plain database column such as <code>beta_access</code> and a check in your auth middleware. The tool matters less than being able to switch access per person.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="if-your-beta-is-a-mobile-app">If your beta is a mobile app<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#if-your-beta-is-a-mobile-app" class="hash-link" aria-label="Direct link to If your beta is a mobile app" title="Direct link to If your beta is a mobile app" translate="no">​</a></h2>
<p>Apple's <a href="https://developer.apple.com/help/app-store-connect/test-a-beta-version/testflight-overview/" target="_blank" rel="noopener noreferrer" class="">TestFlight overview</a> gives the limits. You can invite up to 10,000 external testers and up to 100 internal testers who have App Store Connect access. The first build you add to a group for external testing goes to App Review, and later builds may not need a full review. A build can be tested for up to 90 days, after which it becomes unavailable, so your beta end condition should fit inside that window or you need to upload a fresh build.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-to-track">What to track<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#what-to-track" class="hash-link" aria-label="Direct link to What to track" title="Direct link to What to track" translate="no">​</a></h2>
<p>Keep a simple sheet with one row per tester. Our suggested columns: invite date, first session, reached the main outcome (yes or no), last session, feedback notes, willing to pay (yes, no, unsure). After two weeks, look at the yes and no counts for the main outcome. If fewer than half of your testers get there, fix onboarding before you invite anyone else. That threshold is a rule of thumb, not a standard.</p>
<p>Graham also advises that you take extraordinary measures to make early users happy, and says that the feedback from engaging directly with your earliest users will be the best you ever get.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="turn-the-beta-into-your-first-customers">Turn the beta into your first customers<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#turn-the-beta-into-your-first-customers" class="hash-link" aria-label="Direct link to Turn the beta into your first customers" title="Direct link to Turn the beta into your first customers" translate="no">​</a></h2>
<p>A beta ends with a decision for each tester. Offer the people who reached the main outcome a paid plan, and tell them what the price will be before the beta closes. The <a class="" href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/">first 10 paying customers</a> guide shows how to take payment without building billing first. Testers who will not pay can still tell you why, which is useful data.</p>
<p>When you are ready to be found by people outside your own list, a public launch comes next. <a class="" href="https://dealpuffin.com/blog/general/show-hn-vs-product-hunt-for-early-saas/">Show HN vs Product Hunt</a> compares two common places. Dealpuffin is another route if your product uses Stripe, Paddle or Polar: <a class="" href="https://dealpuffin.com/docs/publishing/go-to-market/">listing is free</a> and you choose which coupons to publish.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-many-testers-do-i-need-for-a-saas-beta">How many testers do I need for a SaaS beta?<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#how-many-testers-do-i-need-for-a-saas-beta" class="hash-link" aria-label="Direct link to How many testers do I need for a SaaS beta?" title="Direct link to How many testers do I need for a SaaS beta?" translate="no">​</a></h3>
<p>There is no fixed number. Ten to thirty hand-picked testers is a practical range for a one-person team, because you can onboard each of them personally. Our reasoning is that you can only learn from people you can watch or talk to.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-a-beta-be-free">Should a beta be free?<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#should-a-beta-be-free" class="hash-link" aria-label="Direct link to Should a beta be free?" title="Direct link to Should a beta be free?" translate="no">​</a></h3>
<p>It can be, but say so and say when it ends. Some founders charge from day one to test willingness to pay. Either way, tell testers the future price before the beta closes.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="open-beta-or-closed-beta">Open beta or closed beta?<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#open-beta-or-closed-beta" class="hash-link" aria-label="Direct link to Open beta or closed beta?" title="Direct link to Open beta or closed beta?" translate="no">​</a></h3>
<p>A closed beta suits a first beta, since you control who is in and can talk to everyone. An open beta, where anyone can opt in, fits later stages when you want volume. PostHog's early access feature lets users opt in themselves, which is the open version.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-long-should-a-beta-last">How long should a beta last?<a href="https://dealpuffin.com/blog/general/how-to-run-a-beta-program-for-a-new-saas/#how-long-should-a-beta-last" class="hash-link" aria-label="Direct link to How long should a beta last?" title="Direct link to How long should a beta last?" translate="no">​</a></h3>
<p>Pick a length before you start. Four to eight weeks is our suggestion for a first beta, and on iOS a TestFlight build is available for at most 90 days.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="go-to-market" term="go-to-market"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
        <category label="launch" term="launch"/>
        <category label="howto" term="howto"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to set up a changelog for a SaaS in an afternoon]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/"/>
        <updated>2026-11-14T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Set up a public SaaS changelog using the Keep a Changelog format, GitHub Releases or a plain page. Covers what to write, how often, dates, and how to flag breaking changes.]]></summary>
        <content type="html"><![CDATA[<p>To set up a changelog for a SaaS, create one public page where each release is a dated entry, newest first, with changes grouped under headings such as Added, Changed, Fixed and Removed. Write it for customers instead of copying commit messages, and flag anything that breaks existing behavior. You can host it as a markdown file, a page on your site, or GitHub Releases.</p>
<p>This guide follows the <a href="https://keepachangelog.com/en/1.1.0/" target="_blank" rel="noopener noreferrer" class="">Keep a Changelog</a> convention and GitHub's release documentation, both read on 14 November 2026. Where a step is our own suggestion, it says so.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-a-changelog-is-for">What a changelog is for<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#what-a-changelog-is-for" class="hash-link" aria-label="Direct link to What a changelog is for" title="Direct link to What a changelog is for" translate="no">​</a></h2>
<p>The Keep a Changelog project defines a changelog as a curated, chronologically ordered list of notable changes for each version of a project. Its stated reason is to make it easier for users to see what changed between releases. For a SaaS the same logic applies, with one difference: your customers do not choose a version, so they find out about changes only when you tell them.</p>
<p>A changelog helps three groups. Existing customers learn what is new and what to retest. Prospects see whether the product is alive. Support gets a link to paste when someone asks "did you fix that?" If you run a public API, it also gives integrators a place to learn about deprecations before they break.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="pick-a-home">Pick a home<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#pick-a-home" class="hash-link" aria-label="Direct link to Pick a home" title="Direct link to Pick a home" translate="no">​</a></h2>
<p>You have three realistic options for a small team.</p>
<table><thead><tr><th>Option</th><th>Good for</th><th>Trade-off</th></tr></thead><tbody><tr><td><code>CHANGELOG.md</code> in the repo, rendered on your site</td><td>Open-source or developer tools</td><td>Needs a build step to appear on your site</td></tr><tr><td>A <code>/changelog</code> page on your own site</td><td>Most SaaS products</td><td>You maintain it by hand</td></tr><tr><td>GitHub Releases</td><td>Products with a public repo</td><td>Visible only on GitHub</td></tr></tbody></table>
<p>Keep a Changelog notes that GitHub Releases create a non-portable changelog that can only be displayed within GitHub, and that the releases page is arguably not very discoverable by end users compared with a conventional file such as <code>CHANGELOG.md</code>. If your customers are not on GitHub, a page on your own domain is the better home. If you build the site with Docusaurus, a post per release is a natural fit, and <a class="" href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/">adding FAQ schema to a Docusaurus blog</a> shows how that kind of setup works.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-format">The format<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#the-format" class="hash-link" aria-label="Direct link to The format" title="Direct link to The format" translate="no">​</a></h2>
<p>Keep a Changelog lists these guiding principles: changelogs are for humans, there is an entry for every version, the same types of changes are grouped, versions and sections are linkable, the latest version comes first, the release date is displayed, and you say whether you follow Semantic Versioning. Its suggested change types are:</p>
<ul>
<li class="">Added for new features</li>
<li class="">Changed for changes in existing functionality</li>
<li class="">Deprecated for soon-to-be removed features</li>
<li class="">Removed for features that are now gone</li>
<li class="">Fixed for bug fixes</li>
<li class="">Security for vulnerabilities</li>
</ul>
<p>For dates it recommends the ISO format, such as <code>2026-11-14</code>, because regional formats overlap in ambiguous ways. A small example entry:</p>
<div class="language-markdown codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-markdown codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token title important punctuation" style="color:rgb(248, 248, 242)">##</span><span class="token title important"> 2026-11-14</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token title important punctuation" style="color:rgb(248, 248, 242)">###</span><span class="token title important"> Added</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token list punctuation" style="color:rgb(248, 248, 242)">-</span><span class="token plain"> CSV export on the Invoices page.</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token title important punctuation" style="color:rgb(248, 248, 242)">###</span><span class="token title important"> Changed</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token list punctuation" style="color:rgb(248, 248, 242)">-</span><span class="token plain"> Webhook retries now stop after 24 hours instead of 72.</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token title important punctuation" style="color:rgb(248, 248, 242)">###</span><span class="token title important"> Deprecated</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token list punctuation" style="color:rgb(248, 248, 242)">-</span><span class="token plain"> The </span><span class="token code-snippet code keyword" style="color:rgb(189, 147, 249);font-style:italic">`/v1/customers`</span><span class="token plain"> endpoint. It will be removed on 2027-03-01. Use </span><span class="token code-snippet code keyword" style="color:rgb(189, 147, 249);font-style:italic">`/v2/customers`</span><span class="token plain">.</span><br></div></code></pre></div></div>
<p>SaaS products rarely have version numbers customers care about, so date-based entries work well. That is our suggestion, and Keep a Changelog mentions that you should say whether you follow Semantic Versioning, so state your choice at the top of the page.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="seven-steps-to-set-it-up">Seven steps to set it up<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#seven-steps-to-set-it-up" class="hash-link" aria-label="Direct link to Seven steps to set it up" title="Direct link to Seven steps to set it up" translate="no">​</a></h2>
<ol>
<li class="">Create the page or file today, with a one-paragraph intro that says how often you update it and how to subscribe.</li>
<li class="">Add an <code>Unreleased</code> section at the top. Keep a Changelog suggests it so people can see what to expect and so that at release time you can move its contents into a dated section.</li>
<li class="">Backfill only the changes customers noticed in the last few months. A short honest history beats a long invented one.</li>
<li class="">Add a line to your release checklist: "write the changelog entry before merging." Ten minutes at release time is cheaper than reconstructing a month later.</li>
<li class="">Write each line from the customer's point of view. "Fixed double charge when a card is retried" is useful. "Refactor billing service" is not.</li>
<li class="">Link out to docs or a longer post for anything that needs explanation.</li>
<li class="">Offer a way to follow along: an RSS or Atom feed, an email, or a link in your product. Pick one.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="do-not-paste-your-commit-log">Do not paste your commit log<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#do-not-paste-your-commit-log" class="hash-link" aria-label="Direct link to Do not paste your commit log" title="Direct link to Do not paste your commit log" translate="no">​</a></h2>
<p>Keep a Changelog is blunt about this: using commit log diffs as changelogs is a bad idea because they are full of noise, such as merge commits and obscure titles. A commit documents a step in the code. A changelog entry documents a noteworthy difference, often across multiple commits.</p>
<p>It lists other failure modes too. Ignoring deprecations is one: when something will break, it should be painfully clear, and at minimum you should list deprecations, removals and breaking changes. Inconsistency is another. A changelog that mentions only some changes can be as dangerous as none, because readers assume it is the single source of truth.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="using-github-releases">Using GitHub Releases<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#using-github-releases" class="hash-link" aria-label="Direct link to Using GitHub Releases" title="Direct link to Using GitHub Releases" translate="no">​</a></h2>
<p>If your product has a public repository, GitHub's documentation on <a href="https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository" target="_blank" rel="noopener noreferrer" class="">managing releases</a> describes the flow. You choose or create a tag, write a title and description, and can click Generate release notes to produce notes automatically. A release can be marked as a pre-release, which signals that it is not ready for production. The <code>gh release create</code> command does the same from the terminal. Generated notes are a starting point, so edit them into customer language before you publish.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="keeping-it-up-to-date">Keeping it up to date<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#keeping-it-up-to-date" class="hash-link" aria-label="Direct link to Keeping it up to date" title="Direct link to Keeping it up to date" translate="no">​</a></h2>
<p>A changelog that goes quiet for three months looks like an abandoned product. Our habit suggestion: put a standing five-minute task on your Friday list to add entries for anything that shipped. If your product exposes an API, <a class="" href="https://dealpuffin.com/blog/general/mcp-server-vs-rest-api-for-a-saas/">MCP server vs REST API for a SaaS</a> covers interface choices where deprecation notices matter most.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-a-saas-changelog-use-version-numbers">Should a SaaS changelog use version numbers?<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#should-a-saas-changelog-use-version-numbers" class="hash-link" aria-label="Direct link to Should a SaaS changelog use version numbers?" title="Direct link to Should a SaaS changelog use version numbers?" translate="no">​</a></h3>
<p>Not necessarily. Customers on a hosted product do not pick versions, so dates often work better. If you publish an API or an SDK, version numbers help integrators, and Keep a Changelog recommends stating whether you follow Semantic Versioning.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-often-should-i-update-a-changelog">How often should I update a changelog?<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#how-often-should-i-update-a-changelog" class="hash-link" aria-label="Direct link to How often should I update a changelog?" title="Direct link to How often should I update a changelog?" translate="no">​</a></h3>
<p>Update it whenever you ship something a customer could notice. For most small teams that means weekly or at each release. The key is consistency, since an incomplete changelog can mislead readers.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-belongs-in-a-changelog-and-what-does-not">What belongs in a changelog and what does not?<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#what-belongs-in-a-changelog-and-what-does-not" class="hash-link" aria-label="Direct link to What belongs in a changelog and what does not?" title="Direct link to What belongs in a changelog and what does not?" translate="no">​</a></h3>
<p>Include new features, behavior changes, deprecations, removals, bug fixes customers could see, and security fixes. Leave out internal refactors and dependency bumps unless they affect users.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="is-github-releases-enough-as-a-changelog">Is GitHub Releases enough as a changelog?<a href="https://dealpuffin.com/blog/general/how-to-set-up-a-changelog-for-a-saas/#is-github-releases-enough-as-a-changelog" class="hash-link" aria-label="Direct link to Is GitHub Releases enough as a changelog?" title="Direct link to Is GitHub Releases enough as a changelog?" translate="no">​</a></h3>
<p>It can be, if your customers use GitHub. For a typical SaaS with non-developer customers, a page on your own domain is easier to find and does not depend on a third-party site.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="devtools" term="devtools"/>
        <category label="saas" term="saas"/>
        <category label="howto" term="howto"/>
        <category label="early-founders" term="early-founders"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Best transactional email services for a new SaaS in 2026]]></title>
        <id>https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/</id>
        <link href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/"/>
        <updated>2026-11-13T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Compare Resend, Postmark, Amazon SES and Mailgun on free tiers, entry prices and overage rates, with a cost check at 30,000 emails a month and a pick for each stage.]]></summary>
        <content type="html"><![CDATA[<p>For a new SaaS, Resend has the largest free tier of the four services below (3,000 emails a month, capped at 100 a day), Postmark is the most focused on transactional delivery, Amazon SES is the cheapest per email, and Mailgun offers a free plan of 100 emails a day. Pick by volume, how much setup you will accept, and whether you need a plan under 10,000 emails.</p>
<p>Prices below were read from each vendor's pricing page on 13 November 2026. They change, so confirm before you commit.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-counts-as-transactional-email">What counts as transactional email<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#what-counts-as-transactional-email" class="hash-link" aria-label="Direct link to What counts as transactional email" title="Direct link to What counts as transactional email" translate="no">​</a></h2>
<p>Transactional email is the mail your app sends because a user did something: password resets, sign-in links, receipts, failed-payment notices and invites. It is different from newsletters, and some providers ask you to keep the two apart. Postmark, for example, says transactional and marketing email should never mix, and offers separate message streams for that reason.</p>
<p>Volume at a new SaaS is small. A few hundred users generate a few thousand emails a month. That means the free tier and the first paid step matter more than the price at a million emails.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-comparison">The comparison<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#the-comparison" class="hash-link" aria-label="Direct link to The comparison" title="Direct link to The comparison" translate="no">​</a></h2>
<table><thead><tr><th>Service</th><th>Free tier</th><th>First paid plan</th><th>Overage</th></tr></thead><tbody><tr><td><a href="https://resend.com/pricing" target="_blank" rel="noopener noreferrer" class="">Resend</a></td><td>3,000/month, max 100/day</td><td>Pro, $20/mo for 50,000</td><td>$0.90 per 1,000</td></tr><tr><td><a href="https://postmarkapp.com/pricing" target="_blank" rel="noopener noreferrer" class="">Postmark</a></td><td>100/month</td><td>Basic, $15/mo for 10,000</td><td>$1.80 per 1,000</td></tr><tr><td><a href="https://aws.amazon.com/ses/pricing/" target="_blank" rel="noopener noreferrer" class="">Amazon SES</a></td><td>AWS Free Tier credits, see below</td><td>Essentials, pay as you go</td><td>$0.16 per 1,000</td></tr><tr><td><a href="https://www.mailgun.com/pricing/" target="_blank" rel="noopener noreferrer" class="">Mailgun</a></td><td>100/day</td><td>Basic, $15/mo for 10,000</td><td>from $1.80 per 1,000</td></tr></tbody></table>
<p>Notes on each row:</p>
<ul>
<li class=""><strong>Resend.</strong> The free plan includes 3 domains and 30-day data retention. The paid Pro plan removes the daily limit. Resend says there is no plan between Free and Pro, but pay-as-you-go lets a paid plan keep sending past its quota at the overage rate. It has a REST API, SMTP relay and official SDKs.</li>
<li class=""><strong>Postmark.</strong> Everyone starts on a free developer plan with 100 emails a month that does not expire. There is no tier between 100 and 10,000 a month. Dedicated IPs start at $50 a month and are available to customers sending 300,000 emails a month or more.</li>
<li class=""><strong>Amazon SES.</strong> Pricing is pay as you go. The Essentials rate is $0.16 per 1,000 emails for the first 10 million a month, plus $0.12 per GB of attachment data. New AWS customers get up to $200 in Free Tier credits that must be used within 12 months. SES gives you the lowest unit price. We did not compare its dashboard or setup effort in depth, so treat that as your own time cost to estimate.</li>
<li class=""><strong>Mailgun.</strong> The free plan is 100 emails a day with 1 custom sending domain and 1 day of log retention. Basic is $15 a month for 10,000 emails. Foundation is $35 a month for 50,000, listed as free for the first month.</li>
</ul>
<p>We could not read SendGrid's pricing today, since its page did not return plan details, so we left it out rather than guess.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-cost-check-at-30000-emails-a-month">A cost check at 30,000 emails a month<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#a-cost-check-at-30000-emails-a-month" class="hash-link" aria-label="Direct link to A cost check at 30,000 emails a month" title="Direct link to A cost check at 30,000 emails a month" translate="no">​</a></h2>
<p>A concrete number helps. Suppose you send 30,000 emails a month and use only the listed prices, with no add-ons.</p>
<table><thead><tr><th>Service</th><th>Plan</th><th>Monthly cost</th></tr></thead><tbody><tr><td>Resend</td><td>Pro (50,000 included)</td><td>$20</td></tr><tr><td>Postmark</td><td>Basic, 10,000 included + 20,000 extra at $1.80 per 1,000</td><td>$15 + $36 = $51</td></tr><tr><td>Amazon SES</td><td>30,000 × $0.16 per 1,000</td><td>$4.80, plus attachment data</td></tr><tr><td>Mailgun</td><td>Basic, 10,000 included + 20,000 extra at $1.80 per 1,000</td><td>$15 + $36 = $51</td></tr></tbody></table>
<p>Two cautions. First, Postmark and Mailgun both list higher plans that bundle more emails at lower overage rates, and moving up a tier would likely beat these figures; the table shows the entry plan only. Second, SES is cheapest on paper, but you pay with your own time: you set up your sending, handle bounces and complaints, and monitor your reputation. For a solo founder, $15 or $20 a month may be a good trade.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="which-to-pick">Which to pick<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#which-to-pick" class="hash-link" aria-label="Direct link to Which to pick" title="Direct link to Which to pick" translate="no">​</a></h2>
<ul>
<li class=""><strong>You want to start today and your volume is under 3,000 a month:</strong> Resend's free plan covers it, as long as you stay under 100 a day.</li>
<li class=""><strong>Delivery of a few critical emails matters most (sign-in links, receipts):</strong> Postmark is built around that job, and the free developer plan lets you test your integration. Plan on $15 a month once you go live.</li>
<li class=""><strong>You send a lot and have someone comfortable with AWS:</strong> SES gives the lowest price per email.</li>
<li class=""><strong>You expect inbound routing, templates or validation add-ons:</strong> Mailgun lists inbound routes and a template builder on its plans. Check which tier includes what you need.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="setup-that-matters-more-than-the-vendor">Setup that matters more than the vendor<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#setup-that-matters-more-than-the-vendor" class="hash-link" aria-label="Direct link to Setup that matters more than the vendor" title="Direct link to Setup that matters more than the vendor" translate="no">​</a></h2>
<p>Whichever you choose, do these before launch:</p>
<ol>
<li class="">Verify your sending domain and set up SPF, DKIM and DMARC. Every vendor above supports this.</li>
<li class="">Send transactional mail from a subdomain such as <code>mail.yourapp.com</code>, so a problem with email sent in volume does not touch your main domain.</li>
<li class="">Use a separate service or subdomain for cold outreach. Our guide to <a class="" href="https://dealpuffin.com/blog/general/how-to-warm-up-a-new-domain-for-cold-email/">warming up a new domain for cold email</a> explains why.</li>
<li class="">Handle bounces and complaints by removing those addresses from your sending list.</li>
<li class="">Send yourself a test of every template, including the failed-payment email. If you use Stripe webhooks to trigger email, <a class="" href="https://dealpuffin.com/blog/general/how-to-test-stripe-webhooks-locally/">test them locally first</a>.</li>
<li class="">Watch for failures. A free monitor is enough to start; see <a class="" href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/">free uptime monitoring tools for indie SaaS</a>.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-is-the-best-free-transactional-email-service">What is the best free transactional email service?<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#what-is-the-best-free-transactional-email-service" class="hash-link" aria-label="Direct link to What is the best free transactional email service?" title="Direct link to What is the best free transactional email service?" translate="no">​</a></h3>
<p>By free allowance, Resend's free plan is the largest in this comparison at 3,000 emails a month with a 100-a-day cap. Mailgun's free plan allows 100 a day, and Postmark's allows 100 a month.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-use-gmail-or-my-own-smtp-server-instead">Can I use Gmail or my own SMTP server instead?<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#can-i-use-gmail-or-my-own-smtp-server-instead" class="hash-link" aria-label="Direct link to Can I use Gmail or my own SMTP server instead?" title="Direct link to Can I use Gmail or my own SMTP server instead?" translate="no">​</a></h3>
<p>You can for a prototype, but you would own bounce handling, reputation and delivery tracking yourself. The services above handle that for $0 to $20 a month at early volumes.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="is-amazon-ses-worth-it-for-a-small-saas">Is Amazon SES worth it for a small SaaS?<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#is-amazon-ses-worth-it-for-a-small-saas" class="hash-link" aria-label="Direct link to Is Amazon SES worth it for a small SaaS?" title="Direct link to Is Amazon SES worth it for a small SaaS?" translate="no">​</a></h3>
<p>If you have the time to set it up, it is cheap: $0.16 per 1,000 emails on the Essentials rate. If you do not, a $15 to $20 plan with a simpler dashboard is a reasonable trade.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-i-need-a-dedicated-ip">Do I need a dedicated IP?<a href="https://dealpuffin.com/blog/general/best-transactional-email-services-for-a-new-saas/#do-i-need-a-dedicated-ip" class="hash-link" aria-label="Direct link to Do I need a dedicated IP?" title="Direct link to Do I need a dedicated IP?" translate="no">​</a></h3>
<p>Not at early-stage volume. Postmark, for example, offers dedicated IPs only to customers sending 300,000 emails a month or more. Shared IPs from a reputable provider are the normal choice until then.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="devtools" term="devtools"/>
        <category label="saas" term="saas"/>
        <category label="comparison" term="comparison"/>
        <category label="early-founders" term="early-founders"/>
        <category label="listicle" term="listicle"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to cap AI API costs in a SaaS before the bill surprises you]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/"/>
        <updated>2026-11-13T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Five layers that keep LLM API spend predictable: provider spend limits, per-feature output caps, prompt caching, batching, and per-customer usage limits.]]></summary>
        <content type="html"><![CDATA[<p>To cap AI API costs in a SaaS, set a hard spend limit at the provider, cap output tokens on every request, cache the repeated part of your prompts, move non-urgent work to batch jobs, and enforce a usage limit per customer in your own code. The provider limit stops a disaster, and the per-customer limit stops one user from eating your margin.</p>
<p>This guide walks through those five layers in order, using the OpenAI and Anthropic documentation read on 13 November 2026. Model names and prices change often, so check your provider's pricing page before you set numbers.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="layer-1-a-hard-limit-at-the-provider">Layer 1: a hard limit at the provider<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#layer-1-a-hard-limit-at-the-provider" class="hash-link" aria-label="Direct link to Layer 1: a hard limit at the provider" title="Direct link to Layer 1: a hard limit at the provider" translate="no">​</a></h2>
<p>Start with the control that works even if your code has a bug. OpenAI's rate limits guide separates two things you can set at the organization or project level. A spend alert sends a notification and API traffic continues. A hard spend limit makes affected API requests return a <code>429</code> error. OpenAI describes the hard limit as the way to enforce a monthly organization or project cap, and it is separate from the approved monthly usage limit OpenAI sets for each organization.</p>
<p>Anthropic takes a similar approach with tiers. Each usage tier has a monthly spend limit, and once you reach it you wait for the next month or qualify for the next tier. Anthropic also lets you set lower limits for individual Workspaces, which is useful if you want production and experiments on separate budgets.</p>
<p>Practical setup:</p>
<ol>
<li class="">Create one project or workspace per environment, so a test script cannot spend the production budget.</li>
<li class="">Set a hard limit slightly above your expected monthly spend.</li>
<li class="">Set an alert at roughly half of that, so you hear about growth before you hit the wall.</li>
<li class="">Make your app handle a <code>429</code> gracefully, with a clear message and no retry loop.</li>
</ol>
<p>Sources: <a href="https://platform.openai.com/docs/guides/rate-limits" target="_blank" rel="noopener noreferrer" class="">OpenAI rate limits</a> and <a href="https://docs.anthropic.com/en/api/rate-limits" target="_blank" rel="noopener noreferrer" class="">Anthropic rate limits</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="layer-2-cap-output-on-every-request">Layer 2: cap output on every request<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#layer-2-cap-output-on-every-request" class="hash-link" aria-label="Direct link to Layer 2: cap output on every request" title="Direct link to Layer 2: cap output on every request" translate="no">​</a></h2>
<p>Output tokens usually cost more than input tokens, and a model that rambles is the cheapest thing to fix. Set a maximum output length on each call, chosen per feature. A classifier needs 20 tokens. A summary needs a few hundred.</p>
<p>There is one subtlety worth knowing. OpenAI notes that your rate limit is calculated as the maximum of your <code>max_tokens</code> setting and an estimate based on the request, so setting it close to the real response size also avoids wasting rate-limit headroom. Anthropic says its <code>max_tokens</code> parameter does not factor into its output-token-per-minute limits, so the rate-limit reason does not apply there, but the cost reason still does.</p>
<p>Also cap the input. Truncate or summarize long histories before sending them, and put a maximum on user-supplied text. An unbounded paste box is an unbounded bill.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="layer-3-cache-the-repeated-prefix">Layer 3: cache the repeated prefix<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#layer-3-cache-the-repeated-prefix" class="hash-link" aria-label="Direct link to Layer 3: cache the repeated prefix" title="Direct link to Layer 3: cache the repeated prefix" translate="no">​</a></h2>
<p>Many SaaS prompts start with the same system instructions, tool definitions or reference text. Both providers discount cached input.</p>
<ul>
<li class="">Anthropic's prompt caching documentation lists cache hits and refreshes at a fraction of the base input price. Its rate limits page says that for most models cached input tokens do not count toward your input-token rate limit and are billed at 10% of the base input price, with some models priced lower still. Cache writes cost more than base input, so caching pays off when the same prefix is reused.</li>
<li class="">OpenAI says cached input tokens are discounted up to 95%, and that the minimum cacheable prompt length is 1,024 tokens for its newest model family. It also notes that cached tokens still count toward tokens-per-minute limits.</li>
</ul>
<p>The design rule is simple: put the stable content first and the changing content (the user's message) last. A prefix only matches if it is identical, so a timestamp at the top of your system prompt will break the cache on every call.</p>
<p>Sources: <a href="https://docs.anthropic.com/en/docs/build-with-claude/prompt-caching" target="_blank" rel="noopener noreferrer" class="">Anthropic prompt caching</a> and <a href="https://platform.openai.com/docs/guides/prompt-caching" target="_blank" rel="noopener noreferrer" class="">OpenAI prompt caching</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="layer-4-batch-what-does-not-need-to-be-instant">Layer 4: batch what does not need to be instant<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#layer-4-batch-what-does-not-need-to-be-instant" class="hash-link" aria-label="Direct link to Layer 4: batch what does not need to be instant" title="Direct link to Layer 4: batch what does not need to be instant" translate="no">​</a></h2>
<p>Nightly summaries, bulk tagging and report generation do not need an immediate answer. OpenAI's rate limits guide points to its Batch API for submitting large collections of requests without affecting your synchronous rate limits, and Anthropic documents a Message Batches API with its own queue limits. Check the current batch discount on each provider's pricing page; we did not verify a figure today, so we leave it out here.</p>
<p>A simple split: anything a user is waiting on goes through the normal API, and anything else goes into a queue.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="layer-5-limit-each-customer-yourself">Layer 5: limit each customer yourself<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#layer-5-limit-each-customer-yourself" class="hash-link" aria-label="Direct link to Layer 5: limit each customer yourself" title="Direct link to Layer 5: limit each customer yourself" translate="no">​</a></h2>
<p>Provider limits protect you from the provider's bill. They do not protect one customer's usage from another's, or your margin from your heaviest user. For that you need a counter in your own database.</p>
<ol>
<li class="">Record the tokens (or the cost) of each call against the customer ID. Both providers return token usage in the response.</li>
<li class="">Define a monthly allowance per plan, in the unit your pricing uses.</li>
<li class="">Check the counter before each call. If the customer is over, either block the request, downgrade to a cheaper model, or offer an upgrade.</li>
<li class="">Show the customer their usage so a block is not a surprise.</li>
</ol>
<p>How you set the allowance is a pricing question. <a class="" href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/">Usage-based vs seat-based pricing for AI products</a> compares the models, and <a class="" href="https://dealpuffin.com/blog/general/usage-based-billing-after-metronome-and-orb/">usage-based billing after Metronome and Orb</a> covers the tooling landscape if you want billing to meter usage for you.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-worked-example">A worked example<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#a-worked-example" class="hash-link" aria-label="Direct link to A worked example" title="Direct link to A worked example" translate="no">​</a></h2>
<p>Say your app summarizes support tickets. Each call sends a 3,000-token system prompt, a 500-token ticket and expects about 150 tokens back.</p>
<ul>
<li class="">Output cap: set it to 300, not the model's maximum.</li>
<li class="">Caching: the 3,000-token prompt is identical on every call, so it is the part to cache and it sits at the top.</li>
<li class="">Batching: summaries for old tickets run in a nightly batch.</li>
<li class="">Per-customer: the free plan gets 200 summaries a month; the paid plan gets 5,000.</li>
</ul>
<p>None of this depends on one provider's price, so it holds if you change models.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-note-on-credits-and-promos">A note on credits and promos<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#a-note-on-credits-and-promos" class="hash-link" aria-label="Direct link to A note on credits and promos" title="Direct link to A note on credits and promos" translate="no">​</a></h2>
<p>Provider credits can fund experiments. Our post on <a class="" href="https://dealpuffin.com/blog/general/chatgpt-pro-api-credits-for-builders/">ChatGPT Pro API credits for builders</a> covers one such offer. Plan unit economics on list prices, not on a promo.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-is-the-fastest-way-to-stop-an-ai-bill-from-running-away">What is the fastest way to stop an AI bill from running away?<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#what-is-the-fastest-way-to-stop-an-ai-bill-from-running-away" class="hash-link" aria-label="Direct link to What is the fastest way to stop an AI bill from running away?" title="Direct link to What is the fastest way to stop an AI bill from running away?" translate="no">​</a></h3>
<p>Set a hard spend limit on the provider project and cap output tokens per request. OpenAI says a hard limit makes affected requests return a <code>429</code> error, so it works even if your own code has a bug.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="does-prompt-caching-reduce-cost-or-just-latency">Does prompt caching reduce cost or just latency?<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#does-prompt-caching-reduce-cost-or-just-latency" class="hash-link" aria-label="Direct link to Does prompt caching reduce cost or just latency?" title="Direct link to Does prompt caching reduce cost or just latency?" translate="no">​</a></h3>
<p>Both. Anthropic bills cache reads at a reduced rate, 10% of base input price for most models, and OpenAI discounts cached input up to 95%. The cache only helps when the start of the prompt is identical between calls.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-i-use-a-cheaper-model-to-save-money">Should I use a cheaper model to save money?<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#should-i-use-a-cheaper-model-to-save-money" class="hash-link" aria-label="Direct link to Should I use a cheaper model to save money?" title="Direct link to Should I use a cheaper model to save money?" translate="no">​</a></h3>
<p>Often, for simple tasks such as classification or extraction. Test the cheaper model on your own examples first, and keep the stronger model for the requests where quality drops.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-do-i-stop-one-customer-from-using-too-much">How do I stop one customer from using too much?<a href="https://dealpuffin.com/blog/general/how-to-cap-ai-api-costs-in-a-saas/#how-do-i-stop-one-customer-from-using-too-much" class="hash-link" aria-label="Direct link to How do I stop one customer from using too much?" title="Direct link to How do I stop one customer from using too much?" translate="no">​</a></h3>
<p>Track usage per customer ID in your own database and check it before each call. Provider-level limits apply to your whole account, so they cannot enforce a per-customer cap.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="ai" term="ai"/>
        <category label="devtools" term="devtools"/>
        <category label="saas" term="saas"/>
        <category label="pricing" term="pricing"/>
        <category label="howto" term="howto"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to handle failed payments in a SaaS (Stripe setup)]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/"/>
        <updated>2026-11-13T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Turn on retries, send the right emails, and decide when to cut access so a failed card does not become lost revenue. A setup guide for Stripe Billing.]]></summary>
        <content type="html"><![CDATA[<p>To handle failed payments in a SaaS, let your billing provider retry the charge on a schedule, email the customer a link to update their card, and decide in advance when access ends if the invoice stays unpaid. With Stripe Billing, the first two are dashboard settings and the third is one dropdown plus a webhook handler in your app.</p>
<p>This guide covers that setup for Stripe, based on Stripe's documentation read on 13 November 2026. The same three decisions apply to Paddle, Polar and others, though the settings are named differently.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="why-failed-payments-deserve-an-afternoon">Why failed payments deserve an afternoon<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#why-failed-payments-deserve-an-afternoon" class="hash-link" aria-label="Direct link to Why failed payments deserve an afternoon" title="Direct link to Why failed payments deserve an afternoon" translate="no">​</a></h2>
<p>A failed renewal is not a cancellation. The customer usually still wants the product: the card expired, the bank declined a charge it did not recognize, or the balance was short that day. If nothing happens next, the subscription ends anyway, and you lose a customer who never decided to leave. Early on, when you have 30 customers, losing three this way is a visible dent.</p>
<p>You do not need a recovery vendor for this. The defaults in Stripe cover most of it, as long as you check that they are on and wire up your own access rules.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-setup-step-by-step">The setup, step by step<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#the-setup-step-by-step" class="hash-link" aria-label="Direct link to The setup, step by step" title="Direct link to The setup, step by step" translate="no">​</a></h2>
<ol>
<li class=""><strong>Confirm Smart Retries are on.</strong> Stripe says it enables Smart Retries by default for new accounts. You find the setting under Billing, then Revenue recovery, then Retries. The default configuration is up to 8 retries within 2 weeks.</li>
<li class=""><strong>Choose the retry window.</strong> You can set the policy to 1 week, 2 weeks, 3 weeks, 1 month or 2 months. A longer window gives a customer more time to fix a card, and it also means more days of unpaid service if you keep access on. Pick the window first, then decide what access looks like during it.</li>
<li class=""><strong>Turn on the failed-payment email.</strong> In the revenue recovery email settings, enable "Send emails when card payments fail". Stripe then emails the customer after each failed payment with a link to update their payment method.</li>
<li class=""><strong>Turn on expiring-card emails.</strong> Stripe sends an email one month before the default card on file expires. This catches the most predictable cause of failure before it happens.</li>
<li class=""><strong>Choose what happens after the last retry.</strong> The options are to cancel the subscription, mark it unpaid, leave it past due, or pause it if it is eligible. Each is explained below.</li>
<li class=""><strong>Listen for <code>invoice.payment_failed</code>.</strong> Stripe sends this webhook for each failed attempt. Use it to flag the account in your own database and show an in-app banner.</li>
<li class=""><strong>Test the flow</strong> before real customers hit it. Stripe lets you test failed payment notifications in the dashboard, and our guide to <a class="" href="https://dealpuffin.com/blog/general/how-to-test-stripe-webhooks-locally/">testing Stripe webhooks locally</a> covers the webhook side.</li>
</ol>
<p>Sources: <a href="https://docs.stripe.com/billing/revenue-recovery/smart-retries" target="_blank" rel="noopener noreferrer" class="">Stripe: Automate payment retries</a> and <a href="https://docs.stripe.com/billing/revenue-recovery/customer-emails" target="_blank" rel="noopener noreferrer" class="">Stripe: Automate customer emails</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-each-end-state-means">What each end state means<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#what-each-end-state-means" class="hash-link" aria-label="Direct link to What each end state means" title="Direct link to What each end state means" translate="no">​</a></h2>
<p>When retries are used up, Stripe moves the subscription according to your settings. According to Stripe's <a href="https://docs.stripe.com/billing/subscriptions/overview" target="_blank" rel="noopener noreferrer" class="">subscription lifecycle documentation</a>, the states behave like this:</p>
<table><thead><tr><th>Setting</th><th>Subscription status</th><th>Invoices</th><th>Best for</th></tr></thead><tbody><tr><td>Cancel</td><td><code>canceled</code>, a terminal state</td><td>Collection disabled</td><td>Simple products where a new signup is fine</td></tr><tr><td>Mark unpaid</td><td><code>unpaid</code></td><td>Keep generating as drafts, no payment attempts</td><td>Keeping the record so the customer can come back and settle</td></tr><tr><td>Leave past due</td><td><code>past_due</code></td><td>Keep generating and charging per retry settings</td><td>Products where you want to keep trying and decide access yourself</td></tr><tr><td>Pause</td><td><code>paused</code>, if eligible</td><td>No new invoices until resumed</td><td>Customers you expect to return</td></tr></tbody></table>
<p>Stripe's own guidance on <code>unpaid</code> is to revoke access to your product, because payment was already attempted and retried while the subscription was <code>past_due</code>. During <code>past_due</code>, Stripe notes it might retry but that the status does not promise another attempt.</p>
<p>A rule we suggest: leave access on while the subscription is <code>past_due</code> and retries are running, show a banner, and cut access when it becomes <code>unpaid</code> or <code>canceled</code>. That keeps the grace period equal to your retry window, so it is a single number you chose on purpose.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="write-the-access-rule-in-one-place">Write the access rule in one place<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#write-the-access-rule-in-one-place" class="hash-link" aria-label="Direct link to Write the access rule in one place" title="Direct link to Write the access rule in one place" translate="no">​</a></h2>
<p>Your app needs one function that answers "can this account use the product right now?" Feed it the subscription status from Stripe, not your own guess. A minimal version:</p>
<div class="language-js codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-js codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">function</span><span class="token plain"> </span><span class="token function" style="color:rgb(80, 250, 123)">hasAccess</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token parameter">status</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token comment" style="color:rgb(98, 114, 164)">// trialing and active are in good standing; past_due is the grace period</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">return</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">[</span><span class="token string" style="color:rgb(255, 121, 198)">"trialing"</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">"active"</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">"past_due"</span><span class="token punctuation" style="color:rgb(248, 248, 242)">]</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">includes</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">status</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><br></div></code></pre></div></div>
<p>Keep this check on the server. Update the stored status from webhooks, since Stripe tells you to monitor status changes to detect transitions to <code>past_due</code> or <code>unpaid</code>. If you also give discounts, remember that a coupon does not change any of this; see <a class="" href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/">how to offer an annual discount in Stripe</a> for the billing side.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="write-a-failed-payment-email-that-gets-a-card-updated">Write a failed-payment email that gets a card updated<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#write-a-failed-payment-email-that-gets-a-card-updated" class="hash-link" aria-label="Direct link to Write a failed-payment email that gets a card updated" title="Direct link to Write a failed-payment email that gets a card updated" translate="no">​</a></h2>
<p>Stripe's default email works. If you send your own, keep it short and specific. State that the renewal payment failed, the amount, the date access will pause, and one button that opens the page where the card can be updated. Stripe's emails link either to a Stripe-hosted page or to your own subscription page, and you choose which. Stripe notes that the hosted link stops working once the subscription becomes <code>canceled</code>, <code>incomplete_expired</code> or <code>unpaid</code>, so do not send a stale link after that point.</p>
<p>Skip the blame and the threats. "This sometimes happens when a card expires or a bank blocks a charge" is accurate and calm.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="cases-people-forget">Cases people forget<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#cases-people-forget" class="hash-link" aria-label="Direct link to Cases people forget" title="Direct link to Cases people forget" translate="no">​</a></h2>
<ul>
<li class=""><strong>The first payment fails.</strong> For a new subscription, Stripe says Smart Retries and custom rules do not retry the initial payment while the subscription is <code>incomplete</code>. Your checkout must collect a working payment method, and the customer has 23 hours to pay before the subscription becomes <code>incomplete_expired</code>.</li>
<li class=""><strong>Bank debits.</strong> Direct debit methods retry under separate settings. For example, Stripe lists ACH Direct Debit as retryable for insufficient funds, with up to 2 retries over 40 days.</li>
<li class=""><strong>Which payment method gets retried.</strong> If you update the card, update the field where the previous payment failed. Stripe's example is a subscription with its own <code>default_payment_method</code>: if you only change the customer's default, Stripe keeps retrying the subscription's card.</li>
<li class=""><strong>Free trials without a card.</strong> If you let people start without a card, decide what happens at the trial end. Stripe can pause the subscription if there is no payment method, which beats a failed charge.</li>
</ul>
<p>If you are still choosing plans, <a class="" href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/">how to price a SaaS product at the early stage</a> is the place to start.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-weekly-check">A weekly check<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#a-weekly-check" class="hash-link" aria-label="Direct link to A weekly check" title="Direct link to A weekly check" translate="no">​</a></h2>
<p>Once a week, open the list of <code>past_due</code> subscriptions. If an account has been there for days, reach out personally with a short note. At early-stage volumes, a human message from the founder will often fix a card faster than a fourth automated retry. Write down what you find: expired cards, bank blocks, or customers who simply did not want to continue.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-long-should-i-keep-retrying-a-failed-payment">How long should I keep retrying a failed payment?<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#how-long-should-i-keep-retrying-a-failed-payment" class="hash-link" aria-label="Direct link to How long should I keep retrying a failed payment?" title="Direct link to How long should I keep retrying a failed payment?" translate="no">​</a></h3>
<p>Stripe's default for new accounts is up to 8 retries within 2 weeks, and you can set the window from 1 week to 2 months. Two weeks is a reasonable starting point; shorten or lengthen it once you see how many customers recover late.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-i-cut-access-as-soon-as-a-payment-fails">Should I cut access as soon as a payment fails?<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#should-i-cut-access-as-soon-as-a-payment-fails" class="hash-link" aria-label="Direct link to Should I cut access as soon as a payment fails?" title="Direct link to Should I cut access as soon as a payment fails?" translate="no">​</a></h3>
<p>Most founders do not. A past-due subscription is still in the retry process, and an immediate cutoff turns a fixable card problem into an angry customer. Stripe advises revoking access when the status becomes <code>unpaid</code>, so that is a safer line.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-i-need-a-separate-dunning-tool">Do I need a separate dunning tool?<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#do-i-need-a-separate-dunning-tool" class="hash-link" aria-label="Direct link to Do I need a separate dunning tool?" title="Direct link to Do I need a separate dunning tool?" translate="no">​</a></h3>
<p>Not at the start. Stripe's built-in retries and customer emails handle the basics, and Stripe says it manages retry logic, dunning and status transitions for subscriptions. Look at specialist tools once failed payments are a measurable share of your revenue.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-if-the-customer-cancels-after-a-failed-payment">What if the customer cancels after a failed payment?<a href="https://dealpuffin.com/blog/general/how-to-handle-failed-payments-in-a-saas/#what-if-the-customer-cancels-after-a-failed-payment" class="hash-link" aria-label="Direct link to What if the customer cancels after a failed payment?" title="Direct link to What if the customer cancels after a failed payment?" translate="no">​</a></h3>
<p>Treat it as a normal cancellation and ask why. If the card was the only issue, offer to restart the subscription with a working payment method.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="billing" term="billing"/>
        <category label="stripe" term="stripe"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
        <category label="howto" term="howto"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to get your first 10 paying customers for a SaaS]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/"/>
        <updated>2026-11-12T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[A step-by-step plan for landing your first 10 paying SaaS customers: charge early, sell by hand, and take payment with a no-code link before you build billing.]]></summary>
        <content type="html"><![CDATA[<p>You get your first 10 paying customers by asking specific people for money, one conversation at a time, before the product is finished. Pick a narrow group who feel the problem now, offer them a price, and take payment with the simplest tool that works. Paul Graham's advice to founders is that recruiting users manually is the most common unscalable thing they have to do, and that you cannot wait for users to come to you.</p>
<p>This guide turns that into a ten-step plan. Quotes come from Graham's essays and Stripe's documentation, read on 12 November 2026. Suggestions that are ours are marked as such.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="why-10-is-a-useful-number">Why 10 is a useful number<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#why-10-is-a-useful-number" class="hash-link" aria-label="Direct link to Why 10 is a useful number" title="Direct link to Why 10 is a useful number" translate="no">​</a></h2>
<p>Ten is small enough to reach by hand and large enough to show a pattern. With one customer you have a story. With ten you can see whether the same problem, the same words, and the same objections keep coming up. If you have not read it yet, <a class="" href="https://dealpuffin.com/blog/general/how-to-get-your-first-100-users-for-a-saas/">how to get your first 100 users</a> covers the earlier stage of finding people at all. This post is about the moment someone pays.</p>
<p>Paying matters because it is the strongest evidence that the problem is real. Graham's essay on <a href="https://paulgraham.com/startupideas.html" target="_blank" rel="noopener noreferrer" class="">startup ideas</a> says the most common mistake is solving problems no one has. It also quotes Paul Buchheit's advice for teams with a shaky idea: go sell the product as soon as possible, before wasting time building it. Founders who try often learn that nobody wants what they are building, and some come back with a real idea they found along the way.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-plan">The plan<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#the-plan" class="hash-link" aria-label="Direct link to The plan" title="Direct link to The plan" translate="no">​</a></h2>
<ol>
<li class="">Write one sentence about who the product is for and what pain it removes. If you cannot name the person, you cannot find ten of them.</li>
<li class="">List 30 people who match. Use people you know, members of communities you already take part in, and customers of the tool you were frustrated with.</li>
<li class="">Message each one individually. Mention something specific about their situation. Ask for a 15-minute call about the problem, not the product.</li>
<li class="">On the call, listen for how they work around the problem today. If they have no workaround, they may not care enough to pay.</li>
<li class="">Offer your solution with a real price. Name the amount, even if the product is a rough version.</li>
<li class="">Take payment in the simplest way you can. See the next section.</li>
<li class="">Set them up yourself. Graham describes the "Collison installation": when anyone agreed to try Stripe, the founders said "give me your laptop" and set them up on the spot.</li>
<li class="">Ask what is missing after a week, then fix the top item.</li>
<li class="">Ask each customer who else has the same problem, and contact those people.</li>
<li class="">Count customers every week, and note which message and which source each one came from.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="take-payment-without-building-billing">Take payment without building billing<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#take-payment-without-building-billing" class="hash-link" aria-label="Direct link to Take payment without building billing" title="Direct link to Take payment without building billing" translate="no">​</a></h2>
<p>You do not need a billing system to take your first payment. Stripe's <a href="https://docs.stripe.com/payment-links" target="_blank" rel="noopener noreferrer" class="">Payment Links</a> let you accept a payment or sell subscriptions without writing code, and the page says you can share a link on social media, in emails, or on your website. For subscriptions, you create a payment link for the subscription. That is enough for ten customers, and it keeps your time on the product and the conversations.</p>
<p>A few things to decide first, as our suggestion. Choose monthly or yearly billing before you send the link, since changing it later takes work. If you plan a launch offer, look at how coupons behave in the billing tool you picked. <a class="" href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/">How to price a SaaS product at the early stage</a> can help you pick the number.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-to-do-when-people-say-yes-but-do-not-pay">What to do when people say yes but do not pay<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#what-to-do-when-people-say-yes-but-do-not-pay" class="hash-link" aria-label="Direct link to What to do when people say yes but do not pay" title="Direct link to What to do when people say yes but do not pay" translate="no">​</a></h2>
<p>Some people agree on the call and then go quiet. Do not read that as a pricing signal. Ask one direct question: what would have to be true for you to pay this week? The answer usually names a missing feature, a procurement step, or a lack of urgency. Each of those calls for a different action, and you will only learn which by asking.</p>
<p>If the same blocker appears in three conversations, it is a product decision. If it appears once, it is that person's situation.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="where-else-early-customers-come-from">Where else early customers come from<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#where-else-early-customers-come-from" class="hash-link" aria-label="Direct link to Where else early customers come from" title="Direct link to Where else early customers come from" translate="no">​</a></h2>
<p>Direct outreach should be your main channel for the first ten, but a few supporting places are worth a small amount of time.</p>
<ul>
<li class="">Communities where your buyers already talk. Answer questions, then mention your product when it applies. <a class="" href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/">Indie Hackers vs Reddit for launching a product</a> compares two of them.</li>
<li class="">Directories and listings. They rarely bring paying customers on their own, but they give people a place to verify that you exist. Dealpuffin is free to list a product on and you can <a class="" href="https://dealpuffin.com/docs/publishing/go-to-market/">publish coupons from your billing provider</a>, which gives early adopters a reason to try you.</li>
<li class="">Customers themselves. Once someone pays, ask for an introduction.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-simple-tracker">A simple tracker<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#a-simple-tracker" class="hash-link" aria-label="Direct link to A simple tracker" title="Direct link to A simple tracker" translate="no">​</a></h2>
<p>A spreadsheet is enough. Use one row per person and these columns: name, source, date contacted, call held, price offered, paid, blocker, next step. At the end of each week, count how many moved from one stage to the next. If you contact 30 people and 10 take calls, you know your call rate. If only 2 of the 10 pay, the problem is probably in the offer or the fit, not in the volume of outreach. Those figures are examples, and your own will differ.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-long-does-it-take-to-get-the-first-10-paying-customers">How long does it take to get the first 10 paying customers?<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#how-long-does-it-take-to-get-the-first-10-paying-customers" class="hash-link" aria-label="Direct link to How long does it take to get the first 10 paying customers?" title="Direct link to How long does it take to get the first 10 paying customers?" translate="no">​</a></h3>
<p>It varies too much to give one figure. Graham's essay on early growth says the founders of Airbnb spent about 30 days meeting users in person, which shows how much a short period of direct effort can matter.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-i-charge-before-the-product-is-finished">Should I charge before the product is finished?<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#should-i-charge-before-the-product-is-finished" class="hash-link" aria-label="Direct link to Should I charge before the product is finished?" title="Direct link to Should I charge before the product is finished?" translate="no">​</a></h3>
<p>Many early founders do, with an honest description of what exists today. Buchheit's advice, quoted by Graham, is to try to sell the product before building more of it.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-i-need-a-payment-system-to-take-my-first-payment">Do I need a payment system to take my first payment?<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#do-i-need-a-payment-system-to-take-my-first-payment" class="hash-link" aria-label="Direct link to Do I need a payment system to take my first payment?" title="Direct link to Do I need a payment system to take my first payment?" translate="no">​</a></h3>
<p>No. Stripe Payment Links accept one-off payments and subscriptions without code.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-if-my-first-customers-are-friends">What if my first customers are friends?<a href="https://dealpuffin.com/blog/general/how-to-get-your-first-10-paying-customers/#what-if-my-first-customers-are-friends" class="hash-link" aria-label="Direct link to What if my first customers are friends?" title="Direct link to What if my first customers are friends?" translate="no">​</a></h3>
<p>Friends can be useful for setup feedback, but they often pay to be kind. Treat the first strangers who pay as your real signal.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="go-to-market" term="go-to-market"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
        <category label="launch" term="launch"/>
        <category label="guide" term="guide"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to offer an annual discount in Stripe]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/"/>
        <updated>2026-11-12T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Create a yearly Price for the annual discount, keep coupons for time-limited promotions, and know what Stripe does to billing dates and prorations when a customer switches plans.]]></summary>
        <content type="html"><![CDATA[<p>The cleanest way to offer an annual discount in Stripe is to give the product a second Price with a yearly interval, set below twelve times the monthly price. A coupon can do the same job, but it is built for discounts that start and end, not for a permanent plan. This guide shows the setup, a worked example, and what happens when a monthly customer switches.</p>
<p>Everything about Stripe's behavior below comes from its documentation, read on 12 November 2026.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="yearly-price-or-coupon">Yearly price or coupon?<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#yearly-price-or-coupon" class="hash-link" aria-label="Direct link to Yearly price or coupon?" title="Direct link to Yearly price or coupon?" translate="no">​</a></h2>
<p>Stripe gives you two mechanisms, and they answer different questions. A Price says how much and how often you charge. A coupon takes money off a charge for a set period. <a href="https://docs.stripe.com/billing/subscriptions/coupons" target="_blank" rel="noopener noreferrer" class="">Stripe's coupon docs</a> say a coupon's duration is <code>once</code> by default, which covers only the first invoice. You can also set <code>repeating</code> with a number of months, or <code>forever</code>.</p>
<p>That default is the trap. If you create a "20% off" coupon and attach it to a yearly subscription with <code>once</code>, the customer gets the discount on the first invoice and pays full price at renewal. A yearly Price avoids the question because the discount is part of the price.</p>
<p>Use a yearly Price when the discount is a standing feature of your pricing page. Use a coupon when you want a launch offer, a partner deal, or a win-back that ends. The post on <a class="" href="https://dealpuffin.com/blog/general/stripe-coupons-vs-promotion-codes/">Stripe coupons versus promotion codes</a> covers the second case in more detail.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-worked-example">A worked example<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#a-worked-example" class="hash-link" aria-label="Direct link to A worked example" title="Direct link to A worked example" translate="no">​</a></h2>
<p>Say your plan costs $20 a month. Twelve months at that rate is $240. If you price the yearly option at $200, a customer pays for ten months and gets twelve. The saving is $40, or about 17%. Those numbers are an example, so pick your own from your churn and cash needs. <a class="" href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/">How to price a SaaS product at the early stage</a> explains how to choose the monthly figure first.</p>
<p>Two things are worth deciding before you set the yearly number. First, whether you want to describe the offer as months free or as a percentage, since buyers compare either. Second, whether the yearly customer gets anything extra. A discount alone is a cash trade: you collect twelve months today and accept less per month.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="set-it-up-in-the-dashboard">Set it up in the Dashboard<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#set-it-up-in-the-dashboard" class="hash-link" aria-label="Direct link to Set it up in the Dashboard" title="Direct link to Set it up in the Dashboard" translate="no">​</a></h2>
<ol>
<li class="">Open the product you already sell monthly.</li>
<li class="">Add another Price on the same product.</li>
<li class="">Choose recurring, and set the billing period to yearly.</li>
<li class="">Enter the yearly amount, for example $200.</li>
<li class="">Copy the new Price ID.</li>
</ol>
<p>Stripe's <a href="https://docs.stripe.com/products-prices/pricing-models" target="_blank" rel="noopener noreferrer" class="">recurring pricing models page</a> lists flat rate, per-seat, tiered, and usage-based models, and each can take a yearly Price. Put both Prices on your pricing page and pass the matching Price ID when you create the Checkout Session. If you use a no-code pricing table, add both intervals to it.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="applying-a-coupon-on-top">Applying a coupon on top<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#applying-a-coupon-on-top" class="hash-link" aria-label="Direct link to Applying a coupon on top" title="Direct link to Applying a coupon on top" translate="no">​</a></h2>
<p>You may still want a coupon for a campaign. In a Checkout Session you pass the coupon ID in the <code>discounts</code> parameter, and the docs show this for subscription mode. Stripe also lets you attach up to 20 discounts to a subscription, and the order matters when you mix a percentage with a fixed amount. For example, 20% off then $5 off gives a different total from $5 off then 20% off.</p>
<p>If the offer should be redeemable by code, wrap the coupon in a promotion code. Stripe's docs list the controls: restrict it to first-time customers, set a minimum order value, set an expiry date, and cap the number of redemptions. A coupon's <code>max_redemptions</code> counts every application, whether it came from a code or from your own backend.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-happens-when-a-monthly-customer-switches">What happens when a monthly customer switches<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#what-happens-when-a-monthly-customer-switches" class="hash-link" aria-label="Direct link to What happens when a monthly customer switches" title="Direct link to What happens when a monthly customer switches" translate="no">​</a></h2>
<p>Existing customers will ask to move to the yearly plan. Stripe's <a href="https://docs.stripe.com/billing/subscriptions/change-price" target="_blank" rel="noopener noreferrer" class="">change-price guide</a> says that if the two Prices have different billing periods, the new price bills at the new interval starting on the day of the change. Switching from monthly to yearly moves the billing date to the date of the switch.</p>
<p>Some practical consequences follow from that page:</p>
<ol>
<li class="">Stripe tries to collect payment immediately when the billing cycle anchor resets. If payment fails, the change still goes through and the subscription becomes <code>past_due</code>.</li>
<li class="">When you update the subscription, pass the existing subscription item ID. Without it, Stripe adds the new Price next to the old one and the customer is charged for both.</li>
<li class="">Updating the price resets the quantity to 1. Include the current quantity if it is higher.</li>
<li class="">Proration can apply to the remaining days. You can preview it before the customer confirms, or disable it.</li>
</ol>
<p>If you prefer to make the switch at the end of the current period, the same page points to subscription schedules.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="who-should-pick-which-approach">Who should pick which approach<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#who-should-pick-which-approach" class="hash-link" aria-label="Direct link to Who should pick which approach" title="Direct link to Who should pick which approach" translate="no">​</a></h2>
<ul>
<li class="">Choose a separate yearly Price if the annual plan is permanent and you want renewals to stay discounted without extra setup.</li>
<li class="">Choose a coupon with <code>repeating</code> duration if the discount should last a fixed number of months, such as a first-year offer.</li>
<li class="">Choose a promotion code on top if you want to hand the offer to a specific audience, such as newsletter readers.</li>
</ul>
<p>If you list your product's offers on other channels, Dealpuffin lets founders who bill through Stripe, Paddle or Polar <a class="" href="https://dealpuffin.com/docs/publishing/go-to-market/">publish coupons from their provider</a>, so the Stripe objects you create here can be reused.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-the-annual-discount-be-a-coupon-or-a-separate-price">Should the annual discount be a coupon or a separate price?<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#should-the-annual-discount-be-a-coupon-or-a-separate-price" class="hash-link" aria-label="Direct link to Should the annual discount be a coupon or a separate price?" title="Direct link to Should the annual discount be a coupon or a separate price?" translate="no">​</a></h3>
<p>A separate yearly Price is simpler for a permanent plan, because the renewal amount stays the same. Coupons suit discounts with an end date.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-long-does-a-stripe-coupon-last">How long does a Stripe coupon last?<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#how-long-does-a-stripe-coupon-last" class="hash-link" aria-label="Direct link to How long does a Stripe coupon last?" title="Direct link to How long does a Stripe coupon last?" translate="no">​</a></h3>
<p>By default a coupon applies once, which is the first invoice only. You can set a repeating duration in months or make it last forever.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-happens-if-a-monthly-subscriber-switches-to-yearly">What happens if a monthly subscriber switches to yearly?<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#what-happens-if-a-monthly-subscriber-switches-to-yearly" class="hash-link" aria-label="Direct link to What happens if a monthly subscriber switches to yearly?" title="Direct link to What happens if a monthly subscriber switches to yearly?" translate="no">​</a></h3>
<p>The new Price bills at the yearly interval starting on the day of the change, so the billing date moves to the switch date. Stripe attempts payment immediately and may prorate the remaining days.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-stack-a-promotion-code-on-a-yearly-plan">Can I stack a promotion code on a yearly plan?<a href="https://dealpuffin.com/blog/general/how-to-offer-an-annual-discount-in-stripe/#can-i-stack-a-promotion-code-on-a-yearly-plan" class="hash-link" aria-label="Direct link to Can I stack a promotion code on a yearly plan?" title="Direct link to Can I stack a promotion code on a yearly plan?" translate="no">​</a></h3>
<p>Yes. Stripe supports up to 20 discounts on a subscription, though you cannot pass a coupon and a promotion code created from that same coupon together.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="billing" term="billing"/>
        <category label="stripe" term="stripe"/>
        <category label="pricing" term="pricing"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Paddle vs Lemon Squeezy for indie SaaS: fees and future]]></title>
        <id>https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/</id>
        <link href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/"/>
        <updated>2026-11-12T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Paddle and Lemon Squeezy both quote 5% + 50¢ as a merchant of record. Compare the extra fees, a worked $29 subscription, and what Stripe's ownership means for Lemon Squeezy.]]></summary>
        <content type="html"><![CDATA[<p>Paddle and Lemon Squeezy publish the same headline fee for a merchant of record: 5% + 50¢ per transaction, with no monthly fee. They differ in the surcharges around it and in where each product is heading. Lemon Squeezy adds fees for international cards, PayPal, and subscription payments, while Paddle's pricing page lists one rate. Lemon Squeezy is also owned by Stripe, and its own pricing page now points to Stripe Managed Payments.</p>
<p>All figures below come from each vendor's own pages, read on 12 November 2026. Check them again before you commit, since both can change.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-a-merchant-of-record-does-here">What a merchant of record does here<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#what-a-merchant-of-record-does-here" class="hash-link" aria-label="Direct link to What a merchant of record does here" title="Direct link to What a merchant of record does here" translate="no">​</a></h2>
<p>Both products act as the seller. They collect the payment, calculate and remit sales tax and VAT, and handle fraud and chargebacks. If that is new to you, <a class="" href="https://dealpuffin.com/blog/general/merchant-of-record-explained-for-indie-founders/">merchant of record explained for indie founders</a> covers what you still owe yourself, such as income tax.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-fees-side-by-side">The fees side by side<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#the-fees-side-by-side" class="hash-link" aria-label="Direct link to The fees side by side" title="Direct link to The fees side by side" translate="no">​</a></h2>
<table><thead><tr><th></th><th>Paddle</th><th>Lemon Squeezy</th></tr></thead><tbody><tr><td>Headline fee</td><td>5% + 50¢ per Checkout transaction</td><td>5% + 50¢ per transaction</td></tr><tr><td>Monthly fee</td><td>None</td><td>None</td></tr><tr><td>International cards</td><td>Not listed separately</td><td>+1.5%</td></tr><tr><td>PayPal</td><td>Not listed separately</td><td>+1.5%</td></tr><tr><td>Subscription payments</td><td>Not listed separately</td><td>+0.5%</td></tr><tr><td>Low-priced products</td><td>Contact Paddle for bespoke pricing under $10</td><td>Contact sales for custom pricing under $10</td></tr><tr><td>Payout fees</td><td>None listed on the pricing page</td><td>Bank payouts via Stripe free in the US, 1% outside the US; PayPal payouts 50¢ in the US, 3% capped at $30 elsewhere</td></tr></tbody></table>
<p>Sources: <a href="https://www.paddle.com/pricing" target="_blank" rel="noopener noreferrer" class="">Paddle pricing</a> and <a href="https://docs.lemonsqueezy.com/help/getting-started/fees" target="_blank" rel="noopener noreferrer" class="">Lemon Squeezy's fees page</a>. Lemon Squeezy also lists extra fees for marketing features: 5% on payments recovered through abandoned-cart emails and 3% on affiliate referrals. Its docs say the platform fee is calculated on the total order value, so VAT you collect counts toward the base. Paddle's page does not say what the percentage is applied to, so ask if that matters to you.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-worked-example-a-29-monthly-plan">A worked example: a $29 monthly plan<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#a-worked-example-a-29-monthly-plan" class="hash-link" aria-label="Direct link to A worked example: a $29 monthly plan" title="Direct link to A worked example: a $29 monthly plan" translate="no">​</a></h2>
<p>Take a US customer paying with a card. Paddle's listed rate is 5% of $29 plus 50¢, which is $1.95. Lemon Squeezy's base fee plus the 0.5% subscription surcharge is 5.5% of $29 plus 50¢, which is about $2.10.</p>
<p>Now make the customer international. Lemon Squeezy adds 1.5%, so the rate becomes 7% of $29 plus 50¢, about $2.53. Paddle's page still shows one rate, so the fee stays at $1.95. The gap on a single payment is small. Over a year of 12 renewals from one international customer it is about $7. That is real money for a tiny product and rounding error for a larger one.</p>
<p>These are our own calculations from the published rates, and they exclude any case where tax is added to the order. The Lemon Squeezy docs show that tax raises the fee base: on a $20 digital product sold to France with 20% VAT, the $24 total produces a $2.06 platform fee.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="where-lemon-squeezy-is-heading">Where Lemon Squeezy is heading<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#where-lemon-squeezy-is-heading" class="hash-link" aria-label="Direct link to Where Lemon Squeezy is heading" title="Direct link to Where Lemon Squeezy is heading" translate="no">​</a></h2>
<p>Lemon Squeezy's <a href="https://www.lemonsqueezy.com/pricing" target="_blank" rel="noopener noreferrer" class="">pricing page</a> now opens with a banner titled "2026 Update: Lemon Squeezy + Stripe Managed Payments", and its footer shows a Stripe badge. Stripe acquired Lemon Squeezy in July 2024. Third-party write-ups of the company's January 2026 update say it described Managed Payments as the future of its merchant-of-record business, and that support and product updates had slowed. We could not read the original post in full, so treat that summary as secondhand and read the <a href="https://www.lemonsqueezy.com/blog/2026-update" target="_blank" rel="noopener noreferrer" class="">update</a> yourself.</p>
<p>Stripe's own product has a different fee shape. Its <a href="https://support.stripe.com/questions/managed-payments-pricing" target="_blank" rel="noopener noreferrer" class="">Managed Payments pricing page</a> says Managed Payments charges 3.5% per successful transaction on top of standard Stripe processing fees, and that Stripe Billing fees apply separately for subscriptions. The 3.5% is calculated on the full amount, including indirect taxes.</p>
<p>None of this says Lemon Squeezy is closing. It does mean a new account there carries a migration question that a Paddle account does not, and that is worth weighing if you plan to stay for years.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="who-should-pick-what">Who should pick what<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#who-should-pick-what" class="hash-link" aria-label="Direct link to Who should pick what" title="Direct link to Who should pick what" translate="no">​</a></h2>
<p>Choose Paddle if you sell subscriptions to buyers in many countries and want one published rate, or if you expect to want sales help later. Paddle's pricing page also describes a migration service and says there is no lock-in period.</p>
<p>Choose Lemon Squeezy if you value its bundled storefront, license keys, and digital downloads, you sell mostly to US buyers with cards, and you accept that its future is tied to Stripe's plans.</p>
<p>Choose neither yet if you charge under $10 a month. Both say fixed fees hurt at low prices and both invite you to ask for custom terms. For a wider view that includes Polar and plain Stripe, see <a class="" href="https://dealpuffin.com/blog/general/stripe-vs-paddle-vs-polar-fees/">Stripe vs Paddle vs Polar fees</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="is-paddle-cheaper-than-lemon-squeezy">Is Paddle cheaper than Lemon Squeezy?<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#is-paddle-cheaper-than-lemon-squeezy" class="hash-link" aria-label="Direct link to Is Paddle cheaper than Lemon Squeezy?" title="Direct link to Is Paddle cheaper than Lemon Squeezy?" translate="no">​</a></h3>
<p>On the published rates, Paddle is the same or cheaper. Both quote 5% + 50¢, and Lemon Squeezy adds surcharges for international cards, PayPal, and subscriptions.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="does-lemon-squeezy-still-work-in-2026">Does Lemon Squeezy still work in 2026?<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#does-lemon-squeezy-still-work-in-2026" class="hash-link" aria-label="Direct link to Does Lemon Squeezy still work in 2026?" title="Direct link to Does Lemon Squeezy still work in 2026?" translate="no">​</a></h3>
<p>Yes. It still takes sign-ups and payments, and its pricing page is live. Its own site now points to Stripe Managed Payments, so check the roadmap before you build on it.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="are-paddle-and-lemon-squeezy-both-merchants-of-record">Are Paddle and Lemon Squeezy both merchants of record?<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#are-paddle-and-lemon-squeezy-both-merchants-of-record" class="hash-link" aria-label="Direct link to Are Paddle and Lemon Squeezy both merchants of record?" title="Direct link to Are Paddle and Lemon Squeezy both merchants of record?" translate="no">​</a></h3>
<p>Yes. Each says it takes on tax collection and compliance for your sales, plus fraud and chargeback handling.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-does-stripe-managed-payments-cost">What does Stripe Managed Payments cost?<a href="https://dealpuffin.com/blog/general/paddle-vs-lemon-squeezy-for-indie-saas/#what-does-stripe-managed-payments-cost" class="hash-link" aria-label="Direct link to What does Stripe Managed Payments cost?" title="Direct link to What does Stripe Managed Payments cost?" translate="no">​</a></h3>
<p>Stripe lists 3.5% per successful transaction on top of its normal processing fees. Billing fees for subscriptions are separate.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="billing" term="billing"/>
        <category label="pricing" term="pricing"/>
        <category label="comparison" term="comparison"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to deploy Next.js on a single VM with Docker]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/"/>
        <updated>2026-11-11T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[A step-by-step way to ship a Next.js app on one VM with Docker: standalone output, a multi-stage Dockerfile, Compose, a reverse proxy and a deploy routine you can repeat.]]></summary>
        <content type="html"><![CDATA[<p>To deploy Next.js on a single VM with Docker, set <code>output: "standalone"</code> in your Next.js config, build a multi-stage image that copies only the standalone server and static files, run it with Docker Compose, and put a reverse proxy such as nginx in front. Next.js documents Docker as a deployment option that supports all features, so you give up nothing by choosing a plain VM.</p>
<p>This guide covers the Dockerfile, the Compose file, the proxy and a deploy routine. Every claim about Next.js behaviour comes from its docs and Docker's own Next.js guide, both read on 11 November 2026.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-you-need-first">What you need first<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#what-you-need-first" class="hash-link" aria-label="Direct link to What you need first" title="Direct link to What you need first" translate="no">​</a></h2>
<p>A Linux VM with Docker and the Compose plugin installed, a domain pointing at the VM, and a Next.js app that builds locally with <code>npm run build</code>. If you are still deciding whether a VM is the right home, the <a href="https://nextjs.org/docs/app/getting-started/deploying" target="_blank" rel="noopener noreferrer" class="">Next.js deployment page</a> lists the options: a Node.js server, a Docker container, a static export, or an adapter for a hosting platform. Node.js and Docker deployments both support all features. A static export supports a limited set.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-1-turn-on-standalone-output">Step 1: turn on standalone output<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#step-1-turn-on-standalone-output" class="hash-link" aria-label="Direct link to Step 1: turn on standalone output" title="Direct link to Step 1: turn on standalone output" translate="no">​</a></h2>
<p>In <code>next.config.ts</code>, add:</p>
<div class="language-ts codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-ts codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">import</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">type</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"> NextConfig </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">from</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">"next"</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> nextConfig</span><span class="token operator">:</span><span class="token plain"> NextConfig </span><span class="token operator">=</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  output</span><span class="token operator">:</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">"standalone"</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">export</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">default</span><span class="token plain"> nextConfig</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><br></div></code></pre></div></div>
<p>Standalone output produces a minimal server in <code>.next/standalone</code> with only the runtime files it needs. The Next.js team ships a <a href="https://github.com/vercel/next.js/tree/canary/examples/with-docker" target="_blank" rel="noopener noreferrer" class="">Docker standalone example</a> built on this setting, described as a way to generate a minimal, production-ready image.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-2-write-a-multi-stage-dockerfile">Step 2: write a multi-stage Dockerfile<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#step-2-write-a-multi-stage-dockerfile" class="hash-link" aria-label="Direct link to Step 2: write a multi-stage Dockerfile" title="Direct link to Step 2: write a multi-stage Dockerfile" translate="no">​</a></h2>
<p>Docker's <a href="https://docs.docker.com/guides/nextjs/containerize.md" target="_blank" rel="noopener noreferrer" class="">Next.js guide</a> uses three stages: one installs dependencies, one builds, and one runs. The runtime stage copies only <code>public</code>, <code>.next/standalone</code> and <code>.next/static</code>. Here is a version of that layout:</p>
<div class="language-dockerfile codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-dockerfile codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token plain">FROM node:24-slim AS deps</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">WORKDIR /app</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">COPY package.json package-lock.json ./</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">RUN npm ci</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">FROM node:24-slim AS builder</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">WORKDIR /app</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">COPY --from=deps /app/node_modules ./node_modules</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">COPY . .</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">ENV NODE_ENV=production</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">RUN npm run build</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">FROM node:24-slim AS runner</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">WORKDIR /app</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">ENV NODE_ENV=production</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">ENV PORT=3000</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">ENV HOSTNAME="0.0.0.0"</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">COPY --from=builder /app/public ./public</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">COPY --from=builder --chown=node:node /app/.next/standalone ./</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">COPY --from=builder --chown=node:node /app/.next/static ./.next/static</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">USER node</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">EXPOSE 3000</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">CMD ["node", "server.js"]</span><br></div></code></pre></div></div>
<p>The guide sets <code>PORT</code>, binds <code>HOSTNAME</code> to <code>0.0.0.0</code>, runs as the non-root <code>node</code> user and starts <code>server.js</code>. Its own example pins an exact Node tag and tells you to check Docker Hub for a current, secure one before building, so pin a specific version in your own file rather than a floating tag.</p>
<p>Add a <code>.dockerignore</code> that excludes <code>node_modules</code>, <code>.next</code>, <code>.git</code> and your env files. Without it, your local build output and secrets get copied into the build context.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-3-handle-environment-variables">Step 3: handle environment variables<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#step-3-handle-environment-variables" class="hash-link" aria-label="Direct link to Step 3: handle environment variables" title="Direct link to Step 3: handle environment variables" translate="no">​</a></h2>
<p>By default, environment variables are only available on the server. A variable prefixed with <code>NEXT_PUBLIC_</code> is inlined into the JavaScript bundle during <code>next build</code>, so it must exist at build time. The <a href="https://nextjs.org/docs/app/guides/self-hosting" target="_blank" rel="noopener noreferrer" class="">self-hosting guide</a> adds that server code can read variables at runtime during dynamic rendering, which lets one image move through several environments with different values.</p>
<p>A simple rule: put anything the browser needs in <code>NEXT_PUBLIC_</code> variables and pass them as build arguments. Put secrets in runtime variables and keep them out of the image.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-4-run-it-with-compose">Step 4: run it with Compose<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#step-4-run-it-with-compose" class="hash-link" aria-label="Direct link to Step 4: run it with Compose" title="Direct link to Step 4: run it with Compose" translate="no">​</a></h2>
<p>Create <code>compose.yaml</code> on the VM:</p>
<div class="language-yaml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-yaml codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token key atrule">services</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token key atrule">web</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token key atrule">build</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> .</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token key atrule">restart</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> unless</span><span class="token punctuation" style="color:rgb(248, 248, 242)">-</span><span class="token plain">stopped</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token key atrule">ports</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token punctuation" style="color:rgb(248, 248, 242)">-</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">"127.0.0.1:3000:3000"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token key atrule">env_file</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token punctuation" style="color:rgb(248, 248, 242)">-</span><span class="token plain"> .env.production</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token key atrule">stop_grace_period</span><span class="token punctuation" style="color:rgb(248, 248, 242)">:</span><span class="token plain"> 30s</span><br></div></code></pre></div></div>
<p>Binding to <code>127.0.0.1</code> keeps the container off the public internet. Only the reverse proxy will reach it. The 30-second grace period matters because the self-hosting guide says the server finishes in-flight requests and runs pending <code>after()</code> callbacks when it receives <code>SIGINT</code> or <code>SIGTERM</code>, and it recommends a drain period of 10 to 30 seconds.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-5-put-a-reverse-proxy-in-front">Step 5: put a reverse proxy in front<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#step-5-put-a-reverse-proxy-in-front" class="hash-link" aria-label="Direct link to Step 5: put a reverse proxy in front" title="Direct link to Step 5: put a reverse proxy in front" translate="no">​</a></h2>
<p>The self-hosting guide recommends a reverse proxy such as nginx in front of the Next.js server rather than exposing it directly. The proxy can handle malformed requests, slow connection attacks, payload size limits and rate limiting, so the Node process spends its time rendering.</p>
<p>A minimal nginx server block:</p>
<div class="language-nginx codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-nginx codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token plain">server {</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  listen 80;</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  server_name example.com;</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  location / {</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    proxy_pass http://127.0.0.1:3000;</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    proxy_http_version 1.1;</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    proxy_set_header Host $host;</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    proxy_set_header X-Forwarded-Proto $scheme;</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  }</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">}</span><br></div></code></pre></div></div>
<p>Add TLS with your usual tool, for example Certbot. If you use streaming and Suspense, the guide says to disable proxy buffering. It shows setting an <code>X-Accel-Buffering: no</code> response header from <code>next.config</code>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-6-deploy-and-redeploy">Step 6: deploy and redeploy<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#step-6-deploy-and-redeploy" class="hash-link" aria-label="Direct link to Step 6: deploy and redeploy" title="Direct link to Step 6: deploy and redeploy" translate="no">​</a></h2>
<p>On the VM, clone your repository and run:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token plain">docker compose up -d --build</span><br></div></code></pre></div></div>
<p>For later releases the routine is the same two lines:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token plain">git pull</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">docker compose up -d --build</span><br></div></code></pre></div></div>
<p>Compose rebuilds the image and replaces the container. Expect a short gap while the new container starts. A single VM gives up rolling deploys. If a few seconds of downtime on release is acceptable at your stage, this setup is enough.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-7-check-the-caching-and-image-behaviour">Step 7: check the caching and image behaviour<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#step-7-check-the-caching-and-image-behaviour" class="hash-link" aria-label="Direct link to Step 7: check the caching and image behaviour" title="Direct link to Step 7: check the caching and image behaviour" translate="no">​</a></h2>
<p>Two details from the docs are worth a look before you call it done.</p>
<p>Image optimisation through <code>next/image</code> works self-hosted with no extra configuration when you run the server. On glibc-based Linux, the guide notes that it may need extra configuration to prevent high memory use. If you are on a small VM, watch memory after your first traffic spike.</p>
<p>Page caching and Incremental Static Regeneration share one server cache, stored by default on the local disk of each instance. That works for one container. The guide says that if you later run several instances, you need a shared cache handler, a shared encryption key for Server Functions and a deployment ID. A single VM sidesteps all of that, which is a good reason to stay on one until traffic forces the issue.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="when-this-setup-stops-being-enough">When this setup stops being enough<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#when-this-setup-stops-being-enough" class="hash-link" aria-label="Direct link to When this setup stops being enough" title="Direct link to When this setup stops being enough" translate="no">​</a></h2>
<p>Move off a single VM when you need zero-downtime releases, when one machine cannot handle peak traffic, or when you want the platform to manage scaling. Until then, one VM, one container and one proxy is easy to reason about and cheap to run.</p>
<p>If you are weighing the framework as well as the host, <a class="" href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/">Next.js vs Astro for a SaaS marketing site</a> covers when a static site is the simpler choice. For the monitoring side of a new deploy, see <a class="" href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/">free uptime monitoring tools for indie SaaS</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-i-need-output-standalone-to-run-nextjs-in-docker">Do I need output standalone to run Next.js in Docker?<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#do-i-need-output-standalone-to-run-nextjs-in-docker" class="hash-link" aria-label="Direct link to Do I need output standalone to run Next.js in Docker?" title="Direct link to Do I need output standalone to run Next.js in Docker?" translate="no">​</a></h3>
<p>No, you can run <code>next start</code> from a full image, but standalone output copies only the files the server needs, which gives a smaller image. Docker's Next.js guide and the official Next.js example both use it.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-one-vm-handle-production-traffic-for-a-saas">Can one VM handle production traffic for a SaaS?<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#can-one-vm-handle-production-traffic-for-a-saas" class="hash-link" aria-label="Direct link to Can one VM handle production traffic for a SaaS?" title="Direct link to Can one VM handle production traffic for a SaaS?" translate="no">​</a></h3>
<p>For an early product, usually yes, if you monitor memory and CPU and accept a brief gap during releases. Plan to move when you need rolling deploys or more capacity than one machine gives you.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="where-should-secrets-live">Where should secrets live?<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#where-should-secrets-live" class="hash-link" aria-label="Direct link to Where should secrets live?" title="Direct link to Where should secrets live?" translate="no">​</a></h3>
<p>Keep secrets in runtime environment variables loaded through an env file or your secret manager, not in the image. Anything prefixed with <code>NEXT_PUBLIC_</code> is inlined into the browser bundle at build time, so never put a secret there.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="is-docker-required-to-self-host-nextjs">Is Docker required to self-host Next.js?<a href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/#is-docker-required-to-self-host-nextjs" class="hash-link" aria-label="Direct link to Is Docker required to self-host Next.js?" title="Direct link to Is Docker required to self-host Next.js?" translate="no">​</a></h3>
<p>No. The Next.js docs say a Node.js server also supports all features: run <code>npm run build</code> and then <code>npm run start</code>. Docker adds a repeatable image and easier rollbacks.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="devtools" term="devtools"/>
        <category label="saas" term="saas"/>
        <category label="deployment" term="deployment"/>
        <category label="howto" term="howto"/>
        <category label="early-founders" term="early-founders"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Indie Hackers vs Reddit for launching a product]]></title>
        <id>https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/</id>
        <link href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/"/>
        <updated>2026-11-11T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Indie Hackers or Reddit for a first launch? How each community treats promotion, what to post where, and a one-week plan that respects the rules of both.]]></summary>
        <content type="html"><![CDATA[<p>Launch on Indie Hackers first, and use Reddit second through the specific subreddits where your buyers already talk. Indie Hackers is built for founders sharing what they are building, so a launch post fits. Reddit is many separate communities, each with its own rules, so a launch post that works in one gets removed in another. Read the rules of each subreddit before you write a word.</p>
<p>This comparison covers how each community works, how to write for each, and a one-week plan. I read Reddit's platform rules and the Indie Hackers front page on 11 November 2026. I did not verify any traffic numbers, and I avoid quoting any.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="how-the-two-differ">How the two differ<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#how-the-two-differ" class="hash-link" aria-label="Direct link to How the two differ" title="Direct link to How the two differ" translate="no">​</a></h2>
<p><a href="https://www.indiehackers.com/" target="_blank" rel="noopener noreferrer" class="">Indie Hackers</a> is one community with one audience: founders, makers and people building small businesses. Its front page on the day I read it was full of posts about first sign-ups, revenue, marketing experiments and launch-site strategy, including a thread asking which launch sites people have combined and in what order. A product launch post sits next to those without looking out of place, as long as it shares something you learned.</p>
<p>Reddit is a network of communities that are, in Reddit's own words, created, run and populated by users. The platform's <a href="https://redditinc.com/policies/reddit-rules" target="_blank" rel="noopener noreferrer" class="">rules</a> apply everywhere, and each community adds its own. Rule 2 asks you to abide by community rules and to "participate authentically in communities where you have a personal interest," and not to spam. Reddit says its communities are shaped explicitly by moderator-enforced rules and implicitly by votes and discussion, and asks you to follow the rules of the communities you join.</p>
<p>Choosing between them means choosing one community with a clear audience or many communities with their own rule sets.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="side-by-side">Side by side<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#side-by-side" class="hash-link" aria-label="Direct link to Side by side" title="Direct link to Side by side" translate="no">​</a></h2>
<table><thead><tr><th>Question</th><th>Indie Hackers</th><th>Reddit</th></tr></thead><tbody><tr><td>Audience</td><td>Founders and makers</td><td>Depends on the subreddit</td></tr><tr><td>Rules</td><td>One site, one set of norms</td><td>Platform rules plus each subreddit's own</td></tr><tr><td>Launch post fit</td><td>Natural if it shares a lesson or numbers</td><td>Allowed in some subreddits, banned in others</td></tr><tr><td>Risk if you get it wrong</td><td>Low engagement</td><td>Post removed, account restricted or banned</td></tr><tr><td>Enforcement</td><td>Community response</td><td>Moderators and platform admins</td></tr><tr><td>Best for</td><td>Feedback from other builders</td><td>Reaching buyers where they already ask questions</td></tr></tbody></table>
<p>The enforcement row comes from Reddit's rules page, which lists the ways it can respond: asking you to stop, removing content, restricting or suspending accounts, and restricting or banning communities. Indie Hackers has no equivalent list that I could read, so I only compare the practical risk.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="writing-for-indie-hackers">Writing for Indie Hackers<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#writing-for-indie-hackers" class="hash-link" aria-label="Direct link to Writing for Indie Hackers" title="Direct link to Writing for Indie Hackers" translate="no">​</a></h2>
<p>Write a post a founder would want to read even if they never click your link. Share what you built, who it is for, one number or decision from your own work, and a specific question you want answered. Posts about a real result or a mistake tend to start conversations more easily than an announcement does.</p>
<p>One headline on the front page the day I read it is a useful warning: a <a href="https://www.indiehackers.com/post/my-reddit-chart-got-153k-views-and-sent-about-5-visitors-what-i-learned-in-month-one-of-a-data-site-P710WeoMTtA2pEiINKtu" target="_blank" rel="noopener noreferrer" class="">post titled "My Reddit chart got 153k views and sent about 5 visitors"</a> I did not read the full post and I cannot vouch for its numbers. The title alone is a useful reminder that views on a post and visits to your product are different numbers, so measure your own clicks.</p>
<p>Put your link in the post where it helps, and answer every comment. Replies are the product on a community site. Your launch post also becomes a page that stays reachable, so link to something that will still exist in six months.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="writing-for-reddit">Writing for Reddit<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#writing-for-reddit" class="hash-link" aria-label="Direct link to Writing for Reddit" title="Direct link to Writing for Reddit" translate="no">​</a></h2>
<p>Before posting anywhere, do these five checks.</p>
<ol>
<li class="">Read the subreddit's rules and pinned posts. Many have a specific thread or day for self-promotion.</li>
<li class="">Read the last twenty posts. Notice what gets removed and what gets upvoted.</li>
<li class="">Check whether the community wants launches at all. Some want only questions and discussion.</li>
<li class="">Lead with the problem or the lesson, not your product name.</li>
<li class="">Disclose that you made the product, and answer every reply.</li>
</ol>
<p>Rule 2 of Reddit's platform rules is the one that gets founders into trouble: authentic participation in communities where you have a personal interest. If your only activity is posting links to your own product, you are not participating, and moderators can tell. Spend a week reading and answering questions in the places you plan to post.</p>
<p>Be careful with advice that claims to know exactly how Reddit detects promotion. I read one Indie Hackers post making detailed claims about account behaviour analysis. Its author sells a Reddit marketing tool and cites no sources, so I would not build a plan on it. The only rules I can point you to are the published ones: Reddit's platform rules and each subreddit's own.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-one-week-plan">A one-week plan<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#a-one-week-plan" class="hash-link" aria-label="Direct link to A one-week plan" title="Direct link to A one-week plan" translate="no">​</a></h2>
<p>This plan assumes you have a working product, a landing page that loads fast, and one thing you can measure, such as signups.</p>
<ol>
<li class="">Monday: write the Indie Hackers post and ask a friend to read it for tone. Make sure the landing page has a clear signup path.</li>
<li class="">Tuesday: publish on Indie Hackers in the morning. Stay in the comments for the day.</li>
<li class="">Wednesday: pick two or three subreddits where your buyers ask questions. Read the rules and recent posts. Do not post yet.</li>
<li class="">Thursday: answer questions in those subreddits with no link, only help. Add your link only where a subreddit's rules allow it.</li>
<li class="">Friday: if a subreddit has a self-promotion thread or allows launches, post there with a disclosure that you built it.</li>
<li class="">Weekend: review which source sent signups, using your own analytics, and write down what people asked.</li>
</ol>
<p>For the launch sites that sit alongside these two, see <a class="" href="https://dealpuffin.com/blog/general/show-hn-vs-product-hunt-for-early-saas/">Show HN vs Product Hunt for early SaaS</a> and <a class="" href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/">SaaS directories worth submitting your product to</a>. A broader plan for your first users is in <a class="" href="https://dealpuffin.com/blog/general/how-to-get-your-first-100-users-for-a-saas/">how to get your first 100 users for a SaaS</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="who-should-pick-what">Who should pick what<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#who-should-pick-what" class="hash-link" aria-label="Direct link to Who should pick what" title="Direct link to Who should pick what" translate="no">​</a></h2>
<p>Choose Indie Hackers if you want feedback from other builders and a low-risk first post. Choose Reddit if your buyers are not founders and you are willing to spend a week reading before posting. Do both if you can, but in the order above, because the Indie Hackers post teaches you what questions people ask.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="is-it-okay-to-promote-my-own-product-on-reddit">Is it okay to promote my own product on Reddit?<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#is-it-okay-to-promote-my-own-product-on-reddit" class="hash-link" aria-label="Direct link to Is it okay to promote my own product on Reddit?" title="Direct link to Is it okay to promote my own product on Reddit?" translate="no">​</a></h3>
<p>It depends on the subreddit. Reddit's platform rules ask for authentic participation and ban spam, and each community sets its own rules on self-promotion. Read them first and disclose that you built the product.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-i-launch-on-indie-hackers-or-product-hunt-first">Should I launch on Indie Hackers or Product Hunt first?<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#should-i-launch-on-indie-hackers-or-product-hunt-first" class="hash-link" aria-label="Direct link to Should I launch on Indie Hackers or Product Hunt first?" title="Direct link to Should I launch on Indie Hackers or Product Hunt first?" translate="no">​</a></h3>
<p>They serve different goals. Indie Hackers is a community for conversation with other founders, and Product Hunt runs a daily leaderboard. The comparison in the Show HN and Product Hunt post covers the launch-day sites in more detail.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-post-the-same-launch-text-in-both-places">Can I post the same launch text in both places?<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#can-i-post-the-same-launch-text-in-both-places" class="hash-link" aria-label="Direct link to Can I post the same launch text in both places?" title="Direct link to Can I post the same launch text in both places?" translate="no">​</a></h3>
<p>You can reuse the facts, but write each post for its audience. Reddit communities often dislike copy-pasted announcements, and the Indie Hackers audience wants a lesson or a number rather than a pitch.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-do-i-know-which-channel-worked">How do I know which channel worked?<a href="https://dealpuffin.com/blog/general/indie-hackers-vs-reddit-for-launching-a-product/#how-do-i-know-which-channel-worked" class="hash-link" aria-label="Direct link to How do I know which channel worked?" title="Direct link to How do I know which channel worked?" translate="no">​</a></h3>
<p>Add a tracking parameter to the link you use in each place and compare signups in your analytics. Judge the channels by signups and conversations, not by views.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="go-to-market" term="go-to-market"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
        <category label="launch" term="launch"/>
        <category label="comparison" term="comparison"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Next.js vs Astro for a SaaS marketing site: a decision rule]]></title>
        <id>https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/</id>
        <link href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/"/>
        <updated>2026-11-11T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Next.js or Astro for your SaaS marketing site? A short decision rule, a feature table based on both docs, and a worked example for a founder with one app and one landing page.]]></summary>
        <content type="html"><![CDATA[<p>Pick Astro if your marketing site is mostly content (landing page, pricing, blog, docs) and lives apart from your app. Pick Next.js if the marketing pages share components, auth state or server logic with your product, or if you already run the app in Next.js and want one codebase. Both can produce fast static pages, so the deciding factor is how much your marketing site has to do beyond showing content.</p>
<p>This comparison sticks to what the Astro and Next.js documentation says, read on 11 November 2026. I did not benchmark either framework, so I make no speed claims.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-each-framework-says-it-is-for">What each framework says it is for<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#what-each-framework-says-it-is-for" class="hash-link" aria-label="Direct link to What each framework says it is for" title="Direct link to What each framework says it is for" translate="no">​</a></h2>
<p>Astro's <a href="https://docs.astro.build/en/concepts/why-astro" target="_blank" rel="noopener noreferrer" class="">Why Astro</a> page states that Astro was designed for building content-rich websites, aimed at sites where the content is the product, such as blogs, docs and storefronts, rather than logged-in applications. It lists server-first rendering, with client-side JavaScript added only where needed, and describes its "islands" architecture and zero JavaScript by default as features. It is UI-agnostic and supports React, Preact, Svelte, Vue, Solid and others.</p>
<p>Next.js is a full-stack React framework. Its <a href="https://nextjs.org/docs/app/getting-started/deploying" target="_blank" rel="noopener noreferrer" class="">deployment page</a> lists four ways to ship it: a Node.js server, a Docker container, a static export, or an adapter for a platform. Node.js and Docker support all features. A static export supports a limited set.</p>
<p>Astro starts from content and adds interactivity where you ask for it. Next.js starts from an application and can also produce static pages.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="side-by-side">Side by side<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#side-by-side" class="hash-link" aria-label="Direct link to Side by side" title="Direct link to Side by side" translate="no">​</a></h2>
<table><thead><tr><th>Question</th><th>Astro</th><th>Next.js</th></tr></thead><tbody><tr><td>Designed for</td><td>Content-rich sites such as blogs, docs and storefronts</td><td>Full-stack React applications</td></tr><tr><td>Default client JavaScript</td><td>Zero by default, added through islands</td><td>React is part of the client model; static export still ships JavaScript for hydration</td></tr><tr><td>UI libraries</td><td>React, Preact, Svelte, Vue, Solid and more</td><td>React</td></tr><tr><td>Static output</td><td>Core use case</td><td>Available through <code>output: 'export'</code></td></tr><tr><td>Server features on static output</td><td>Not the main path</td><td>Several unsupported (see below)</td></tr><tr><td>Shares code with a Next.js app</td><td>Only via packages or copy</td><td>Same project or monorepo</td></tr></tbody></table>
<p>The one claim in the table I should flag: Next.js docs say a static export generates an HTML file per route and "can avoid loading unnecessary JavaScript code on the client-side." They do not say it ships none. Compare the two on your own pages with a real build before relying on either description.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-you-lose-with-a-nextjs-static-export">What you lose with a Next.js static export<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#what-you-lose-with-a-nextjs-static-export" class="hash-link" aria-label="Direct link to What you lose with a Next.js static export" title="Direct link to What you lose with a Next.js static export" translate="no">​</a></h2>
<p>If you choose Next.js and export statically, the <a href="https://nextjs.org/docs/app/guides/static-exports" target="_blank" rel="noopener noreferrer" class="">static export guide</a> lists features that are not supported because they need a Node.js server or dynamic logic: dynamic routes without <code>generateStaticParams()</code>, route handlers that rely on the request, cookies, rewrites, redirects, headers, proxy, Incremental Static Regeneration, image optimisation with the default loader, Draft Mode, Server Actions and intercepting routes.</p>
<p>Some of those matter for marketing sites. If you rely on redirects for old URLs, you need to handle them at your web server or CDN. If you use <code>next/image</code>, you need a custom image loader. If you want a signup form that posts to a Server Action, you need a separate endpoint.</p>
<p>What you keep is also worth knowing. Server Components run at build time and render to static HTML, and Client Components work for interactive parts.</p>
<p>You avoid that list by running Next.js as a server or in a container, as covered in <a class="" href="https://dealpuffin.com/blog/general/how-to-deploy-next-js-on-a-single-vm-with-docker/">how to deploy Next.js on a single VM with Docker</a>. The price is that you now run and patch a Node process for pages that rarely change.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-decision-rule">A decision rule<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#a-decision-rule" class="hash-link" aria-label="Direct link to A decision rule" title="Direct link to A decision rule" translate="no">​</a></h2>
<p>Answer these four questions in order and stop at the first yes.</p>
<ol>
<li class="">Does the marketing site need logged-in state, such as showing the user's name or plan in the header? Choose Next.js, and run it as a server.</li>
<li class="">Do you want one repository and one set of React components for app and marketing? Choose Next.js.</li>
<li class="">Is the site mostly written content, updated by a person or a content tool, with a handful of interactive widgets? Choose Astro.</li>
<li class="">Is your team comfortable with a framework other than React? If not, choose Next.js. If yes, Astro's UI-agnostic design means you can still drop in a React component where you need one.</li>
</ol>
<p>If none of these gives a clear answer, choose the one your team already knows. A fast site shipped this week beats a theoretically better one next month.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-worked-example">A worked example<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#a-worked-example" class="hash-link" aria-label="Direct link to A worked example" title="Direct link to A worked example" translate="no">​</a></h2>
<p>Take a founder with a product dashboard already built in Next.js and a marketing site of five pages: home, pricing, a changelog, a blog and a docs section.</p>
<p>The dashboard needs auth and server logic, so it stays on Next.js. The marketing pages are content. Under the rule above, question 1 is no, question 2 is a maybe, and question 3 is yes, so Astro fits well for the marketing site, hosted separately from the app at the root domain with the app on a subdomain.</p>
<p>Now change one fact: the pricing page must show the visitor's current plan and a personalised upgrade button. Question 1 becomes yes. Keep those pages in the Next.js app and skip the second framework.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="costs-of-running-two-frameworks">Costs of running two frameworks<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#costs-of-running-two-frameworks" class="hash-link" aria-label="Direct link to Costs of running two frameworks" title="Direct link to Costs of running two frameworks" translate="no">​</a></h2>
<p>Splitting marketing and app means two builds, two deploys and two places to update shared design tokens and copy. It also means analytics and consent have to work across both. That overhead is small for a one-person team if the marketing site rarely changes, and larger if three people edit both weekly. For measurement across the two, see <a class="" href="https://dealpuffin.com/blog/general/posthog-vs-plausible-vs-ga4-for-early-stage-saas/">PostHog vs Plausible vs GA4 for early-stage SaaS</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="who-should-pick-what">Who should pick what<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#who-should-pick-what" class="hash-link" aria-label="Direct link to Who should pick what" title="Direct link to Who should pick what" translate="no">​</a></h2>
<p>Choose Astro when content leads and your app lives elsewhere. Choose Next.js when marketing and product overlap, when you want one codebase, or when you need server features on your public pages. Choose a Next.js static export only if you can live with the unsupported list above.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="is-astro-better-than-nextjs-for-seo">Is Astro better than Next.js for SEO?<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#is-astro-better-than-nextjs-for-seo" class="hash-link" aria-label="Direct link to Is Astro better than Next.js for SEO?" title="Direct link to Is Astro better than Next.js for SEO?" translate="no">​</a></h3>
<p>Both can output crawlable HTML, so the differences come from your content, page speed and how well you handle redirects and metadata. Astro's content-first design makes the static path the default one.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-use-react-components-in-astro">Can I use React components in Astro?<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#can-i-use-react-components-in-astro" class="hash-link" aria-label="Direct link to Can I use React components in Astro?" title="Direct link to Can I use React components in Astro?" translate="no">​</a></h3>
<p>Yes. Astro's docs list React among the UI frameworks it supports, so you can render a React component inside an Astro page and hydrate it only where it needs to be interactive.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="does-a-nextjs-static-export-work-with-a-blog">Does a Next.js static export work with a blog?<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#does-a-nextjs-static-export-work-with-a-blog" class="hash-link" aria-label="Direct link to Does a Next.js static export work with a blog?" title="Direct link to Does a Next.js static export work with a blog?" translate="no">​</a></h3>
<p>Yes. Server Components run at build time and render static HTML, and dynamic routes work if you provide <code>generateStaticParams()</code>. You lose the features on the unsupported list, such as redirects and Incremental Static Regeneration.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-i-switch-an-existing-site">Should I switch an existing site?<a href="https://dealpuffin.com/blog/general/nextjs-vs-astro-for-a-saas-marketing-site/#should-i-switch-an-existing-site" class="hash-link" aria-label="Direct link to Should I switch an existing site?" title="Direct link to Should I switch an existing site?" translate="no">​</a></h3>
<p>Only if you have a concrete problem, such as maintenance cost or a feature you keep working around. Switching frameworks for a small site rarely pays back quickly.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="devtools" term="devtools"/>
        <category label="saas" term="saas"/>
        <category label="comparison" term="comparison"/>
        <category label="frameworks" term="frameworks"/>
        <category label="early-founders" term="early-founders"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Free uptime monitoring tools for an indie SaaS, compared]]></title>
        <id>https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/</id>
        <link href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/"/>
        <updated>2026-11-10T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[UptimeRobot, HetrixTools, Better Stack and self-hosted Uptime Kuma compared on monitors, check interval and status pages, with a rule for which to pick first.]]></summary>
        <content type="html"><![CDATA[<p>For an indie SaaS, the best free uptime monitor is usually HetrixTools if you want one-minute checks, UptimeRobot if you want the most monitors, Better Stack if you want a polished status page and on-call tools, and Uptime Kuma if you are happy to host it yourself. All four cost nothing to start. The differences are the check interval, the monitor count and what happens when you outgrow the free plan.</p>
<p>This comparison uses each vendor's pricing page as read on 10 November 2026. Limits change, so check the page before you commit.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-an-early-saas-actually-needs">What an early SaaS actually needs<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#what-an-early-saas-actually-needs" class="hash-link" aria-label="Direct link to What an early SaaS actually needs" title="Direct link to What an early SaaS actually needs" translate="no">​</a></h2>
<p>You need to know within a few minutes that your marketing site, your app login and your API health endpoint respond. You need an alert that reaches you where you will see it, such as email or Slack. A public status page is a bonus once you have paying users.</p>
<p>You do not need server agents, transaction scripts or phone trees on day one. Pick the tool that covers three or four URLs well and has a clear next step.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-four-options-side-by-side">The four options side by side<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#the-four-options-side-by-side" class="hash-link" aria-label="Direct link to The four options side by side" title="Direct link to The four options side by side" translate="no">​</a></h2>
<table><thead><tr><th>Tool</th><th>Free monitors</th><th>Free check interval</th><th>Status page on free</th><th>Notes</th></tr></thead><tbody><tr><td><a href="https://uptimerobot.com/pricing/" target="_blank" rel="noopener noreferrer" class="">UptimeRobot</a></td><td>50</td><td>5 minutes</td><td>Yes, basic</td><td>Page states the free plan suits personal and commercial projects</td></tr><tr><td><a href="https://hetrixtools.com/pricing/uptime-monitor/" target="_blank" rel="noopener noreferrer" class="">HetrixTools</a></td><td>15 uptime + 15 server</td><td>1 minute</td><td>Yes, public pages</td><td>Free plan requires a login every 90 days</td></tr><tr><td><a href="https://betterstack.com/pricing" target="_blank" rel="noopener noreferrer" class="">Better Stack</a></td><td>10 monitors and heartbeats</td><td>Not stated for free</td><td>1 status page</td><td>Plan is labelled free for personal projects</td></tr><tr><td><a href="https://github.com/louislam/uptime-kuma" target="_blank" rel="noopener noreferrer" class="">Uptime Kuma</a></td><td>As many as your server handles</td><td>20 seconds</td><td>Multiple status pages</td><td>MIT license, you run it</td></tr></tbody></table>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="uptimerobot-most-monitors">UptimeRobot: most monitors<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#uptimerobot-most-monitors" class="hash-link" aria-label="Direct link to UptimeRobot: most monitors" title="Direct link to UptimeRobot: most monitors" translate="no">​</a></h2>
<p>The free plan gives you 50 monitors with a 5-minute interval and basic HTTP, port, ping and keyword checks. SSL monitoring and the faster 60-second interval sit on the paid Solo plan, which UptimeRobot lists at $144 a year. For a small product the 5-minute interval means an outage can run for up to five minutes before you hear about it.</p>
<p>Pick it if you have many small sites or endpoints and a few minutes of delay is acceptable.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="hetrixtools-fastest-free-checks">HetrixTools: fastest free checks<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#hetrixtools-fastest-free-checks" class="hash-link" aria-label="Direct link to HetrixTools: fastest free checks" title="Direct link to HetrixTools: fastest free checks" translate="no">​</a></h2>
<p>HetrixTools checks every minute on every plan, including free, and the free plan includes 15 uptime monitors, 15 server monitors and public status pages. The trade-offs are that free accounts use 4 of its 12 monitoring locations, and the account must be logged into at least once every 90 days or the monitors can be switched off. Paid plans start at $9.95 a month.</p>
<p>Pick it if detection speed matters more than monitor count.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="better-stack-best-status-page-and-on-call-story">Better Stack: best status page and on-call story<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#better-stack-best-status-page-and-on-call-story" class="hash-link" aria-label="Direct link to Better Stack: best status page and on-call story" title="Direct link to Better Stack: best status page and on-call story" translate="no">​</a></h2>
<p>Better Stack's free plan includes 10 monitors and heartbeats, one status page, and Slack and email alerts. The plan is described as free for personal projects, so read the terms before putting a revenue-generating product on it. Paid features such as phone call alerts start on the Responder license at $29 per month when billed annually.</p>
<p>Pick it if you expect to add on-call, logs and incident management later and want one vendor for all of it.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="uptime-kuma-self-hosted-and-free">Uptime Kuma: self-hosted and free<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#uptime-kuma-self-hosted-and-free" class="hash-link" aria-label="Direct link to Uptime Kuma: self-hosted and free" title="Direct link to Uptime Kuma: self-hosted and free" translate="no">​</a></h2>
<p>Uptime Kuma is an MIT-licensed monitor you run yourself. It supports HTTP, TCP, keyword, JSON query, ping, DNS and Docker checks, 20-second intervals, 90-plus notification services and multiple status pages.</p>
<p>The catch is obvious: if you host it on the same server as your app, it goes down with your app. Run it on a different provider or a small separate VM. The time you spend patching and backing it up is the real price.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-decision-rule">A decision rule<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#a-decision-rule" class="hash-link" aria-label="Direct link to A decision rule" title="Direct link to A decision rule" translate="no">​</a></h2>
<ol>
<li class="">Start with one hosted monitor on a different network from your app. UptimeRobot or HetrixTools takes ten minutes.</li>
<li class="">Add three checks: the marketing page, the login page, and a <code>/health</code> endpoint that touches your database.</li>
<li class="">Send alerts to a channel you read on your phone, not only email.</li>
<li class="">Add a second tool only when you have a reason, such as needing a one-minute interval or a branded status page.</li>
<li class="">Test the alert by taking a check offline on purpose and timing how long the message takes to arrive.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-to-monitor-beyond-the-homepage">What to monitor beyond the homepage<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#what-to-monitor-beyond-the-homepage" class="hash-link" aria-label="Direct link to What to monitor beyond the homepage" title="Direct link to What to monitor beyond the homepage" translate="no">​</a></h2>
<p>A homepage that returns 200 does not mean your product works. The most useful extra check for a SaaS with billing is the payment webhook path. If you built <a class="" href="https://dealpuffin.com/blog/general/how-to-test-stripe-webhooks-locally/">Stripe webhook handling</a>, add a heartbeat that your handler pings after each successful event, so silence becomes an alert.</p>
<p>Keep the number of checks low at first. Every check that fires without a real problem teaches you to ignore alerts.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="publishing-a-status-page">Publishing a status page<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#publishing-a-status-page" class="hash-link" aria-label="Direct link to Publishing a status page" title="Direct link to Publishing a status page" translate="no">​</a></h2>
<p>Once you have customers, a status page saves support email during an outage. All four options above offer one on the free tier, though limits differ. A status page is also a trust signal for buyers evaluating you, the same way a clear <a class="" href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/">pricing page</a> is.</p>
<p>If your product has real uptime data, you can also publish it as a proof point rather than a claim. Dealpuffin lets founders show provider-read readings such as uptime on a listing, with exact value, a band or hidden at their choice; you can start at <a href="https://dealpuffin.com/list" target="_blank" rel="noopener noreferrer" class="">dealpuffin.com/list</a>. It is one option among the status-page routes above, not a replacement for them.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-is-the-best-free-uptime-monitor-for-a-small-saas">What is the best free uptime monitor for a small SaaS?<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#what-is-the-best-free-uptime-monitor-for-a-small-saas" class="hash-link" aria-label="Direct link to What is the best free uptime monitor for a small SaaS?" title="Direct link to What is the best free uptime monitor for a small SaaS?" translate="no">​</a></h3>
<p>HetrixTools gives the fastest free interval (one minute) and UptimeRobot gives the most free monitors (50 at five minutes). Better Stack suits you if you want status pages and on-call in one place.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-use-a-free-uptime-monitor-for-a-commercial-product">Can I use a free uptime monitor for a commercial product?<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#can-i-use-a-free-uptime-monitor-for-a-commercial-product" class="hash-link" aria-label="Direct link to Can I use a free uptime monitor for a commercial product?" title="Direct link to Can I use a free uptime monitor for a commercial product?" translate="no">​</a></h3>
<p>UptimeRobot says its free plan is good for personal and commercial projects. Better Stack labels its free plan as for personal projects, so read its terms before relying on it for a paying product.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="is-self-hosting-uptime-kuma-a-good-idea">Is self-hosting Uptime Kuma a good idea?<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#is-self-hosting-uptime-kuma-a-good-idea" class="hash-link" aria-label="Direct link to Is self-hosting Uptime Kuma a good idea?" title="Direct link to Is self-hosting Uptime Kuma a good idea?" translate="no">​</a></h3>
<p>It is a good idea if you host it somewhere other than your app. If it shares a server with your product, an outage takes out the monitor too.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-often-should-an-uptime-monitor-check">How often should an uptime monitor check?<a href="https://dealpuffin.com/blog/general/free-uptime-monitoring-tools-for-indie-saas/#how-often-should-an-uptime-monitor-check" class="hash-link" aria-label="Direct link to How often should an uptime monitor check?" title="Direct link to How often should an uptime monitor check?" translate="no">​</a></h3>
<p>One to five minutes is enough for most early products. Faster intervals matter when an outage costs money every minute, which is rare before you have steady revenue.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="devtools" term="devtools"/>
        <category label="saas" term="saas"/>
        <category label="comparison" term="comparison"/>
        <category label="early-founders" term="early-founders"/>
        <category label="monitoring" term="monitoring"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[SaaS directories worth submitting your product to]]></title>
        <id>https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/</id>
        <link href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/"/>
        <updated>2026-11-10T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[A short list of launch sites and directories to submit a new SaaS to, with the rules that matter, a reusable submission kit and a rule for when to skip a listing.]]></summary>
        <content type="html"><![CDATA[<p>A new SaaS is worth submitting to a small set of places: Product Hunt, Show HN, the Indie Hackers product database, and one or two directories in your own niche. Prepare one submission kit once, reuse it everywhere, and skip any directory that charges for placement you cannot measure. Free directories cost an hour each, so the question is whether the audience there matches your buyer.</p>
<p>I only list sites whose rules I could read directly on 10 November 2026. I do not rank directories by traffic, because I could not verify those numbers.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="build-the-submission-kit-first">Build the submission kit first<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#build-the-submission-kit-first" class="hash-link" aria-label="Direct link to Build the submission kit first" title="Direct link to Build the submission kit first" translate="no">​</a></h2>
<p>Every directory asks for roughly the same things. Write them once.</p>
<ol>
<li class="">A one-line description under 80 characters that says who it is for and what it does.</li>
<li class="">A 250-word description with one concrete use case.</li>
<li class="">Three screenshots and one short demo video or GIF.</li>
<li class="">A logo in square format and a social image.</li>
<li class="">Your URL with a clear signup or try-it path and no broken links.</li>
<li class="">A founder name and photo, since most communities favour real makers.</li>
</ol>
<p>Keep a document with these. A submission that takes ten minutes gets done; one that needs new copy each time gets skipped.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-sites-worth-the-hour">The sites worth the hour<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#the-sites-worth-the-hour" class="hash-link" aria-label="Direct link to The sites worth the hour" title="Direct link to The sites worth the hour" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="product-hunt">Product Hunt<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#product-hunt" class="hash-link" aria-label="Direct link to Product Hunt" title="Direct link to Product Hunt" translate="no">​</a></h3>
<p><a href="https://www.producthunt.com/launch" target="_blank" rel="noopener noreferrer" class="">Product Hunt</a> is free to use. Makers submit products, the community upvotes and comments, and products compete on a daily leaderboard. Its one hard rule is that you cannot directly ask people to upvote; ask them to visit and comment instead. You can launch again when you have a significant new iteration, so you do not have to spend your only shot on version one.</p>
<p>Best for: products with a visual demo and a maker who can spend launch day answering comments. The comparison in <a class="" href="https://dealpuffin.com/blog/general/show-hn-vs-product-hunt-for-early-saas/">Show HN vs Product Hunt</a> goes deeper on fit.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="show-hn">Show HN<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#show-hn" class="hash-link" aria-label="Direct link to Show HN" title="Direct link to Show HN" translate="no">​</a></h3>
<p>The <a href="https://news.ycombinator.com/showhn.html" target="_blank" rel="noopener noreferrer" class="">Show HN guidelines</a> say the project must be something you worked on personally, non-trivial, and something people can try, ideally without barriers like signups or emails. Blog posts, sign-up pages and newsletters are off topic. The community accepts early-stage work.</p>
<p>Best for: developer tools and technical products where a reader can try the thing in a minute.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="indie-hackers">Indie Hackers<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#indie-hackers" class="hash-link" aria-label="Direct link to Indie Hackers" title="Direct link to Indie Hackers" translate="no">​</a></h3>
<p><a href="https://www.indiehackers.com/" target="_blank" rel="noopener noreferrer" class="">Indie Hackers</a> has a products database with an "Add Yours" option, alongside a discussion feed where founders post progress and ask for feedback. The listing is a permanent page; the discussion posts are where conversations happen. Write posts that share a lesson or a number from your own work rather than a link drop.</p>
<p>Best for: bootstrapped products where buyers are other founders.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="dealpuffin">Dealpuffin<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#dealpuffin" class="hash-link" aria-label="Direct link to Dealpuffin" title="Direct link to Dealpuffin" translate="no">​</a></h3>
<p><a href="https://dealpuffin.com/list" target="_blank" rel="noopener noreferrer" class="">Dealpuffin</a> is free to list, with no application or revenue minimum. You submit a URL, verify domain ownership, connect Stripe, Paddle or Polar with a read-only key, and publish the coupons you choose. It does not take the payment or redeem the code. Proof points such as MRR or uptime are optional. I am listing it here as one path among several, and I make no claim about search or traffic value from a listing.</p>
<p>Best for: products that can offer a real discount and want it backed by a provider integration.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="niche-directories-a-screening-rule">Niche directories: a screening rule<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#niche-directories-a-screening-rule" class="hash-link" aria-label="Direct link to Niche directories: a screening rule" title="Direct link to Niche directories: a screening rule" translate="no">​</a></h2>
<p>Beyond the four above, there are hundreds of directories. Use this checklist before spending time on one.</p>
<ol>
<li class="">Is it free to submit? If it charges, find out what you get and whether it can be measured.</li>
<li class="">Does it show real products with working links? Empty or broken pages signal a dead site.</li>
<li class="">Is it about your category? A directory for developer tools suits a developer tool; a generic list of "startups" rarely sends buyers.</li>
<li class="">Can you describe the last three listings added? If recent activity is zero, skip it.</li>
</ol>
<p>Do not expect a link from a directory to carry search value on its own. Treat each listing as a place a human might find you, and measure referrals in your analytics to see which ones do. The guide on <a class="" href="https://dealpuffin.com/blog/general/how-to-get-backlinks-for-a-new-saas-site/">getting backlinks for a new SaaS site</a> covers links that tend to matter more.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="order-of-operations">Order of operations<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#order-of-operations" class="hash-link" aria-label="Direct link to Order of operations" title="Direct link to Order of operations" translate="no">​</a></h2>
<p>Submit to the sites with the strongest communities on days when you can respond. Then add directories in batches of two or three, and write down the date and the referral count from each after a month. Drop what produced nothing.</p>
<p>If you have no users yet, the better first step may be direct conversations; <a class="" href="https://dealpuffin.com/blog/general/how-to-get-your-first-100-users-for-a-saas/">how to get your first 100 users</a> lays out that route.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="which-directories-should-a-new-saas-submit-to-first">Which directories should a new SaaS submit to first?<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#which-directories-should-a-new-saas-submit-to-first" class="hash-link" aria-label="Direct link to Which directories should a new SaaS submit to first?" title="Direct link to Which directories should a new SaaS submit to first?" translate="no">​</a></h3>
<p>Start with Product Hunt, Show HN if your product is easy to try, and the Indie Hackers products database, then add one or two directories in your own niche. These cost nothing but time.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="are-paid-saas-directories-worth-it">Are paid SaaS directories worth it?<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#are-paid-saas-directories-worth-it" class="hash-link" aria-label="Direct link to Are paid SaaS directories worth it?" title="Direct link to Are paid SaaS directories worth it?" translate="no">​</a></h3>
<p>Only if you can see what you get and measure referrals from it. Without that, treat a paid placement as a guess and prefer free options first.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-ask-friends-to-upvote-my-product-hunt-launch">Can I ask friends to upvote my Product Hunt launch?<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#can-i-ask-friends-to-upvote-my-product-hunt-launch" class="hash-link" aria-label="Direct link to Can I ask friends to upvote my Product Hunt launch?" title="Direct link to Can I ask friends to upvote my Product Hunt launch?" translate="no">​</a></h3>
<p>Product Hunt says you cannot directly ask people to upvote. It suggests asking them to visit and comment instead.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-directory-links-help-seo">Do directory links help SEO?<a href="https://dealpuffin.com/blog/general/saas-directories-worth-submitting-your-product-to/#do-directory-links-help-seo" class="hash-link" aria-label="Direct link to Do directory links help SEO?" title="Direct link to Do directory links help SEO?" translate="no">​</a></h3>
<p>It is uncertain, and I would not plan around it. Judge a directory by the visitors it sends, which you can measure in analytics.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="go-to-market" term="go-to-market"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
        <category label="launch" term="launch"/>
        <category label="listicle" term="listicle"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Usage-based vs seat-based pricing for AI products]]></title>
        <id>https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/</id>
        <link href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/"/>
        <updated>2026-11-10T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Seats, usage or outcomes? How Intercom Fin and GitHub Copilot price AI features, and a decision rule for choosing a model based on your cost curve and buyer.]]></summary>
        <content type="html"><![CDATA[<p>Use seat-based pricing when each person gets their own value and your cost per user is stable. Use usage-based pricing when your cost rises with every request, which is usually true of AI features. Many AI products land on a hybrid: a seat price that includes a pool of usage, with paid overage after that. Intercom and GitHub both do versions of this, and their pricing pages show how.</p>
<p>Facts below come from vendor pages read on 10 November 2026. Prices change, so confirm before copying a number.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="why-ai-products-strain-seat-pricing">Why AI products strain seat pricing<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#why-ai-products-strain-seat-pricing" class="hash-link" aria-label="Direct link to Why AI products strain seat pricing" title="Direct link to Why AI products strain seat pricing" translate="no">​</a></h2>
<p>A normal SaaS feature costs you almost nothing extra when a user clicks it twice as often. An AI feature does: every call has a model cost. Under flat seat pricing, one heavy user can cost you more than the seat brings in, while a light user subsidises them. That is the core tension.</p>
<p>The opposite risk is real too. Pure usage pricing makes bills unpredictable, and buyers dislike not knowing what they will owe next month.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-three-models">The three models<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#the-three-models" class="hash-link" aria-label="Direct link to The three models" title="Direct link to The three models" translate="no">​</a></h2>
<table><thead><tr><th>Model</th><th>You charge for</th><th>Works well when</th><th>Main risk</th></tr></thead><tbody><tr><td>Seat-based</td><td>Each named user per month</td><td>Value is per person; usage varies little</td><td>Heavy users erode margin</td></tr><tr><td>Usage-based</td><td>Units consumed (requests, tokens, credits)</td><td>Cost scales with use; buyers think in units</td><td>Bill shock; metering work</td></tr><tr><td>Outcome-based</td><td>A successful result</td><td>You can define and verify a result</td><td>Disputes over what counts</td></tr></tbody></table>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="example-1-intercoms-fin-charges-per-outcome">Example 1: Intercom's Fin charges per outcome<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#example-1-intercoms-fin-charges-per-outcome" class="hash-link" aria-label="Direct link to Example 1: Intercom's Fin charges per outcome" title="Direct link to Example 1: Intercom's Fin charges per outcome" translate="no">​</a></h2>
<p>On its <a href="https://fin.ai/pricing" target="_blank" rel="noopener noreferrer" class="">pricing page</a>, Fin AI Agent is priced at $0.99 per outcome. A billable outcome is a resolution (no further help requested), a completed procedure handoff, a disqualification or a self-serve routing, and the page lists qualifications at $9.99. Intercom's helpdesk separately charges per seat, listed from $19 per helpdesk seat per month, so the company combines both models: seats for the humans, outcomes for the AI.</p>
<p>The lesson is that you can price the AI part on the thing the buyer cares about while keeping seat pricing for the part that behaves like normal software. It only works because "resolved" is something you can define and report on.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="example-2-github-copilot-sells-seats-with-a-credit-pool">Example 2: GitHub Copilot sells seats with a credit pool<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#example-2-github-copilot-sells-seats-with-a-credit-pool" class="hash-link" aria-label="Direct link to Example 2: GitHub Copilot sells seats with a credit pool" title="Direct link to Example 2: GitHub Copilot sells seats with a credit pool" translate="no">​</a></h2>
<p><a href="https://github.com/features/copilot/plans" target="_blank" rel="noopener noreferrer" class="">GitHub Copilot's plans</a> list Pro at $10 per user per month and Pro+ at $39, each with a monthly allowance of GitHub AI Credits (the page lists $15 and $70 of credits respectively). One credit equals $0.01, and when you hit the limit you can wait for the reset, set a dollar budget for extra usage, or switch to a cheaper model.</p>
<p>This is the hybrid most AI tools settle on: a predictable seat price, a usage allowance sized so the typical user never notices it, and metered overage for the heavy tail.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="a-decision-rule">A decision rule<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#a-decision-rule" class="hash-link" aria-label="Direct link to A decision rule" title="Direct link to A decision rule" translate="no">​</a></h2>
<p>Ask three questions in order.</p>
<ol>
<li class="">Does your marginal cost per use matter? If one request costs you real money, you need some usage component. If it costs you fractions of a cent, a flat seat may be fine.</li>
<li class="">Who is the buyer, and what do they budget for? Teams buying for employees expect per-seat prices they can multiply by headcount. Teams buying automation expect to pay per result.</li>
<li class="">Can you measure the unit honestly? If you cannot show a customer exactly what they were charged for, do not use usage pricing yet.</li>
</ol>
<p>If the answers are "yes, yes, no", start with seats and a fair-use limit, then add metering when you can show it. The earlier post on <a class="" href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/">pricing a SaaS product at the early stage</a> covers the value-metric choice in more depth.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="worked-example">Worked example<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#worked-example" class="hash-link" aria-label="Direct link to Worked example" title="Direct link to Worked example" translate="no">​</a></h2>
<p>Say your AI feature costs you about $0.02 per run and you charge $20 per seat per month.</p>
<ul>
<li class="">A light user runs it 100 times: $2 of cost, $18 margin before fees.</li>
<li class="">A heavy user runs it 2,000 times: $40 of cost, a $20 loss on that seat.</li>
</ul>
<p>A hybrid fixes this without scaring buyers. Include 500 runs per seat, which covers the typical user, and charge overage per extra 100 runs. Most customers never see an overage, and the heavy user pays for what they use. The numbers here are my own illustration, not a benchmark.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-you-need-to-build">What you need to build<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#what-you-need-to-build" class="hash-link" aria-label="Direct link to What you need to build" title="Direct link to What you need to build" translate="no">​</a></h2>
<p>Seat pricing needs a subscription and a way to count active users. Usage pricing needs meters that record events, a way to aggregate them each billing period, and an invoice that explains them. Stripe documents this in its <a href="https://docs.stripe.com/billing/subscriptions/usage-based" target="_blank" rel="noopener noreferrer" class="">basic usage-based billing guide</a>, and notes that Metronome, now part of Stripe, is its recommended starting point for new usage-based integrations. For tooling options after that acquisition, see <a class="" href="https://dealpuffin.com/blog/general/usage-based-billing-after-metronome-and-orb/">usage-based billing after Metronome and Orb</a>.</p>
<p>Add spending alerts and limits from the start. Intercom and GitHub both let customers set budgets, which is what makes unpredictable bills acceptable.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="who-should-pick-what">Who should pick what<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#who-should-pick-what" class="hash-link" aria-label="Direct link to Who should pick what" title="Direct link to Who should pick what" translate="no">​</a></h2>
<ul>
<li class="">Solo tool with light AI use: seats, with a stated fair-use limit.</li>
<li class="">AI is the product and cost scales with use: usage or credits, with a monthly minimum so revenue is predictable.</li>
<li class="">AI replaces a measurable task: consider outcome pricing, but only if you can verify the outcome.</li>
<li class="">Unsure: hybrid, with seats plus an included allowance.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-an-ai-saas-charge-per-seat-or-per-usage">Should an AI SaaS charge per seat or per usage?<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#should-an-ai-saas-charge-per-seat-or-per-usage" class="hash-link" aria-label="Direct link to Should an AI SaaS charge per seat or per usage?" title="Direct link to Should an AI SaaS charge per seat or per usage?" translate="no">​</a></h3>
<p>Charge per seat if value and cost are per person and stable. Charge per usage if each request costs you money and customers think in units. A hybrid of seat plus included usage is the most common answer.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="what-is-outcome-based-pricing">What is outcome-based pricing?<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#what-is-outcome-based-pricing" class="hash-link" aria-label="Direct link to What is outcome-based pricing?" title="Direct link to What is outcome-based pricing?" translate="no">​</a></h3>
<p>It means charging only when the product delivers a defined result. Intercom lists $0.99 per Fin outcome, where an outcome is a resolution, procedure handoff, disqualification or self-serve routing.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-do-i-avoid-bill-shock-with-usage-pricing">How do I avoid bill shock with usage pricing?<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#how-do-i-avoid-bill-shock-with-usage-pricing" class="hash-link" aria-label="Direct link to How do I avoid bill shock with usage pricing?" title="Direct link to How do I avoid bill shock with usage pricing?" translate="no">​</a></h3>
<p>Include an allowance in the base price, show usage in the product, and let customers set alerts and spending limits. GitHub Copilot and Intercom both offer budget controls.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-i-need-special-billing-software-for-usage-based-pricing">Do I need special billing software for usage-based pricing?<a href="https://dealpuffin.com/blog/general/usage-based-vs-seat-based-pricing-for-ai-products/#do-i-need-special-billing-software-for-usage-based-pricing" class="hash-link" aria-label="Direct link to Do I need special billing software for usage-based pricing?" title="Direct link to Do I need special billing software for usage-based pricing?" translate="no">​</a></h3>
<p>You need metering and invoicing that handle events, which Stripe supports through its meters API and Metronome. A simple product can start with seats and add metering later.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="pricing" term="pricing"/>
        <category label="saas" term="saas"/>
        <category label="ai" term="ai"/>
        <category label="billing" term="billing"/>
        <category label="comparison" term="comparison"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to add FAQ schema to a Docusaurus blog (and what it still does)]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/"/>
        <updated>2026-11-09T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Add FAQPage JSON-LD to Docusaurus blog posts with a remark plugin and a wrapped BlogPostPage. Includes code, validation steps, and what Google's 2026 FAQ change means.]]></summary>
        <content type="html"><![CDATA[<p>To add FAQ schema to a Docusaurus blog, write each post's FAQ as a <code>## Frequently asked questions</code> section with <code>###</code> question headings, add a remark plugin that exports those pairs from the compiled MDX, and wrap <code>BlogPostPage</code> so it prints them as <code>FAQPage</code> JSON-LD in the page head. You edit one plugin and one wrapper once, and every later post gets the markup from its own text.</p>
<p>Before you spend an afternoon on it, know that Google stopped showing FAQ rich results on 7 May 2026, so the markup no longer earns a visible search feature. This guide shows the build and then covers what is still worth doing. Google's documentation was read on 9 November 2026.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="what-changed-at-google">What changed at Google<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#what-changed-at-google" class="hash-link" aria-label="Direct link to What changed at Google" title="Direct link to What changed at Google" translate="no">​</a></h2>
<p>Google's <a href="https://developers.google.com/search/updates" target="_blank" rel="noopener noreferrer" class="">Search documentation changelog</a> says the FAQ rich result feature stopped appearing in Google Search starting 7 May 2026, and that the documentation page was removed in June. Since August 2023 the feature had only been shown for well-known government and health sites, so most blogs never saw it anyway.</p>
<p>Valid <code>FAQPage</code> markup is still a schema.org type, and leaving it on a page does no harm. What you should not expect is a rich result. The reasons left to add it are cheap ones: it forces every post to carry clean question-and-answer pairs, and the data sits in a machine-readable form for any tool that wants it. Whether a particular AI search product uses it is not documented, so treat that as unproven. Our post on <a class="" href="https://dealpuffin.com/blog/general/does-llms-txt-help-ai-citations/">whether llms.txt helps AI citations</a> takes the same approach to another unproven signal.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="the-approach-in-three-parts">The approach in three parts<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#the-approach-in-three-parts" class="hash-link" aria-label="Direct link to The approach in three parts" title="Direct link to The approach in three parts" translate="no">​</a></h2>
<p>Docusaurus has no built-in FAQ field, so the setup has three pieces:</p>
<ol>
<li class="">A convention in your Markdown: one <code>## Frequently asked questions</code> heading, then <code>### Question?</code> headings, each followed by the answer.</li>
<li class="">A remark plugin that reads that section at build time and exports it as <code>faqs</code> from the compiled page.</li>
<li class="">A swizzled wrapper around <code>BlogPostPage</code> that reads <code>faqs</code> and renders the JSON-LD script.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-1-write-the-faq-in-plain-markdown">Step 1: write the FAQ in plain Markdown<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#step-1-write-the-faq-in-plain-markdown" class="hash-link" aria-label="Direct link to Step 1: write the FAQ in plain Markdown" title="Direct link to Step 1: write the FAQ in plain Markdown" translate="no">​</a></h2>
<div class="language-md codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-md codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token title important punctuation" style="color:rgb(248, 248, 242)">##</span><span class="token title important"> Frequently asked questions</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token title important punctuation" style="color:rgb(248, 248, 242)">###</span><span class="token title important"> Does this need a plugin from npm?</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">No. A short local remark plugin is enough.</span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token title important punctuation" style="color:rgb(248, 248, 242)">###</span><span class="token title important"> Can I reuse it for docs pages?</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">Yes. Add the same plugin to the docs preset options.</span><br></div></code></pre></div></div>
<p>The text stays in the post body, so readers see the same answers the markup describes. Google's structured data rules have long required that marked-up content be visible on the page, and this approach satisfies that without extra work.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-2-the-remark-plugin">Step 2: the remark plugin<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#step-2-the-remark-plugin" class="hash-link" aria-label="Direct link to Step 2: the remark plugin" title="Direct link to Step 2: the remark plugin" translate="no">​</a></h2>
<p>Create <code>src/remark/blogFaqExport.mjs</code>. The plugin walks the top-level nodes, finds the FAQ heading, collects each <code>###</code> question and the paragraphs below it, and appends an <code>export const faqs = ...</code> node. A minimal version looks like this:</p>
<div class="language-js codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-js codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> </span><span class="token constant" style="color:rgb(189, 147, 249)">FAQ_HEADING</span><span class="token plain"> </span><span class="token operator">=</span><span class="token plain"> </span><span class="token regex regex-delimiter">/</span><span class="token regex regex-source language-regex anchor function" style="color:rgb(80, 250, 123)">^</span><span class="token regex regex-source language-regex group punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token regex regex-source language-regex">frequently asked questions</span><span class="token regex regex-source language-regex alternation keyword" style="color:rgb(189, 147, 249);font-style:italic">|</span><span class="token regex regex-source language-regex">faqs</span><span class="token regex regex-source language-regex quantifier number">?</span><span class="token regex regex-source language-regex group punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token regex regex-source language-regex anchor function" style="color:rgb(80, 250, 123)">\b</span><span class="token regex regex-delimiter">/</span><span class="token regex regex-flags">i</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> </span><span class="token function-variable function" style="color:rgb(80, 250, 123)">text</span><span class="token plain"> </span><span class="token operator">=</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token parameter">node</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token arrow operator">=&gt;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  node</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">value</span><span class="token plain"> </span><span class="token operator">??</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">node</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">children</span><span class="token plain"> </span><span class="token operator">??</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">[</span><span class="token punctuation" style="color:rgb(248, 248, 242)">]</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">map</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">text</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">join</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token string" style="color:rgb(255, 121, 198)">''</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token keyword module" style="color:rgb(189, 147, 249);font-style:italic">export</span><span class="token plain"> </span><span class="token keyword module" style="color:rgb(189, 147, 249);font-style:italic">default</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">function</span><span class="token plain"> </span><span class="token function" style="color:rgb(80, 250, 123)">blogFaqExport</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">return</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token parameter">root</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token arrow operator">=&gt;</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> kids </span><span class="token operator">=</span><span class="token plain"> root</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">children</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> start </span><span class="token operator">=</span><span class="token plain"> kids</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">findIndex</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token parameter">n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token arrow operator">=&gt;</span><span class="token plain"> n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">type</span><span class="token plain"> </span><span class="token operator">===</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'heading'</span><span class="token plain"> </span><span class="token operator">&amp;&amp;</span><span class="token plain"> n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">depth</span><span class="token plain"> </span><span class="token operator">===</span><span class="token plain"> </span><span class="token number">2</span><span class="token plain"> </span><span class="token operator">&amp;&amp;</span><span class="token plain"> </span><span class="token constant" style="color:rgb(189, 147, 249)">FAQ_HEADING</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">test</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token function" style="color:rgb(80, 250, 123)">text</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">if</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">start </span><span class="token operator">===</span><span class="token plain"> </span><span class="token operator">-</span><span class="token number">1</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">return</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> faqs </span><span class="token operator">=</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">[</span><span class="token punctuation" style="color:rgb(248, 248, 242)">]</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">let</span><span class="token plain"> current </span><span class="token operator">=</span><span class="token plain"> </span><span class="token keyword null nil" style="color:rgb(189, 147, 249);font-style:italic">null</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">for</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> n </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">of</span><span class="token plain"> kids</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">slice</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">start </span><span class="token operator">+</span><span class="token plain"> </span><span class="token number">1</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">if</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">type</span><span class="token plain"> </span><span class="token operator">===</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'heading'</span><span class="token plain"> </span><span class="token operator">&amp;&amp;</span><span class="token plain"> n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">depth</span><span class="token plain"> </span><span class="token operator">&lt;=</span><span class="token plain"> </span><span class="token number">2</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">break</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">if</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">type</span><span class="token plain"> </span><span class="token operator">===</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'heading'</span><span class="token plain"> </span><span class="token operator">&amp;&amp;</span><span class="token plain"> n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">depth</span><span class="token plain"> </span><span class="token operator">===</span><span class="token plain"> </span><span class="token number">3</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        current </span><span class="token operator">=</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token literal-property property">question</span><span class="token operator">:</span><span class="token plain"> </span><span class="token function" style="color:rgb(80, 250, 123)">text</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">trim</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"> </span><span class="token literal-property property">answer</span><span class="token operator">:</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">''</span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        faqs</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">push</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">current</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token plain"> </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">else</span><span class="token plain"> </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">if</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">current</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        current</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">answer</span><span class="token plain"> </span><span class="token operator">+=</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">' '</span><span class="token plain"> </span><span class="token operator">+</span><span class="token plain"> </span><span class="token function" style="color:rgb(80, 250, 123)">text</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">n</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">trim</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">if</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token operator">!</span><span class="token plain">faqs</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">length</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token keyword control-flow" style="color:rgb(189, 147, 249);font-style:italic">return</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> json </span><span class="token operator">=</span><span class="token plain"> </span><span class="token known-class-name class-name">JSON</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">stringify</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">faqs</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    root</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">children</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">push</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token literal-property property">type</span><span class="token operator">:</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'mdxjsEsm'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token literal-property property">value</span><span class="token operator">:</span><span class="token plain"> </span><span class="token template-string template-punctuation string" style="color:rgb(255, 121, 198)">`</span><span class="token template-string string" style="color:rgb(255, 121, 198)">export const faqs = JSON.parse(</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:rgb(248, 248, 242)">${</span><span class="token template-string interpolation known-class-name class-name">JSON</span><span class="token template-string interpolation punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token template-string interpolation method function property-access" style="color:rgb(80, 250, 123)">stringify</span><span class="token template-string interpolation punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token template-string interpolation">json</span><span class="token template-string interpolation punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token template-string string" style="color:rgb(255, 121, 198)">);</span><span class="token template-string template-punctuation string" style="color:rgb(255, 121, 198)">`</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token comment" style="color:rgb(98, 114, 164)">// MDX also needs an estree for the node; see the note below.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><br></div></code></pre></div></div>
<p>The MDX compiler wants a parsed <code>estree</code> on any <code>mdxjsEsm</code> node you inject, so the production version of this plugin builds an <code>ExportNamedDeclaration</code> by hand. If you would rather not write that tree, <code>estree-util-value-to-estree</code> or a call to <code>acorn</code> on the <code>value</code> string produces it. Whichever route you pick, test with a post that has no FAQ section too; the plugin should return without adding anything.</p>
<p>Register it in <code>docusaurus.config.ts</code> for the blog, and for docs if you want it there:</p>
<div class="language-ts codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-ts codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">import</span><span class="token plain"> blogFaqExport </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">from</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'./src/remark/blogFaqExport.mjs'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token comment" style="color:rgb(98, 114, 164)">// inside presets -&gt; classic options</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">blog</span><span class="token operator">:</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"> remarkPlugins</span><span class="token operator">:</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">[</span><span class="token plain">blogFaqExport</span><span class="token punctuation" style="color:rgb(248, 248, 242)">]</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">docs</span><span class="token operator">:</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"> remarkPlugins</span><span class="token operator">:</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">[</span><span class="token plain">blogFaqExport</span><span class="token punctuation" style="color:rgb(248, 248, 242)">]</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><br></div></code></pre></div></div>
<p>If you run a second blog instance through <code>@docusaurus/plugin-content-blog</code>, give that instance the same <code>remarkPlugins</code> entry.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-3-wrap-blogpostpage-and-print-the-json-ld">Step 3: wrap BlogPostPage and print the JSON-LD<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#step-3-wrap-blogpostpage-and-print-the-json-ld" class="hash-link" aria-label="Direct link to Step 3: wrap BlogPostPage and print the JSON-LD" title="Direct link to Step 3: wrap BlogPostPage and print the JSON-LD" translate="no">​</a></h2>
<p>Run the swizzle command in wrap mode so you keep the original component and only add around it:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token plain">npm run swizzle @docusaurus/theme-classic BlogPostPage -- --wrap</span><br></div></code></pre></div></div>
<p>Docusaurus's <a href="https://docusaurus.io/docs/swizzling" target="_blank" rel="noopener noreferrer" class="">swizzling guide</a> recommends wrapping over ejecting where you can, because a wrapper survives theme upgrades better. Then edit <code>src/theme/BlogPostPage/index.tsx</code>:</p>
<div class="language-tsx codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-tsx codeBlock_bY9V thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#F8F8F2"><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">import</span><span class="token plain"> </span><span class="token imports maybe-class-name">React</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">from</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'react'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">import</span><span class="token plain"> </span><span class="token imports maybe-class-name">Head</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">from</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'@docusaurus/Head'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">import</span><span class="token plain"> </span><span class="token imports maybe-class-name">BlogPostPage</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">from</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'@theme-original/BlogPostPage'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">export</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">default</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">function</span><span class="token plain"> </span><span class="token function" style="color:rgb(80, 250, 123)">BlogPostPageWrapper</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">props</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> faqs </span><span class="token operator">=</span><span class="token plain"> props</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">content</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">faqs</span><span class="token plain"> </span><span class="token operator">??</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">[</span><span class="token punctuation" style="color:rgb(248, 248, 242)">]</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">const</span><span class="token plain"> faqPage </span><span class="token operator">=</span><span class="token plain"> faqs</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">length</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token operator">?</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        </span><span class="token string-property property">'@context'</span><span class="token operator">:</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'https://schema.org'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        </span><span class="token string-property property">'@type'</span><span class="token operator">:</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'FAQPage'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        mainEntity</span><span class="token operator">:</span><span class="token plain"> faqs</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token method function property-access" style="color:rgb(80, 250, 123)">map</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain">f</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token arrow operator">=&gt;</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">          </span><span class="token string-property property">'@type'</span><span class="token operator">:</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'Question'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">          name</span><span class="token operator">:</span><span class="token plain"> f</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">question</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">          acceptedAnswer</span><span class="token operator">:</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token string-property property">'@type'</span><span class="token operator">:</span><span class="token plain"> </span><span class="token string" style="color:rgb(255, 121, 198)">'Answer'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"> text</span><span class="token operator">:</span><span class="token plain"> f</span><span class="token punctuation" style="color:rgb(248, 248, 242)">.</span><span class="token property-access">answer</span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token operator">:</span><span class="token plain"> </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">null</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token keyword" style="color:rgb(189, 147, 249);font-style:italic">return</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">    </span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&lt;</span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&gt;</span><span class="token plain-text"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain-text">      </span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token plain">faqPage </span><span class="token operator">&amp;&amp;</span><span class="token plain"> </span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">        </span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&lt;</span><span class="token tag class-name" style="color:rgb(255, 121, 198)">Head</span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&gt;</span><span class="token plain-text"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain-text">          </span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&lt;</span><span class="token tag" style="color:rgb(255, 121, 198)">script</span><span class="token tag" style="color:rgb(255, 121, 198)"> </span><span class="token tag attr-name" style="color:rgb(241, 250, 140)">type</span><span class="token tag attr-value punctuation attr-equals" style="color:rgb(248, 248, 242)">=</span><span class="token tag attr-value punctuation" style="color:rgb(248, 248, 242)">"</span><span class="token tag attr-value" style="color:rgb(255, 121, 198)">application/ld+json</span><span class="token tag attr-value punctuation" style="color:rgb(248, 248, 242)">"</span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&gt;</span><span class="token plain-text">{JSON.stringify(faqPage)}</span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&lt;/</span><span class="token tag" style="color:rgb(255, 121, 198)">script</span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&gt;</span><span class="token plain-text"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain-text">        </span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&lt;/</span><span class="token tag class-name" style="color:rgb(255, 121, 198)">Head</span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&gt;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">      </span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token plain-text"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain-text">      </span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&lt;</span><span class="token tag class-name" style="color:rgb(255, 121, 198)">BlogPostPage</span><span class="token tag" style="color:rgb(255, 121, 198)"> </span><span class="token tag spread punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token tag spread operator" style="color:rgb(255, 121, 198)">...</span><span class="token tag spread" style="color:rgb(255, 121, 198)">props</span><span class="token tag spread punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token tag" style="color:rgb(255, 121, 198)"> </span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">/&gt;</span><span class="token plain-text"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain-text">    </span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&lt;/</span><span class="token tag punctuation" style="color:rgb(248, 248, 242)">&gt;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain">  </span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#F8F8F2"><span class="token plain"></span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><br></div></code></pre></div></div>
<p><code>props.content</code> is the compiled MDX module, which is why a named export from the plugin shows up as <code>content.faqs</code>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="check-that-it-works">Check that it works<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#check-that-it-works" class="hash-link" aria-label="Direct link to Check that it works" title="Direct link to Check that it works" translate="no">​</a></h2>
<ol>
<li class="">Run <code>npm run build</code>. A build catches MDX errors from a malformed injected node.</li>
<li class="">Open <code>build/blog/&lt;your-post&gt;/index.html</code> and search for <code>"@type":"FAQPage"</code>. The script should be in the head, and the question count should match your headings.</li>
<li class="">Paste the live URL into the <a href="https://validator.schema.org/" target="_blank" rel="noopener noreferrer" class="">Schema Markup Validator</a>. Google's Rich Results Test dropped FAQ support in June 2026, so use the schema.org validator for syntax.</li>
<li class="">Check a post without an FAQ section and confirm it has no <code>FAQPage</code> script.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="mistakes-to-avoid">Mistakes to avoid<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#mistakes-to-avoid" class="hash-link" aria-label="Direct link to Mistakes to avoid" title="Direct link to Mistakes to avoid" translate="no">​</a></h2>
<p>Keep answers to one to three sentences. Long answers are harder to quote and make the JSON-LD bulky. Do not add questions that appear only in the markup. Strip links and formatting down to plain text in the plugin, since the schema <code>text</code> field is plain. And put the FAQ last in the post; the plugin stops at the next <code>##</code> heading, so a section after it is safe, but a stray <code>##</code> inside the FAQ cuts it short.</p>
<p>If you are also deciding what to measure on the site, see <a class="" href="https://dealpuffin.com/blog/general/posthog-vs-plausible-vs-ga4-for-early-stage-saas/">PostHog vs Plausible vs GA4 for an early-stage SaaS</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="does-google-still-show-faq-rich-results">Does Google still show FAQ rich results?<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#does-google-still-show-faq-rich-results" class="hash-link" aria-label="Direct link to Does Google still show FAQ rich results?" title="Direct link to Does Google still show FAQ rich results?" translate="no">​</a></h3>
<p>No. Google's changelog says the FAQ rich result feature stopped appearing in Search starting 7 May 2026. Before that it was limited to well-known government and health sites.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="is-faqpage-markup-still-valid">Is FAQPage markup still valid?<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#is-faqpage-markup-still-valid" class="hash-link" aria-label="Direct link to Is FAQPage markup still valid?" title="Direct link to Is FAQPage markup still valid?" translate="no">​</a></h3>
<p>Yes. It is still a schema.org type and validators accept it. It just no longer produces a Google search feature.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="do-i-need-to-swizzle-docusaurus-to-add-faq-schema">Do I need to swizzle Docusaurus to add FAQ schema?<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#do-i-need-to-swizzle-docusaurus-to-add-faq-schema" class="hash-link" aria-label="Direct link to Do I need to swizzle Docusaurus to add FAQ schema?" title="Direct link to Do I need to swizzle Docusaurus to add FAQ schema?" translate="no">​</a></h3>
<p>You need some way to place a script in the page head. Wrapping <code>BlogPostPage</code> is the lightest option; another is a <code>&lt;Head&gt;</code> block inside each MDX file, which means repeating the JSON by hand in every post.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-the-same-plugin-work-for-docs-pages">Can the same plugin work for docs pages?<a href="https://dealpuffin.com/blog/general/how-to-add-faq-schema-to-a-docusaurus-blog/#can-the-same-plugin-work-for-docs-pages" class="hash-link" aria-label="Direct link to Can the same plugin work for docs pages?" title="Direct link to Can the same plugin work for docs pages?" translate="no">​</a></h3>
<p>Yes. Add it to the docs <code>remarkPlugins</code> list and wrap the docs page component the same way, reading <code>content.faqs</code>.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="devtools" term="devtools"/>
        <category label="seo" term="seo"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
        <category label="guide" term="guide"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[How to price a SaaS product at the early stage: a decision rule]]></title>
        <id>https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/</id>
        <link href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/"/>
        <updated>2026-11-09T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Pick a value metric, set three tiers, and test the price with real buyers before launch. Includes a worked example and the fee drag that low prices carry on small plans.]]></summary>
        <content type="html"><![CDATA[<p>To price an early-stage SaaS product, choose one value metric that grows with the benefit a customer gets, anchor the price to the cost of the problem it replaces, offer two or three simple tiers, and test the number in conversations with real buyers before you build the billing. Expect to change the price in the first year, and keep the first customers' price fixed for a stated period so changing it stays fair.</p>
<p>This guide is a method, not a benchmark. Pricing data differs a lot between markets, and I cite only vendor documentation for the facts below, read on 9 November 2026.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-1-pick-the-value-metric">Step 1: pick the value metric<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#step-1-pick-the-value-metric" class="hash-link" aria-label="Direct link to Step 1: pick the value metric" title="Direct link to Step 1: pick the value metric" translate="no">​</a></h2>
<p>The value metric is what you count to charge: seats, projects, events, API calls, tracked pages. Stripe's documentation on <a href="https://docs.stripe.com/products-prices/pricing-models" target="_blank" rel="noopener noreferrer" class="">recurring pricing models</a> lists the common shapes: flat rate (a tier at a fixed price), per-seat, tiered (price per unit changes with quantity), and usage-based.</p>
<p>A useful test: if a customer gets twice the benefit, would they accept paying more? If yes, that unit is a candidate.</p>
<ul>
<li class="">Per-seat suits tools that each person on a team uses separately.</li>
<li class="">Flat tiers suit products where usage is hard to meter or customers dislike surprise bills.</li>
<li class="">Usage-based suits products whose cost to you rises with use, such as AI calls or data processing. It brings more engineering work: you need metering, and invoices that vary. The post on <a class="" href="https://dealpuffin.com/blog/general/usage-based-billing-after-metronome-and-orb/">usage-based billing after Metronome and Orb</a> covers the tools.</li>
</ul>
<p>If you are unsure, start with flat tiers and a usage limit on the lowest one. They are the easiest to explain and the easiest to build.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-2-anchor-to-the-problem-you-replace">Step 2: anchor to the problem you replace<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#step-2-anchor-to-the-problem-you-replace" class="hash-link" aria-label="Direct link to Step 2: anchor to the problem you replace" title="Direct link to Step 2: anchor to the problem you replace" translate="no">​</a></h2>
<p>List what the customer does today without you: hours of manual work, another tool's subscription, an agency, or nothing at all. Put a rough monthly cost on that. A price well below it is easy to justify.</p>
<p>Worked example: a tool that generates compliance reports saves a founder about three hours a month. If their time is worth $50 an hour, the problem costs $150 a month. A $29 plan is a clear yes, and a $149 plan asks for the whole saving. A rule of thumb I use is to start near a fifth of the cost removed, then adjust from the answers you get. That is my heuristic, not a published figure.</p>
<p>If the honest answer is "nothing", the product may be a nice-to-have. Many first users will pay little for those, so expect a slow start rather than a pricing problem.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-3-set-two-or-three-tiers">Step 3: set two or three tiers<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#step-3-set-two-or-three-tiers" class="hash-link" aria-label="Direct link to Step 3: set two or three tiers" title="Direct link to Step 3: set two or three tiers" translate="no">​</a></h2>
<p>Three tiers is the common pattern, and it helps because each plan answers a question for a different buyer.</p>
<table><thead><tr><th>Tier</th><th>Who it is for</th><th>What changes</th></tr></thead><tbody><tr><td>Starter</td><td>A solo user trying it for real work</td><td>Low limit on the value metric; core features</td></tr><tr><td>Team</td><td>A small group using it every week</td><td>Higher limit; collaboration; export</td></tr><tr><td>Scale</td><td>A company with a process around it</td><td>Highest limits; support terms; invoicing</td></tr></tbody></table>
<p>Keep the differences in limits and support, not in whether the product basically works. Hiding the main benefit behind a higher tier tells early adopters you are playing games with them.</p>
<p>Avoid a free forever plan until you can measure what it costs you and what share upgrades. A time-limited trial or a generous first tier has a built-in end.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-4-check-the-price-against-fees">Step 4: check the price against fees<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#step-4-check-the-price-against-fees" class="hash-link" aria-label="Direct link to Step 4: check the price against fees" title="Direct link to Step 4: check the price against fees" translate="no">​</a></h2>
<p>Low prices carry a fixed cost per transaction. Using the published rates read today, a $9 monthly plan loses about $0.56 to Stripe's standard US card fee of 2.9% + 30¢ (6.2%), or $0.95 to the 5% + 50¢ that <a href="https://www.paddle.com/pricing" target="_blank" rel="noopener noreferrer" class="">Paddle</a> and <a href="https://polar.sh/resources/pricing" target="_blank" rel="noopener noreferrer" class="">Polar</a>'s free plan charge (10.6%), before taxes and payout fees. At $29 the same two rates take $1.14 and $1.95 (3.9% and 6.7%).</p>
<p>Higher fees are not automatically worse: the merchant-of-record providers also handle sales tax and VAT, which Stripe's basic payments leave to you. The post on <a class="" href="https://dealpuffin.com/blog/general/stripe-vs-paddle-vs-polar-fees/">Stripe vs Paddle vs Polar fees</a> works through the trade, and <a class="" href="https://dealpuffin.com/blog/general/merchant-of-record-explained-for-indie-founders/">merchant of record explained</a> covers what the term means. Very low prices put a fixed fee on every payment, so a $5 plan needs a real reason to exist.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-5-test-before-you-build">Step 5: test before you build<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#step-5-test-before-you-build" class="hash-link" aria-label="Direct link to Step 5: test before you build" title="Direct link to Step 5: test before you build" translate="no">​</a></h2>
<p>You can test a price without a billing system.</p>
<ol>
<li class="">Show the pricing page to 10 to 20 people who fit your target customer.</li>
<li class="">Ask "which plan would you pick, and what would make you not buy?" rather than "would you pay $X?". The second question gets polite answers.</li>
<li class="">Count the answers. If almost everyone picks your cheapest plan, your middle plan is probably overpriced or poorly defined. If nobody objects to the price, it is probably too low.</li>
<li class="">Ask for a card or a signed intent from a few. A pre-order or a paid pilot says more than approval.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="step-6-plan-for-the-first-change">Step 6: plan for the first change<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#step-6-plan-for-the-first-change" class="hash-link" aria-label="Direct link to Step 6: plan for the first change" title="Direct link to Step 6: plan for the first change" translate="no">​</a></h2>
<p>You will adjust the price. Decide the rules ahead of time and write them on the pricing page: early customers keep their price for 12 months, or for as long as they stay subscribed, and later customers pay the new price. Changing a price quietly is the fastest way to lose the users who helped you most.</p>
<p>For more on finding those first buyers, see <a class="" href="https://dealpuffin.com/blog/general/how-to-get-your-first-100-users-for-a-saas/">how to get your first 100 users for a SaaS</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_zFqj" id="frequently-asked-questions">Frequently asked questions<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently asked questions" title="Direct link to Frequently asked questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="how-much-should-i-charge-for-my-first-saas-product">How much should I charge for my first SaaS product?<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#how-much-should-i-charge-for-my-first-saas-product" class="hash-link" aria-label="Direct link to How much should I charge for my first SaaS product?" title="Direct link to How much should I charge for my first SaaS product?" translate="no">​</a></h3>
<p>Start from the cost of the problem you remove, then price near a fifth of that and adjust from buyer feedback. There is no standard number; the rule is a heuristic you should test.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-an-early-stage-saas-use-usage-based-pricing">Should an early-stage SaaS use usage-based pricing?<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#should-an-early-stage-saas-use-usage-based-pricing" class="hash-link" aria-label="Direct link to Should an early-stage SaaS use usage-based pricing?" title="Direct link to Should an early-stage SaaS use usage-based pricing?" translate="no">​</a></h3>
<p>Only if your own cost rises with use or customers clearly think in units, such as AI calls. Usage-based pricing needs metering and produces varying invoices, so flat tiers are simpler to start with.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="should-i-offer-a-free-plan">Should I offer a free plan?<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#should-i-offer-a-free-plan" class="hash-link" aria-label="Direct link to Should I offer a free plan?" title="Direct link to Should I offer a free plan?" translate="no">​</a></h3>
<p>Only if you can measure what it costs and what share of users upgrade. A time-limited trial gives you the same learning with a clear end.</p>
<h3 class="anchor anchorTargetStickyNavbar_zFqj" id="can-i-raise-prices-after-launch">Can I raise prices after launch?<a href="https://dealpuffin.com/blog/general/how-to-price-a-saas-product-early-stage/#can-i-raise-prices-after-launch" class="hash-link" aria-label="Direct link to Can I raise prices after launch?" title="Direct link to Can I raise prices after launch?" translate="no">​</a></h3>
<p>Yes, and most founders do. State the policy for early customers up front, such as keeping their price for 12 months, so a change does not break trust.</p>]]></content>
        <author>
            <name>Dealpuffin</name>
            <uri>https://dealpuffin.com</uri>
        </author>
        <category label="pricing" term="pricing"/>
        <category label="saas" term="saas"/>
        <category label="early-founders" term="early-founders"/>
        <category label="billing" term="billing"/>
        <category label="guide" term="guide"/>
    </entry>
</feed>