The Founder's Black Box

The most expensive thing in your startup is the function you don't understand.

---

Sioux Falls. Early days of Prismatic. Michael Zuercher is an electrical engineer by training, a CEO by necessity, and he’s about to do the thing that most technical founders refuse to do.

He picks up the phone and starts selling.

Not once. Not as a favor to a warm lead. He runs roughly the first hundred demos himself — a technical founder explaining an integration platform to prospects who don’t care about architecture. They care about their problem.

Call after call, he listened. He got better. He heard the same pain described in enough different ways that he could finally articulate it back in the language buyers actually used. He learned which features sparked genuine interest and which ones got polite nods. He started to feel the rhythm of a sales conversation — when to push, when to listen, when the deal was real and when it wasn’t. And the listening didn’t just sharpen his sales pitch — it reshaped the product roadmap. Those hundred conversations told him what to build next in a way no internal planning session ever could.

And when he finally hired a sales leader, he knew exactly what to look for. What the role required. What “good” sounded like.

Prismatic went on to raise $34 million, serve over 200 customers, and build a 60-person team — all from South Dakota.

Michael didn’t become a salesperson. He became a founder who understood sales. That distinction matters more than almost anything else I’ve learned in the last ten years.

The Black Box Problem

Every founder has at least one. The part of the business they don’t understand and hope someone else will handle.

For technical founders, it’s usually sales. For product founders, it’s development. For sales founders, it’s the architecture underneath the thing they’re selling. For almost everyone, it’s finance — the unit economics, the burn rate mechanics, the difference between revenue and cash.

The instinct is to hire around it. “I’m not a marketer, so I’ll hire a marketer.” “I’m not technical, so I’ll find a CTO.” And to be clear — you should hire people who are better than you at these things. That’s not the problem.

The problem is what happens next.

You hand off the function. You stop paying attention to it. When the person you hired gives you an update, you nod along because you don’t have the vocabulary to push back. When they ask for budget or headcount, you approve it because you can’t evaluate whether the request makes sense. You’ve outsourced your judgment along with the work.

And then it breaks.

The marketing agency burns through $120,000 optimizing for vanity metrics that have zero correlation with sales — and you don’t catch it for six months because you never understood what the metrics should have been. The dev team builds the wrong thing for a quarter because the product founder said “just make it work” instead of understanding the technical constraints well enough to scope it properly. The sales hire flames out, and you replace them, and the replacement flames out too — and it takes three cycles before you realize the problem was never the hire. It was that you never understood the sales motion well enough to know what you were hiring for.

This is the black box. Not a mystery. A choice. The choice to leave part of your business opaque to yourself and hope it works out.

There’s a word for this that sounds like good leadership but isn’t. Founders call it delegation. But delegation means handing someone the work while retaining the ability to evaluate it, coach through it, and fix it when it breaks. What most founders do with their black boxes is abdication — handing it off and hoping for the best.

Here’s the practical test. If one of your direct reports told you their function was underperforming, could you help them troubleshoot it? Not solve it for them — troubleshoot it. Could you ask the five questions that narrow the problem? Could you tell the difference between a people problem, a process problem, and a strategy problem in that function?

If the answer is no, you have a black box. And the longer it stays closed, the more expensive it gets. A literate founder catches a problem when it’s a conversation. A black-boxing founder catches it when it’s a crisis.

The Mindset That Opens the Box

Here’s the thing nobody talks about: most founders don’t black-box functions because they’re lazy. They do it because they’re afraid of looking stupid.

There’s a strange pressure on founders to project competence in every direction. You’re supposed to be the visionary, the expert, the person with the answers. And when you’re sitting in a meeting about a function you don’t understand — development, marketing, finance, whatever it is — the instinct is to nod along rather than ask the basic question. Because asking “what does that metric actually mean?” or “why did we choose that architecture?” feels like admitting you don’t belong in the room.

That instinct is the black box’s best friend.

The founders who open every box share a trait, and it’s not intelligence or experience. It’s intellectual honesty. The willingness to say “I don’t understand this yet” and mean it — not as a performance of humility, but as an actual starting point. They’re curious enough to ask the question that sounds dumb and secure enough to survive the moment of not knowing.

Michael Zuercher didn’t walk into those first demos pretending to be a salesperson. He walked in as an engineer who knew he didn’t understand how buyers think — and he stayed in the room long enough to learn. That takes more confidence than faking expertise. It takes the kind of confidence that doesn’t need to already have the answer.

What Leaving Looks Like

Brady Chandler came in knowing cattle economics cold — six-figure lending decisions, herd composition, seasonal cycles. He’d never managed a development team. By the time he left, he could sit in a sprint review, evaluate architecture decisions, and tell you whether a feature estimate was reasonable. He didn’t become a developer. He became a founder who could manage development.

That’s what no black boxes means. Not expertise in everything. Literacy in everything. The ability to walk into any room in your company and add value — not by doing the work, but by understanding the work well enough to see what’s broken and ask the question that fixes it.

The Question

If you’re a founder reading this, walk through every function in your business — sales, marketing, product, development, finance, customer success, operations. For each one, ask yourself: if this broke tomorrow, could I help troubleshoot it?

Where the answer is no — that’s your black box. And it’s the part of your company most likely to hurt you in a way you won’t see coming.

Open the box. You don’t have to master what’s inside. But you have to understand it well enough to know when it’s working and when it’s not. That’s not optional. That’s the job.