Tech for older adults that isn’t a pill box
How to design apps for older adults that are accessible and dignified, not patronising. Principles, a swap table and lessons from the Elli Cares app.
28 May 2026
Your pricing page is your second homepage
More SaaS deals are decided on /pricing than on /. Why most pricing pages underperform, and the six-question audit that fixes them.
TL;DR
The pricing page does a different job than the homepage. The homepage convinces a stranger you might be relevant. The pricing page convinces a warm visitor you are the right choice over the three competitor tabs they have open. Designed as a spreadsheet, it underperforms. Designed as a closing surface, it earns its keep.
Founders pour effort into the homepage.
They wireframe it, A/B test it, hire copywriters for it, argue about the hero for a week.
Then they design the pricing page like a spreadsheet.
The pricing page is where more deals are decided than anywhere else on your site. It is the second homepage. Most teams treat it like an internal admin screen.
The pricing page does a different job
The homepage convinces a stranger that you might be relevant. The pricing page convinces a warm visitor that you are the right choice over the three competitor tabs they have open.
Different job, different energy. The mistake is treating the pricing page as a continuation of the homepage instead of a stand-alone closing surface.
What buyers actually do on a pricing page
They scan plan names. They compare the middle column to the right column. They look for the catch. They look for who else uses it. They look for "no credit card." They scroll to the FAQ. They open three competitor tabs.
The whole sequence happens in under two minutes. If your page doesn't answer the obvious questions in that window, the buyer goes to whoever does.
4 mistakes the spreadsheet view makes
1. No headline.
The page opens with three plan cards and no claim about what you do for the buyer. The hero is a price grid.
2. Feature parity theatre.
Every plan lists every feature with a green checkmark, defeating the entire point of having tiers in the first place.
3. No anchor.
The page doesn't tell the buyer which plan to pick. Three equally weighted options is a decision the buyer wasn't asking to make.
4. FAQ as graveyard.
The hard objections sit at the bottom in tiny accordions, treated like footnotes instead of the most important section on the page.
What the good ones have in common
A one-sentence claim at the top, in the same voice as the homepage. A clear recommendation (most teams pick X). A side-by-side, not three columns of identical checkmarks. A row that compares you to the one competitor people are switching from. A FAQ that answers the four objections sales reps hear every week.
Linear, Stripe, and Vercel have done variations of this for years. The pattern is older than your pricing meeting.
The audit, in 6 questions
1. Does the page open with a headline that promises a buyer outcome, not a list of features?
2. Is there a default plan an unsure buyer can pick in four seconds?
3. Are the top three objections from sales answered above the fold?
4. Does the FAQ answer the questions a buyer is too embarrassed to email?
5. Is there a "no credit card" path for self-serve, or a "talk to us" path for assisted?
6. Could a stranger pick a plan without scrolling twice?
If two or more answers are no, your pricing page is a spreadsheet.
Related reading: our take on why most SaaS websites feel harder to use after every update covers the same subtraction discipline applied to the rest of the site.
If your pricing page is a calculator
It's converting in spite of itself.
We help SaaS teams turn pricing pages into the closing surface they should be.
→ Book a free pricing-page audit at dtailstudio.com
Climate tech pitch decks investors trust
Energy investors read a climate deck differently. What they look at first: technology readiness, unit economics, real installs and impact with a method.
One app for patients and the people who care
Patients want independence, carers want reassurance. How to design one health app that serves both without turning care into surveillance.
