Five calls, about 56 minutes of dial time. Three meetings booked, one follow-up, one dead end. The dead end was the most avoidable, and it cost 13 minutes.
The prospect was the finance director at an automotive components maker. Within the first few minutes he said his team runs commissions on a custom-built internal application and has no interest in replacing it. He was generous enough to refer us to a former employer that tracks commissions in Excel and needs standardization, and suggested we contact their HR team. Useful referral, wrong buyer for us, and the answer was clear once he named the tool.
A two-minute check of how a company pays its reps would have flagged it. If the comp plan lives in a home-built system, the buyer has already solved the problem in-house. So before we dial now, we answer four questions from public sources.
Business model. Is the company in a stage where our service fits? A fund founder winding down a vehicle is a different buyer from one raising a new fund. Our call with a fund founder ended with him cutting from 50 entities to about 10 across several states. He was low priority, but he agreed to a demo to see the platform’s efficiency, and a meeting landed for Monday at 1:15 PM. Knowing the lifecycle first tells you how to open.
Volume and timing. Our tax practice owner is a CPA who runs his own business and is training his son to take over more responsibility. He turned down an immediate meeting and asked for a follow-up after tax season, in late April or early May. The signal was in the calendar and the ownership structure, not the pitch. Check how the business operates before you assume a decision-maker wants help now.
Comp structure. Commission-heavy teams with home-built tools are a different conversation from teams on spreadsheets. The first is a replacement project. The second is a standardization project. Both are real, but they need different proof and different buyers.
Product surface. Our CFO contact confirmed the company runs Salesforce, Monday.com, and Foundation ERP, and said he wanted those systems integrated. He was also evaluating BuildOps. Knowing the stack before the call lets you lead with integration instead of spending the first five minutes on discovery. That call ran about nine minutes and ended with a 15-minute meeting the following Wednesday at 12:00 PM ET.
The pattern across these calls is simple. The conversations that went well started with a fact we could have verified: the lifecycle, the timing, the stack. The one that failed was a fact we only learned by asking. A short pre-dial check costs a few minutes. A dead call costs 10 to 15, and it also costs the next dial you could have made in that slot.
Note for you (not part of the post): The four financial-services cases in your angle (a PE firm with no commission team, a cash-only company, an API-only fintech, and a firm already talking to institutional customers) are not in the call data you sent, so I did not write them up as real observations. The post uses the five calls you provided, anonymized. Only one of them was a dead dial, and three booked meetings, so I framed the post around a pre-dial check rather than four failed financial-services calls. If you send the notes on the four financial-services calls, I can rewrite the post around them.