Too Dependent on One Customer
in Restaurants & Food Service

The short answer

Concentration on third-party delivery is only a problem in proportion to how easily the platform could reduce orders or change terms, which is a question about contract flexibility rather than about the revenue share. 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 revenue concentration will stay a matter of opinion.

A delivery channel at 31% of revenue is dangerous or fine depending entirely on the structure underneath. If the platform can cut visibility within weeks, that is an exposure. If replacing the channel means reconfiguring kitchen capacity and losing table turns, it is a strong position that happens to look concentrated.

The trap is that delivery usually comes with worse economics — the platform negotiates lower net margins, demands packaging, and pays on its schedule — so the risk and the margin damage arrive together. Diluting concentration by growing dine-in is slow; the faster lever is usually renegotiating the delivery terms to reflect the kitchen capacity being strained.

It is also worth separating revenue concentration from contribution concentration. Delivery and dine-in can point in opposite directions on margin, and the second is the one that would actually hurt.

How to tell this is actually your problem

These three together are the signature. One on its own usually points somewhere else.

✓ Delivery share appears in the weekly split between covers and average check while table turns remain at 2.9
✓ The same platform shows materially lower net margin than dine-in and pushes food cost above the 33.4% level
✓ A drop in that platform's volume would require immediate cuts to labor or capacity rather than a plan to rebalance

The move that usually makes it worse. Chasing more delivery volume to dilute the percentage, which adds kitchen strain while leaving the margin dependency intact.

Who this is for — and who it is not

It is for you if you run or finance a casual dining restaurant and one customer exceeds a quarter of revenue. 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.

What this looks like when the analysis is actually run

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.

This is one move out of a full analysis. Read a complete report — every page, no email required.

What the engine does with this question

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.

Questions people ask about this

What level of customer concentration is dangerous?

There is no threshold that means much on its own. What matters is how quickly they could replace you and what happens to your fixed costs if they do. Both are answerable.

Should I turn away business from a large customer?

Rarely on concentration grounds alone, and often on margin grounds. If the largest account is also the worst-priced, the concentration problem and the margin problem have the same fix.

How do I reduce dependency without losing the account?

Increase what it would cost them to leave, and reprice the exposure. Growing a second segment is the right long answer and does not help within the notice period you actually have.

Is this different in restaurants & food service than in other industries?

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.

What data do I need before this analysis is worth running for a casual dining restaurant?

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.

When is Percision the wrong tool?

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.

Does Percision replace a lawyer, tax advisor, auditor, or AI implementation team?

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.