Opens in a new tab
All articles
B2B Web Design

8 Rules for B2B SaaS Website Design That Win Demos

B2B SaaS website design has to work for a buying group, not one visitor. Eight rules from my Snappy Kraken and Advisor Websites builds: pricing pages a committee can read, short demo requests, webinar replay pages and templates marketing can run alone, with CAD prices.

31 firms in Johnston and Bonoma's 1981 buying center study, beside three pricing cards with the middle plan carrying a written reason

Published 24 January 2025 · Last updated and fact-checked November 2026

Short answer: B2B SaaS website design has to work for a buying group, not one visitor. That means a pricing page a committee can read, a short demo request, a replay page for every webinar and templates marketing can run alone. The group is real: its makeup differed by purchase type across 31 firms (Johnston and Bonoma, 1981).

An operations lead at a 12-person advisory firm has two tabs open. She sat through both product demos last week. Now she is on the pricing pages, and her managing partner wants a recommendation by Friday. The homepage got the budget. The page where she has to defend a number got a table of ticks.

It isn’t a looks problem. A software site carries jobs a services site never has. I run Jackai Agency in Vancouver, and I’ve built each of these jobs for two SaaS companies that sell to financial advisors: Snappy Kraken on HubSpot CMS, and Advisor Websites, a Vancouver platform. These 8 rules follow the order a buyer meets the site.

Key takeaways

  • A meta-analysis of 99 observations found choice overload grows with complex option sets and unsure buyers (Chernev and colleagues, 2015), so write plan differences as sentences.
  • Improved web forms were finished faster in a 65-person eye-tracking study at the University of Basel (Seckler and colleagues, 2014).
  • At Advisor Websites, a replay library and opt-in templates came with organic traffic up 58% and MQL conversion up 28%.
  • Snappy Kraken went from Figma to production on HubSpot CMS in 3 weeks, and its marketing team now ships pages alone.
  • A custom B2B website from Jackai Agency starts at CA$7,450; a SaaS marketing site of 8 to 15 pages starts at CA$10,495 (price table, November 2026).
#RulePage it fixesEvidence
1Plan pages for the buying groupSitemapJohnston and Bonoma, 1981
2Write pricing differences as sentencesPricing pageIyengar and Lepper, 2000; Chernev and colleagues, 2015
3Give the middle plan a reason, not a badgePricing pageSimonson, 1989
4Ask only what sales will useDemo request pageSeckler and colleagues, 2014
5Choose demo or trial by time to valueMain buttonFoubert and Gijsbrechts, 2016
6Give every webinar a replay pageWebinar libraryPirolli and Card, 1999
7Write product pages for the buyer’s checksProduct pagesLindgaard and colleagues, 2006; Fogg and colleagues, 2003
8Let marketing ship pages without a developerCMS and templatesSnappy Kraken case

1. Plan pages for the buying group, not one buyer

B2B SaaS website design starts from a different page list than a services site, because a group buys software, not a person. It suits any SaaS team selling to firms with more than one decision maker. Johnston and Bonoma studied that group, the buying center, across 31 firms (Journal of Marketing, 1981).

Diagram of three readers in one buying group, the user on product pages, the budget holder on the pricing page and the compliance reviewer on the compliance answer, each with the page they read; Johnston and Bonoma 1981
  • Who reads it: a user, a budget holder and often a compliance reviewer
  • First conversion: a demo request, a free trial or a webinar sign-up
  • Where the decision happens: on the pricing page, often before any call
  • Traffic sources: search, webinars, partners, events and paid campaigns

A services site sells a team and a conversation. The visitor decides whether to talk to you, and the first conversion is a booked call. A SaaS site sells a product that someone has to evaluate, compare and then defend to the people who share the budget. Most of that work happens before anyone fills in a form.

“Equipment and service purchase measures differed reliably across several indices suggested by our theoretical orientation,” wrote Wesley Johnston of Ohio State University and Thomas Bonoma of Harvard University (Journal of Marketing, 1981).

That paper studied industrial purchases in 1981, not software, so read it as a direction. On the SaaS sites I’ve built, it held up. Each member of the group read a different page. The user read the product pages. The person who signs read the pricing page. The compliance officer looked for one answer and left if it sat in a PDF.

So I draw the sitemap from the readers first. Every reader needs one page that answers their question without a salesperson. If a reader has no page, that reader becomes the reason the deal stalls.

2. Write pricing differences as sentences, not ticks

