← Back to blogProduct

What 50,000 sandbox sessions taught us about buyer intent

•3 min read

We analyzed 50,000 anonymized sandbox sessions across our customer base to understand what separates a buyer who converts from one who quietly disappears. A few patterns held up consistently.

A quick note on methodology, because it shapes how much weight to put on what follows: we're looking at behavior inside a sandbox, not survey responses about behavior, and behavior data has a specific bias — it only captures people who got far enough to start a session in the first place. These findings describe what separates a converting explorer from a non-converting one, not what gets someone to click "start" in the first place. That's a different, earlier-funnel question we're still working on.

First, time-to-first-interaction matters more than total session length. Buyers who click something meaningful within the first 30 seconds are dramatically more likely to book a follow-up call than buyers who passively scroll for minutes before engaging.

Second, the specific feature a buyer tests first is a strong signal of what they'll ask about in the sales call. Security and SSO configuration testers ask compliance questions; automation testers ask about API limits and integration depth.

Third — and this one surprised us — buyers who trigger an error state or an edge case convert at a higher rate than buyers who never leave the happy path. Curiosity about how the product fails is, apparently, a sign of serious evaluation.

Fourth, the pattern shifts by company size in a way our sales team had suspected but couldn't prove until we had the data. Buyers from smaller companies gravitated toward the automation and integration features first; buyers from larger organizations went straight for the security and audit-log sections, often before looking at any core product functionality at all. Neither group is wrong — they're just answering different first questions — but it means a single "recommended path" through the sandbox was actively working against about half of our visitors.

We used this to make two concrete changes. The sandbox now infers a likely persona from the referral source and the first click, and reorders which capabilities are surfaced first — without hiding anything, since the earlier finding about letting people wander held true here too. And we rewrote the AI copilot's opening prompts so a security-first explorer isn't greeted with an automation pitch. Early results suggest the reordering alone accounts for a meaningful chunk of the completion-rate improvement we've seen this quarter, though we want another full quarter of data before we're confident calling out a specific number.

None of this is a finished model — 50,000 sessions is enough to find patterns, not enough to fully explain every one of them, and we're still cautious about reading too much into the smaller segments. But treating the sandbox as an instrumented product surface, rather than a one-off sales tool, is what makes this kind of analysis possible at all.