Quick Answer
A SaaS website converts a trial signup by removing uncertainty, not friction. The highest-leverage changes are showing the product immediately, publishing real pricing, and cutting everything between the click and a working account. Most SaaS homepages fail because they describe a category instead of demonstrating a product, and the visitor leaves without ever seeing the thing.
By Cody Wise, founder of Wise Media, Calgary. Last updated 6 November 2026.
Summary
- Show the product in the first screen. A screenshot or a short loop beats any headline you can write.
- Publish pricing. Hiding it filters out the self-serve buyers you built a trial for and fills your calendar with demos you did not want.
- No credit card for a self-serve trial, unless your abuse problem is real and measured.
- The signup form is not the conversion. A configured account that has done the core action once is.
- Measure signup to activation, not signups. Signups are easy to raise and tell you almost nothing.
Table Of Contents
- Why Most SaaS Homepages Fail
- The First Screen
- Pricing: Publish It
- The Signup Itself
- Trust For A Buyer Who Has Not Heard Of You
- The Real Conversion Is Activation
- Canadian Specifics Worth Getting Right
- What To Measure
- Common Mistakes
- FAQ
Why Most SaaS Homepages Fail
Three failures account for most of it, and none of them are design problems.
The page describes a category, not a product. “The modern platform for revenue teams” tells a visitor nothing they can evaluate. They cannot tell what it does, whether it replaces something they already pay for, or whether it would work for a team of four. So they leave, and the analytics records a bounce that looks like a traffic quality problem.
The product is invisible. An enormous share of SaaS homepages show an abstract illustration, a gradient, and some logos. A visitor deciding whether to spend twenty minutes setting up an account wants to see the interface. Showing it is the single highest-return change available on most of these pages, and it costs a screenshot.
Pricing is hidden behind a demo request. If you built a self-serve trial, you built it for buyers who want to evaluate without talking to anyone. Hiding price forces exactly those buyers into the one interaction they were avoiding. They do not convert to a demo. They go and look at a competitor who published a number. Getting that handoff right is the whole job on a technology and SaaS site.
The 50 Word Version
Show the actual interface in the first screen, say in one plain sentence what the product does and who for, publish pricing, and ask for the minimum needed to create a working account. Then measure how many new accounts complete the core action, not how many signed up.
The First Screen
Five things, and nothing else competing with them.
- A plain sentence naming what it does and who for. Test it by reading it to someone outside your industry. If they cannot repeat back what the product does, rewrite it. Specific beats aspirational: an audience and a job, not a transformation.
- A real view of the product. A screenshot with real-looking data, or a short silent loop showing one task being completed. Not a laptop mockup on a desk, and not an abstract illustration of connectivity.
- One primary action. Start free. One button, repeated down the page, not competing with a demo request of equal weight. If you need both, make one secondary and visually quieter.
- What happens when they click. One line under the button: no credit card, two minutes to set up, free for 14 days. Removing uncertainty about the next step converts better than any adjective in the headline.
- One concrete proof point. A specific customer with a specific outcome, or a number you can substantiate. Not a wall of grey logos, which at this stage says only that somebody signed up once.
On that last point, be careful with statistics. Published SaaS conversion benchmarks almost never disclose their sample, their definition of a conversion, or their date, and quoting one on your own site invites the same scrutiny you should be applying to theirs. Use your own numbers or use a named customer’s.
Pricing: Publish It
The argument against publishing is always that pricing is complex, varies by customer, or would help competitors. The first two are usually true of the final number and almost never of the floor. The third is not a real concern, because your competitors already know what you charge.
What to publish, in descending order of preference:
- Full self-serve tiers with numbers. Best for anything a team can buy on a card.
- Published tiers plus a Contact us enterprise tier. The standard and it works, provided at least one real number appears.
- A starting point. “From $X per month.” Enough for a buyer to place themselves.
- A range with the variable named. “Most teams pay between $X and $Y depending on seats and volume.” Also fine.
What not to do: a pricing page where every tier says Contact us. That page is worse than no pricing page, because the visitor came specifically to resolve the price question and you confirmed that you will not tell them.
Three details that matter more than the number itself. Say the currency explicitly, because a Canadian buyer looking at an unlabelled dollar sign assumes USD and mentally adds a third. Show annual and monthly side by side with the discount visible. And make the included limits legible, because a tier whose limits are buried produces churn at the first invoice.
The general argument, including when hiding price is genuinely correct, is in should you put pricing on your website.
The Signup Itself
Every field is a decision point where someone can leave. Ask for what you need to create a working account and nothing else.
| Field | Verdict | Why |
|---|---|---|
| Required | Unavoidable | |
| Password | Required, or use a single sign-on provider | SSO removes a step and a forgotten password |
| Full name | Collect in-app, after signup | Not needed to provision an account |
| Company name | In-app | Same |
| Company size | In-app, as part of setup | Framed as configuration it feels useful, on a form it feels like qualification |
| Phone number | Remove | Reads as “a salesperson will call”, which is what the trial was meant to avoid |
| Credit card | Remove for self-serve | See below |
| Job title | In-app | Useful data, wrong moment |
The principle: move qualification after the account exists. The same questions asked during onboarding, framed as configuring the product, get answered at a far higher rate than the same questions on a form, because at that point answering them produces something for the user.
Credit Card Or Not
The real trade. Requiring a card produces far fewer trials and a much higher share that convert, because the card itself is the qualification step. Not requiring one produces many more trials and a lower conversion rate.
For most self-serve SaaS the no-card option is correct, for a reason that is not about volume. A trial is how a buyer evaluates whether the product works for them. Putting a payment barrier in front of the evaluation contradicts the purpose of offering one. If you want the qualification that a card provides, you are describing a sales-led motion, and you should run a demo rather than a trial.
The honest exception is abuse. If you have a measured problem with trial farming, particularly anything that gives users compute or sending capacity, a card or another verification step is a legitimate control. Measure the abuse before you assume it.
Trust For A Buyer Who Has Not Heard Of You
A visitor is about to put company data into software from a company they do not know. Four things answer that without a sales call.
- Named people. A real team page with real faces and real roles. Anonymous SaaS reads as risky, and the fix costs nothing.
- Security and data handling, findable. Where data is hosted, how it is encrypted, what happens on cancellation. A plain page beats a badge.
- Specific customer evidence. One named customer saying something concrete outperforms twelve logos. If you cannot name anyone yet, say what the product does and skip the social proof rather than faking it.
- Visible, honest support. Response times you actually meet, a real inbox, documentation a visitor can read before signing up. Public docs are one of the most underrated trust assets in SaaS, because they let a technical evaluator answer their own questions at 11pm.
One thing to avoid: fabricated testimonials, invented logos, or metrics you cannot substantiate. Beyond the obvious, Canadian competition law takes a dim view of misleading representations, and a buyer who catches one invented claim discounts everything else on the page.
The Real Conversion Is Activation
A signup is not a conversion. An account that never does anything costs you support capacity, email reputation and a distorted dashboard.
Define activation as the moment a new account completes the core action your product exists for once. Importing the data, connecting the integration, sending the first thing, running the first report. One action, defined in writing, measurable.
Then design the first session around getting there:
- One path, not a tour. Guide the user to the single action that demonstrates value. Everything else can wait.
- Sample data available. The biggest blocker to activation is usually that the product is empty and the user has nothing to put in it. Let them see it working with example data before they commit their own.
- Remove the setup that is not needed yet. Inviting teammates, configuring permissions and connecting billing can all happen after the user has seen the product work.
- One email, triggered on inactivity, not on a schedule. If an account signed up and did nothing in 24 hours, ask what got in the way. A question outperforms a feature tour.
- Make the empty state do work. The screen a new user sees before they have any data is the most-viewed screen in your product and is usually the least designed.
Canadian Specifics Worth Getting Right
- Label the currency. An unlabelled dollar sign is read as USD by Canadian buyers. If you price in CAD, say so prominently; it is a competitive advantage against US vendors right now.
- Say where data is hosted. Canadian buyers ask, particularly in regulated sectors and the public sector. Worth knowing: PIPEDA imposes no general data localisation requirement, a point we covered in does Canadian customer data have to stay in Canada. Some provincial public sector rules and contracts do impose requirements, so the honest answer is to state where the data lives and let the buyer assess it.
- Get consent right on the signup. Creating an account is one thing; adding that address to a marketing list is another. Under CASL, whose Act, regulations and guidelines the CRTC publishes, those are different purposes and the signup form should reflect that. The mechanics are in building an email list in Canada without breaking CASL.
- Show taxes clearly. Present what the customer will actually pay. Advertising a price and adding mandatory charges at the last step is drip pricing, which Canadian competition law addresses, and we covered in drip pricing rules for Canadian websites.
- Price in CAD if your market is Canadian. Currency conversion at checkout is a real abandonment point for smaller purchases.
What To Measure
| Metric | What it tells you | Where to act |
|---|---|---|
| Visitor to signup | Whether the page explains the product | First screen, pricing visibility |
| Signup to activation | Whether onboarding works | First session, empty states, sample data |
| Activation to paid | Whether the product delivers value in the trial | Product, trial length |
| Signup form start to completion | Field-level friction | Remove a field |
| Pricing page to signup | Whether the price fits the audience you attract | Packaging, or targeting |
| Docs visits before signup | Whether evaluators can self-serve answers | Documentation coverage |
The pair that matters is visitor-to-signup alongside signup-to-activation. Watching only the first lets you celebrate a change that raised signups and lowered activation, which is a worse business with a better dashboard.
Compare against your own previous quarter rather than published benchmarks, for the same reason given earlier: cross-company SaaS conversion figures rarely disclose sample, definition or date, and they vary enormously by price point and motion.
Common Mistakes
- No screenshot of the product. The most common and most expensive omission on SaaS homepages.
- A headline describing a category. Say what it does and who for.
- Every pricing tier says Contact us. Worse than having no pricing page.
- Requiring a card for a self-serve trial. Contradicts the purpose of the trial unless you have a measured abuse problem.
- Asking for a phone number at signup. Signals a sales call and costs you the self-serve buyer.
- Demo and trial given equal visual weight. Pick a primary motion. Two equal buttons is a decision you pushed onto the visitor.
- Measuring signups only. You can always get more by qualifying less.
- An empty product on first login. The most-viewed screen in your app, usually the least designed.
- Unlabelled currency. Canadian buyers assume USD and mentally inflate your price.
FAQ
Should A SaaS Trial Require A Credit Card?
Usually not, for a self-serve product. A card requirement is a qualification step, and if you want that qualification you are running a sales-led motion and should offer a demo instead. The genuine exception is measured abuse, particularly where the trial grants compute or sending capacity.
How Many Fields Should A SaaS Signup Form Have?
Enough to create a working account, which is usually email plus password, or a single sign-on button. Collect company, role and team size during onboarding where answering them configures the product and therefore feels useful rather than like screening.
Should I Publish Pricing On My SaaS Site?
Yes, if you offer self-serve signup. Buyers who chose a trial over a demo are specifically avoiding a conversation, and hiding price pushes them to a competitor who published one. At minimum publish a starting point with the currency labelled.
How Long Should A Free Trial Be?
Long enough for a user to complete the core action and see a result, which for most tools is 14 days. Longer trials mainly extend the delay before the decision. If your product only shows value over a full monthly cycle, a 30 day trial is defensible.
What Is Activation And Why Does It Matter More Than Signups?
Activation is a new account completing the core action your product exists for, once. It matters more because signups are trivially easy to increase by asking for less, while activation measures whether anyone actually experienced the product.
Should I Offer A Demo And A Trial?
You can, but make one primary. Two calls to action of equal weight pushes a decision onto the visitor that you should have made. For products under roughly $200 CAD a month, lead with the trial. Above that, lead with the demo and keep the trial as the secondary path.
Does My SaaS Need Canadian Data Hosting?
Not as a general legal requirement. PIPEDA imposes no general data localisation obligation. Some provincial public sector rules and individual contracts do, so publish where your data is hosted and let buyers assess it. It is a sales question more often than a compliance one.
Conclusion
Put the product on the page, say in plain words what it does and who for, publish a number with the currency on it, and ask for nothing at signup beyond what creates an account. Then stop counting signups and start counting how many of them reach the one action that shows the product working. That second number is the one that predicts revenue.
If your traffic is fine and your signups are not, the problem is almost always the first screen and the pricing page. Send us the URL through our intake form and we will tell you which of the two it is before you commit to a rebuild.