A SaaS pricing page is the page where a buyer builds the case she will defend to her partners. Writing the differences between plans as sentences suits any product with more than one tier. Choice overload grew with complex option sets and unsure buyers across 99 observations (Chernev and colleagues, 2015).

B2B SaaS website design example: Snappy Kraken pricing page rebuilt with plan differences written as sentences
Snappy Kraken pricing page, a Jackai Agency build. Graphic generated with Higgsfield from a screenshot of the live page.
  • One focal action per screen: each plan gets its own space and one next step
  • Differences in words: what changes from the plan below, and who it suits
  • The objection beside the number: setup time or contract length next to the price
  • Full comparison table: kept, but lower on the page

On the Snappy Kraken project, the pricing page carried the most traffic on the site and had the least design. Snappy Kraken is a B2B FinTech SaaS company that sells marketing systems to financial advisors. Its old pricing page was a three-column plan table with rows of feature names and ticks. Nothing on it said what changed between plans, or who each plan was for.

A tick table works for a buyer who already knows which feature matters. Most don’t.

“Findings from 3 experimental studies starkly challenge this implicit assumption that having more choices is necessarily more intrinsically motivating than having fewer,” wrote Sheena Iyengar and Mark Lepper (Journal of Personality and Social Psychology, 2000).

Their shoppers bought jams more often from 6 options than from 24. Chernev’s later meta-analysis is the more useful one for software, because it names when the effect grows: complex options, hard tasks and buyers unsure what they want. Three plans across nine rows of features is a complex set. Should you publish prices? For a product sold to small firms, I’d say yes. That is my experience from client projects, not a research finding.

The middle plan is the one most B2B buyers end up defending, so it needs a written reason a buyer can paste into an email. This suits any SaaS pricing page with three or more plans. Simonson found a middle option gains share as a compromise, more so when people expect to justify the choice (Journal of Consumer Research, 1989).

Two pricing cards compared: one carries a struck Most Popular badge, the other names its buyer as firms with 5 to 20 advisors; Simonson 1989
  • Badge test: delete “Most Popular” and check whether the plan still explains itself
  • Labels that name the buyer: “Firms with 5 to 20 advisors” beats a tier name
  • Reason in one line: who it suits and why, in words a partner would repeat
  • Starting price for enterprise: plus what changes the quote, not “contact us”

That last point in Simonson’s paper is the B2B buyer exactly. She is not only choosing. She is choosing something she can explain to a managing partner on Friday. A badge gives the committee nothing to repeat. A sentence does.

So the middle plan earns its place only when its reason is written where she can copy it. “Most firms our size pick this” is not a reason. “Includes the compliance review queue, which firms with more than 5 advisors need” is a reason, because it names who and why.

The same logic covers plan names. “Starter, Pro, Business” tells a reader nothing about where she fits. A label that names the buyer does the sorting for her, and she stops comparing rows she doesn’t need.

For enterprise contracts, a starting price plus the three things that change the quote still beats a blank “contact us” box. A buyer who can’t find any number has to book a call just to learn whether she can afford you, and plenty won’t book it. That part is my judgment from projects, not a finding.

4. Ask only what sales will use on the demo request

The demo request is the SaaS version of a contact form, and it’s the first step I check on any SaaS site. Cutting it to what sales will use suits every team that judges marketing on demo count. Improved forms were finished faster with fewer failed submissions in a 65-person study (Seckler and colleagues, 2014).

Annotated demo request page with four fields, a calendar slot picker, what happens next and a hidden source field passed to the CRM; Seckler and colleagues 2014
  • Fields: name, work email, company and one qualifying question
  • What happens next: how long the demo runs, who runs it, whether a colleague can join
  • Booking: a calendar on the page, not an email back and forth
  • Source: page, campaign and channel carried into the CRM

At Advisor Websites, a Vancouver SaaS platform that builds websites for financial advisors, the booking page asked for a decision before it gave a reason. The old version was a plain form. The rebuilt page offers real-time calendar booking, with a video from the CEO and named testimonials beside it.

“Improved web forms lead to faster completion times, fewer form submission trials, and fewer eye movements,” reported Mirjam Seckler and colleagues at the University of Basel (CHI Conference Proceedings, 2014).

Those were forms on real company websites, close to a demo form but not the same page. The form I remove first asks for budget, timeline, headcount and tech stack before a time slot appears. Ask those on the call.

