A SaaS sales engine reads trial behavior, champion job changes, competitor price moves, and stack signals, profiles which account is in a buying window, and answers demo requests while they are still warm. Demo requests cool in hours: at $36,000 average ACV, four lost deals a quarter is $576,000 a year.
Request a briefingEvery point is $8,000 of annual leak, orbiting at the speed this industry's inquiries cool (window: 6 hours). The flash is a buying signal firing, caught or missed. Full table: the Bottleneck Index · Feel it: the window game
| Metric · SaaS | Representative value |
|---|---|
| Average deal value | $36,000 |
| Typical sales cycle | 30 to 60 days |
| Window before an inquiry cools | 6 hours |
| Winnable deals lost per quarter (typical) | 4 |
| Annual cost of the bottleneck | $576,000 |
JSU Bottleneck Index · representative values from deal-pattern work since 2009 · your briefing runs your real numbers
The engine opens conversations before the RFP exists. In saas, the four signals that matter most:
Signal finds the buyer in motion. Profile reads what they need to believe, using AI.DA models in production since 2012, three years before OpenAI existed. Message aims every word and follows up around the clock. Revenue is the only scoreboard: pipeline created, deals closed, ROI you can audit.
Demo requests cool in roughly 6 hours. Four lost deals per quarter at $36,000 ACV is $576,000 a year, mostly lost to whoever responded the same morning.
Volume without aim. The engine profiles which segment the visitor belongs to (evaluator, champion, economic buyer) and aims the message accordingly, instead of sequencing everyone identically.
Champion job changes, competitor pricing moves, revealing job posts, and product-qualified behavior. The engine reads all four daily.
No. It feeds them accounts already in motion and the opening line that matches the buyer, which is why the same team books more with fewer touches.