We logged five calls in this batch. Three ended with a follow-up request, one was a dead number, and one booked a meeting. The three follow-ups tell the same story, and it changes how we should work these accounts.

The first was a VP of Finance at a construction company. His team runs Procore alongside Jonas, and he said he wants a unified system eventually. He does not want to replace anything yet. He would rather wait for the AI market to settle and for “proven winners” to emerge before touching a stack that works. He asked us to come back in 8 to 12 months. The call ran 849 seconds, and he was clearly a decision maker. It was not a no.

The second was a CFO at a company with three AI users and about $1,500 a year in AI spend. Most of their 45 developers are outsourced to a single partner. He liked the product, but the current footprint does not justify a meeting. He asked for an email and a follow-up in six months, to see whether usage grows. The call ran 532 seconds.

The third was a CISO at a contractor that uses Procore. He was interested, but federal contract work means the platform must be FedRAMP authorized before he will sit down with us. He would not book a meeting until we confirmed compliance status. We treated that as a question for the founder, not a rejection. The call ran 514 seconds.

What these have in common is that each buyer agreed the problem was real and that consolidation made sense. None of them agreed to evaluate anything this year. Their current stack works, the cost of change is visible, and the cost of waiting feels like nothing. Pushing for an immediate intro in that situation gets a polite no.

What works better is to treat consolidation as a planned project with a date attached. Here is what we would do next time:

Name the date early. “Would it make sense to revisit this in the second half of next year, once your current contract renews?” lands better than “Can we get 20 minutes this week?”

Book the follow-up before the call ends. A calendar invite for a specific date turns “in eight months” into an event. A note in the CRM does not do that.

Ask what has to be true. For the CISO it was FedRAMP. For the CFO it was usage growth. For the VP it was proof from peers running the same stack. Write those conditions down and read them back to the prospect.

Send a short recap the same day with the date, the trigger, and the one thing you will bring to that conversation.

A 12-month follow-up is a long way off, and we are not counting these as wins. But a dated, qualified opportunity with stated conditions is more useful than a meeting nobody asked for.