When I joined Citrix, annual recurring revenue was $1 billion. When I left, it was approaching $4 billion. The delta was not a better product. It was not a bigger marketing budget. It was not a more aggressive sales team.
The delta was infrastructure partnership — building the connective tissue that made every other company's growth also Citrix's growth. One integration with the right enterprise vendor didn't add a customer. It multiplied the addressable market by thousands. The product became invisible. The distribution became automatic. And the revenue compounded with every new deployment the partner ecosystem acquired.
I'm Rohan Doodnauth, Head of Partnerships & Co-Founder of OPA!. Before OPA!, I spent a decade building enterprise infrastructure at Lockheed Martin and Citrix, then founded an RCM company that hit $2 million in revenue at 60% EBITDA margins. Each chapter taught me something different about how to build infrastructure that other businesses depend on. This article is about all three lessons — and how they converge in what we're building at OPA!.
The 3 Laws of Enterprise ARR Growth
These are not theories. These are patterns I observed over a decade of building enterprise infrastructure — first at Lockheed, then at Citrix, then at my own company. Every one of them applies directly to what OPA! is building today.
Law 1: Infrastructure Beats Features Every Time
Enterprises don't buy the best product. They buy the product that integrates seamlessly with everything they already have. At Citrix, the products that grew fastest were never the ones with the most features. They were the ones that plugged into existing workflows without disruption — the ones that IT departments could deploy without retraining a single user.
OPA! follows the same principle. We integrate directly with Toast, Square, Clover, and Shift4. Orders arrive in the kitchen through the same POS the staff already uses. No new tablets. No new training. No new workflow. The restaurant's operations are identical — the only thing that changes is the economics. That is not a feature. That is infrastructure. And that is why it wins.
Law 2: One Integration Is Worth 100 Direct Sales
At Citrix, a single enterprise partner integration — say, with Microsoft Azure or VMware — could unlock thousands of enterprise deployments overnight. The integration became the distribution channel. Every new customer that partner acquired was also, by extension, a potential Citrix customer.
At OPA!, the math is the same. Integrating with Toast doesn't add one restaurant. It adds access to every restaurant in Toast's network — over 120,000 locations — that now has a seamless path to commission-free ordering. The Lunchbox partnership alone represents infrastructure for 32,000 locations. One agreement. 32,000 potential operators. Zero additional sales reps needed.
Law 3: The Moat Is the Network, Not the Technology
Technology can be copied. A feature can be replicated in six months. But a network of live integrations, active partnerships, and operating locations cannot be replicated quickly. At Citrix, the technology was good — but the moat was the ecosystem. Thousands of enterprise partners, millions of deployments, deep integration with every major operating system. A competitor could build similar technology. They could not rebuild the network.
OPA!'s moat is the same: 2,400+ live locations, 6 POS partners, 5 loyalty integrations, and the Lunchbox partnership covering 32,000 locations. Every new operator deepens the network. Every new integration widens it. The moat grows with every transaction processed.
What Lockheed Martin Taught Me About Mission-Critical Infrastructure
Before Citrix, I was at Lockheed Martin. In defense and aerospace, the word "infrastructure" carries weight that the tech industry has never fully understood. Infrastructure failure in defense is not a customer complaint. It is not a Slack notification. It is a catastrophe with consequences measured in lives, not revenue.
The discipline I learned at Lockheed — around redundancy, reliability, uptime guarantees, and failure-mode analysis — directly shapes how OPA!'s technical partnerships are built. Restaurant ordering is mission-critical infrastructure. If OPA! goes down during a Friday dinner rush, that restaurant loses revenue it will never recover. The tolerance for failure is zero. The engineering philosophy from defense and aerospace applies directly.
This is why our POS integrations are built as direct API connections — not middleware, not webhooks, not third-party bridges. Direct connections mean fewer failure points, lower latency, and the kind of reliability that a restaurant operator can stake their business on.
Learning to Build Lean: The RCM Company
After Citrix and Lockheed, I founded a Revenue Cycle Management company. It was the smallest thing I'd ever built — and it taught me the most important lesson of my career.
The lesson: the best business models are the ones where the infrastructure is so tight and the unit economics so clean that profitability isn't a growth phase — it's the starting point. You don't build a lean business and then scale it. You build a business that is lean because it scales.
OPA!'s ~$65/month subscription at near-zero marginal cost per location is the same model. We don't need to charge 30% commission to sustain operations. We don't need to burn venture capital to subsidize growth. The economics work at $65 because the infrastructure is built to be lean from the first line of code. That's not accidental. That's a design decision informed by building a business where every basis point of margin mattered.
Bringing It All to OPA!
Every career chapter that looked like a detour was actually a different angle on the same problem: how do you build infrastructure that other businesses depend on?
Lockheed taught me that infrastructure must be mission-critical reliable. Citrix taught me that infrastructure scales through ecosystem partnerships, not direct sales. The RCM company taught me that infrastructure must be economically lean enough to sustain itself without extraction.
OPA! is all three. Mission-critical ordering infrastructure that integrates seamlessly with the restaurant's existing POS, scales through partnership-driven distribution, and operates on unit economics clean enough to charge $0 in commission — permanently.
The restaurant industry is a $1 trillion sector that has never had infrastructure built specifically for it by people who understand enterprise-scale systems. It has been served by platforms built to extract from it. OPA! is built to serve it.
I've spent fifteen years learning how to build infrastructure that compounds. Every career step — from defense to enterprise SaaS to bootstrapped profitability — was a different lesson in the same discipline. OPA! is where all of those lessons converge.
