Home · Built for · Product & software
A product site that explains itself.
Most software marketing sites describe features. The ones that work explain a problem so precisely that the reader recognises their own week in it.
Product companies have the opposite problem to local businesses: distribution is not the constraint, comprehension is. Someone lands on the page, has thirty seconds to work out whether this is for them, and leaves if the answer requires effort.
Pricing is where most of these sites fall apart. A contrarian or unusual pricing model needs a page that argues for it, not a table that leaves the visitor to reverse-engineer the reasoning and quietly conclude it is expensive.
Then it is the funnel: which step loses people, and why. That is an analytics question before it is a design one.
How it is done
04Narrative before features
The first screen names the problem in the reader’s own words. Features come after the recognition, because a feature list means nothing to someone who has not yet decided the problem is theirs.
Pricing that argues its case
If the model is unusual, the page has to make the argument. A pricing page is often the second most visited page on a product site and it is almost always the least written.
Trial and demo paths
The route from interested to trying, with the friction removed from the parts that do not qualify anyone and kept in the parts that do.
See where they drop
Funnel analytics from first visit to activation, so a redesign is a response to evidence rather than a matter of taste.
What a product company gets
7 items- Product narrative and positioning, written not templated
- A pricing page that makes the argument
- Trial, demo and onboarding paths
- Documentation and changelog structure
- Funnel analytics from visit to activation
- Search built around the problem, not just the category
- A login to publish, and the repository in your name
Live work
Open any of themEvery site below is live and reads under the same site check as yours. Nothing here is a mockup.
Questions
We already have a designer. Can you just build?+
Yes. A fixed-scope build handed over on acceptance is one of the shapes we work in, and it ends with the repository in your account and a written note that we are done.
Can you write for a technical audience?+
Yes, and the constraint is accuracy rather than tone. We write from your material, you check it, and nothing ships that your engineers would wince at.
Do you do ads for SaaS?+
Where the maths works. Some products have a customer value that supports paid acquisition and some do not, and it is worth being honest about which one you are before spending.
Next
Tell us about the business.
We come back with a first look at what your site could be and a fixed quote. No deck, no discovery fee.