← All projects
Constraint
No performance data verified, so no number appears
Client
Advisor Websites, a Vancouver SaaS platform for financial advisors
Scope
Homepage, webinar library, replay template, booking page, personalized pages
Stack
Web, template system

A webinar library and booking page rebuilt for a financial advisor SaaS platform

Webinar library and booking page redesign for a financial advisor SaaS platform. Client: Advisor Websites, A Vancouver SaaS platform serving financial advisors.

An advisor registers for a webinar at 11 in the morning and forgets it by 3 in the afternoon. The session runs without her. 2 days later she remembers, searches her inbox, finds the invitation, and clicks the link. It goes to a registration page for an event that has already happened. There is no recording, no summary, no next session, and no way to ask for one. She was the most interested person on that list. The company spent money to find her, she raised her hand, and then the only door left open was the one she had already walked through. Nothing failed. Nothing was built.

A webinar is not an event. It is a page that keeps answering after the room empties.

What was actually happening?

Recordings expired inside an inbox, so every session stopped earning the day after it aired. The booking page asked for a decision before it had given a reason. Partner traffic and general traffic landed on the same page and were asked the same question, which meant the page could only be right for one of them.

Every figure below is a real capture of the live page. Each frame caps its height and scrolls inside itself, so a full-page capture can be read end to end without leaving the figure. Both frames are reachable by keyboard. Nothing here is a mockup or a drawn schematic.

1. What does a SaaS homepage owe an advisor who arrived from a webinar?

Before: a homepage with several competing actions and no route back to the session the visitor came from.
Before: a homepage with several competing actions and no route back to the session the visitor came from.
After: a homepage with 1 primary action and a visible route into the replay library.
After: a homepage with 1 primary action and a visible route into the replay library.

2. How should a webinar replay library be structured?

Before: no library. Recordings live in email and expire with the invitation.
Before: no library. Recordings live in email and expire with the invitation.
After: a library page where each replay is a page of its own, browsable after the session has aired.
After: a library page where each replay is a page of its own, browsable after the session has aired.

3. What belongs on a single webinar replay page?

Before: a registration page for an event that has already happened.
Before: a registration page for an event that has already happened.
After: a replay page holding the recording, the summary and 1 next action, built as a template the marketing team can fill.
After: a replay page holding the recording, the summary and 1 next action, built as a template the marketing team can fill.

4. How much should a booking page ask for before it has given a reason?

Before: a booking form presented before any reason to book is stated.
Before: a booking form presented before any reason to book is stated.
After: a booking page that states the reason, then asks once, with 1 focal action.
After: a booking page that states the reason, then asks once, with 1 focal action.

5. Should partner traffic land on the same page as everyone else?

Before: 1 generic landing page serving partner traffic and general traffic identically.
Before: 1 generic landing page serving partner traffic and general traffic identically.
After: a personalized page naming the partner audience it was built for.
After: a personalized page naming the partner audience it was built for.

Before against after, with the measured column

WhatBeforeAfterMeasured
RecordingsExpired in emailA replay library with 1 page per sessionNot measured
Replay pageDid not existA template the marketing team fillsNot measured
Booking pageForm before reasonReason, then 1 askNot measured
Partner trafficGeneric landing pagePersonalized pages per segmentNot measured

What was built?

  • A webinar replay library where each recording is a page that can be found after the session has aired.
  • A replay template the marketing team can fill without a designer.
  • The booking page rebuilt to state the reason before it asks, with 1 focal action.
  • Personalized landing pages for partner segments, separate from general traffic.

What changed, and what is not claimed?

5 page types were rebuilt: homepage, webinar library, replay template, booking page and personalized pages. Each answers 1 question, and the replay library keeps every session in circulation instead of letting it expire in an inbox. No performance number is claimed for this engagement.

What this case cannot tell you

  • Whether replay page visits turned into demonstration requests.
  • Whether the rebuilt booking page raised completed bookings.
  • Whether personalized pages outperformed the generic page for partner traffic.
  • Whether the library changed the cost of acquiring an advisor.

The honest limitation

No performance data for this engagement has been verified, so no number appears on this page. The captures show the design states and the reasoning stands on architecture, not on outcomes.

This engagement runs as Website Design.

Get an Estimate
Thirty minutes

Pick a time. We set the baseline on the call.

Mobile conversion rate, AI-referred traffic and lead count, measured before any work starts. You leave with the window and the number, whether or not you hire me.

Thirty-minute call with Joshua Open in a new tab

If the calendar does not load here, the host is blocking the frame. Open it in a new tab with the link above.

×

Privacy Preference Center