Stories from the field.

New Year, New Rep — the territory reshuffle.

Fiscal Q1. Sarah has been moved from enterprise to mid-market. Her €4M pipeline now belongs to Tom, who started Monday. Until Sarah has clarity on her new patch, she is taking it easy.

Tom received a Salesforce export, a territory map, and a welcome email from the CRO heralding the Hebung von Synergien. On the export: 23 accounts, 47 open opportunities, stage fields populated from whatever Sarah clicked last Thursday.

What isn't on the export: which champion is about to change jobs (the signs were in his last email, if you knew what to look for), which procurement director still hasn't forgiven the company for a 2022 invoicing mistake, which deal Sarah kept parked at Stage 3 for forecast-smoothing reasons nobody will put in writing, which CIO replies to email and which one only reads WhatsApp after 20:00.

Tom's first call, Account #3:

"Hi, I'm your new rep."
"Who are you? Where is Sarah? You are the 6th contact in 3 years!"

By April, three deals have slipped a quarter. By July, one champion has left for the competitor. Nobody tracks it, because there's no line in the P&L called revenue lost to territory reshuffles. Sales Ops files it under normal ramp. Finance calls it forecast variance. It's neither. It's the cost of walking a fresh person into a room full of relationships they haven't been introduced to.

Just ask Sven.

Every company has a Sven. His LinkedIn says Senior Analyst. His actual job, the one nobody writes down, is holding it all together.

Which supplier accepts late changes? Ask Sven. Why does SAP throw error 47B on the 15th of every month? Ask Sven. Why is the Belgian subsidiary invoiced a week late, on purpose, for reasons that sound insane until Sven explains them? Ask Sven.

Then once a year Sven goes on vacation to Mallorca. By day four, three people have WhatsApp'd him at the pool. By day nine, leadership discovers that roughly forty percent of departmental throughput depends on one man's memory and the Wi-Fi at a rental apartment in Cala d'Or.

Sven isn't the problem. Every org has a Sven or two. Officially he's a Senior Analyst. Unofficially, he's the reason payroll still runs, the CRM still works, and someone in Legal hasn't had a breakdown. Nobody designed it that way. It just happened, slowly, the way browser tabs do.

The holy Excel.

On the shared drive, in a folder that hasn't been cleaned since the last IT migration, sits a file: Q4_Reporting_FINAL_v7_USE_THIS_ONE_Markus.xlsx

Over forty tabs. About a dozen of them hidden. VBA macros last modified in 2019. It drives a monthly report that lands in the CFO's inbox every sixth working day, like clockwork.

Markus left in 2020. Nobody knows exactly what it does. Nobody dares open the VBA editor. When a consultant suggests replacing it with Power BI, the CFO changes the subject. Once a year, a junior analyst attempts a rebuild, and two weeks later they quietly return to v7_USE_THIS_ONE and stop making eye contact at work events.

This isn't a file. This is organisational dark matter. A business-critical process encoded in a medium nobody alive can read.

Calling Klaus.

Klaus retires after 28 years. Leaving do, Edeka gift card, LinkedIn post with a couple hundred likes, a speech from the Geschäftsführer involving the word Familie.

A couple of months later, a finance manager stares at a supplier rebate accrual that makes no arithmetic sense. The number isn't wrong. It's just unexplainable. Someone in the room says: "Maybe call Klaus?"

Klaus is on a boat in Croatia. Klaus is now a consultant. Klaus charges €200 an hour, and the first call runs close to an hour. There will be more calls.

The quiet tragedy is this. In the last month before he left, Klaus had almost nothing to do. Nobody asked. So now both sides pay: Klaus with his retirement, the company by the hour.

The cron job that wasn't important enough to write down.

Anya has been on the platform team for eight years. She knows things the runbook doesn't. She knows the cron job at 02:17 every Tuesday gets re-run by hand because of an off-by-one nobody patched. She knows the feature flag LEGACY_INVOICE_PATH has been on for three years and turning it off costs about six thousand euros a month — there was a Slack thread once, nobody can find it. She knows why the line if (date.getDay() === 6) skipJob() exists. She lived through the Saturday it was added.

Anya gets an offer she can't refuse. Two weeks' notice. Slack message: "I'll write up everything important before I go — Confluence page coming." The page is 200 lines. It covers her main responsibilities cleanly. It doesn't mention the Tuesday cron, the feature flag, or the Saturday skip. None of those felt important enough to write down.

Six months later, on a Saturday at 03:42, the cron job at 02:17 didn't run. By the time anyone connects the two on Tuesday morning, the reconciliation reports are off by twelve million euros.