When you only have one plan, your pricing page should do one job: make the paid offer obvious enough that a visitor can decide in under a minute. Put the plan name, the price with the billing period, who it is for in one line, and a single primary CTA above the fold. Then earn the price with a short list of buyer outcomes, answer the four objections that stall one-plan pages, and send people into checkout or signup without a maze. You already picked a number; this post is about the page that sells it.
Below: why one plan is often better early, what belongs above the fold, how to write the feature list, what to leave off, honest social proof at tiny scale, an FAQ that kills the usual stalls, CTA and post-click path, a light measurement sheet, traps, a made-up example, a one-page wireframe checklist, and a 14-day plan.
Why is one plan often better early?
Early products do not need a menu. They need a clean yes or no.
One paid plan cuts cognitive load. Visitors do not have to decode which tier is "for them," and you do not have to invent fake differences between Pro and Pro+. A single offer also forces honest positioning: you say who the product is for, at what price, and what result they should expect. That is harder than stacking three cards, and that is why it works.
You can still have a free trial or a free tier somewhere else. This guide is about the pricing PAGE that shows one clear paid offer. If you have not settled the number yet, start with how to price your first SaaS when you have almost no data, then come back here and build the page around that number.
What belongs above the fold on a one-plan pricing page?
Above the fold, a visitor should be able to answer: what is this, how much, billed how often, is it for me, and what do I click next. If any of those is missing, they bounce or open a competitor who shows a price.
Nielsen Norman Group has argued for years that pricing is a top information need, including on B2B sites, and that hiding it pushes people to competitors. In State the Price to Give B2B Sites a Competitive Advantage (Hoa Loranger, 2013), they note that business customers report pricing as the most needed piece of information online, and that participants leave sites that do not show it. Your one-plan page should make the price impossible to miss.
Put these five pieces near the top, in roughly this order:
Plan name. Plain words beat marketing poetry. "Maker" or "Solo" is fine. Avoid "Unlimited Infinity."
Price and billing period on the same line. Write "$29 / month" or "$290 / year," not "$29" with the period buried in fine print.
Who it is for, in one sentence. Steal the language from your best users or from a one-page positioning brief. Example shape: "For freelance designers who need client feedback on one active project at a time."
Primary CTA. One button. "Start free trial" or "Get [Plan]" or "Continue to checkout." Do not put "Contact sales" next to it unless you truly cannot sell online.
One trust cue. Cancel anytime, 14-day trial, or "No card until day 8." Pick the one that is true.
Everything else can wait below the scroll.
How do you write a feature list that earns the price?
List buyer outcomes, not every toggle in settings.
A laundry list of features makes a one-plan page feel like a brochure for a product that is still unsure. Group three to seven bullets around what the buyer gets done. Prefer verbs they would use:
Good: "Send a shareable link and collect comments without another Slack thread."
Weak: "Real-time collaboration engine with nested threads."
A practical pattern:
Start from the jobs your paying users already finish.
Write one bullet per job, in their words when you have them.
Add limits only when they change the buy decision (seats, projects, export). Hide implementation limits that do not matter yet.
Stop at seven bullets. If you need more, you are either stacking features or avoiding a clearer "who it is for" line.
If a feature only exists to fill a comparison matrix against yourself, cut it. One plan does not need three fake tiers to look serious.
What should you leave off the page?
Less is a feature on a single-plan pricing page. Leave these off unless a real buyer asked for them in the last month:
Three fake tier cards with "Most popular" on the middle one you invented last night.
A vague "Custom" CTA that opens a calendar for every visitor. Keep custom for people who already outgrew the plan.
Legal walls in the hero. Link terms and privacy in the footer; do not paste policy text into the pricing fold. If you need a terms page later, that is a separate job.
Feature tables that restate the same six bullets three times with checkmarks.
A price hide ("See pricing" after a form). If you can charge online, show the number.
How should you show annual vs monthly without turning this into a pricing essay?
Keep it presentation, not strategy.
A simple default for a one-plan page:
Show monthly as the default number people expect.
Offer annual as a toggle or second line: "or $290 / year (2 months free)" only if that math is true for you.
Do not write a long justification. One short line is enough: "Pay yearly if you already know you will stick around."
You are not deciding whether annual is good for cash flow here. You are deciding whether the visitor can see both options without confusion. If annual is not ready in checkout, do not put it on the page.
What social proof works when you are still tiny?
Honest proof at small scale beats a logo wall of tools you used, not customers who paid.
Options that stay honest:
One short quote with a first name, role, and permission.
A defended number you can explain: "12 paying customers in 8 weeks" with the date range.
A screenshot of a real outcome (blurred) with one sentence of context.
If you have none of that yet, skip the social-proof block. An empty "Trusted by teams at..." section with stock logos trains people to distrust the rest of the page. A calm "Used by early freelancers who bill by the project" line is better than fake authority.
Which FAQ kills the four objections that stall one-plan pages?
Most one-plan stalls are the same four questions. Answer them on the page so people do not have to email you mid-decision:
"Can I cancel?" Say how and when access ends. "Cancel anytime from billing settings; you keep access through the period you paid for" is clearer than "flexible plans."
"Is there a cheaper plan?" Be direct. "Not right now. This is the only paid plan. If it is not a fit, do not stretch for a smaller tier that does not exist." Soften only if you truly have a free trial path.
"Do you have X?" List the three features people ask about most, with yes / not yet / never. "Not yet" with a date range beats silence.
"What if I outgrow it?" Tell them the limit that matters (seats, projects, usage) and what happens next: email you, waitlist for a team plan, or export. Do not invent Team Pro on the spot.
Keep the FAQ under six items. The pricing page is not your help center.
Do you need a comparison section when you only sell one plan?
Not a full alternatives page. One short status-quo line is enough.
Compare against the DIY default, not against three fictional versions of yourself. Example: "Compared with juggling spreadsheets, email threads, and a shared drive, you get one place for feedback and a link you can send." That is a positioning line, not a competitor matrix. If you later need a real vs page, write it separately; do not bolt a fake three-tier comparison onto a one-plan offer.
Where should the CTA sit, and what happens after the click?
Repeat the same primary CTA in three places: above the fold, after the feature list, and after the FAQ. Same label, same destination.
The post-click path should be short:
CTA goes to signup or straight to hosted checkout.
If you use a hosted checkout, Stripe's Checkout Sessions can show a full order summary with tax, trials, and promo codes on a Stripe-hosted or embedded page (see Stripe Checkout docs). Your pricing page still needs to set the expectation before they land there.
Confirmation page or email should restate plan name, price, and how to cancel.
Do not send people to a homepage tour and hope they find billing later. The pricing page already did the hard work; finish the handoff.
How do you measure a one-plan pricing page without rebuilding analytics?
Track three steps for this page only: visits to /pricing, checkout or signup starts from that page, and paid conversions. A light sheet is enough at the start.
Metric | How to capture | What you use it for |
|---|---|---|
Pricing page visits | Pageview on /pricing (or UTM landing) | Denominator for everything else |
Checkout / signup starts | Click on primary CTA, or checkout session created | Whether the offer is clear enough to try |
Paid | Successful payment or trial-to-paid | Whether the page and offer convert together |
Write the three numbers weekly. Do not turn this into an A/B testing program until you have steady traffic; one quiet change at a time is enough. For product metrics beyond the page (activation, retention), use tracking product metrics before your first 100 users rather than stuffing a full analytics install guide into the pricing rewrite.
What traps wreck one-plan pricing pages?
Feature laundry list. Forty checkmarks hide the one job that is worth paying for.
Three fake tiers. If two of the cards are "coming soon," you do not have three plans. You have theater.
Vague custom CTA. "Talk to us" as the only path kills self-serve buyers.
Hiding the price. If the number is on the checkout page only, many people never get there.
Stuffing legal walls. Terms belong in the footer and at signup, not as a wall of text in the hero.
Copying a big-company matrix. Enterprise pages optimize for procurement. Your page optimizes for a solo buyer with a credit card and five minutes.
A made-up example: Draftwick
Everything in this example is made up. Draftwick is a fictional tool that turns a short project brief into a one-page client proposal. Maya, a freelance brand designer, sells one paid plan.
Plan: Solo, $32 / month or $320 / year.
Who it is for line: "For freelancers who send one active client proposal at a time and want comments in one link."
Above-the-fold CTA: "Start 7-day trial."
Outcome bullets (5): paste a brief and get a proposal draft; share one link for comments; lock a version before send; export PDF; keep past proposals in one folder.
FAQ answers: cancel anytime; no cheaper plan; team seats not yet; if you need more than one active proposal, email Maya for a waitlist note.
Week-four sheet (made-up): 410 pricing visits, 48 checkout starts, 11 paid. She did not split-test the page. She rewrote the who-it-is-for line once after three sales calls used the same phrase, and checkout starts rose on the next 200 visits (still small numbers, still direction only).
Draftwick's page works because the offer is one sentence long and the CTA has nowhere confusing to go.
A one-page wireframe checklist
Use this as a section checklist while you draft. Order can shift slightly; contents should not.
Section | Must include | Skip if... |
|---|---|---|
Hero / above the fold | Plan name, price + period, who it is for, primary CTA, one trust cue | Never skip |
Outcome feature list | 3-7 buyer-outcome bullets; limits that change the buy | You somehow have fewer than three real outcomes (then the product is not ready to sell) |
Annual / monthly | Toggle or second line with true math | Annual is not available in checkout yet |
Social proof | One honest quote or defended number | You have neither; leave the block empty |
Status-quo line | One sentence vs DIY default | Your homepage already says it clearly above |
FAQ | Cancel, cheaper plan, do you have X, outgrow it | Never skip the first two |
Final CTA | Same button label and destination as the hero | Never skip |
Footer links | Terms, privacy, contact | Never skip; keep them quiet |
A 14-day plan to ship the page
Day | Focus | Done when |
|---|---|---|
1-2 | Lock the offer | Plan name, price, period, who-it-is-for sentence written in a doc |
3-4 | Outcome bullets | 5 bullets in buyer language; two cut candidates listed |
5 | FAQ draft | Four objections answered in plain sentences |
6-7 | Build the page | Hero, list, FAQ, two CTA repeats live on a staging URL |
8 | Checkout path | Primary CTA reaches signup or hosted checkout; confirmation restates plan and price |
9 | Trust and footer | One trust cue true; terms/privacy linked; no legal wall in the hero |
10 | Proof pass | One quote or defended number added, or block intentionally omitted |
11 | Read-aloud edit | You can explain the offer in 20 seconds without scrolling |
12 | Measurement sheet | Visits, starts, paid columns ready for next week |
13-14 | Ship and watch | Page live; first week of numbers written down; one note on where people stall |
Times are planning guesses, not measurements. If day 8 breaks, fix the handoff before polishing adjectives.
FAQ
Should I add a free plan on the same page?
Only if free is a real product path you want people to choose. Otherwise keep free trial as a CTA label and leave freemium decisions for a separate access-model choice. The page should still show one paid offer clearly.
What if buyers keep asking for a cheaper tier?
That can mean the price is high for the ICP, the who-it-is-for line is wrong, or they want a subset you should not support yet. Do not invent a weaker plan to win a polite maybe. Fix positioning or the number first.
Can I show "from $X" when I only have one plan?
No. "From" implies a range. With one plan, show the price.
When should I split the page into multiple plans?
When a second segment pays today, needs different limits, and you can support both without fake cards. Until then, one plan keeps the story honest.
Ship the simple page
Single plan pricing is not a smaller version of an enterprise matrix. It is a clear offer: who it is for, what it costs, what they get, how to cancel, and where to click. Write that pricing page copy, measure visits to paid, and resist the urge to decorate with empty tiers.
When you want more maker playbooks like this, browse MakerHunt.