Early access for B2B SaaS and service websites

Every cue, recognized. Every visit, understood.

A pause on a price. A scroll past your case studies. A quick trip back to Pricing. On their own, small cues say little. Cuebased adds them up with what was on the page and tells you what each visit was about, and what keeps happening across all of them.

We keep your address only to invite you, and delete it on request. to help us prioritize. Details

  • No session recordings
  • Nothing runs before consent
  • For B2B SaaS and service sites

Visit Qm81xT…r4sD · desktop · 1:24

Synthetic example

sample-saas.example/pricing

Pricing

Pricing plans
Choose Growth
Request a demo
Pricing FAQ
+
+
+

The story, as it’s written

Ready

One visit, as Cuebased reads it: the cues on the left, the story being written on the right.

How it works

A pause means nothing. A pause on your pricing means something.

Cues only make sense next to what was on the page. Cuebased ties every cue to the section it happened in, then reads them in order, like sentences.

Every cue, in detail
  1. Pricing

    Pricing plans
    Pricing FAQ
    Hosting and data residency

    Your content

    What was on the page

    The pages, sections, buttons and forms you name, so every cue lands on something that means something. The script never reads page text or what visitors type.

    • Lingering
    • Pausing
    • Scrolling past
    • Going back
    • Opening
    • Leaving a form
    • Dead ends
    • Stepping away
    • Waiting
    • Asking

    Their cues

    What people did there

    Ten kinds of small signals, each tied to the section it happened in: a pause, a scroll past, a quick trip back, a form left halfway.

  2. Story · one visit

    Pricing-to-Security exploration before a confirmed demo request

    Returned to Pricing after visiting Security.

    The sequence is consistent with checking implementation or security requirements while evaluating the offer.

    One story per visit

    What it adds up to

    What the visit looked like, in a few plain sentences with evidence behind every line. Guesses are marked as guesses, never about feelings.

Across every visit

Same visits. Different answers.

One story explains one visit. Put them together and patterns appear: what keeps happening, how often, and what to change about your product, your pages or your follow-up.

Your analytics

Last 6 weeks
809
Visits
56 s
Median visit
1.8
Pages per visit
20%
Asked for a demo
Goal: demo request164 of 809

All true. None of it tells you what happened.

Cuebased · the same 809 visits

Synthetic example
  • 36 of 36 visits clicked “Compare all features” and nothing happened.

    ProductFix the button, or say what it does.

  • 96 of 287 visits had the plans on screen for a long time, then clicked nothing.

    PageMake the next step from the plans obvious.

  • 45 of 193 visits started the demo form and left it.

    FormTest a shorter form.

  • 30 of 30 visits scrolled to the end of Security; 25 then asked for a demo.

    Follow-upOpen those replies with security and hosting.

Your questions

Ask what you’ve always wanted to know.

“Did they see our security page before booking a demo?” Build the question from your own pages and sections, add what your team should do about it, and every visit answers: yes, no, or not enough evidence.

Answers are counted across all visits, and each yes opens the visits behind it.

YoursSaw the security details before asking for a demo?

Synthetic example
  1. WhenHosting and data residency on screen for 10 s or more
  2. thenYour server confirmed the demo request

Yes in 44 of 809 visits

5%

Team note on every yesShow a hosting summary on Pricing, so the detour to Security is shorter.

YoursLooked at the plans but never clicked “Request a demo”?

Synthetic example
  1. WhenPricing plans on screen for 15 s or more
  2. notClicked “Request a demo”

Yes in 150 of 809 visits

19%

Team note on every yesMake the next step from the plans easier to see.

Private by design

Understanding, without watching anyone.

What the SDK collects
  • Nothing before consent

    No listeners, IDs or storage until a visitor allows analytics. Revoking clears everything.

  • No recordings, no page text

    Only what an element is and what happened to it. Never what people read or type.

  • Facts apart from guesses

    Every sentence points to its evidence. Explanations are hedged, never about feelings.

  • Works with your consent tool

    One callback from the consent manager you already use.

Questions

The short answers.

Is this another session recording tool?

No. Nothing is recorded and there is nothing to watch. Cuebased keeps a short list of what happened on each page, such as a section in view or a button clicked, and writes the story from that.

How is this different from Google Analytics?

Analytics counts: visits, pages, conversion rates. Cuebased reads each visit in order and tells you what it looked like and what keeps happening across visits, in sentences, with the visits behind every claim. Keep your analytics; this answers the questions it cannot.

Does it guess what people feel or who they are?

Never. Visits stay anonymous, and Cuebased does not score emotions, personality or likelihood to buy. When the evidence is thin, it says “not enough evidence” instead of guessing.

When can I try it?

We are inviting B2B SaaS and service websites in small groups. Join the waitlist and we will email you when there is a spot for your site.

Every visit has a point.

We’re opening Cuebased to a small group of B2B SaaS and service sites first. Leave your email and we’ll invite you when there’s a spot.

We keep your address only to invite you, and delete it on request. to help us prioritize. Details