Sevginur Ak Parlak
Oct 12, 2026
8 min read
SaaS Landing Page Design: The Structure I Use and What I Test First
A landing page is not a poster. It is a flow with 1 exit, and most of the pages I am asked to redesign fail long before the visual layer. They fail in the first sentence, where the product is described in words the buyer would never type into Google.
I design landing pages for SaaS and B2B products, usually next to the product itself, and the pattern repeats. The team spends 4 weeks on illustrations and 20 minutes on the headline. Then traffic arrives, bounces, and everyone concludes that the design needs to be more modern.
This post is the structure I use, what the top of the page has to do, what I change first when a page is not converting, and what a landing page project costs at Studio Scale.
The page has 1 job, and it is not to explain everything
Before structure, the decision that saves the most time: name the 1 action. Book a demo, start a free trial, join a waitlist, request pricing. 1 page, 1 primary action, repeated 3 or 4 times down the page in the same words.
Pages with 2 equal actions perform worse than pages with 1, because the visitor now has a decision to make about your product and a decision to make about your page. Secondary actions still exist, they just look secondary: a text link instead of a filled button.
The second decision is who the page is for. A page written for 3 audiences at once produces sentences so general that they describe every product in the category. If you serve 3 audiences, that is 3 pages, and each of them can be specific.
What the fold has to answer in 5 seconds
I test every fold against 4 questions. A visitor should be able to answer all 4 without scrolling, in about 5 seconds.
1. What is this?
A category the reader already knows. "Scheduling software for clinics" tells me more than "the operating system for modern care".
2. Who is it for?
Name the role or the company type. Specific exclusion is what makes the right reader feel recognised.
3. What changes for me?
The outcome in the buyer's own words, not the feature list. This is the sentence I spend most time on, and I write it with the founder using language from sales calls and support tickets rather than from the pitch deck.
4. What do I do next?
1 button, high contrast, above the fold, with a label that describes what happens after the click.
I also put the product in the fold. A real screenshot of the interface with real data outperforms an abstract illustration in every test I have run, because the visitor is trying to work out what they will be using. If the interface is not ready to show, show a small part of it rather than an invented one.
The 9 blocks, in reading order
This is the structure I start from for a SaaS product page. Not every page needs all 9, and the order matters more than the count.
1. Fold.
The 4 answers above, 1 action, a real product image.
2. The problem, in their words.
2 or 3 sentences that describe the situation the visitor is in today. When this block is written well, the reader recognises their own week, and everything after it is easier to believe.
3. How it works, in 3 steps.
Numbered, concrete, with an interface image per step. This block replaces the feature list for most visitors, because a person can hold 3 steps in their head and cannot hold 14 features.
4. Proof.
Logos, a metric a customer will let you publish, a quote with a full name and a role, a case study link. Anonymous testimonials read as invented. If you have 2 real customers, name those 2, it works better than 10 grey logos nobody recognises.
5. Use cases or roles.
Short blocks that let different readers find themselves. This is also where you catch search traffic for the job rather than the category.
6. Objections.
The 4 or 5 reasons a buyer hesitates: migration effort, security, pricing model, integrations, what happens to their data, whether it works at their size. Answer them on the page. Every objection you do not answer becomes an email you have to answer anyway, or a visitor who leaves.
7. Pricing, or a clear reason there is none.
More on this below.
8. FAQ.
Real questions from sales calls, written as the buyer asks them. This block also does most of the work for AI search and for long tail queries, because it matches the way people phrase questions.
9. Closing action.
The same button, plus 1 line that removes the last bit of friction: how long the call takes, that no card is needed, that setup is 10 minutes.
Pricing pages, where most B2B sites lose people
"Contact us" as the only pricing signal is a filter, and it filters out more good buyers than bad ones. If you cannot publish a number, publish the shape: what drives the price, a starting point, what a typical customer of your size pays, and what is included at each tier.
3 things I fix on almost every pricing page:
The plan names say nothing.
Starter, Growth and Scale do not tell me which one I am. "For teams up to 10" does.
The comparison table is too long.
30 rows of feature names, most of which mean nothing before purchase. I cut it to the 8 to 12 lines that actually differ and put the rest behind a toggle.
There is no annual and monthly clarity.
Show both numbers, show the saving as a number, and never make the visitor calculate.
What I change first when a page is not converting
I work through this in order, because the earlier items move the number more and cost less than a redesign.
1. The headline and the outcome sentence.
Free to change, largest single effect in my experience. Most rewrites come directly from customer language.
2. The action.
Its label, its position, how many times it appears. Changing "Get started" to "Book a 15 minute demo" sets an expectation, and expectations reduce drop off on the next screen.
3. The proof block.
Moving proof higher, and replacing generic quotes with a named customer and a number.
4. The form.
Every field costs completions. I ask which fields the sales team actually uses before the first call, and remove the rest. Most B2B forms can lose 3 fields without losing anything.
5. Page speed and the fold on mobile.
More than half of first visits are on a phone, and on a phone the fold is roughly 1 screenshot high. If the page takes 6 seconds and the headline sits below a large image, nothing else on this list matters.
6. The visual design.
Last, deliberately. A page with the right message and a plain layout outperforms a beautiful page that describes the wrong thing to the wrong person.
Writing for AI search as well as Google
Buyers now ask a model "what is the best scheduling software for small clinics" and read the answer instead of the results page. That changes 3 things on a landing page.
Be explicit about the category, the audience and the constraints you serve, in plain sentences. Models summarise what a page states clearly, and they cannot infer what your metaphor was meant to imply.
Put facts in a structure: pricing as numbers, integrations as a list, limits and plan sizes as text rather than only inside images. A fact that exists only in a screenshot is invisible.
Keep an FAQ written in question form, matching how a person would ask it out loud. This is also the block that most often gets quoted back in an AI answer.
None of this is a trick. It is the same discipline as writing for a busy human, applied to a reader that cannot see your illustrations.
Mistakes I see most often
Describing the product as a vision instead of a category. The visitor cannot buy a vision, and they cannot search for it either.
Hiding the interface. If a buyer has to book a call to see what the product looks like, a share of them will simply not book.
Auto playing a hero video instead of showing 1 clear screen. A video is a request for 90 seconds from someone who has given you 5.
Writing the page for the team rather than the buyer. Internal vocabulary, module names and the roadmap have no meaning outside the company.
Testing the button colour before the message. Colour tests are easy to run and almost never the reason the page is not working.
FAQ
How long does a SaaS landing page design take?
1 week for a single page on an existing brand, 2 weeks when messaging and copy are included, and 3 to 5 weeks for a marketing site of 5 to 7 pages.
What should be above the fold on a SaaS landing page?
A headline naming the category and the audience, 1 sentence on the outcome, 1 primary action, and a real image of the product. A visitor should answer what it is, who it is for, what changes and what to do next without scrolling.
Do I need a copywriter as well as a designer?
Not always separately. The structure and the words are 1 decision, so I write the page with the founder as part of the design. For long marketing sites or a specific tone of voice, a copywriter is worth it.
Should I show pricing on the website?
Yes, or at least the shape of it: what drives the price, a starting number, and what a customer of a given size pays. A page with no pricing signal loses buyers who were ready and keeps the ones who wanted a call anyway.
How do I know if the page is working?
Pick 1 number before the redesign, usually demo bookings or trial starts per 100 visits, and measure the same number after. Session recordings and scroll depth tell you where people stop. Without a before number, a redesign is a matter of taste.
Working with us
We design landing pages and marketing sites for SaaS and B2B products, usually in 1 to 3 weeks, and we write the message with you rather than dressing up a paragraph we were given. You get the page, the mobile layout, the states of every form, and the build in your own stack.
If your page gets traffic and not many signups, book a free 15 minute intro call and send us the link. We will tell you the 3 things we would change first, in order.
