| |
|
BY BILL MURPHY
|
THE OPERATIONS
BRIEF
|
|
|
|
ISSUE #6 · APRIL, 2026
|
|
| |
|
| |
|
Hi there,
The companies pulling ahead right now are not the ones with better forecasts. They are the ones that stopped depending on one person to hold the whole operation together.
This issue is about that difference — why the founder bottleneck is now a market response problem, what it looks like on the floor, and the one system your team can build this week to stop depending on memory.
|
| |
The Founder Bottleneck is now
a market response problem.
Why holding tighter in volatility is exactly backward
Every operator I talk to right now is dealing with some version of the same problem. Tariffs are stacking. Input costs are moving. Supply chains are getting rearranged on short notice. And the instinct — for most founders, most leadership teams — is to hold tighter. Control more. Make more decisions yourself.
That instinct is exactly backward.
I wrote about this recently in a piece on the founder bottleneck — the pattern where everything in a company still runs through one person. The revenue flattens. The team waits for approvals. The sales cycle stretches because no one else can close the deal. The skills that built the company to $3M are the same ones preventing it from reaching $10M.
One symptom I flag in that piece: when your positioning is built entirely around the founder's personal credibility, every deal collapses into a vendor comparison the moment you're not in the room. If that's where deals are dying for you, the Revenue Messaging Audit is where we start with every client — it shows you exactly why you're stuck there, and what the path to strategic partner positioning looks like.
That framing is about growth ceilings. But the same dynamic is showing up right now in how companies respond to market volatility.
|
The numbers operators are responding to
· ISM Prices Index hit 78.3% in March — up 7.8 points from February, with price increases across 17 of 18 sectors tracked
· 48% of organizations are actively modeling and deploying tariff mitigation strategies (KPMG 2026 CEO Outlook)
· 41% are deploying AI to manage trade compliance
· $127 billion in tariff returns now being processed electronically by CBP
|
When one person holds all the context — the supplier relationships, the pricing logic, the customer commitments — the business can only react as fast as that person's calendar allows. And in a market moving this fast, "as fast as one person's calendar" is not fast enough.
The operators getting ahead are doing something different. They are building systems that carry context forward without depending on any single person to hold it. Documentation discipline. Decision frameworks that let the team act without waiting. Intelligence layers that surface the right information before someone has to go looking for it.
Those KPMG numbers are not "wait and see" numbers. Those are companies that decided their response system matters more than their forecast accuracy. Even the recovery side now requires operational readiness — companies that documented their exposure cleanly are recovering money. Companies that ran everything through one person's head are still trying to reconstruct what they paid.
|
The real cost of the Chief Everything Officer is not just slower growth. It is slower response to a market that is not going to slow down for you.
Bill Murphy, Founder & Chief Strategist · Colony Spark
|
|
|
| |
Black swans don't wait
for your planning cycle.
Jason Wong, Paking Duck, on stacked disruption in packaging
Jason Wong, founder and CEO of Paking Duck, put into words in a Supply Chain Dive interview what a lot of operators are feeling right now but struggling to articulate.
Packaging manufacturers and brands are getting hit from multiple directions at once: tariffs, metal duties, shipping disruption, and oil-driven material costs. Many brands feel they have exhausted their options and are now waiting to see what happens next. The disruptions are not arriving one at a time anymore — they are stacking on top of each other, shortening every planning window and punishing every slow response.
|
"These black swan events keep coming at us. We just don't have time to prepare."
|
Wong's comment captures the emotional and operational truth of the moment. But it also points at the trap: "we don't have time to prepare" is what it feels like when preparation depends on one person making time in their calendar. Operators who have built response systems don't need to prepare in the moment — their systems already are prepared.
|
For manufacturers and distributors
If your response to each new disruption is a scramble from scratch, you're paying the founder-bottleneck tax. The work isn't to predict the next black swan. It's to build the decision infrastructure so the team can respond to whatever comes next without waiting for the calendar to open.
|
|
For vendors selling to manufacturers
Your customers are exhausted. They don't have mental space to onboard another vendor who shows up vague. The rep who walks in already knowing the last stated priority, the unresolved issue, and the commercial context wins the meeting. That's what The Stack this week is about.
|
|
|
| |
The Post-Call Intelligence Agent.
Build memory into the workflow. Stop trusting memory itself.
No more lost commitments. No more tribal knowledge trapped in one person's inbox. The system carries context forward automatically.
The best operators are quietly building a layer between every important conversation and every next action. After a customer call, supplier check-in, plant review, or commercial meeting, the system takes the transcript and turns it into operating leverage. It extracts commitments, flags unresolved risk, updates the CRM or project tracker, and creates the next brief automatically.
Nobody has to trust memory. Nobody has to dig through notes three weeks later. The system carries context forward. In a stable market, dropped context is annoying. In a volatile market, dropped context gets expensive fast. If tariffs shift, a supplier slips, a customer changes volume, or a margin assumption moves, the companies that win are the ones that can reconnect today's conversation to last week's decision and next week's action without friction. That is the real use case. Not AI as novelty. AI as continuity.
|
What the agent does
After every important conversation, the system:
· Extracts commitments made by both sides, with deadlines and owners
· Flags unresolved risk or open questions that need escalation
· Updates the CRM or project tracker without human touch
· Creates the brief for the next conversation automatically
· Surfaces patterns across accounts — if five customers raise the same concern, leadership sees it early
|
|
For operators
Fewer missed follow-ups. Fewer handoff errors. Less tribal knowledge trapped in inboxes or in one person's head. And faster pattern recognition — when the same concern shows up across accounts or suppliers, leadership sees it earlier, not after the damage is done.
|
|
For vendors selling into manufacturing
Reps stop showing up vague. They walk in knowing the customer's last stated priority, the unresolved issue, the promised follow-up, and the commercial context. That changes the quality of the conversation immediately — and it changes how the customer perceives your team.
|
|
The build · Claude Code or equivalent
Step 1: Transcript ingestion — from Gong, Fathom, Otter, or Zoom
Step 2: Extraction agent — commitments, risks, decisions, open questions
Step 3: CRM connector — write commitments as action items against the account
Step 4: Pattern layer — weekly roll-up of recurring themes across accounts
Step 5: Brief generator — auto-creates the pre-call brief for the next meeting
Complexity: Moderate. Works with whatever meeting recorder and CRM you already have. Can be built as a single agent in Claude Code with read/write access to both.
|
|
The edge is not more activity. The edge is building memory into the workflow so the business becomes harder to knock off course. In a year like this, that is what being proactive actually looks like.
Bill Murphy
|
|
|
| |
|
THE OPERATIONS BRIEF
by Bill Murphy · Powered by Colony Spark
|
|
Building memory into your workflow instead of trusting memory itself? Hit reply. I read every one.
|
|
| |
|