Problems › Should We Buy a Competitor? › Restaurants & Food Service
Acquisitions fail when the merged kitchens cannot sustain table turns or keep food cost in line once third-party delivery orders from both operations share the same capacity. Casual dining restaurants carry a specific bind here — delivery contributes 31% of revenue at 3.9% net margin versus 14.8% on dine-in while straining kitchen capacity. Until that is priced, 8.6% EBITDA margin will keep moving for reasons nobody can attribute, and the debate about synergy realism will stay a matter of opinion.
Acquisitions fail when the merged kitchens cannot sustain table turns or keep food cost in line once third-party delivery orders from both operations share the same capacity. Casual dining restaurants carry a specific bind here — delivery contributes 31% of revenue at 3.9% net margin versus 14.8% on dine-in while straining kitchen capacity. Until that is priced, 8.6% EBITDA margin will keep moving for reasons nobody can attribute, and the debate about synergy realism will stay a matter of opinion.
The case for buying a competitor is usually built on lifting covers and average check from the combined customer base, which are the least reliable category of benefit and the slowest to arrive. The 3.9% net margin on the 31% of revenue that comes through delivery is more predictable, and the honest contribution is usually smaller than the model assumes once kitchen capacity is shared.
The number that decides most outcomes is integration cost — kitchen reconfiguration, added third-party delivery coordination, customer loss during the overlap, and the management attention diverted from the existing 22 locations for a year or more. It is routinely omitted because it does not appear on either set of P&Ls and cannot be read from the 8.6% EBITDA margin.
The disciplined version asks what specifically you get that you could not build or buy more cheaply another way, and what the business looks like if none of the added covers materialise while table turns remain at 2.9 and food cost stays at 33.4%.
These three together are the signature. One on its own usually points somewhere else.
✓ The rationale leans on combining the two customer lists to raise covers per location
✓ Integration is described but no dollar figure is attached to extra delivery coordination or lost table turns during the overlap
✓ The acquisition is partly motivated by own locations showing flat covers and delivery already at 31% of revenue
The move that usually makes it worse. Underwriting the deal on higher average check from the merged menus, which typically arrives late, smaller than modelled, or not at all.
It is for you if you run or finance a casual dining restaurant and the rationale leans on cross-selling to each other's customers. It is the situation where the numbers are available but nobody has put them in an order that produces a decision.
It is not for you if Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Below is an excerpt from a real run of this analysis on a casual dining restaurant. It is a sample profile rather than a customer, and it is unedited engine output — this is the format you get, on your own numbers.
The subject is Ferro & Vine Restaurant Group, a sample company profile used for testing rather than a customer — $98.4 M system-wide revenue across 22 locations.
Excerpt from a real Percision run · Customer Value Architecture · sample company profile
The move. Cap third-party delivery at 25 % and re-deploy the $3.4 M FY2026 budget to drive 6 pp of dine-in recapture across the 22 existing sites.
| Investment required | $0.8–1.2 M over 18 months (marketing reallocation + server incentives + modest curbside signage) |
| Expected return | 2.4×–3.1× within 18 months |
| Revenue, year 1 | $96.8–99.2 M (flat to +1 %) |
| Revenue, year 2 | $99.5–103.4 M (+2–5 %) |
| Revenue, year 3 | $102.1–108.7 M (+3–6 %) |
| Exit criteria | If, by Month 9, delivery mix has not fallen below 28 % OR dine-in covers have not risen by at least 3 pp, the CEO must decide by Month 10 whether to (A) pivot remaining budget to direct-order app BUILD or (B) accept permanent delivery mix at 28–30 % and re-forecast group EBITDA at 7–8 %. |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to Growth Portfolio Framework, one of 29 engagements the platform runs. For casual dining restaurants it works through 8.6% EBITDA margin, 31% delivery revenue, 2.9 table turns and 33.4% food cost, then produces the sequence rather than a list of options — which move first, what it funds, and the observation that would say the sequence is wrong.
You watch the analysis get built before paying anything. Read a complete report here if you would rather see the depth first.
Twice — once standalone, and once for what it is worth specifically to you. The gap between those is the most you can pay and still create value, and it is usually narrower than expected.
Cost, substantially. They are within your control and can be scheduled. Revenue synergies depend on customers behaving as modelled, which is the assumption most often wrong.
Integration consuming more management attention than anyone budgeted, so that both businesses underperform during the period the deal was supposed to be paying back.
Materially, yes. Delivery contributes 31% of revenue at 3.9% net margin versus 14.8% on dine-in while straining kitchen capacity — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are 8.6% EBITDA margin, 31% delivery revenue, 2.9 table turns, and an answer built on industry-general benchmarks will usually point at the wrong one first.
Less than most people expect. Your last twelve months of revenue and cost split the way you already split it, plus whatever you hold on 8.6% EBITDA margin and 31% delivery revenue. The analysis is explicit about what it is assuming where your data stops, which is more useful than waiting for numbers you may never have.
Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Describe the situation in your own words and we will tell you which analysis answers it — before you sign up for anything.
Describe my situation →Prefer to skip ahead? Go straight to the free diagnostic.
English · Español · Deutsch · Português · Français · Italiano · Nederlands · 日本語 · 한국어 · 中文 · Polski · Svenska · Türkçe · العربية · Tiếng Việt · ไทย · हिन्दी · עברית