In the last two weeks, three deals started with a 30-day pilot request and a security review before we even scheduled the full demo, which tells me buyers want risk off the table first and clear ROI. I’m leaning into that by opening with an implementation checklist and a 6-month ROI calc — are you seeing the same shift, and what’s working to meet those needs without stalling momentum?
Seeing the same — my last two started with a ‘30-day pilot’ and security review, . What’s worked: a mutual action plan with day-1 success criteria, a day-21 checkpoint, and a day-30 exec hold for go/no-go, plus we pre-share a completed CAIQ and DPA so security runs in parallel (CAIQ: https://cloudsecurityalliance.org/artifacts/caiq-v4-0/). Your 6‑month ROI calc lands, but I keep it to one CFO metric to prevent scope creep.
On my last 30-day pilot, we sent a pre-filled SIG Lite + SOC 2 pack and booked the security call for week 1 with a day-28 exec decision hold, framing it as “risk off the table first” — it cut two weeks of back-and-forth. If they won’t commit to that, I shrink the pilot to one workflow tied to your 6‑month ROI calc so it still moves.
I’ve been gating evals on a named internal owner and Slack Connect; once that’s set, we scope to one high‑velocity workflow and track impact in their BI, which cut cycle time by about 7 days — @amoore only caveat: loop RevOps in early. How are you handling BI access?
I’m seeing the “risk off the table” push too, and what’s sped things up is a one‑pager we call the data boundary + revert plan that spells out scopes (read‑only, two tables, no PII), rollback steps, and a single metric owned by finance, stapled to the security review. Getting that acknowledged before kickoff plus a penciled decision slot on the exec’s calendar keeps the eval tight and the ROI convo credible; the watchout is you have to keep scope ruthless or it drifts.