HexvorSaaS and software products
A website for your software product
A software product is sold by being understood. What it does, who it is for, and what it costs — in that order, above the fold, before any of the screenshots.
Describe your siteTry something like this
A landing page for a scheduling tool for small clinics. What it does, three real features, pricing with three tiers, and a sign-up. Modern and precise, one accent colour.
The more of it that is true of your business, the less of the result you will have to change. Hexvor never invents a phone number, an address, a price or a review — anything you leave out comes back as an obvious placeholder rather than as a plausible lie.
60 rules the engine applies to this kind of site
Not a feature list. These are the actual instructions sent with your request when Hexvor recognises the trade, on top of the 607 that apply to every site.
Say what it does first
Explain the product before explaining its features. Somebody who cannot repeat what it does to a colleague will not buy it.
One benefit, immediately
Make the primary customer benefit understandable in the first sentence.
One headline, one action
A dominant headline, one supporting sentence, one primary action. Everything else is below.
Show the interface
A real screenshot or a drawn representation of the product wherever it helps understanding. A product site with no product is a brochure.
Features in the order of use
Present features along the customer's journey rather than by internal category.
The problem before the solution
Where the audience may not know they have the problem, establish it before introducing the answer.
Features as outcomes
Translate every technical capability into what somebody gets from it.
Credibility near the decision
Put proof beside the moments where somebody hesitates, not in a strip at the bottom.
Trial and demo stand apart
Make the trial or demo action visually distinct from everything else on the page.
Pricing that can be compared
Make the difference between plans immediately clear. If prices are known, publish them.
No baroque comparison tables
A comparison nobody can read is worse than three sentences.
Real screens, not grey rectangles
Abstract placeholder blocks where a product should be are the clearest sign of a page written before the product existed.
Show the workflow
Place the product inside a real sequence of work rather than describing it in isolation.
Use cases by need
Group use cases by what somebody is trying to do, not by industry labels chosen for a slide.
Enterprise on purpose
Enterprise material should feel designed rather than appended to the bottom of the page.
Integrations where they decide
Show the integrations that change a purchase decision; hide the rest.
Show the setup
Where friction is the objection, show how little there is.
One CTA sentence everywhere
Use the same words for the primary action on every page and every repetition.
Technical depth without exclusion
Speak to engineers without losing the person who signs.
A product has a face
Establish a visual identity rather than reproducing the standard SaaS page.
Dashboards prove, not decorate
Show a dashboard to demonstrate value, never as an image of sophistication.
Say what a trial gives
State exactly what is included, for how long, and whether a card is needed.
Security where trust decides
Where security is part of the purchase, put it where the purchase happens.
Docs are findable
A developer product makes its documentation easy to reach from the front page.
Explain the move
Where switching is the barrier, explain how migration works.
Never imply what it cannot do
Do not describe capabilities the product does not have, in words or in screenshots.
Never invent metrics
No user counts, revenue figures, uptime numbers or growth statistics that were not provided.
Never invent customer logos
A wall of logos of companies that are not customers is fraud with good kerning.
Understanding before decoration
No visual effect may compete with understanding what the product is.
Understand, trust, prove, act
Structure the page in that order. Asking for the action before the proof is asking early.
One goal
A landing page has a single conversion objective and everything serves it.
Clear in seconds
The offer is understood immediately or it is not understood.
Specific over slogan
A specific value proposition beats a memorable but empty line.
Supporting copy removes doubt
One sentence under the headline that answers the obvious question.
One dominant action
A single primary CTA, visually above everything else.
Do not crowd the hero
Secondary content below the fold, not beside the headline.
Show the thing
The product, the result, the experience — whatever can be shown.
Name the problem
Where the audience may not have named it, do it for them.
Solution straight after
Introduce the answer immediately once relevance is established.
Benefits as outcomes
What somebody ends up with, not what the feature is called.
Evidence for claims
Support the big claims visually or textually.
Proof at the doubt
Credibility placed where hesitation happens, not in a strip at the bottom.
Testimonials must be specific
Vague praise persuades nobody. Use only what was provided.
Answer the objection
Address the real reasons not to act before the final ask.
FAQs answer purchases
Use them for the questions that block a decision.
Repeat the action naturally
On a long page the CTA reappears where a decision becomes possible.
Same words every time
One phrase for the primary action throughout.
Vary the density
Alternate heavy and light sections to hold attention.
Every section justifies itself
If you cannot say why a section is there, remove it.
Never add a section by convention
A section included because landing pages usually have one is filler.
Understanding above the fold
The first screen belongs to comprehension and action, not decoration.
Remove steps
Every step between intent and action loses people.
Trust before commitment
Provide enough evidence before asking for something significant.
Price when it can be judged
Introduce pricing once there is enough context to read it as value.
The action stays reachable on a phone
Keep the primary action within reach on a small screen.
Forms as short as possible
Every field costs conversions. Ask only for what the business truly needs.
Say what happens next
After submission, say what was received and what follows.
Speed is conversion
Heavy effects that delay the page cost more than they add.
One thing to remember
Include a single distinctive element that stays in the memory.
Finish with the ask
End on a clear, confident next step.
Describe yours
Free to start, no card. Publish when it looks right.
Build a site