Olo Goes Private. Here's the Operator Playbook for the Next 90 Days.

I spent Tuesday morning on the phone with a multi-brand CIO who runs eight concepts across four states, and the first thing she said when she picked up was, “So when do you think the layoffs hit?” Not if. When. She had already pulled her Olo contract out of the renewal queue, asked her vendor manager to flag every dependency that touches the platform, and quietly emailed two competing ordering vendors for “informational” decks. She did all of that before the stockholder vote was even counted. By the time the press release confirming the Thoma Bravo deal closes lands later this week — the calendar says Friday, September 12 — she will be on her second round of red-team scenarios. She is not panicking. She is doing the job. And most of you, frankly, are not.

Here is the contrarian thesis, stated plainly so you can disagree with it before you keep reading: every Olo customer should be in renegotiation mode this quarter. Not after the close. Not after the layoffs the PE pattern almost guarantees. Not after the inevitable “we’re sharpening focus on our highest-impact integrations” email lands in your inbox. Now. The stockholder approval today gives you a finite, calendar-bounded window — roughly 90 days between the announcement of new ownership and the first meaningful change in vendor posture — to extract concessions, lock in roadmap commitments, and pre-empt the margin compression that always follows when Thoma Bravo takes a SaaS asset private. Operators who treat this as a story to read instead of a process to run are going to eat that compression. Operators who treat it as a 90-day project can come out of it with better contracts than they had before the deal was announced.

The deal itself is not the story. The deal is the starting gun.

The PE pattern: what comes next is not a mystery

There is a temptation, especially among operators who have lived through one previous vendor acquisition, to treat each PE deal as bespoke. It isn’t. Thoma Bravo runs a remarkably consistent playbook across software assets, and the steps are knowable in advance. The firm took Olo private at a premium to the recent trading range, which means the equity check is large and the debt component still needs to be serviced from operating cash flow. That math drives everything that follows.

Step one is almost always a near-term reduction in force, usually announced within the first business week after close. Restaurant Dive has been tracking the pattern across PE-owned restaurant-tech vendors, and the timeline is consistent enough that the trade press already has the story scaffolded. The cuts tend to land disproportionately in functions that don’t generate revenue in the next four quarters — long-horizon R&D, partner ecosystem teams, mid-tier customer success, some portion of corporate G&A. The effect on customers is also consistent: integration partners get less attention, mid-market operators get less hand-holding, and the roadmap quietly narrows to whatever the largest 20 customers are asking for.

This wouldn’t be alarming if it were Olo’s first round. It is not. The company has already cut staff twice in the past three years — about 11% in 2023 and roughly 9% in 2024, public-company moves driven by very different pressures than the ones a leveraged owner will apply. Olo ended 2024 with roughly 617 employees. A third round, layered onto a base that has already been thinned twice, is not a haircut — it is a structural reshaping of the people who answer your support tickets, build the integrations you depend on, and ship the features your operations team has been asking for since spring. The expected mid-September window, telegraphed in trade coverage for around the 16th or 17th, is too soon for the new owners to have done deep diligence on individual roles. The first round under PE is rarely scalpel work. It is almost always a percentage-of-payroll target handed to functional leaders, who are asked to hit it within two pay cycles.

Step two, usually layered in around month three to month six, is a pricing model review. This is where the genuine margin pressure on customers begins. Public-company SaaS prices tend to be sticky and discount-heavy, because the sales team is optimizing for ARR growth and Wall Street wants the bookings. PE-owned SaaS prices tend to harden — fewer renewal discounts, more enforcement of usage tiers, fewer free overages, more “platform fees” or “integration fees” or “data fees” that did not previously appear on the invoice. Operators who have been quietly exceeding their order-volume tiers without consequence for the past three years tend to find this out the hard way at their next renewal. By that point, leverage is already gone.

Step three, around month nine to twelve, is the consolidation of overlapping product lines. If Thoma Bravo holds any adjacent assets in payments, loyalty, marketing, kitchen display, or back-of-house, expect a “platform” pitch within a year. Some of these will be genuinely useful and priced fairly. Some will be bolt-ons that customers are encouraged, then nudged, then required, to adopt as part of their renewal. The pattern is not unique to Thoma Bravo, but Thoma Bravo executes it more aggressively than most because their underwriting math depends on cross-sell.

None of this is hypothetical. It is the model. The only variable is how cleanly it plays out, and how prepared individual customers are when it does.

The 30-day window: demand the things you’ll wish you had later

