You have an idea for a small software product, and the question keeping you up is simple: will anyone actually pay for it? Most micro-SaaS founders find out the hard way, after months of building something nobody buys. If you've ever typed "how do I validate my SaaS" into a search bar, this playbook is for you. You'll build a one-page smoke test with Carrd, attach a Stripe Payment Link that takes real pre-orders, send qualified people to it, and decide go or no-go against a threshold you set before a single line of code exists. The people who pay are your future customers: small teams, freelancers or shop owners with a recurring, annoying problem your tool would remove.
Playbook at a glance
| Item | Details |
|---|---|
| Who pays | A narrowly defined buyer (for example, owners of small coaching businesses or independent accountants) who feels a specific, recurring pain your micro-SaaS would fix. |
| What you sell | A paid pre-order or founding-member spot for a tool that doesn't exist yet, with a stated delivery window and a clear refund promise. |
| Business model | Pre-sale now, then a subscription or one-time licence once the product ships. The pre-order price is usually a discounted first period or a lifetime deal you define. |
| Main cost drivers | Carrd plan, a custom domain, Stripe processing fees on each payment, optional paid ads, and your own time spent on outreach. |
| Skills needed | Clear copywriting, basic page layout, comfort messaging strangers, and the discipline to read numbers honestly. |
| Regulatory touchpoints | Consumer refund obligations, tax registration (GST in India, VAT in the UK, state and federal rules elsewhere), privacy notice for collected emails, and Stripe's own account terms. |
| Difficulty | Low to Medium. The tooling is easy; the hard part is getting the right people to the page and resisting the urge to call weak results a win. |
Evidence of demand
Here's the honest answer: demand for your specific micro-SaaS idea is unproven.
The research behind this guide confirms what the tools do and what they cost. That's exactly why the next sections exist. A paid pre-order is the strongest signal you can collect before building, because it costs the buyer something real. Email signups, likes and "I'd use that" comments are weaker; treat them as leads, not proof.
So the evidence you need is evidence you'll generate yourself: visitors, checkout clicks, completed payments and the replies to your outreach. The steps below show you how to collect it cleanly.
What you need before you start
Skills
- Writing a headline that names the customer and the outcome in one line.
- Basic layout sense (Carrd is drag-and-drop, so no code).
- Comfort sending direct messages to people you don't know yet.
- Reading a simple funnel: visitors, clicks, payments.
Tools and accounts
- Carrd account. Carrd's Pro Standard plan costs $19 per year. That plan includes forms, widgets, embeds and analytics according to Carrd's plan documentation. If you want advanced options such as custom forms, Carrd's Pro Plus plan is listed at $49 per year. You can also try Pro first, since Carrd offers a 7-day Pro trial with no payment or card details required.
- Stripe account. You'll use Stripe Payment Links to collect one-time pre-order payments without building a checkout flow. Stripe needs business and bank details before it pays out, so start verification early.
- A domain name (optional but it makes the page look trustworthy).
- A spreadsheet for your outreach log and results.
- A dedicated email inbox for replies and refund requests.
Starting budget categories
- Landing page plan (Carrd).
- Domain registration.
- Payment processing fees, which are taken per transaction rather than upfront.
- Optional ad spend for traffic, capped at a number you're willing to lose completely.
- Refund reserve: keep enough aside to refund every pre-order if you decide not to build.
Time commitment
Pick your test window before you start and write it down as [TEST_DAYS]. Shorter windows force focus; longer ones help if your buyers are slow to respond. What matters is that the window is fixed in advance, so you can't keep extending it until the numbers look nice.
Block out daily time for outreach. The page builds in an afternoon. Traffic is the real job.
Launch it step by step
Step 1: Validate the problem before the page
Don't open Carrd yet. A landing page for the wrong problem just tells you the wrong problem is unpopular.
- Write one sentence: "[CUSTOMER TYPE] struggle to [TASK] because [CAUSE], which costs them [TIME, MONEY OR STRESS]."
- List the places those customers already talk: specific subreddits, LinkedIn groups, WhatsApp or Telegram communities, Slack groups, industry forums.
- Read recent threads in each place. Copy exact phrases people use about the problem into a "voice of customer" tab in your spreadsheet.
- Message people who complained publicly (use the outreach template below). Ask how they handle the problem today and what that workaround costs them.
- Record each conversation: current workaround, tools they already pay for, how often the problem happens, and whether they'd want to see a fix.
In practice, the workaround is the most useful answer. If people already pay for a clunky spreadsheet template, a virtual assistant or a costly tool, they've proven the pain has a budget.
Check: Go if several conversations describe the same pain in similar words and mention an existing workaround they're unhappy with. No-go (or pivot the customer) if people shrug, can't remember the last time it happened, or say a free tool already solves it.
Step 2: Define the offer and your pass/fail threshold
Now turn the problem into something a stranger can buy in one visit.
- Name the outcome, not the feature list. "Send every client invoice reminder automatically" beats "AI-powered billing suite".
- Choose the pre-order format. Options: a discounted first period, a founding-member lifetime deal, or a paid waitlist spot credited against the first bill.
- Set the price as [PREORDER_PRICE]. Base it on the workaround costs you heard in Step 1, not on what feels comfortable to ask.
- Set the delivery promise as [DELIVERY_DATE]. Be conservative. Missing it damages trust before you've even launched.
- Write the refund terms: full refund on request until launch, and an automatic full refund if you don't build. Put this in plain words on the page.
- Write your threshold before traffic arrives. Fill in: "If [MIN_PAID_PREORDERS] people pay within [TEST_DAYS] days from [MIN_QUALIFIED_VISITORS] qualified visitors, I build. Otherwise I refund everyone and pivot or stop."
That last item is the whole point. Write it in your spreadsheet and share it with a friend who'll hold you to it.
Check: Go if you can explain the offer, price, delivery date and refund terms in two sentences, and your threshold is written down with real numbers you chose. No-go if you catch yourself leaving the threshold vague "to see how it goes".
Step 3: Build the Carrd page
Keep it to one screen of value and one action.
- Sign up at Carrd and start the Pro trial if you want Pro features while you build. Pick a blank or minimal template.
- Add these elements top to bottom: headline, subheadline, a short "who this is for" list, three outcome bullets, a "how it works" section, price and delivery date, refund terms, the pre-order button, and a short FAQ.
- Add a Button element labelled "Pre-order for [PREORDER_PRICE]". You'll paste the Stripe link into its URL setting in Step 4.
- Add a secondary email form for people who aren't ready to pay. Carrd says its Pro Standard plan supports businesses using forms to collect email addresses and customer feedback. Label it "Not ready? Get launch updates". Keep it visually smaller than the pay button.
- Add a footer with your contact email, a link or section for your privacy notice, and your refund terms repeated.
- Connect your domain if you bought one, then publish.
- Turn on site analytics (Pro Standard lists analytics as included) so you can count visitors. Confirm the exact setting name in Carrd's Pro documentation, because menus change.
Don't add a mockup gallery or a ten-item feature list. Clarity sells pre-orders. Decoration doesn't.
Check: Go if a friend who matches the customer profile can tell you, after a short look, who it's for, what it does, what it costs and when it arrives. No-go if they ask "so what is this?" Rewrite the headline and test again.
Step 4: Create the Stripe Payment Link
- In your Stripe Dashboard, open the Payment Links area and create a new link.
- Add a product named "[PRODUCT_NAME] founding pre-order". In the description, repeat the delivery date and refund promise.
- Set it as a one-time price of [PREORDER_PRICE] in your chosen currency.
- Turn on email collection for the customer (you'll need it for updates and refunds). Optionally add a custom field asking "What's the main thing you want this tool to do?"
- Set the after-payment confirmation to show a thank-you message, or redirect to a thank-you section on your Carrd page.
- Copy the link and paste it into the Carrd button's URL setting. Republish.
- Make a test purchase in Stripe's test mode first, then a small live purchase with your own card and refund it, so you see the full flow your buyer sees.
Know your fees before you price. On Stripe India's Link page, the listed processing rate is 2% for most cards issued in India. The same Stripe India page lists 4.3% for cards issued anywhere. Check the pricing page for your own Stripe country, because rates differ by region.
Check: Go if a live test payment lands in your Dashboard with the buyer's email captured and you can refund it. No-go until it does; a broken checkout makes every result meaningless.
Step 5: Get qualified people to the page
Traffic quality matters far more than traffic volume. Random visitors teach you far less than a small group of people who actually have the problem.
- Warm outreach first. Go back to everyone from Step 1. Send the "page is live" message from the templates below.
- Community posts. Share the problem and your planned fix in the communities you mapped, following each group's self-promotion rules. Lead with the problem, not the link.
- Cold direct messages. Find people whose public posts or job titles match your buyer. Send short, personal notes. Log each one.
- Optional paid test. Run a small, tightly targeted ad with your capped budget. Use one audience and one message so the result is readable.
- Tag every link with a simple source label (for example, add "?src=linkedin" to the URL) so you can tell which channel produced clicks. Confirm in Carrd's analytics how it reports referrers.
Log daily: messages sent, replies, page visits, button clicks, payments, email signups.
Check: Go if you reach your planned qualified-visitor number inside the test window. If you can't get enough of the right people to even look, that's a distribution problem, and it'll be worse once you're charging monthly. Fix the channel before judging the offer.
Step 6: Read the results and decide
The test window closes. Now compare against the threshold you wrote in Step 2, not a new one.
- Paid pre-orders at or above threshold: Go. Email every buyer to thank them and book a short call with each.
- Many clicks, few payments: people want it but something at checkout or on price stopped them. Ask the clickers why (use the follow-up template). One price or offer revision, then rerun the test once.
- Visitors but few clicks: the page or the promise isn't landing. Rewrite the headline around the exact customer phrases you collected.
- Few visitors: you haven't tested demand yet, only distribution.
- Lots of email signups and no payments? That's interest, not demand.
What most guides miss is that a "no" is a good outcome. You just saved months.
Check: Go only if the paid number meets the threshold you set in advance. If you miss, refund everyone promptly, tell them why, and either pivot the customer or idea and rerun, or stop.
Step 7: Deliver to your founding customers
- Within a day of the decision, email every buyer with the build plan, the delivery date and how they can request a refund.
- Run short calls with each buyer. Ask them to walk you through the problem the last time it happened. Build the smallest version that solves that.
- Send a progress update on a fixed schedule you choose (weekly is easy to keep). Silence is what triggers refund requests.
- Give founders early access before public launch, and collect their feedback in one place.
- If you must slip the date, tell them before it passes and re-offer the refund.
Check: Go to public launch when founding customers use the first version on their real work and keep using it. If they log in once and vanish, fix the core workflow before you sell to anyone else.
Step 8: Systemise the test so you can run it again
- Duplicate your Carrd page as a template for future ideas.
- Save your Stripe product and Payment Link setup notes in a document.
- Keep the spreadsheet tabs (voice of customer, outreach log, daily funnel, decision) as a reusable workbook.
- Write a one-page retro: what the threshold was, what happened, which channel worked, what you'd change.
- When the product is live, move buyers from the pre-order to the regular subscription, honouring whatever founding price you promised.
Check: Go if you could run the whole test again for a new idea using only your saved template, workbook and notes. If you'd have to rebuild from memory, finish the documentation now while it's fresh.
Unit economics worksheet
Fill this in before you set the pre-order price, then again with real results after the test. Use your own numbers; the only benchmark here is the cited Stripe rate, and you should confirm the rate for your country.
| Line | Variable | Formula or source |
|---|---|---|
| Pre-order price | P | Your chosen [PREORDER_PRICE] |
| Payment processing fee per sale | F | P × your Stripe rate (for example, the 2% for most India-issued cards listed on Stripe India's Link page) plus any fixed fee shown on your Stripe pricing page |
| Tax collected (if registered) | T | Per your GST, VAT or sales tax registration; held for the authority, not revenue |
| Net per pre-order | N | P − F − T |
| Monthly running cost per customer after launch | C | (Hosting + software + support time × your hourly value) ÷ number of customers |
| Fixed test costs | X | Carrd plan + domain + any other tools |
| Ad spend | A | Total spend during the test window |
| Paid pre-orders | Q | Count from your Stripe Dashboard |
| Customer acquisition cost | CAC | A ÷ Q (add your outreach hours × hourly value for a fuller picture) |
| Visit-to-payment conversion | R | Q ÷ qualified visitors |
| Contribution margin per customer per month | M | Monthly price − monthly fees − C |
| Payback period | PB | CAC ÷ M (in months) |
| Break-even customers | BE | Monthly fixed costs ÷ M |
If CAC is larger than several months of M, the idea may still work, but only with a cheaper channel. Write that down as a risk.
Scripts and templates
Problem interview message (Step 1)
Hi [NAME], I saw your post in [COMMUNITY] about [PROBLEM IN THEIR WORDS].
I'm researching how [CUSTOMER TYPE] deal with this. Not selling anything.
Could I ask you three quick questions by message?
1. How do you handle [PROBLEM] today?
2. What does that workaround cost you in time or money?
3. What have you tried that didn't work?
Thanks either way, [YOUR NAME]
"Page is live" message (Step 5)
Hi [NAME], thanks again for explaining how you handle [PROBLEM].
I'm building [PRODUCT_NAME] to fix exactly that: [ONE-LINE OUTCOME].
Founding pre-orders are open at [PREORDER_PRICE], delivery by [DELIVERY_DATE],
full refund any time before launch.
Here it is: [PAGE_URL]?src=[CHANNEL]
If it's not right for you, I'd really value one line on why.
Cold direct message
Hi [NAME], quick one. Do you still [PAINFUL TASK] manually at [COMPANY/ROLE]?
I'm pre-selling a small tool that [ONE-LINE OUTCOME]. If that's a headache
for you, the details are here: [PAGE_URL]?src=[CHANNEL]
No worries if not.
Follow-up to people who clicked but didn't pay
Hi [NAME], I noticed you checked out [PRODUCT_NAME]. What stopped you from
pre-ordering? Price, timing, trust, or it's not quite the right fix?
Any honest answer helps me build the right thing.
Carrd offer page outline
HEADLINE: [OUTCOME] for [CUSTOMER TYPE], without [CURRENT WORKAROUND]
SUBHEADLINE: [PRODUCT_NAME] [WHAT IT DOES] so you can [BENEFIT].
WHO IT'S FOR:
- [CUSTOMER TYPE] who [SITUATION]
- Anyone tired of [WORKAROUND]
WHAT YOU GET:
- [OUTCOME 1]
- [OUTCOME 2]
- [OUTCOME 3]
HOW IT WORKS: 1. [CONNECT/UPLOAD] 2. [SET RULE] 3. [GET RESULT]
STATUS: In development. Founding customers get access by [DELIVERY_DATE].
BUTTON: Pre-order for [PREORDER_PRICE]
REFUND: Full refund on request before launch. If I don't build it, everyone is refunded automatically.
SECONDARY FORM: Not ready? Get launch updates [EMAIL FIELD]
FAQ: When will I get access? / What if it doesn't work for me? / Who is behind this?
FOOTER: [CONTACT_EMAIL] | Privacy notice | Refund terms
Pricing section copy
FOUNDING MEMBER: [PREORDER_PRICE] [ONE-TIME / FIRST PERIOD]
Includes:
- Early access from [DELIVERY_DATE]
- [FOUNDING PRICE LOCK OR LIFETIME TERMS]
- Direct input on what gets built first
Regular price after launch: [REGULAR_PRICE]
You're paying for something that doesn't exist yet. That's why the refund
is unconditional until launch. Questions? [CONTACT_EMAIL]
Refund and "not building" email
Subject: Refunding your [PRODUCT_NAME] pre-order
Hi [NAME], thank you for backing [PRODUCT_NAME]. The test didn't reach the
level I set before starting, so I won't build it in this form. I've issued a
full refund to your original payment method today. If you'd like to hear what
I try next, just reply. Thanks for trusting me, [YOUR NAME]
Legal and admin checklist
Taking money for something not yet built carries real obligations. Check each item with the authority for where you and your buyers are.
- India, GST. India's government provides an online portal for businesses to register for GST. Check on that portal whether your turnover and the fact that you sell digital services across states or abroad require registration.
- UK, VAT. GOV.UK says businesses can usually register for VAT online and can start charging VAT from their effective date of registration. Read the full page to see if your sales cross the registration threshold.
- United States and elsewhere. The research behind this guide doesn't cover US business registration or sales tax. Check your state's Secretary of State website for business registration and your state revenue department for sales tax on software, and the IRS website for federal income reporting.
- Selling to EU or other foreign buyers. Digital services can trigger tax in the buyer's country. Check the relevant tax authority before opening the link internationally.
- Stripe account terms. Read Stripe's services agreement and restricted business list for your country, and confirm how Stripe treats pre-orders and delayed delivery.
- Refunds and consumer law. Your local consumer protection authority sets the rules on pre-payment and refunds. Your written refund promise should be at least as generous as the law.
- Privacy. You're collecting emails. Publish a short privacy notice saying what you collect, why, and how to ask for deletion, and check your country's data protection authority for specifics (in India, the Digital Personal Data Protection framework; in the UK, the ICO).
- Keep records of every payment and refund.
Why this fails and how to avoid it
- Moving the goalposts. Warning sign: you catch yourself saying "it's still early" after the window closes. Fix: the threshold from Step 2 is final. Rerun as a new test if you change anything.
- Testing on friends. Warning sign: most buyers are people who know you. Fix: count only payments from people outside your personal circle toward the threshold.
- Vague customer. Warning sign: your headline says "businesses" or "creators". Fix: name one role in one situation, then rewrite.
- Feature-led page. Visitors read but don't click. Fix: replace features with the outcome in the customer's own words from your Step 1 notes.
- No traffic plan. Warning sign: you published and are waiting. Fix: outreach is the job, so set a daily message quota and log it.
- Broken checkout. Warning sign: clicks but zero Stripe sessions. Fix: test the link in a private browser window and on mobile.
- Treating emails as demand. Many signups, no payments. Fix: invite signups to pre-order directly and ask the non-payers why.
- Overpromising delivery. Warning sign: your date depends on everything going right. Fix: add a generous buffer to the build time you think you need, then promise that.
- Underpricing to get a yes. Warning sign: the pre-order price is far below what buyers said they pay for workarounds. Fix: price against the workaround; a cheap yes tells you little.
Hand this to ChatGPT or Claude
You can paste the brief below (or this page's link) into an AI assistant along with your city, budget and skills, and ask it for a tailored version of this plan.
GOAL: Decide go/no-go on my micro-SaaS idea using a paid pre-order smoke test
before writing code. Help me write the page, outreach and decision threshold.
CUSTOMER: [ROLE], [SITUATION], [WHERE THEY HANG OUT ONLINE], based in [CITY/COUNTRY]
OFFER: [PRODUCT_NAME] that [ONE-LINE OUTCOME]. Pre-order price [PREORDER_PRICE],
delivery by [DELIVERY_DATE], full refund until launch.
VALIDATION STEPS:
1. Problem interviews with people who complained publicly
2. One-page Carrd site with one pre-order button (Stripe Payment Link) and a secondary email form
3. Targeted outreach and community posts with tagged links
4. Compare paid pre-orders with my written threshold
LAUNCH STEPS:
1. Email buyers and book calls
2. Build the smallest version that solves the core problem
3. Regular progress updates, early access, then public launch
NUMBERS TO FILL IN: [TEST_DAYS], [MIN_QUALIFIED_VISITORS], [MIN_PAID_PREORDERS],
[PREORDER_PRICE], [REGULAR_PRICE], [AD_BUDGET], [MY_HOURLY_VALUE], my Stripe fee rate
CONSTRAINTS: Budget [BUDGET]. Skills [SKILLS]. Hours per week [HOURS].
No invented statistics; flag anything I must confirm with official tax or payment docs.
Frequently Asked Questions
Is it okay to take money for a product that doesn't exist yet?
Yes, as long as you're open about it. Say clearly on the page that the product is in development, give a delivery date, and offer an unconditional refund until launch. Check your local consumer protection rules and Stripe's terms for your country before going live.
How many pre-orders mean my SaaS is validated?
There's no universal number, and anyone quoting one is guessing. Set your own threshold in Step 2 based on what would justify your build time, write it down before traffic arrives, and stick to it.
Why use pre-orders instead of an email waitlist?
Signing up costs nothing, so it mostly measures curiosity. A payment measures willingness to pay, which is the thing you actually need to know. Keep the email form as a secondary option, not the main test.
Do I need Carrd Pro, or will the free plan work?
A plain button linking out to Stripe may work on a lower tier, so check Carrd's plan comparison before you choose.
What if I get clicks on the pre-order button but no payments?
That usually points to price, trust or a checkout problem. Test the Payment Link yourself on mobile, then message the people who clicked and ask what stopped them. Change one thing at a time and rerun.
Do I have to register for GST or VAT before running the test?
It depends on your country, your turnover and where your buyers are. Check the GST registration portal in India or GOV.UK's VAT registration guidance in the UK, and consider a quick consult with a local accountant.
What should I do if the test fails?
Refund everyone quickly with a short honest email, then write a retro. A failed test usually points to the wrong customer, the wrong channel or the wrong promise; change one and rerun with a fresh threshold.
Your first step
Today, write your one-sentence problem statement and send the problem interview message to people who've complained about it publicly. Don't build the page until those conversations confirm the pain has a budget.
Sources
- Go Pro! - Carrd
- Stripe Payment Links | Simple Links to Accept Payments
- Register for VAT: How to register for VAT - GOV.UK
- Register for GST Online
- Carrd Pricing (Oct 2026): Plans, Cost per User & Free Plan
- Carrd Review 2026: Pricing, Limits and Who It Suits
- Carrd Review 2026: Pages From $19, Payment Forms Need $49
- Carrd Pricing (2026): Free, Pro $9 a Year, Own Domain $19