A fractional strategy consultant had a past client, a founder of a logistics tech company. They had worked together on organisation design eighteen months earlier. The founder posted about a major hiring drive. They were bringing on three senior operations leaders as the company prepared to scale. The consultant noticed the post because hiring signals were part of their operating rhythm. They remembered the specific conversation about how the founder had become a bottleneck in decision-making and how that was blocking the team. The hiring was directly relevant to the work they had discussed. They sent a short, specific email: they remembered the conversation about the founder as a bottleneck. They congratulated the company on the hiring. They offered one thought: if the founder wanted to think through how to position these new leaders so they could take weight off the founder, they had a perspective and had done it before. They did not ask for a meeting. They did not offer a proposal. They simply put the thing back in the room at the moment it had become urgent. The founder replied the same day. Two days later, they had a conversation. Two weeks later, there was an engagement. The timing was small but real. The founder had not forgotten the consultant. They had simply been in motion and had lost the thread. The signal made it easy to reconnect because the consultant was watching. This is what timing looks like.

A fractional operations leader worked with financial services companies on policy automation and workflow redesign. They had built a relationship with a Chief Risk Officer at a major bank over several years, mostly dormant. They knew the Chief Risk Officer well. They had done good work together. But the opportunity had stalled and they had both moved on to other priorities. The bank announced a regulatory change that would force them to re-evaluate their entire policy framework. The operations leader saw the announcement and immediately thought of the Chief Risk Officer, not because they had not thought of them before, but because the news made the relationship relevant in a new way. They sent a message: they saw the announcement. They remembered the past conversation about how the bank's policies were a workflow disaster that was consuming resources. They suspected the regulatory change had become the forcing function that would restart a project that had been blocked before. They asked if that was true. If it was, they had already done similar work elsewhere and had ideas about the approach. They did not try to close. They asked a question. The Chief Risk Officer replied within hours. The regulatory change had created the urgency that had been missing before. But the message had arrived at the crucial moment, because the operations leader was paying attention to signals and had reviewed the relationship context before sending anything. The email felt like the Chief Risk Officer's own thoughts coming back to them, not like a sales outreach. The relationship was not cold because the work did not matter. It was cold because the urgency was not there. Timing changed that.