Operator
Spend runs through the holiday
Every Eid has the same Thursday evening, and this Friday is Eid al-Adha in Saudi Arabia.
Spend is running. The client is on the road, or at the airport, or already at the family's house with the phone face down. The outsourced team, an agency in another city or a freelancer with the login, is watching the account do what it did on Wednesday, in a market that stopped being Wednesday at about four in the afternoon.
Nobody ever decided what the team may do now. Not in the contract, not in the scope. May they pause it? Lift it, because Eid evenings are a delivery night? Leave it, because that is what the plan said?
So they choose between two ways of being wrong.
Do nothing, and the account buys a Friday morning at full price, a morning when the whole market is at prayer, at the butcher or asleep. Sunday's question is why nobody reacted.
Do something, and Sunday's question is who told you to touch it.
From the platform side I have watched this play out across a great many accounts at once. The teams that come through a holiday well have one thing in common: a client who wrote one paragraph, weeks before, saying if I do not answer within two hours you may pause, you may not lift by more than a fifth, and here is the second number to call. That paragraph is the whole of account governance. Everything else is a permission structure for days when everyone is at their desk, and those are the days that need it least.
The default is a decision. It is just the one nobody has to sign.
The only governance document that matters for an account is the one that says what may be done when nobody answers. It has to be written on an ordinary Tuesday. By the Thursday, nobody is reading.