At Citrix, I learned something that most people outside enterprise SaaS never fully grasp: the fastest way to scale is not to acquire customers one at a time. It is to build infrastructure that sits underneath an entire ecosystem — so that every new customer that ecosystem gains is also your customer.
One partnership with the right enterprise software vendor could unlock thousands of deployments overnight. The integration is the distribution. The product doesn't need a sales rep at every door when it's already embedded in the workflow the customer uses every day.
I helped scale Citrix's ARR from $1 billion to $4 billion using that exact model. And it is the same model driving OPA!'s growth today — applied to an industry where the stakes are higher and the inefficiency is deeper.
I'm Rohan Doodnauth, Head of Partnerships & Co-Founder of OPA!. This is how partnership-driven infrastructure scales — and why every POS integration we sign is worth a thousand new restaurant locations.
The Ecosystem Insight
There are two ways to scale a technology platform. The first is direct sales: one customer at a time, one relationship at a time, one integration at a time. It works. It is slow. And it does not compound.
The second is ecosystem partnership sales: one integration unlocks an entire network. You build the API layer. You connect to the operating system that thousands of businesses already run. And every business in that network now has a seamless, no-friction path to your platform. One integration. Thousands of customers. Zero additional sales reps.
At Citrix, this was the difference between linear growth and exponential growth. A single partnership with a major enterprise vendor — say, Microsoft or VMware — would make Citrix's product available to every organization running that vendor's stack. The integration was invisible to the end user. The distribution was automatic. And the revenue compounded with every new customer the partner ecosystem acquired.
At OPA!, the dynamics are identical. Integrating with Toast doesn't add one restaurant to our platform. It adds every restaurant running Toast that now has a seamless, zero-code path to commission-free ordering. One API connection. Over 120,000 potential locations. The integration is the distribution.
The OPA! Partnership Stack
Every integration in our stack was selected for one reason: it sits at the operational center of the restaurant it serves. The POS is the nervous system. If your ordering platform doesn't connect directly, you're adding friction — extra tablets, manual entry, error-prone workflows. If it does connect, you're invisible. And invisible integration is the highest form of infrastructure.
The Lunchbox partnership deserves specific attention. When Andrew Boryk — Forbes 30 Under 30, one of the most respected voices in restaurant technology — selected OPA! to build the white-label marketplace infrastructure for up to 32,000 locations, it was the single largest network unlock in our history. It wasn't just a partnership. It was validation from the inside of the ecosystem that the model works.
The Flywheel in Motion
Every great infrastructure business has a flywheel. At Citrix, I watched it power $3 billion in ARR growth. At OPA!, the flywheel is just beginning to turn — and each rotation is faster than the last.
Here is why the flywheel accelerates: every new POS integration doesn't just add supply to the platform. It adds credibility that makes the next integration easier to close. Toast integration validates us to Square. Square validates us to Clover. Lunchbox validates us to enterprise brands. Each partner reduces the sales cycle for the next one. The flywheel compounds.
What Partnership Means for Operators
If you are a restaurant already running Toast, Square, Clover, or Shift4, here is what OPA!'s partnership stack means for you: joining OPA! is not a technology project. It is a configuration.
The infrastructure already exists in your kitchen. Your POS is already connected to our API layer. The menu sync is automatic. The order flow is identical to what your kitchen staff already processes. The only thing that changes is the economics — from 30% commission to $0 commission. From platform-owned data to restaurant-owned data. From DoorDash's customer to your customer.
48 hours. That is the average time from signing to live orders flowing through your existing POS. Not 48 business days. Not 48 calendar days. 48 hours. Because the partnership layer has already done the hard work. The integration is built. The connection is waiting. You just have to say yes.
Infrastructure That Disappears
The best infrastructure in enterprise technology is the kind you never see. It sits underneath the workflow. It powers the transaction. It enables the experience. And it does not ask for 30% of revenue in exchange.
At Citrix, the best product we built was the one the end user never noticed — because it was so deeply integrated into the tools they already used that it felt native. That is exactly what OPA!'s partnership layer achieves. Orders arrive in the kitchen the same way they always have. The customer experience is seamless. The only difference is that the restaurant keeps its revenue, owns its data, and controls its customer relationship.
The most powerful growth engines in enterprise tech are never the ones talking the loudest. They are the ones quietly becoming infrastructure. That is what OPA!'s partnership network is building.
