Problems › We Cannot Tell If the Strategy Is Working › Restaurants & Food Service
A strategy that cannot be wrong cannot be checked, and most written strategies in casual dining are written so that they cannot be wrong. The version of this question that applies to casual dining restaurants is not the generic one. Delivery contributes 31% of revenue at 3.9% net margin versus 14.8% on dine-in while straining kitchen capacity — so an answer that ignores 8.6% EBITDA margin will be confidently wrong. The analysis has to start from 31% delivery revenue and 2.9 table turns rather than from revenue.
A strategy that cannot be wrong cannot be checked, and most written strategies in casual dining are written so that they cannot be wrong. The version of this question that applies to casual dining restaurants is not the generic one. Delivery contributes 31% of revenue at 3.9% net margin versus 14.8% on dine-in while straining kitchen capacity — so an answer that ignores 8.6% EBITDA margin will be confidently wrong. The analysis has to start from 31% delivery revenue and 2.9 table turns rather than from revenue.
The usual reason a strategy cannot be evaluated is that it was never stated in a form that could fail. Statements such as increase delivery share or raise table turns produce no observation that would contradict them, so they survive indefinitely regardless of results on net margin or kitchen capacity.
A checkable strategy names the mechanism — this change in third-party delivery mix produces this shift in net margin and table turns by this date — and the observation that would say the mechanism is not working, such as delivery staying at 31 percent while overall EBITDA margin remains at 8.6 percent or table turns stay at 2.9.
The other frequent cause is lag. Strategies operate on horizons longer than weekly covers or monthly food cost reports, so the honest response is to identify leading indicators that move early, such as average check on delivery orders or kitchen ticket times, and to state in advance what they should read.
These three together are the signature. One on its own usually points somewhere else.
✓ The strategy document contains no target value for net margin by channel or table turns that would mark the plan as unsuccessful.
✓ Weekly reports list completed tasks such as new third-party menus or added delivery drivers without showing movement in food cost or covers per hour.
✓ Operators disagree on whether the current delivery mix supports the plan and cannot settle the question with existing data on dine-in versus delivery margins.
The move that usually makes it worse. Adding more reporting on covers and average check, which increases the volume of numbers without making the strategy falsifiable.
It is for you if you run or finance a casual dining restaurant and the strategy has no failure condition written anywhere. 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 · Quick Market Scan · 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 Proprietary EFF Methodology, 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.
The mechanism it depends on, not the outcome it promises. Outcomes lag; mechanisms move early and tell you sooner whether the causal claim holds.
Decide before starting, and tie it to the mechanism's natural cycle. Deciding afterwards guarantees the timeline is chosen to fit whatever result arrived.
That is usually a sign the strategy was not specific enough to produce a clean test. Narrow it until one number would settle the argument.
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 · ไทย · हिन्दी · עברית