The first 30 days after a private-equity close are an unusual moment in vendor relationships. The new owners have not yet imposed their playbook. The existing customer success and account management teams are nervous about their own jobs and unusually motivated to demonstrate retention strength. Old commitments that were verbal are still remembered. The legacy public-company instinct — say yes to anything that protects ARR — has not yet been replaced by the leveraged-owner instinct, which is say yes to anything that protects gross retention but tightens net retention.

Use this window. Here is the operator’s punch list for the next 30 days, and I would argue every Olo customer with more than 25 locations should have this on a project plan by the end of next week.

Demand a written roadmap commitment for any integration you depend on. Not a sales-deck slide. A signed letter, attached to your master agreement, that names the integration partners or features you rely on, and commits to a continued investment level (engineering headcount allocated, release cadence, or specified deliverables) for a defined period — twelve months at minimum, 24 if you can get it. If your account team balks, that is itself information. The 400-plus integration partners in the broader Olo ecosystem are about to have a hard year, and the operator who has a written commitment for their POS, their loyalty platform, or their delivery aggregator integration is going to sleep better than the operator who has a verbal “yeah, we’ll keep supporting that.”

Lock the price. Whatever your current per-location, per-order, or per-feature pricing is, get a multi-year price lock with a cap on annual escalators. The default escalator in most Olo agreements has been CPI or a fixed 3-5%. Push for a cap at 3% or, if you have the leverage of multi-brand volume, a flat price for 24 months. I know operators who got 36-month flat-price commitments in the two weeks after Thoma Bravo’s last major restaurant-adjacent deal closed, simply because they asked before the new owners had standardized the customer-facing playbook.

Get a service-level commitment with teeth. Most SaaS SLAs are paper tigers — they refund a percentage of monthly fees for downtime, which on a per-location basis is meaningless. Push for an SLA tied to dollars rather than percentages, and an early-termination right if the SLA is missed for two consecutive months. The new owners will almost certainly cut some portion of the on-call and customer support organization within the first two quarters. An SLA you can actually enforce is the only thing that gives you recourse if response times degrade.

Reserve a data-portability right in writing. Your customer database, your order history, your menu structures, your modifier logic — make sure your agreement explicitly grants you the right to export this data in a machine-readable format on demand, at no charge, within a specified number of business days. The default in most vendor contracts is a vague “customer’s data remains customer’s property.” That is not enough. You want a specific, time-bound, no-cost data export right that you can invoke unilaterally. This is the foundation of any future migration, and it is also the single biggest source of leverage you will have at your next renewal.

Audit your integration dependencies and rank them by criticality. This is internal work, not vendor work. Within 30 days, your tech team should have a single-page matrix that lists every integration touching Olo — POS systems, kitchen displays, loyalty platforms, delivery aggregators, payment processors, marketing tools, BI exports — and ranks each one as “operationally critical” (the restaurants stop functioning without it), “revenue critical” (we lose orders or visibility), “convenience” (annoying to lose but not blocking), or “vestigial” (we forgot we still pay for this). The integrations you list as operationally critical are exactly the ones you should be asking for written commitments on in the bullet above. Most operators have never done this exercise rigorously, and the new ownership transition is the right moment to force it.

If you do nothing else in the next four weeks, do these five things. The cost of running this project is, at most, a couple of legal hours and a focused week of internal coordination. The value, if any of the PE-pattern scenarios plays out, is six figures of avoided cost or margin compression per year for a mid-size operator, and substantially more for an enterprise.

The 60-day window: pressure-test the alternatives without lighting your hair on fire

In the second month, the new ownership is starting to make itself known. Communications from the vendor will be carefully worded — “exciting new chapter,” “deeper investment in our platform” — and you will get one or two account-team turnover notices, framed as growth opportunities for departing reps. Layoff news, if the PE pattern holds, will be a few weeks old. The mood will be more anxious than the external communications suggest. This is the right time for the second-tier work: pressure-test what your alternatives actually look like, without doing anything that signals you’re about to bolt.

A forthcoming May piece — the broader roundup of restaurant-tech consolidation in 2025 — makes a point worth bringing forward here: the alternatives to Olo are not nothing, but they are also not what they look like in a vendor’s deck. There are a handful of credible ordering platforms that can plausibly serve enterprise QSR and fast-casual operators. The substitution cost, however, is meaningful — typically nine to fifteen months for a multi-brand operator to migrate cleanly, with worst-case scenarios stretching past two years if the underlying POS or loyalty integrations are complex. You are not going to switch in 90 days. You are also not stuck for five years.

Structure this exercise in three parts.

