A payments sales engine reads new locations, platform migrations, chargeback pain, and processor outages, profiles which merchant is ready to switch, and opens with their statement math before the current processor's retention desk calls. At $30,000 average annual value per account, four lost merchants a quarter is $480,000 a year.
Request a briefingEvery point is $8,000 of annual leak, orbiting at the speed this industry's inquiries cool (window: 8 hours). The flash is a buying signal firing, caught or missed. Full table: the Bottleneck Index · Feel it: the window game
| Metric · Payments | Representative value |
|---|---|
| Average deal value | $30,000 |
| Typical sales cycle | 14 to 45 days |
| Window before an inquiry cools | 8 hours |
| Winnable deals lost per quarter (typical) | 4 |
| Annual cost of the bottleneck | $480,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 payments, 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.
Merchant inquiries cool in about 8 hours. Four lost accounts per quarter at $30,000 annual value is $480,000 a year, plus the compounding residual walk-away.
Because everyone leads with rates. The engine leads with the merchant's trigger (the outage, the hold, the new location) and the statement math, which reads as help, not pitch.
New locations, POS migrations, outages and funding holds, and chargeback spikes. All visible before the merchant starts shopping.
Yes. ISOs hunt merchants; ISVs hunt platforms. Different prey, same engine: timing and aim at first contact.