Registration pages designed for a 75-year-old deciding whether to protect their savings

The default event template is built for a B2B conference: three-column benefit grids, small grey type on white, a countdown timer, social proof logos, and a form asking for company and job title. Put that in front of a retired couple deciding whether to attend a free session about protecting their savings from care costs and every element is doing damage. The type is unreadable, the countdown reads as pressure, and the company field tells them the page was not written for them.

The default event template asked a retired couple for their company name and job title before it would let them attend a free talk about their own savings.

1. 01

   Field count is the whole story on a free consumer event

   There is no qualifying value in a longer form when the event is free, and every additional field costs registrations from an audience less comfortable with web forms. Each field has to justify itself against a specific follow-up it enables, and most cannot.

2. 02

   A phone route is a primary path for this audience, not an accessibility fallback

   A meaningful share of this audience would rather call someone and be registered by a person. That is not a failure of the form, it is a preference, and it belongs above the form rather than in the footer.

3. 03

   Pressure devices read as a scam when the subject is a spouse's care

   Countdowns, seat counters and 'only 3 spots left' language are read by this audience against a background of constant financial-scam warnings aimed at them. The page's credibility is worth more than the urgency, so none of them are used.

4. 04

   Saying what the session is not is as valuable as saying what it is

   A short, plain statement that nothing will be sold and no personal financial information is collected removes the objection the audience arrives with. Leaving it unsaid does not make the objection go away, it just leaves it unanswered.

Senior housing occupancy is at **89.9%**, with **15 of 31 markets ≥90%** and supply growth under **1.0%** (NIC MAP Vision, Q2 2026). At that occupancy the job is fit, timing and education, not raw lead volume — so the landing page's job is trust and clarity, not conversion tricks.

Single column, generous line height, body type no smaller than eighteen pixels, and high contrast throughout. Two fields: name and email. A phone number sits above the form with an explicit invitation to register by calling. The page states in plain language what the session covers, who it is for, and what it is not — nothing sold, no personal financial details collected. No countdown, no seat counter, no scarcity language anywhere. Confirmation goes out with a calendar file and a plain-text alternative, followed by three reminders, and a replay link reaches everyone who registered whether or not they attended.

1. 1

   Week 1

   Template audit

   Every element of the standard event page tested against the actual reader

   Owner: OmniFlow

2. 2

   Weeks 1–2

   Page build

   Single column, two fields, phone route, plain-language promise and exclusions

   Owner: OmniFlow

3. 3

   Week 2

   Confirmation and reminder sequence

   Calendar file, plain-text alternative, three reminders, replay to all registrants

   Owner: OmniFlow

4. 4

   Ongoing

   Per-session reuse

   One page per session from the same pattern, never a shared template with a swapped title

   Owner: OmniFlow

This entry makes no performance claim. It documents a page pattern and the reasoning behind each decision, most of which are removals rather than additions. The pattern is written down as a pattern rather than saved as a template, because a template gets duplicated and the title swapped while the body copy slowly stops matching the session it is advertising. Each session gets its own page built from the same rules, which costs an hour and keeps the promise on the page accurate to the talk being given.

These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

The first build treated the phone route as an accessibility fallback and put it in the footer under a small heading. For this audience it is a primary registration path and it belongs above the form. We found that out from the people who called the main office to register rather than from the page analytics, which is the wrong way round.

Real client work that shipped. No performance figures are published, because none have been verified and approved for release. See all our work