Case study · Hostfully · 2024 → 2026

Lead preservation

Visitors who started a demo request and left used to vanish. Now they stay in the pipeline.

sales-qualified leads we used to lose
1,010sales-qualified leads we used to lose
leads kept since 2024
3,802leads kept since 2024
of website SQLs in 2026
31%of website SQLs in 2026
of preserved leads become SQLs
27%of preserved leads become SQLs
Role
My idea. Designed it and led it with RevOps
Team
The second engineer on my team, RevOps and Sales
Timeline
2024 → today
Stack
In-house WordPress plugin, Account Engagement (Pardot), Salesforce, Turnstile

01·The problem

Before 2024.

Only a couple of pages had a form, and a visitor who started a demo request but didn't finish simply disappeared.

1

Half-finished requests vanished

Someone could fill in their details, get distracted before picking a time and leave. Nothing was kept, so Sales never knew they existed.

2

No attribution

Paid ads had no conversion tracking, so nobody could say which channel actually brought a demo.

3

No protection

No CAPTCHA, no structure, almost nothing inside the forms except a chat modal.

“Just forms from Pardot with really nothing inside except a Qualified modal.”
Me, describing the old demo flow

02·The idea

A visitor who starts a request is already a lead. Keep them.

Before

  1. Visitor starts a demo request
  2. Leaves before booking
  3. Lost

Now

  1. Visitor starts a demo request
  2. Leaves before booking
  3. Kept as a lead
  4. Salesforce, with source and UTMs
  5. Sales follows up
  1. 1

    One widget, everywhere

    The in-house Book a Demo engine sits on every page: booking, dynamic time zones and CAPTCHA.

  2. 2

    Details first

    Contact details are saved when the form is sent, before the calendar step.

  3. 3

    No time picked? Still a lead

    If the visitor leaves, the lead still reaches Salesforce, tagged so Sales knows the demo wasn't booked.

  4. 4

    Routed with context

    Source and UTMs travel with it, so Sales knows where the visitor came from.

03·Results

1,010 sales-qualified leads that used to vanish.

Measured in Salesforce, by the lead source that marks a demo that was started but not booked.

31%

of the website's SQLs came from lead preservation in 2026.

5%
2024
24%
2025
31%
2026

Share of website sales-qualified leads that came through lead preservation. 2026 to mid-October.

32%

of preserved leads became SQLs in 2026, up from 15%.

15%
2024
26%
2025
32%
2026

Preserved leads that became sales-qualified, by year. The share that turned into SQLs doubled as the engine matured.

04·How it evolved

From a couple of forms to a conversion engine.

  1. 2022
    Request-a-demo forms on a couple of pages.
  2. 2023
    A chat-style booking modal, with A/B tests.
  3. 2024
    Forms move to Account Engagement, and lead preservation starts: 5% of website SQLs that year.
  4. Jan 2025
    Our own form handler replaces third-party form logic.
  5. Jun 2025
    The in-house Book a Demo engine: booking, time zones, attribution and Salesforce hand-off.
  6. Oct 2025
    Widget v1.2 rolls out across the site.
  7. Nov 2025
    Cloudflare Turnstile CAPTCHA on every form.
  8. Jun 2026
    Booking analytics, a listings-size question, a sticky Book a Demo bar and a review badge.

05·Attribution

Then the next question: which channel really brought them?

With RevOps, I analyzed the journeys behind our demo leads and proposed recording first and last touch in Salesforce.

2,624

demo leads analyzed over 180 days

12.5%

convert on a different channel than the one they arrived from

22 days

average journey before converting

06·What it unlocked

The point was never just the feature.

01

Paid ads became measurable

Ad landing pages, Google and Meta conversion events and ad leads routed into Salesforce. With paid landing on the site, the website's share of new pipeline reached 76% in 2026.

02

A first- and last-touch model

The attribution analysis led to a proposal for first- and last-touch fields in Salesforce, plus AI assistants as their own channel.

03

Reused on a second site

The same routing and conversion tracking now run on a second company website.

More case studies

Every figure on this page traces back to a system of record: Salesforce, Chrome UX Report, PageSpeed captures, WordPress databases, Jira and git. Business figures are shown as percentages or indexes.

Let's build what's next.

Looking for a marketing technology leader who can also ship? Let's talk.

Based in Europe · Open to relocating to the US or Europe

What I'm looking for

Roles

  • Head, Director or Manager of Marketing Technology
  • Revenue and GTM Systems
  • Head of Web or Digital, Website Manager

Setup

  • Full-time
  • Remote for US or global companies
  • On-site or hybrid in the US or Europe, any time zone

Especially

  • Music and audio technology
  • AI companies
  • Open to relocating to the US or Europe
© 2026 Pablo PereyraDesigned and built with Next.js, Framer Motion and AI.Privacy