Usually, right when it becomes clear that your current contact can’t decide the purchase on their own—or can’t drive it internally without additional support.
With the objection “I need to align this internally first,” multithreading is often not a nice-to-have—it’s necessary. As soon as more roles, like the business unit, IT, procurement, data protection, management, or day-to-day users, come into play, a good relationship with a single person is no longer enough. Then you need multiple conversation threads in the account to spot risks earlier and avoid being dependent on one single perspective internally.
What matters here is how you bring it up. Multithreading shouldn’t sound like you’re bypassing your contact—it should come across as support for a complex buying process. That’s why strong questions are process-oriented: Who, in your view, should be involved early? Where do follow-up questions typically arise? Who evaluates value, risk, and implementation?
If you lead clearly at this point, you can often turn an objection into real progress in the deal.