Early in my career, I was frustrated. Maybe not constantly, but certainly frequently.
We were a software company. We had engineers. We had customers. Why weren't we moving faster? Why was leadership so allergic to risk? Why did every bold idea die in committee?
It took years to understand: I wasn't failing to read the room. I was failing to read the business model.
The Model Tells You the Rules
Not all software companies are the same. The code might look identical. The org charts might be similar. But the underlying business model dictates what "good decisions" actually means — and if you don't know which game you're in, you'll optimize for the wrong thing.
Here's a simple way to think about it:
Growth companies live and die by market capture. Risk is fuel. Moving fast and being wrong is acceptable — even expected. The model rewards bold bets because there's a massive upside if you're right and a fundable story if you're wrong.
Value companies (on-prem software, established SaaS, enterprise licenses) are optimized for margin protection and retention. Every customer you have is expensive to replace. Churn is existential. The model punishes risk because the downside is asymmetric.
All companies use growth language regardless of what they actually are. Find the most recent earnings call transcript. Ctrl+F for "growth" vs. "margin" vs. "efficiency." Count the ratio. Then read the analyst questions - sell-side analysts are paid to know exactly what kind of company they're covering, and their questions will tell you immediately what the market is holding your management accountable for.
Infrastructure and Regulated Players Play a Different Game
Infrastructure and ecosystem players (think Dell, distribution companies, platform integrators) have a different constraint entirely: reliability as the product. Their customers are buying dependability, not innovation. A Dell employee who pushes for wild product bets is misreading their entire value proposition. Their job is to be the stable backbone of an ecosystem that thousands of other companies depend on. Disruption is catastrophic. For innovation, they partner with companies whose model affords taking risks.
Regulated-industry companies (healthcare, fintech, defense, federal contractors) must accept compliance as the floor, not the ceiling. Risk is legally and reputationally catastrophic. A fast-moving bet that breaks a HIPAA boundary, trips an SOC 2 audit, or violates a FedRAMP requirement can end the business, trigger personal liability for executives, or harm the people the product serves. The "why are we moving so slow" frustration in these environments often comes from engineers who don't yet see that the legal and compliance surface area is the product. Customers in regulated industries are buying your ability to operate inside their risk framework without blowing a hole in it, not flashy innovative new features.
Before You Push, Ask
Before you push for a strategy, a roadmap, a hire, or a risk - ask yourself:
What does my company get paid for, really? Margin? Growth? Reliability? Compliance coverage?
What happens if this bet fails? Is it a learning, a write-off, or a company-ending event?
Who depends on us being boring? If the answer is "lots of people," bold is not your friend.
Who gets hurt if we're wrong? If the answer includes patients, financial accounts, or national security infrastructure - that's not a constraint to work around. Reliability is your entire business.
Find The Money, Pick It Up
The company I was frustrated with wasn't broken. It was rational. It was protecting margins in a low-growth market with sticky enterprise customers who paid predictable license fees. Any disruption to that - new pricing models, riskier product bets, faster release cycles - could erode the very thing customers were paying for: stability and trust.
I was trying to play growth-company chess on a value-company board.
Once I understood that, I stopped being frustrated. I started asking better questions: not "why won't we take this risk?" but "what risk profile does this business model actually support?"
That reframe made me a better engineer, a better leader, and eventually, a better strategist.
The takeaway: Your business model is the operating system. Everything else - culture, strategy, appetite for risk - is an application running on top of it. Learn the OS first.