Advisor Websites also needed a way in for each role: the advisor who owns the firm, the office manager and the compliance officer. Then record the source. In my experience, demo count is the number marketing gets judged on. If the first month of demos arrives untagged, you lose the baseline that tells you whether the redesign worked. My lead attribution method shows how the tags travel from link to form to CRM.

5. Choose demo or free trial by how fast a buyer sees value

The main button on a SaaS site is either a demo request or a free trial, and the right one depends on how fast a buyer sees value. It suits teams arguing about which button goes first. A study of a digital TV service found free trials can win subscribers or lose them for good (Foubert and Gijsbrechts, 2016).

Decision diagram for the main button: trial first when one person can set it up and see a result alone, demo first when several people share the decision or setup needs help; Foubert and Gijsbrechts 2016
  • Trial first: one person can set it up and see a result alone
  • Demo first: several people share the decision, or setup needs help
  • Second button: the other option, smaller, never competing
  • Trial risk: a poor first week can lose the prospect for good

Free trials feel like the generous choice. They are only generous when the product works on day one without a guide.

“Free trials constitute a double-edged sword, and that timing and consumers’ usage intensity during the trial are key to the effectiveness of these promotions,” wrote Bram Foubert of Maastricht University and Els Gijsbrechts of Tilburg University (Marketing Science, 2016).

Their data came from an interactive television service, not B2B software, so take the direction and not the size of the effect. The direction is clear enough. A trial where the buyer never reaches the useful part is worse than no trial, because she leaves with a verdict.

At Advisor Websites, booking a demo is the main goal and a free trial is second. Several people at an advisory firm share the decision, and the compliance officer won’t sign off on a trial account alone. A tool one analyst can test in an afternoon goes the other way.

Whichever goes first, use one action and repeat it in the same words. The old Snappy Kraken homepage showed its main action 4 times in 4 different phrasings, so it read like 4 different choices.

6. Give every webinar a replay page that keeps working

A webinar replay page holds the recording, a short summary and one next action, at a stable address that search engines can index. It suits any SaaS team running webinars. At Advisor Websites, a replay library and opt-in templates came with organic traffic up 58% and MQL conversion up 28% (Advisor Websites case study).

Before and after flow of an old webinar invite, before leading to a dead registration page and after leading to a replay page with summary and one next action; Pirolli and Card 1999
  • Replay library: every session is its own page, browsable after it airs
  • Replay template: recording, summary and one next action; marketing fills it alone
  • Old invite links: open the replay, not a sign-up form
  • Route from the homepage: one visible path into the library

In my experience, webinars rarely make it into a brief for a SaaS site, yet webinar traffic behaves like nothing else on it. Picture an advisor who registered, missed the session, and finds the invite two days later. She clicks the link. It opens a registration page for an event that already happened. No recording, no summary and no next step.

That was the situation at Advisor Websites. The sessions were being recorded, but the recordings lived in email and expired with the invite. So every webinar stopped earning the day after it aired.

The research term for what broke is information scent. Pirolli and Card describe how people judge a path from the cues in front of them and change what they do to find useful information at the best rate (Psychological Review, 1999). A webinar invite is a strong cue. A dead registration page cuts the trail where the visitor was most interested.

The fix was not more webinars. It was a page for each one. MQL means marketing-qualified lead, a contact marketing has judged ready for sales. Those two figures belong to the replay library and opt-in template work, in that period, not to webinars in general.

7. Write product pages for the buyer’s checks, not the feature list

A SaaS product page explains why the product fits one buyer, using the checks that buyer runs before saying yes. It suits any SaaS team whose pages are named after internal modules. Looks still count, and fast: people rated a homepage’s visual appeal within 50 milliseconds (Lindgaard and colleagues, 2006).

Before: the Snappy Kraken homepage before the rebuild
Before: the Snappy Kraken homepage before the rebuild.
  • A named reader in the first screen: “For firms with 3 to 30 advisors”
  • Real screenshots: the actual product with realistic data, not a drawn mockup
  • One proof point near the claim: a named customer and one number
  • The compliance answer: on the page, not in a PDF behind a form

Before the redesign, the Snappy Kraken homepage led with features and never said who it was for. After the rebuild, the advisor is named in the first screen, and one action repeats in the same words down the page.

Product pages follow the same rule. At Advisor Websites, each page was built around what an advisor checks before buying: compliance, how far a site can be personalized, search performance, CRM integration and the template library. A feature list says what the product has. A page built on those checks says why it fits this buyer and not the next one.

