I've watched it happen dozens of times and it still catches people off guard. The first meeting is electric. Everyone can see the solution, the energy is high, people leave buzzing. The second meeting goes deep: requirements, constraints, timelines, budgets. Hard conversations, but productive ones. Then silence. Meeting three gets rescheduled. Then rescheduled again. Then it quietly dies in someone's inbox. And a project that could've changed the business never gets off the ground.
The pattern is so consistent I've given it a name. The three meeting trap. And it kills more enterprise projects than technical failure ever will.
Why It Happens
Meeting one is about possibility. The problem is real, the solution is tangible, and everyone in the room can see it. There's no friction because nobody's committing to anything yet.
Meeting two is about reality. Budgets are discussed. Timelines are estimated. Scope is debated. This is where the work of enterprise procurement actually starts. It's harder, but it's necessary.
Meeting three is where commitment happens. And commitment is where enterprise organisations slow down. Not because they don't want to proceed. Because proceeding requires someone to own the decision.
The sponsor who was enthusiastic in meeting one now needs to get budget approval. The CTO who was excited about the technical approach now needs to check with the security team. The project manager who was ready to start now needs to navigate the procurement process.
Nobody says no. They just stop saying yes.
Enterprise deals don't die in meeting one. They die in the gap between two and three, where internal politics, procurement, and competing priorities quietly suffocate momentum. Confidence is contagious, but so is inertia.
Tim Hatherley-Greene
Chief Operating Officer
How to Keep It Moving
Leave every meeting with homework. Not for you. For the client. A specific action, owned by a specific person, with a specific deadline. "Could you confirm the budget allocation by Friday?" is better than "let us know when you're ready to proceed." The first gives them a task. The second gives them permission to wait.
Send the proposal before meeting three. Don't wait for the third meeting to present options. Send a clear, concise proposal after meeting two, while the detail is fresh. Give them something to react to. A document sitting in an inbox is more likely to generate a response than a meeting sitting in a calendar.
Identify the decision maker early. If the person in meeting one doesn't have budget authority, find out who does. Enterprise buying decisions are made by committees. If you don't know who's on the committee, you can't help your sponsor navigate it.
Shrink the first commitment. A $500,000 platform build is a big commitment. A $30,000 discovery phase is not. Start small. Deliver value quickly. Let the momentum of a successful first phase carry the larger engagement forward. We've found that 80% of our discovery engagements lead to full builds. The discovery phase isn't just valuable in itself. It's the bridge across the commitment gap.
Be honest about the stall. If meeting three has been rescheduled twice, name it. "It seems like there might be some internal alignment needed before we can move forward. Is there anything we can do to help with that?" Sometimes the sponsor is stuck and doesn't know how to ask for help.
The Deeper Problem
The three meeting trap isn't really about meetings. It's about the gap between individual enthusiasm and organisational commitment. In enterprise, those two things are connected by a long chain of approvals, risk assessments, and budget negotiations that most vendors never see.
Understanding that chain, and helping your sponsor navigate it, is the difference between a deal that closes and one that dies quietly. The best technology in the world doesn't matter if you can't get past meeting three. Stop planning and start building, but first, help your sponsor clear the path to get there.