First, commission an internal migration cost estimate. Not a vendor-supplied estimate, an internal one. How many engineering weeks would it take your team to migrate to the most credible alternative, including the integrations you flagged as operationally critical in month one? How much in implementation services? What is the realistic revenue risk during the cut-over? Be honest. If your real estimate is twelve months and $1.4M, write that down. It does not need to be a number you would ever publish; it needs to be a number you would trust.

Second, take two or three “informational” meetings with credible alternatives. Do not RFP. An RFP is a signal that you are buying, and you are not — you are gathering market intelligence. Frame the conversations as “we are doing routine market scans every 18 months.” Pay attention to which vendors have specific, credible answers to the migration questions you raised internally; the ones that wave them away are not real options.

Third, read the broader commerce landscape carefully. An upcoming May piece on DoorDash’s commerce ambitions will argue, defensibly, that the marketplace operators are becoming serious infrastructure players, and the line between “aggregator” and “commerce platform” is fuzzier than it has been in five years. That has implications for Olo’s strategic position and for the calculations a leveraged owner will make about pricing and partner economics. You do not need to bet on any specific outcome; you do need to be aware of it. The question “how essential is Olo in 2027” is not the same as “how essential was Olo in 2023.”

The point of this second-month work is not to switch vendors. It is to know, with precision, what switching would cost. That knowledge is your real source of leverage in the third-month conversation.

The 90-day window: the renegotiation conversation

By month three, two things will be true that are not true today. One, the new ownership will have begun communicating its priorities — usually through a customer advisory board, a key-account program, or a wave of executive customer visits. Two, the structural cuts and the early integration-of-priorities decisions will be visible enough that you can read the tea leaves. This is when the renegotiation conversation, if you’ve done the prep work, becomes productive.

I want to be clear about what this conversation is and is not. It is not a threat. You should not walk in waving an RFP or telling your account team you’ve been talking to competitors. (You have been, but they don’t need to know that.) The conversation is a calm, prepared, professional exchange in which you communicate two things: the dependencies you have, and the assurances you need to continue confidently investing in the platform.

Here is roughly the structure of the meeting I would advise a multi-brand operator to take in early December.

Open by acknowledging the transition positively. The new owners need to see customer-side confidence in the platform. You want to give the account team a story they can carry upward. This is not insincere; you have not actually decided to leave, and assuming the platform continues to perform, you have no plans to. State that clearly.

Then state your dependencies specifically. “We have X locations on the platform. We process Y orders per week through it. We have Z integrations that are operationally critical to us — here is the list. Our digital revenue through Olo is a material percentage of our enterprise revenue, and our operational continuity depends on the platform being stable, the integrations we depend on being maintained, and the pricing being predictable.”

Then make your asks. This is where the work of months one and two pays off. You want, in writing: the integration commitments you started asking for in month one, ideally signed and attached to your MSA by this point; the multi-year price lock with a capped escalator; the SLA with teeth; the data portability provisions; and, ideally, a roadmap roadshow — a commitment that your team gets a quarterly product briefing from someone senior enough to actually answer questions about direction. The roadmap roadshow is something a public-company Olo would have refused to put in writing. A PE-owned Olo, in the first 90 days when net retention is the religion, is more likely to say yes.

Close by making it easy for them to say yes. “We are not asking for a price cut. We are asking for predictability and commitment. If we can get there on these terms, we are happy to be a reference customer for the new ownership and a participant in the customer advisory board.” The new owners genuinely need reference customers in year one. They will pay for them, in the form of contract concessions, more readily than they will pay for them in cash discounts.

If you walk into that meeting with the homework done, the alternative analysis quietly in your back pocket, and a calm, constructive tone, the outcome is almost always better than the outcome you would have gotten by waiting for the renewal to come up naturally six months later. The reason is structural: in the first 90 days after a PE close, the vendor’s incentive structure favors net retention over net new bookings, and that is the only quarter in the entire ownership cycle when that is true. After the first year, the incentives flip.

The integration partner problem is bigger than the layoffs

Most of the operator commentary I’ve read this week has focused on the layoff risk and the support degradation risk. Those are real. But they are not, in my view, the biggest risk to operators in this transition. The biggest risk is the integration partner ecosystem.

Olo’s platform is, in operational reality, a hub-and-spoke system in which the company itself owns the ordering, menu management, and dispatch logic, while several hundred third-party integrations handle the things that touch the actual restaurants — the POS connections, the loyalty integrations, the marketing platforms, the kitchen display systems, the payment processors, the BI tools. The strength of that ecosystem is one of the genuine strategic moats of the company. The weakness of that ecosystem, from a leveraged-owner’s perspective, is that maintaining 400-plus integrations costs more than most of them generate in revenue. Mark this: the partner ecosystem is exactly the kind of asset that looks beautiful in a strategic narrative and ugly in a 90-day cost review.

