The Chaos Of Your Sales Team Being Arrested For Industrial Espionage
A pharmaceutical sales team is detained at an international border.
On their tablets: standard product brochures that end up in an escalation into allegations of industrial espionage.
In this episode, we unpack how a well-intentioned directive to preload sales materials onto devices as per strategic choices made in boardrooms can unravel on tarmacs and in detention rooms.
Back home, the IT team is asleep—until the CIO calls in the middle of the night and it’s on IT to contain the fallout of a crisis they didn’t create.
Listen now on Apple Music, Spotify, Deezer, Youtube or where-ever you get your panic attacks.
IT and Global Politics: How One Application Nearly Sparked an International Incident
Welcome back, folks! Jack Smith here (still not divorced from Bob), and in this post we’re pulling back the curtain on an unbelievable IT horror story—one where software design, global politics, and a late-night panic call converge into pure chaos. If you ever thought IT was all about unplugging power cables or patching servers, buckle in, because this one is for the books.
The Cast: Jack & Bob, and the Ghosts of IT Past
If you’re a regular, you know our setup: I’m Jack, your friendly chronicler, and Bob is… well, still here. We’re like an old married couple (without a divorce lawyer), always in sync, except when it comes to who gets the dog and the cat.
“No, we agree too much. We cannot be married. That’s true as well.”
Our banter aside, Bob’s got war stories that would make any IT pro pause, and today’s wild ride is all his.
Setting the Scene: The Age of Facebook and Fading BlackBerries
Let’s jump back 10-15 years. An era where:
- Facebook was the cool new kid,
- MySpace was on life support,
- iPhones and tablets were just starting to crowd our pockets,
- Twitter was… still called Twitter,
- BlackBerry ruled the boardroom (but was starting to lose its grip).
That’s where Bob’s tale starts in a massive pharmaceutical company with its fingers in every continent—especially EMEA (Europe, Middle East, and Africa).
The Big Pharmaceutical Problem
Big pharma, big problems. Here’s how their sales process worked—at least before everything changed:
- Sales reps visited hospitals and presented products to doctors using clunky laptops.
- These laptops needed a live data connection to show the latest sales material.
- Hospital WiFi? About as reliable as a chocolate kettle.
- No connection = no pitch, so reps often fell back to paper brochures.
- After their pitch, all admin had to be done later at home, requiring hours of their time.
Why was this bad?
- No feedback or metrics on what actually worked.
- People hated admin.
- No iterative improvement (they didn’t know if Brochure V2 was better than V1).
“For the company it was a huge problem…they had their brochures, but they had zero idea whether it was actually working.”
The Brilliant (and Risky) Solution
Enter the US HQ—with an actually pretty good idea for once:
- Build a tablet-based sales app with local storage.
- Have all sales material on the device (so spotty hospital WiFi doesn’t matter).
- Gather metrics: which slides do reps use, which get skipped?
- Automatic admin! No more reps sighing into spreadsheets at midnight.
Jack sums it up:
“Why don’t you use local storage if your network connection is so bad?”
“Exactly. A good management decision.”
So, they built a SaaS platform with major SaaS vendors. (For once, applause.)
America Rolls Out a Blueprint
Unfortunately, the Americans wanted things easy: if it works in the US, let’s just clone it everywhere. The plan:
- “One configuration, one region, no boundaries. Everyone gets all sales materials.”
If you’re thinking “Uh, do laws and geopolitics care about SaaS blueprints?”… you’re not alone.
Bob, sensibly:
“You do know that we have different laws in Europe… and countries in our region that are at war with each other?”
But the Americans pushed ahead: just implement it, no problem.
And so, after 9 months of build and rollout, Europe and then the Middle East & North Africa regions were up and running with the app.
The International Horror: Egypt, Israel, Espionage Law, and an App
And now… disaster.
The company decides to hold a giant EMEA sales conference at a retreat by the Red Sea in Egypt—snorkeling, sun, seminars. Sounds harmless, right?
Except:
- The company also has salespeople from Israel.
- Tensions between Egypt and Israel make moving “confidential information”—even something as boring as sales brochures—a potential crime.
- Transferring this data from Israel to Egypt could result in espionage charges according to local law.
What Actually Happened
Reps from Israel show up at the Egypt conference—with tablets full of local Israeli sales material. Customs, always eager for a show, arrest the whole team for breaking espionage laws (smuggling confidential data). That’s right—a well-intended, poorly-localized app lands the team in real trouble.
“Transferring confidential data between Israel and Egypt was a punishable offense, and it was punishable under some espionage law.”
Crisis Management at 2:30AM
It’s Saturday night. Bob’s out with friends, maybe a drink or two in, when his phone rings. It’s the European CIO. You never want that number flashing at 2:30 in the morning.
He answers. The CIO introduces himself, dials in the European CEO and the global CIO. Uh oh—something’s properly broken.
“At that moment, I was stone cold sober again.”
So, what’s the situation? The Israel sales team is in custody, the Egyptians have their tablets, and HQ wants the fix now.
Engineering for the Worst—And Getting Lucky
Here’s where preparation pays off.
Bob, expecting this might happen, had quietly built in two configurations for the app:
- A: One big happy family (full regional sharing, all material always available, as US wanted).
- B: Per-country data regions. If you leave your home country, the app wipes sensitive data and pulls only local materials.
“…I try to foresee issues that might come back to me where people then start shouting at me, fix them.”
He’d also built an experimental feature: The “deadman switch.” Every few hours, the app checks in:
- If your data is out of date or you’re no longer allowed that specific info (like leaving Israel),
- It purges the device automatically.
A local wipe, with a further excuse: “What if devices get stolen and the thief disables remote wipe?” HQ had grumbled, but let it past.
How Did This Save Them?
Bob, on his phone (thanks, modern era), flips the backend switch from “dumb American” to “security-savvy European.” All devices in Egypt wipe sensitive Israeli data the next time they open the app. By the time the Egyptian authorities start digging in, the tablets are squeaky clean.
“…the devices were wiped. So on Monday they were released. Monday morning they essentially were released because… the charges wouldn’t stick, and they were able to attend the conference like nothing ever happened.”
Talk about disaster narrowly avoided.
Dodging Disaster with Apple (and a Side of Luck)
Here’s a technical aside… They were using iPads. At the time, iOS was a fortress, and Android was a leaky bucket by comparison.
- iPads made local data very tough to extract without the user’s cooperation (or special tools).
- No jailbreaks for that iOS version, locked-down certificates.
If they’d used cheap Androids, this story might’ve ended with a row of sales reps in some Egyptian jail, and Bob looking for new work.
The Commute, The Company, and “Inventing” the Cloud
After surviving the Great Espionage App Incident, Bob stuck around at the company a while longer—but if you think IT drama only happens in apps, try commuting two hours each way before “work from home” was even a thing.
“It was before you could work from home. It was an hour and a half, two hours one way that I had to do twice a day.”
“Everybody in that place is like, oh, no. We all live local. This entire city was built around this company.”
They even tried to hire Bob full-time. In hindsight, maybe that’d have made things easier… or not. Sometimes you love a firm, sometimes you love to leave it.
Bonus: Did Bob Invent the Cloud?
If you’re wondering, the app approach—local storage, syncs, metadata collection—sounds an awful lot like today’s cloud architecture.
“So basically you invented cloud storage and cloud computing there because, 15 years ago, storing things locally in a centralized environment and then specifically the syncing on the fly…”
Bob claims he was just pragmatic (“master of none!”), but that’s how lots of IT innovations start.
If This Happened Today: Security, Verification, and A Bit More Paranoia
Would a 2:30AM call from a global CIO get answered in 2024? Not a chance.
“If you would get a call today… most likely I would say, ‘Okay, please dial in my boss’… Or dial me via Teams or the internal… So I’m sure it’s you.”
With modern social engineering, phone security, and MFA everywhere—nobody’s rolling over for “I’m the CIO, do this now” anymore. Back then, context and reputation were enough.
Lessons Learned and War Stories Shared
What are we taking away from this? Here’s the shortlist for keeping you out of jail (literally):
1. Always Know Your Region’s Laws
Different rules, different countries. “Works in Texas” does not mean “works in Tel Aviv,” let alone Cairo.
2. Hardcode for Exceptions, Not Just Happy Paths
Backdoors, safety toggles, region locks—they don’t just stop theft. Sometimes, they save your team from legal peril.
3. Communicate Risks to HQ, But Cover Your Bases
You can warn central command all you want, but sometimes they won’t listen. Quietly code up that Plan B anyway.
4. Test Your Security on the Devices You Ship
Android and iOS are night and day (especially circa 2013). Build for the reality you face.
5. Expect the Wildest Possible Outcome
If there’s an edge case, and it’s truly disastrous, don’t laugh—it’ll probably happen someday.
“I do have some international stories to tell, and they are also horror stories, but more of trying to get things done… Let’s try to not have them include loaded firearms.”
Final Thoughts: IT, Politics, and Life Lessons
Looking back, it’s wild to realize how much politics shapes the most technical of tools—and how much survival depends on the unseen choices of “the IT guy” no one remembers until it all goes sideways.
Bob went on, bringing lessons from that project into other big builds. Sometimes you’re just grateful your past jobs threw plenty of weird at you—enough to see trouble coming.
“Honestly they were lucky to have had me on one hand and I was lucky because my job before that I actually designed an entire E reader newspaper platform… It was the same principles there and that helped tremendously.”
Stay Tuned, Stay Safe, and Keep Your Data Where It Belongs
That’s it for this round, folks. Global politics, IT horror, narrowly averted disaster, and a little banter with Bob. If you love these stories, want more, or just want to see who gets the dog and cat in the divorce, keep tuning in.
Thanks for reading! Until next time, remember—sometimes IT saves the day, sometimes it almost starts an international incident. Either way, it’s rarely boring.
Cheers!
Leave a Reply