Inside a single company, escalation is boring. If a teammate is sitting on something you need, you mention it in standup, or you ping their manager, and nobody thinks twice. The hierarchy exists precisely so that “this is stuck” can travel upward without anyone taking it personally.
Between two companies, that machinery is gone. When your vendor, your agency, or your integration partner is sitting on something you need, there is no shared manager to absorb the friction. There is you, your counterpart, and the relationship. Every escalation becomes a social calculation before it becomes an operational one.
Chase too soon and you’re the nag — the client who emails twice a day, the partner who cc’s people’s bosses, the account nobody enjoys working on. Chase too late and you become something quieter and worse: the bottleneck’s accomplice. You knew the work was stuck, you watched it stay stuck, and you said nothing, because saying something felt rude.
A game nobody wins by playing well
Look at the incentives and the stalemate stops being surprising. The cost of chasing is paid personally and immediately: you spend relationship capital, you look distrustful, you become slightly harder to work with. The benefit of chasing accrues to the project — diffusely, later, and mostly to other people. So the individually rational move is always to wait one more day. Both sides know this. Both sides do it. The blocker ages while two reasonable people each conclude, correctly, that it isn’t quite their turn to be the bad guy.
It gets worse, because everyone escalates from a private threshold. You might think three days of silence justifies a nudge; your counterpart might think a week is perfectly normal. Neither threshold is visible, so every nudge arrives carrying a judgment: apparently you think I’m slow. The chased party hears an accusation. The chasing party braces for resentment. Run that loop a few times and people stop raising blockers at all — they route around them, absorb the delay, and let the project quietly rot rather than risk the conversation.
The standard advice here — communicate more, be direct, assume good intent — asks individuals to keep paying a personal cost for a collective benefit. That isn’t a fix. It’s a tax on the conscientious.
Make the referee a machine
The way out is to take the decision away from the humans. In Beevyl, a blocker is a first-class object, not a worried sentence in an email thread. It names which company is blocking. It says what’s stuck. And it carries an aging clock that both sides can see from the moment it’s raised.
Then it escalates on a timer that nobody has to trigger. By default, the counterpart is notified at 24 hours; at 48, it goes to the other side’s workspace lead. The thresholds are adjustable, but they are always symmetric — the same clock runs in both directions, because a referee is only credible if it calls the game the same way for both teams.
What this changes is the story the escalation tells. “Sarah went over my head” is a story about Sarah’s opinion of you, and it demands a response in kind. “The blocker aged past 48 hours” is a story about a clock. Nobody decided to escalate. Nobody weighed the relationship and found it expendable. The system did what everyone agreed the system would do, exactly as it would have done if the roles were reversed. The accusation has been removed from the act.
This is what referees are actually for. Players foul less when a referee is on the field — not mainly because they fear the whistle, but because the rules stop being something the players negotiate with each other mid-game.
The referee’s real product isn’t the calls it makes. It’s all the arguments the players no longer have to have.
The clock works before it rings
Here is the part that took us longest to appreciate: when escalation is mechanical and visible, it almost never happens.
A deadline you might get chased about is an ambiguity you can live inside. A clock counting up on a shared screen is not. When your counterpart can see the same timer you can, they clear the blocker at hour 20 — not because anyone chased them, but because the chase was already scheduled and everyone knew it. The escalation does its work as deterrence, the way a posted speed camera slows traffic that never gets photographed.
The visible clock also dissolves the oldest excuse in cross-company work: I didn’t know it was urgent. Urgency stops being a vibe that someone has to convey at social risk — with the right tone, at the right moment, to the right person — and becomes a number that both companies are looking at. There’s a reason chess is played with the clock face-up on the table. Nobody has to lean over and tell you that you’re using time. The clock is right there, and it is unambiguously yours.
None of that awkwardness ever belonged in the relationship. It was structural — the predictable output of two companies sharing work without sharing a hierarchy — and structural problems deserve structural fixes, not braver emails. When the mechanical parts of trust are handled mechanically, the humans get to spend their conversations on the work.