What I would expect in the first six to twelve months of new ownership is a quiet tiering of integration partners. The top tier — integrations the largest customers depend on, generating enough usage to justify continued engineering — will be fine, and may even get more attention because they protect enterprise retention. The middle tier — useful integrations used by a meaningful but not large fraction of customers, requiring ongoing work to keep current with API changes on both sides — will become a battle. Maintenance will slow. Bug fixes will lag. New features will stop. The bottom tier — legacy, lightly used, or disproportionately expensive — will be deprecated, sometimes formally, often by attrition.

If your operationally critical integrations are in the top tier, you are likely fine, though I would still get the written commitments. If they are in the middle, you have a genuine problem coming, and you should start cultivating direct relationships with the partner, separate from the Olo channel. If they are in the bottom tier, migrate proactively in 2026, before the deprecation forces your hand on the vendor’s schedule.

How do you know what tier your integrations are in? Ask. The partner reps will not say “we are in tier two and about to be neglected,” but they will tell you, with surprising candor, how much volume they’re doing through Olo and how the relationship has been trending. Three or four of those conversations gives you a tiering map more accurate than anything Olo will ever share.

The talent dislocation is a hiring opportunity

One thing the trade press will under-cover: the people leaving Olo in the forthcoming reduction — assuming the PE pattern holds — are some of the most experienced restaurant-technology talent in the industry. They know your accounts, your integration quirks, the things that have been duct-taped since 2019. A meaningful number will land at competing vendors. Some will start companies. Some will take in-house roles at large operators, which is a hiring opportunity I would encourage any operator with the budget to seize. The next 60 to 90 days are probably the best moment in five years to recruit deep restaurant-tech expertise into your own organization. If you have an open role for a director of digital, a head of integrations, or a product manager who can sit between operations and vendors — be on LinkedIn. Talent that has been locked inside a single platform is about to become unusually fluid, and the operators who absorb it will own the deepest in-house understanding of their stack.

What I would not do

A short list, because there is going to be no shortage of bad advice in the operator forums over the next month.

Do not switch vendors in a panic. The PE pattern is a knowable risk, but it is a manageable one. A poorly planned migration is a far bigger threat to your digital revenue than a vendor with a new owner.

Do not sign anything new for at least 30 days without legal review with the transition explicitly in mind. The boilerplate that was reasonable in a public-company contract may be unreasonable in a leveraged-owner contract. The change-of-control clause is the obvious one to check, but so are the assignment provisions, the data ownership clauses, and any auto-renewal language.

Do not let your account team manage the relationship purely on the vendor’s terms. Insist on quarterly business reviews. Insist on roadmap visibility. Insist on access to product leadership at least once a year. These are reasonable asks that public-company Olo sometimes pushed back on. PE-owned Olo, in the first 90 days, has a strong incentive to say yes.

Do not assume the worst about the new owners themselves. Thoma Bravo runs the playbook I described, but they also genuinely invest in the assets they own, and the long-run product quality of PE-owned SaaS is sometimes better than the public-company predecessor — leaner organizations make sharper decisions, and a focused roadmap is often a better roadmap. The customers who are worst off in these transitions are not the customers of well-run PE-owned vendors. They are the customers who failed to use the first 90 days.

The interpretation

The deal closes Friday. The stockholders approved it today. The layoffs the trade press is already preparing to cover are weeks, possibly only days, away. None of this is a surprise to anyone who has watched a Thoma Bravo SaaS deal play out.

What is in your control is how you respond. The next 90 days are a window of unusual leverage for customers of any vendor going private — a window that closes the moment new ownership finishes its first cost review and begins enforcing its standardized customer playbook. Operators who treat this quarter as a chance to renegotiate, lock in commitments, and pressure-test their alternatives will come out with stronger contracts than they had before the deal was announced. Operators who treat it as a news story will, in twelve to eighteen months, find themselves paying more for less, with thinner support, slower integrations, and weaker recourse.

The CIO I spoke with Tuesday is doing the work. Most of you are not. The 30-day punch list is genuinely a 30-day punch list. You can start it tomorrow. You can finish it before Halloween. The cost of running it is small. The cost of not running it, if any of the PE-pattern scenarios plays out, is going to be paid quietly, on every invoice, for the next five years.

Pick up the phone today. Email your account team and request a meeting in the first week of October. Pull your contract. Build the matrix. Make the asks. The window is open. It is not going to be open for long.

— Priya covers operators for TableTransfers. Tips: [email protected].