“Visual appeal can be assessed within 50 ms, suggesting that web designers have about 50 ms to make a good first impression,” wrote Gitte Lindgaard and colleagues (Behaviour and Information Technology, 2006).

Credibility rides on the same first look. In a study of 2,684 people judging live websites at Stanford University, the design look came up more than any other feature (Fogg and colleagues, 2003).

“Was mentioned most frequently, being present in 46.1% of the comments,” wrote B. J. Fogg and colleagues about the design look (DUX Conference Proceedings, 2003).

Buyers search for the job they need done, not your team’s module names, so name each page after the job it does.

8. Let marketing ship pages without a developer

A SaaS marketing site needs new pages for launches, webinars and segments, often within days. Building it from modules marketing can assemble alone suits any SaaS company whose roadmap outruns its developers. At Snappy Kraken, I took 6 responsive pages from Figma to production on HubSpot CMS in 3 weeks (Snappy Kraken case study).

After: the Snappy Kraken homepage I rebuilt on HubSpot CMS, live in 3 weeks
After: the Snappy Kraken homepage I rebuilt on HubSpot CMS, live in 3 weeks.
  • Modules, not one-off pages: hero, proof block, pricing table, replay embed and form
  • Locked styles: type, colour and spacing live in the theme
  • Templates for repeat pages: replays, product pages, customer stories, comparisons
  • A short handover guide: which module does which job

On my projects, services firms rarely needed this. SaaS companies almost always did. A software company ships features, runs webinars and changes plans, and each of those needs a page. If every page waits for a developer, the site falls behind the product. That is why I treat editing as part of the design, not a handover detail.

At Snappy Kraken, marketing owned a roadmap larger than the team could build. So anything I shipped had to be editable by the in-house team, with no designer in the loop. I used HubL templates and a bound design system. The clock started from designs already in Figma, not from a blank page. Afterwards, the marketing team edits and ships pages inside that system on its own.

Sales, pricing and product all moved in the same period, so I can’t separate my pages from those changes, and I won’t pretend to.

HubSpot CMS and WordPress can both do this. If your CRM is already HubSpot, keeping the site there removes one integration to maintain. My HubSpot CMS redesign service covers that route.

What does B2B SaaS website design cost in Canada, and how long does it take?

These are my own prices from the Jackai Agency price table, in Canadian dollars, current in November 2026. Every quote is fixed, with two revision rounds per phase. You own the site, the domain and the hosting, and I reply within 1 business day. Snappy Kraken went from Figma to production in 3 weeks (case study).

ScopePrice (CAD)
Custom B2B website, up to 5 pages, on HubSpot CMSCA$9,700
Custom B2B website, up to 5 pages, on WordPressCA$8,950
Custom B2B website, up to 5 pages, on Framerfrom CA$7,450
Marketing site, 8 to 15 pages, 4 to 6 weeksfrom CA$10,495
Landing page design, 1 to 2 weeksfrom CA$3,795
Lead source reporting, 2 weeksCA$2,600

For a SaaS site, the marketing site row is the usual fit, because a pricing page, a demo path, product pages and a replay library run past 5 pages. The full menu is on my pricing and calculator page.

In my experience, what slows a SaaS site is rarely the build. It’s plan pricing that isn’t final, product screenshots nobody has captured, and compliance copy waiting on review. If you can only fund one piece this quarter, this is how I’d choose.

What you see nowWhere I’d start
The pricing page gets traffic but few demo requests followRebuild the pricing page and the booking step
You run webinars and the recordings sit in emailA replay library and a replay template
Marketing waits on a developer for every new pageA design system and page templates on your CMS
Nobody can say where last month’s demos came fromLead source reporting, before any redesign
All four at onceA marketing site build, 8 to 15 pages

Which rule fits the problem on your site?

Most SaaS sites don’t need all 8 rules at once. Filter the matrix by the page that worries you and by budget to see which rule applies, what it costs from my price table and the research behind it. A pricing page fix, for example, sits in the CA$3,795 landing page scope (pricing).

