SaaS website design: three questions in order
**What is this, in the language I already use?** Category first, cleverness later. A visitor who cannot place the product in a category in four seconds has nowhere to put anything else you tell them. Naming the category is not beneath you; it is the price of being understood.
**Is it for someone like me?** Team size, industry, stage, the shape of the problem. Vagueness here is expensive: a site that could be for anyone reads as built for no one, and the people who would have paid assume it is not for them.
**Can I believe it works?** This is where most SaaS sites are thinnest, and it is the one that decides. Logos, numbers, a real screen showing real data, an integration list — anything that is checkable rather than claimed.
Those three in that order. A homepage that opens with the third question is bragging to strangers, and one that never reaches it is a brochure.
The screenshot problem
Every SaaS site shows the product, and almost every one shows it in a way that proves nothing: a dashboard at an angle, too small to read, filled with placeholder rows called Lorem Corp.
A screenshot earns its space when a visitor can read one real number in it and recognise the situation. That usually means cropping hard into a single view rather than showing the whole application, and using data that looks like somebody's actual Tuesday.
Motion helps here more than anywhere else, because it can show a sequence — this state becomes that state — which a static frame cannot. It also helps less than people hope, and motion that sells covers where the line is.
What technical buyers need that others do not
Marsec is the sharp version of this. Stablecoin infrastructure sells on one feeling: nothing here is improvised. That is not a message you can write down — it has to be produced by how the page behaves, how the type is set, how consistent the spacing is. In this segment the site is a competence demonstration before it is a sales document.
Same with i4B: an engineering partner is hard to photograph, so the car became the picture and the software was drawn around it. When the product cannot be shown directly, the design has to find the object the buyer already trusts and attach to that.
Practical consequences: documentation and status pages linked from the top level rather than the footer, security and compliance stated plainly, and no marketing language over anything a technical reader can verify in ten seconds. One inflated claim costs the whole page its credibility with this audience.
Pricing, and the page everyone gets wrong
Show it. “Contact us for pricing” is a reasonable enterprise motion and a bad default, because it removes the visitor's ability to qualify themselves and moves that cost onto your sales time.
If the model genuinely is bespoke, publish the shape of it — what it is priced on, and a range. That is the same argument as our own four bands: a range tells someone in thirty seconds whether to keep going.
And write the plan names for the buyer rather than for the roadmap. Names that describe who a plan is for outperform names that describe what it contains, because the visitor is trying to locate themselves, not audit the feature matrix.
Questions we get asked
What should a SaaS marketing website include?
The category in plain language, a clear statement of who it is for, and checkable proof that it works — in that order. Then pricing, real product screens cropped tight enough to read, and documentation linked at top level rather than buried in the footer.
Should a SaaS site show pricing?
Almost always. Hiding it removes a visitor's ability to qualify themselves and shifts that work onto sales calls. If pricing is genuinely bespoke, publish what it is priced on and a range — the shape of the number is what people need to decide whether to continue.
How do you show a product that has no physical form?
Crop hard into one real screen with readable, plausible data rather than showing the whole application small and tilted. Where the product resists being shown at all, attach it to an object the buyer already understands — the way an engineering partner is shown through the machine it works on.