Sample report: Shiftswap

An example report for Shiftswap, a made-up product, with made-up visitors: this is what you get on day 7.

The page we tested

Shiftswap's page as its 140 visitors saw it. Everything below is what they did on it.

Shiftswap
Shiftswap's landing page on a laptop
Shiftswap's landing page on a phone

Promising

6% of visitors left an email; 34% of button clicks were on paid plans.

Recommendation

Build

Build the smallest version: a swap request, manager approval and a record of who agreed. Start with the restaurants that left an email.

visitors in 7 days
140
left an email, 6% of visitorslikely 3–11%
8
of button clicks were on a paid planlikely 22–48%
34%
read to the endlikely 18–32%
24%

The thresholds behind this verdict are starting guesses.

What happened

140 people found the page over 7 days and 8 of them left an email: 6% of visitors (likely range 3–11%). 34% of button clicks went to a paid plan, all of them to Team at $29 a month. People reached for the paid tier before trying anything, which is the signal this test exists to find.

Working

  • Reddit DMs brought the most visitors and the most emails of any channel.
  • Pricing pulled clicks to Team (16 clicks), not to the free Starter plan.
  • The answers keep returning to the same moments: weekend gaps, sick calls and who agreed to what.

Not working

  • 34% of visitors stopped between Problem and How it works: the problem section loses them before they see the product.
  • Only 24% of visitors reached the end of the page.

The riskiest assumption

Held

The riskiest assumption was that managers would pay for swaps instead of using a free group chat. 34% of clicks on a paid plan, and answers about the chaos of covering shifts by text, say it held for this sample.

How we reached them

High-intent leads on Reddit, already asking about the problem, found and contacted for you.

High-intent leads found
742
Contacted
689
Comment replies
311
DMs
378

  • How do you handle last-minute shift swaps?

    r/restaurateur, comment reply, Oct 8

  • Our group chat for shift covers is a nightmare

    r/KitchenConfidential, DM, Oct 9

  • Any app that tracks who agreed to cover?

    r/restaurantowners, comment reply, Oct 11

  • Managers: how do you approve swaps without losing track?

    r/serverlife, DM, Oct 13

What visitors told us

  • Weekend cover

    Last-minute weekend gaps are the moment the group chat breaks down.

  • Proof of who agreed

    Managers want a record of who said yes to a swap.

  • Overtime

    A swap can push someone into overtime, and the manager only finds out on payroll day.

In their words

  • I need a record of who said yes, for when there's an argument.
  • Covering last-minute sick calls takes me an hour of texting.
  • Someone always ends up in overtime and I find out on payroll day.
  • Two of my servers swapped and both thought the other one was covering. Nobody came.
  • I approve swaps by text and then forget who agreed to what.
  • Weekend shifts are the worst, the group chat explodes every Friday night.

Your leads

8 people left their email. They're yours to contact.

EmailPlanWhat they wroteJoined
maria.lopez@example.comTeamWeekend shifts are the worst, the group chat explodes every Friday night.Oct 8
dev.patel@example.comTeamI approve swaps by text and then forget who agreed to what.Oct 8
nina.cho@example.com——Oct 9
sam.okafor@example.comTeamTwo of my servers swapped and both thought the other one was covering. Nobody came.Oct 9
jules.martin@example.comTeamSomeone always ends up in overtime and I find out on payroll day.Oct 10
li.wei@example.com——Oct 10
ana.ruiz@example.comTeamCovering last-minute sick calls takes me an hour of texting.Oct 11
tom.becker@example.comTeamI need a record of who said yes, for when there's an argument.Oct 12

For the next run

  • Move the approval step into the hero: it's the reason people clicked.
  • Shorten the problem section and show how it works sooner: that's where most readers leave.

The numbers behind it

The pale band on a bar shows where the true rate likely sits, given how many people we saw.

Funnel

  1. Messages sent

    689

  2. Visited

    14020 visits per 100 messages

  3. Engaged

    13999% of the step before, likely 96–100%

  4. Clicked a button

    4734% of the step before, likely 26–42%

  5. Opened the waitlist

    2451% of the step before, likely 37–65%

  6. Left an email

    833% of the step before, likely 18–53%

  7. Answered follow-up

    675% of the step before, likely 41–93%

How far they read

  • Hero
    100%likely 97–100%
  • Problem
    91%likely 86–95%
  • How it works
    57%likely 49–65%34% stopped before this
  • Features
    51%likely 43–60%
  • Audience
    46%likely 38–54%
  • Comparison
    41%likely 34–50%
  • Founder note
    37%likely 30–45%
  • Pricing
    34%likely 27–42%
  • FAQ
    29%likely 22–37%
  • Final CTA
    26%likely 19–34%
  • Footer
    24%likely 18–32%

Plans they reached for

  • Starter Free 0 clicks, 0 emails

  • Team $29 / month16 clicks, 6 emails

  • Group $79 / month0 clicks, 0 emails

Day by day

  • Oct 8: 22 visits, 2 emails
  • Oct 9: 22 visits, 2 emails
  • Oct 10: 21 visits, 2 emails
  • Oct 11: 22 visits, 1 email
  • Oct 12: 21 visits, 1 email
  • Oct 13: 22 visits, 0 emails
  • Oct 14: 10 visits, 0 emails

Where they came from

ChannelVisitorsEngagedClickedEmails
Reddit DM5655193 5%
Reddit comment282891 4%
Reddit post2828102 7%
Reddit282892 7%

Who they were

  • mobile 66%
  • desktop 34%
  • GB 47
  • US 47
  • CA 46

Questions they opened

  1. Do my staff need to download an app?9 opens

Don't build it yet. Ghostlaunch it.

Validate my idea