RuleWhat you see nowScope and price (CAD)Research behind it
1. Plan pages for the buying groupOne page tries to answer the user, the budget holder and compliance at onceMarketing site, 8 to 15 pages, from CA$10,495Johnston and Bonoma, 1981 (31 firms)
2. Write pricing differences as sentencesThe pricing page gets traffic but few demo requests followLanding page design, from CA$3,795Iyengar and Lepper, 2000; Chernev and colleagues, 2015
3. Give the middle plan a reasonA “Most Popular” badge with no reason beside itLanding page design, from CA$3,795Simonson, 1989
4. Ask only what sales will useThe booking form asks budget, timeline and headcount before a time slotLanding page design, from CA$3,795Seckler and colleagues, 2014 (65 people)
4. Record the source of every demoNobody can say where last month’s demos came fromLead source reporting, CA$2,600First-party method
5. Choose demo or trial by time to valueTwo main buttons compete in different wordsLanding page design, from CA$3,795Foubert and Gijsbrechts, 2016
6. Give every webinar a replay pageRecordings sit in email; old invites open a sign-up formCustom B2B website, from CA$7,450Pirolli and Card, 1999
7. Write product pages for the buyer’s checksPages named after internal modules, no named readerCustom B2B website, from CA$7,450Lindgaard and colleagues, 2006; Fogg and colleagues, 2003
8. Let marketing ship pages aloneMarketing waits on a developer for every new pageCustom B2B website on HubSpot CMS, CA$9,700Snappy Kraken project, first-party

Showing 9 of 9 rows.

Prices from the Jackai Agency price table, November 2026. Matching a rule to a scope is my judgment; the final quote is fixed after a call.

Work out what a better pricing page is worth

This calculator shows your pricing page to demo rate, what one more point of that rate means in demos and customers, and how many months that lift takes to cover a build price. Enter your own numbers; the defaults are placeholders. Prices come from my November 2026 table (pricing).

Defaults are placeholders, not a forecast or a promise. The only fixed numbers are the prices, from the Jackai Agency price table, November 2026.

Questions about B2B SaaS website design, answered

These are the questions Canadian SaaS teams ask me before a project, worded the way they come up in search. Each answer is short and stands alone, with a price or a source where one exists. The buying-group research behind several answers covers 31 firms (Johnston and Bonoma, 1981).

What pages should a B2B SaaS website have?

At minimum: a homepage that names the buyer, product pages built on the buyer’s checks, a pricing page with differences written as sentences, a demo request page, a replay library if you run webinars, and a compliance answer. A marketing site of 8 to 15 pages usually covers it.

How much does a B2B SaaS website cost in Canada?

From my November 2026 price table: a custom B2B website of up to 5 pages starts at CA$7,450 on Framer, CA$8,950 on WordPress and CA$9,700 on HubSpot CMS. A SaaS marketing site of 8 to 15 pages starts at CA$10,495 and takes 4 to 6 weeks.

Should a SaaS website show pricing?

For a product sold to small firms, I think yes. A buyer who can’t find a number has to book a call to learn whether she can afford you, and many won’t. For enterprise contracts, show a starting price plus what changes the quote. That’s my project experience, not research.

Should the main button be a demo request or a free trial?

Use a free trial when one person can set it up and see value alone. Use a demo request when several people share the decision or setup needs help. Research on a TV service found free trials cut both ways, because a poor first week loses prospects.

Want a second pair of eyes on your pricing page and demo path?

I design and build B2B SaaS websites from Vancouver for Canadian software teams, on a fixed quote. A Website Audit costs CA$995 and is credited if a project starts within 30 days. On a 30-minute call I measure your starting numbers first: mobile conversion rate, AI-referred traffic and lead count.

The recordings at Advisor Websites already existed. At Snappy Kraken, the product was never the problem. In both cases the gap sat on a handful of pages: the price, the demo request, and replays that expired in an inbox.

“In both cases the gap sat on a handful of pages: the price, the demo request, and replays that expired in an inbox,” said Joshua Jackai, Vancouver web designer.

Before you brief anyone, run this 20-minute check on your own site:

  1. Open your pricing page on a phone and time how long it takes to learn what changes between plans.
  2. Click your demo request button, count the fields, and read what the confirmation page says happens next.
  3. Open a webinar invite from three months ago and follow its link.
  4. Open two product pages and check whether the first screen names who each one is for.
  5. Pull last month’s demos from the CRM and count how many carry a source.

“If every page waits for a developer, the site falls behind the product,” said Joshua Jackai, Vancouver web designer.

Book a 30-minute call and bring the page you’re least sure about, or start with a Website Audit. You leave the call with your starting numbers whether or not you hire me.

Sources

Peer-reviewed research

Industry and vendor data (not peer reviewed)

×

Privacy Preference Center