SaaS website personalization means changing what your marketing site shows (headline, proof, recommended plan, CTA) based on who is visiting: their industry, company size, or relationship with you. The usual alternative for getting more signups is buying more traffic, which raises cost in step with volume. Personalization works on the conversion rate of the traffic you already have, which is why it tends to come up once paid acquisition gets expensive.
SaaS personalization is not ecommerce personalization. You are not recommending products; you are reframing one product for very different buyers. A 10-person startup and a 5,000-person company need to hear different things about the same tool, and the page that tries to address both at once usually speaks to neither. Affiliate and partner traffic is a segment of its own; see SaaS affiliate marketing commission models. This post covers what to change for each segment, then a 30-day rollout plan and how to measure it.
Why SaaS Sites Suit Personalization
- Buyers come back several times. SaaS evaluations rarely end on the first visit. Check your own analytics for the number of sessions before signup or demo request; each return visit is a chance to show something more relevant than last time.
- One product, many segments. A project management tool might sell to marketing, engineering and operations teams, each caring about different features and integrations. One homepage cannot lead with all of them.
- The site does much of the selling. In self-serve and product-led motions, many buyers evaluate without talking to anyone. The website has to answer the objections a rep would otherwise handle.
The Pricing Page
The pricing page is where intent is highest and where the personalization logic is easiest to justify. For a baseline of how leading SaaS companies lay theirs out, see these pricing page examples; for the build, follow B2B pricing page personalization.
Highlight the plan that fits
If you know the visitor's company size from identification or the CRM, change which plan carries the "recommended" badge. A 500-person company sees the Business or Enterprise card highlighted; a 20-person team sees Starter or Pro. All plans and all prices stay visible and identical for everyone. Changing prices by visitor is a different (and much riskier) thing; changing which plan you point to is not.
Match the proof
A healthcare buyer on your pricing page is asking "do companies like us use this?" A healthcare logo row and a short quote from a healthcare customer answer that; a startup founder's testimonial does not. You need real proof for each segment you personalize for. If you do not have a healthcare customer, do not build a healthcare variant.
Match the CTA to the buying process
Larger companies often need a quote, a security review and a contract, so "Talk to sales" fits. Small teams usually want to try the product first, so "Get started" fits. Showing the wrong one adds friction in either direction. Where the two overlap (a mid-sized team on a mid-tier plan), offer both. Our post on personalized CTAs covers testing CTA variants.
Industry Messaging
Headlines
Generic value propositions ("Streamline your workflow") tell nobody that the product is for them. If identification gives you the industry, the homepage headline can lead with what that industry cares about. Illustrative variants for a workflow tool:
| Segment | Headline | What it leads with |
|---|---|---|
| Healthcare | "Patient data workflows with the audit trail your compliance team asks for" | Compliance |
| Financial services | "Approval workflows that hold up in an audit" | Control and auditability |
| Ecommerce | "Get orders, returns and supplier updates out of the inbox" | Operations speed |
| Default | "The workflow platform for growing teams" | Broad benefit |
Each claim in a variant has to be true for that segment, and the page below the headline has to back it up. Our guide to industry-specific website personalization goes deeper on picking industries and writing variants.
Case studies and use cases
Surface the case study from the visitor's industry in the homepage proof block, the blog sidebar and the pricing page. Even with only a handful of case studies, showing the relevant one first saves the visitor from hunting for it. Measure whether it changes anything: track case study clicks and downstream conversion for the matched variant against a holdout that sees the default order.
Feature emphasis
Reorder, rather than rewrite, the features section by segment. A logistics company may care first about the API and real-time tracking; an agency may care about collaboration and client reporting. Same features, different order.
By Company Size
Company size is often the most dependable dimension for SaaS, because it changes budget, buying process and feature needs together, and identification tools return it reliably for companies they can match.
| Size band (example) | What to lead with | What to play down | CTA |
|---|---|---|---|
| Small (1-50) | Quick setup, self-serve, entry price | SLAs, SSO, dedicated account managers, custom contracts | Get started |
| Mid-market (50-500) | Scaling with the team, integrations, collaboration, peers of similar size | Heavy enterprise procurement language | Both: start, or book a walkthrough |
| Enterprise (500+) | Security certifications, SSO/SAML and SCIM, admin controls, data residency, support terms | "Up and running in 5 minutes" messaging that implies a toy | Talk to sales |
Pick band edges from your own customer data (where does the buying process actually change?), not from the example above. And only list security and compliance items you actually have; an enterprise variant that mentions certifications you cannot evidence will fail the first security review.
Free-Plan Users Who Come Back to the Site
Users on a free plan often return to the marketing site to compare plans or find material to justify a budget request. They do not need the "what is this product" story again.
- Recognise them. Set a first-party cookie or pass a parameter when a logged-in user clicks from the app to the marketing site. Use it to swap the hero from "Get started" to the upgrade path, and to show plan comparisons that start from their current plan.
- Tie the upgrade pitch to the limit they are hitting. If your app knows a user is near the storage or seat limit, the marketing site can lead with the plan that removes that limit. This needs your product data to reach the website, so check with your privacy lead which usage data you may use this way.
- Give them a business case. A short page or PDF a user can forward to their manager (what the paid plan adds, price, security summary) helps with the internal sell that free users often struggle with.
Existing Customers
When identified customers visit the blog or resources, prioritise material for features they have and the stage they are at, rather than beginner content aimed at prospects. Hide signup and "Book a demo" CTAs for them; offer support, training and "What's new" instead.
Customers browsing pages for higher tiers or other products are an expansion signal. Route it to the account manager rather than showing an aggressive upgrade banner. Our guide to routing website leads by intent covers how to send account-level alerts.
Where to Start
- Pricing page by company size. High intent and clear logic: recommended plan, proof and CTA by size band. Measure plan-card clicks, signups and sales form starts against a holdout.
- Homepage hero by industry or size. The broadest reach. Change headline, subheadline, proof and CTA; keep the layout fixed. Our B2B homepage personalization guide lists what to change.
- Proof matching across pages. One rule that swaps logos and the featured case study by segment, applied everywhere those blocks appear.
- Free users and customers. Stop showing acquisition messaging to people who already signed up.
Product and feature pages (proof blocks) and blog CTAs come after these. They get less traffic per page and sit further from a signup.
A 30-Day Rollout Plan
Work in this order: identify, segment, map content, measure. Each step depends on the one before it. You cannot segment visitors you have not identified, and a content variant without a defined segment is just a guess.
| Week | Do | Done when |
|---|---|---|
| 1 | Deploy visitor identification and connect it to the CRM so identified companies are matched to existing accounts, open deals and customers. Spot-check twenty or thirty identified companies you know. | You know what share of your own sessions resolve to a company, by size band and industry. |
| 1-2 | Read the homepage and pricing page as each segment would. Note where the headline, proof or CTA does not fit them. | A short list of gaps per segment. |
| 2 | Define two to four segments from closed-won data (size bands first, then your top industries), with a one-line rule each and a fallback for partial data. | Each segment has enough sessions to reach your planned sample size within a quarter. |
| 2-3 | Fill a content map: segments as rows, page elements (headline, proof, CTA, feature order, recommended plan) as columns. Leave a cell on the default when you have nothing better to say. | Every filled cell has real proof behind it. |
| 3 | Set up the holdout, the conversion events and the segment reporting before launch. | You can report conversions per segment for both the variant and the holdout. |
| 4 | Launch on the pricing page or homepage. Check every variant on desktop and mobile, and check page speed with the tag on and off. | No layout breaks, no visible flicker, variants recorded in analytics. |
The segment matrix grows fast: three industries times three size bands is already nine variants of every element you personalize. Start with one dimension, and add the second only when the first has shown a result.
Measuring It
Measure each variant against a holdout from the same segment, decide the sample size before launch (our A/B test sample size guide shows the arithmetic), and give each test long enough to cover full weeks. The size of any lift depends on your traffic, segments and offer, so plan around your own test results rather than published benchmarks.
- Conversion per segment. Signups, plan-card clicks and sales form starts for the variant against its holdout, reported per segment rather than only in total.
- Quality, not just volume. Check whether demo requests and signups from personalized sessions become qualified opportunities or paid accounts at the same rate as the holdout. A CTA can win clicks and lose pipeline.
- Pipeline by segment. Over a quarter, compare pipeline created from each segment's personalized and holdout sessions. Our guide to measuring personalization ROI covers the setup.
Review the numbers weekly for the first couple of months, then monthly once the tests are stable.
Common Mistakes
- Too many segments at launch. Every segment multiplies the content work and splits your traffic. A handful of segments you can measure beats a long list you cannot.
- Personalizing on data you have not checked. If identification puts visitors in the wrong size band, the "recommended plan" points them at the wrong card. Check match quality on your own traffic first.
- Neglecting the default. Unidentified visitors, and visitors who decline consent, still see the default page. Keep improving it with ordinary A/B tests.
- Slowing the page down. A personalization script that delays the hero costs more than the variant gains. Compare Largest Contentful Paint with the tag on and off.
- Treating it as a one-off project. Positioning, pricing and case studies change. Give each rule an owner and a review date so variants do not go stale.
A Practical First Test
A practical first step: define two segments (for example, companies under and over 100 employees), write a pricing page hero for each, and run it against the current page for a few weeks. Markettailor handles both the visitor identification that supplies company size and the personalization that serves the variant, if you would rather not connect separate tools.