This case study reflects my thinking at a specific point in time (Q1 2021). It is NOT a current recommendation. The company discussed may have materially changed since this analysis was conducted. This is presented for educational purposes only — to demonstrate how I evaluate enterprise software businesses with government exposure, not to suggest any investment action. Markets change; so do companies. Past performance doesn't predict future results.
In early 2021, I was examining a data analytics company that had become synonymous with government intelligence work. The company had gone public via direct listing in late 2020, and the stock had run up significantly on AI hype. The question wasn't whether the technology was real — it clearly was. The question was whether the business model could translate into durable shareholder value.
The company occupied a unique position: providing data integration and analytics software to intelligence agencies, defense departments, and increasingly, large commercial enterprises. The numbers told a polarizing story:
The 125% net dollar retention was exceptional — existing customers were expanding rapidly. But the losses were staggering. Stock-based compensation alone exceeded revenue. This was either a generational opportunity or a value trap masquerading as a growth story.
Can a company built on bespoke government deployments — with heavy professional services and long implementation cycles — ever achieve software-like margins? Or is this fundamentally a consulting business with software economics priced in?
For intelligence agencies, switching is nearly impossible. The software becomes embedded in critical workflows, handles classified data, and requires extensive security clearances for support. Years of institutional knowledge live in the system. For commercial customers, switching costs are high but not insurmountable — more like enterprise software generally.
This is where it gets interesting. Each deployment generates data about what works — which integrations, which workflows, which analytics patterns. The company was building what I call a "deployment knowledge network." The more they deployed, the faster and better subsequent deployments became. Not a traditional network effect, but a compounding advantage.
The security clearances, government certifications, and reputation for handling classified data create barriers competitors can't easily overcome. You can't just decide to compete for CIA contracts — you need decades of trust-building.
No meaningful cost advantage. In fact, the heavy professional services component was a cost disadvantage compared to pure SaaS competitors.
The subsequent years validated some aspects of the thesis while challenging others:
The company proved it could grow and eventually profit. But the journey was far from smooth — the stock fell over 80% from peak to trough before recovering. Timing and valuation discipline mattered as much as thesis quality.
This case study illustrates how I evaluate enterprise software businesses with government exposure — not to suggest what you should buy or sell. Every investment decision depends on your circumstances, timeline, and risk tolerance. If you'd like to discuss how these frameworks apply to your portfolio, let's talk.