Every hack on the roster is a legitimate single-domain solution to a multi-domain problem. That mismatch is why the repair market never runs out of customers.
The last three posts named the worldview ([Hacksterism]), the architecture ([The Hack Funnel]), and the reader’s right objection (how do I read the practice writing this post). This post — and the three that follow — opens the actual product roster. The named categories the operator encounters every week. The specific pitches, the specific limits, the specific preconditions that determine whether the product is a tool the operator uses or a bandaid the operator funds.
Before the roster runs, I need to make one thing explicit and give the operator the diagnostic sequence that has to run before any product decision. That is this post.
I Am A Consultant
Everything that follows applies to my practice as much as any other. I ran the diagnostic in the prior post, and you can too. If a claim in the roster below reads uncomfortably against my own work, that is the point — the roster is not a claim of superiority. It is a diagnostic run against the architecture of the products the industry sells.
I am also not opposed to single-domain experts. I have worked with dozens of them across my career. Some of them are among the best operators I know in their specific domain. The argument in this roster is not against expertise. It is not against depth. It is about where single-domain expertise ends and where a different kind of read has to begin.
The single-domain expert who understands where their scope ends is a legitimate tool the operator can hire. The single-domain expert who sells their scope as the full read of the operation is a hack — regardless of the depth of their expertise, and regardless of whether they know they are running as a hack.
The distinction is not credential. It is scope-awareness.
The Pitch You’ve Already Heard
Every operator has heard these numbers. Every operator will hear them again this month.
Lower your food cost 5%. Raise your average check $5. Increase your table turns 20%. Grow your social following to 10,000. Reduce your labor cost 3 points. Improve your Guest satisfaction score by 15 points.
Every one of those claims is mathematically real. On a tuned base, with the right product applied correctly, those numbers are achievable. I have seen operations produce every one of those outcomes with the right work. The pitch is not fraud in the “the number is fake” sense.
That is exactly what makes the pitch dangerous. It is not lying. It is omitting two things.
What has to be true before the product delivers. The 5% food cost reduction assumes a kitchen culture that can hold a new recipe standard. The $5 average check lift assumes a hospitality execution that can convert a suggestion into a purchase. The 20% table turn improvement assumes a Guest experience that survives faster service. The pitch does not surface any of these preconditions. It sells the output as if the output were universally accessible.
What has to stay true after it does. The 5% food cost reduction stays in place only if the kitchen culture that produced it stays in place. The $5 average check lift stays in place only if the hospitality standard that produced it stays in place. Without the underlying culture, the improvement decays inside a fiscal quarter — sometimes inside a fiscal month. The pitch does not surface any of this either. It sells the output as if the output were durable by default.
The operator who buys without those answers gets a temporary correction and a recurring problem. The correction fades. The source keeps running. The market has another solution ready. The cycle is the product.
The Structural Problem: Multi-Domain Operations, Single-Domain Fixes
The cycle runs deeper than the pitch. Even when the pitch is honest, even when the base is tuned, even when the product is legitimate — the single-domain solution has a structural limit that shows up on every operation.
Restaurant operations do not produce single-domain problems. They produce multi-domain signals whose causes run across domains.
The average check signal has roots in hospitality execution, menu architecture, cast development, and price signal simultaneously. Every one of those causes contributes to what the number is doing. A consultant who addresses only the server’s upsell technique — the hospitality-execution root — will produce a bump. Then the number will drift back down because the other three causes are still running, and one of them will overwhelm the correction within a quarter.
The food cost variance has roots in kitchen culture, management posture, vendor relationship, and labor environment simultaneously. The food cost auditor finds the variance in the kitchen and stops at the kitchen boundary. What is producing the drift in kitchen culture? Management posture. What is producing the loose management posture? Operator’s own read discipline. The signal is in the kitchen. The source is in the operator. The kitchen-scoped consultant cannot reach it because it is out of scope. Not out of competence — out of scope.
The loyalty program rewards return frequency without addressing why frequency dropped. Somewhere in the operation is the cause that made the Guest stop returning at the previous rate. That cause is still running. The loyalty program overlays incentives on top of that cause. Some fraction of Guests come back for the incentive. The rest do not. The cause continues to erode the base rate the loyalty program is fighting against.
Each expert is legitimate within their domain. Each misses the signal running in the adjacent domain — not from incompetence, but from scope.
A single-domain read produces a single-domain diagnosis on a multi-domain problem. The fix is incomplete by definition. The adjacent domain signal keeps running. The operator corrects one leak while three others compound.
This is the structural limitation of the entire product roster — not just the hack pitch, but the legitimate single-domain expert. Both fail for the same reason. The system doesn’t care whether the incomplete read came from a $97 program or a $5,000 consulting engagement.
The operation is one system. The read has to match the system.
The Diagnostic Sequence: What Runs Before Any Product Decision
Before the operator buys any product, they run five steps in sequence. This is not optional pre-work. This is the read discipline that determines whether any product purchase is a tool or a bandaid.
Step one: Read. The building is already broadcasting. The signal surfaces in the read — the pre-service audit tour, the travel path during service, the weekly numbers cadence, the cast read in the pre-shift. The building is telling the operator what is happening every day. The question is whether the operator is running the read discipline that lets them hear it.
The operator who is not running the read is waiting for the P&L to confirm what the building already knew three weeks earlier. The P&L is the report of what already happened. The read is the direct observation of it happening. Reports lag the operation by whatever the closing cycle is. The read runs at operational speed.
The read is the starting point. Everything else follows from it. No product purchase happens before the read produces something to purchase against.
Step two: Signal. What the read is producing. Not the P&L number — the live observation. The cast member who is not reading the table. The ticket time that is stretching. The Guest who is recalculating whether they’ll order the second round. The kitchen running behind. The dish-return-rate that is edging up. The check-to-check variance widening.
The signal arrives in the read before it arrives in the report. Follow it. Name it precisely. What specifically is the operation doing that it should not be doing, or not doing that it should be doing. Vague signals produce vague diagnoses. Precise signals let you follow them to their source.
Step three: Source. Where in the operation is the signal being generated? Follow it upstream.
The average check signal lives downstream of the hospitality execution, which lives downstream of cast development, which lives downstream of the environment the operator built. The signal is at the register. The source is in the environment.
The signal points at the symptom. The source is the cause. The operator who stops at the signal and buys a product that addresses the signal has not found the source. They have funded a temporary correction while the source keeps running.
Following the signal upstream requires domain-crossing. If your read shows the average check dropping, the source may not be in average-check-land. It may be in cast development. If your read shows food cost drifting, the source may not be in the kitchen. It may be in management posture. The upstream follow cannot respect the boundaries the product market draws.
Step four: Fix. What changes at the source level that eliminates the signal?
This may not be purchasable. It may be an environmental change, a training discipline, a standard being held, a conversation that has not happened, an operator behavior that has to shift. The fix that addresses the source is the only fix that does not require repeat purchase to maintain — because the cause is no longer producing the signal.
If the fix at the source is purchasable, buy it. If it is not purchasable, do it. The fix is the fix regardless of whether it comes with an invoice.
Step five: Tool. Is there a product that amplifies or accelerates the fix at the source level? This is where legitimate products earn their place.
The product that helps the operator fix the source faster or more completely is a tool. The scheduling software applied to a developed cast is a tool. The food cost consultant applied to an operator who is changing kitchen culture is a tool. The mystery shopper program applied to an operator who is already reading the building is a tool.
The product that skips the source and addresses the signal is a bandaid — expensive, temporary, and requiring repeat purchase to sustain the temporary improvement. The bandaid is the entire hack roster when applied without the source-level fix already running.
The tool amplifies fixes. The bandaid substitutes for them. Same products. Different application.
Step six: Read again. After the fix is applied, return to the read. If the signal persists, the source diagnosis was wrong. Follow it upstream again — deeper this time, with one wrong answer already eliminated. The loop closes at the read. The read is both the starting point and the correction mechanism.
One Caution: Misdiagnosis Compounds
The operator who identifies the wrong source and applies the wrong fix is paying the [Lost Opportunity Tax] on every day the actual source ran untreated while they believed the problem was being addressed.
This is worse than not fixing at all. The operator who has not fixed knows they have not fixed. They are still looking. Their attention is still on the problem. The next opportunity to correctly diagnose the source is still in front of them.
The operator who has misdiagnosed and applied a wrong fix believes they are done. Their attention has moved on. The signal that persists in the read gets rationalized — “the fix hasn’t kicked in yet,” “there must be seasonal variance,” “the market softened,” “the new cast is still ramping.” The rationalization protects the belief that the fix was correct.
Meanwhile the actual source keeps running. The [Lost Opportunity Tax] compounds day over day. By the time the operator returns to the diagnosis with fresh eyes, the source has produced additional damage that the initial correct diagnosis would have prevented.
The wrong fix is more expensive than no fix — because no fix at least leaves the operator knowing they have not solved the problem yet. This is the deep case against buying single-domain products against multi-domain problems: the wrong fix does not just fail to work, it accelerates the underlying failure by convincing the operator the failure is being addressed.
Run the diagnostic sequence carefully. Compounding misdiagnosis is the worst failure mode in the operator’s toolkit.
The Repairman Problem
Every single-domain solution is a repair. Read that carefully. Not “some” — every.
A repair returns the operation to the state that existed before the signal surfaced. Food cost back to budget. Average check back to standard. Schedule back to coverage. Table turn back to plan. The architecture that produced the variance is still intact. The signal will surface again — because the cause that produced it in the first place is still running. The market has the next repair ready. The invoice cycle continues.
The state the repair returns the operator to is zero. Not negative, not positive. Zero. The condition that existed before the signal broke through into the operator’s field of view.
The operator who only ever buys repairs never innovates out of the condition producing the breaks. They are permanently at zero — always returning to it, never building past it. The condition that broke this quarter will break next quarter. The condition that produces the average-check drift this year will produce it next year. Repair economics keep the operation at ground level, indefinitely, at recurring cost.
The hack market is not doing this to the operator. The operator is holding the door open. The market is walking through it — profitably, indefinitely, for the practitioner. The dynamic is not villainy. It is misaligned incentive between a market whose economics require repairs to keep coming and an operator whose economics require the repairs to eventually stop.
Fixing makes you a repairman. The hack market needs you to stay one.
The Three Questions For Every Product Purchase
Every product in this roster — and every product not on it — gets three questions before the purchase decision. Not skipped. Not deferred. Answered explicitly before money moves.
Question one: Does this product require a tuned base to deliver the claimed result?
The seller who answers this question clearly is selling a tool. “Yes — the loyalty program works if you have earned trust across a meaningful Guest base. If you don’t, we’ll help you identify what has to happen first, or we’ll recommend you address that first before engaging us.” That is a tool seller. They understand where their product operates and where it does not.
The seller who deflects, generalizes, or skips to the output is selling the compounding without the repair cost. “The program works for everyone. Every operator sees results. Just deploy it and follow the playbook.” That is a hack seller regardless of the price point. They are unwilling or unable to name the precondition — because naming it disqualifies operators who are not ready, and their generic-volume math cannot afford the disqualification.
Question two: Does this product address the root cause or is it an expensive bandaid on the symptom?
The symptom is what the promoter can package and measure. The average check number. The food cost percentage. The Guest satisfaction score. These are surface-readable. They can be tracked, reported, marketed.
The cause is what requires structural work — and may live in a domain adjacent to the one the product addresses. Cast development. Environment design. Operator’s own read discipline. These are harder to package and harder to sell in a funnel because they resist templating. But they are where the causes live.
The product that addresses the symptom while the cause runs untouched in the next domain over is a recurring purchase, not a fix. If you run the diagnostic sequence and the product only touches the signal-level, not the source-level, the product is a bandaid regardless of what the sales page says.
Question three: Who benefits if this doesn’t work?
If the answer is “the promoter sells the next product in the funnel,” the architecture is telling you something. The practice whose success depends on the operator’s continued problem is not structured to solve the problem. It is structured to manage it — profitably, indefinitely, for the practitioner.
If the answer is “the promoter loses their reputation because their reputation runs on the operator’s outcome,” the architecture is telling you something else. That practitioner cannot survive on operators who don’t succeed. They need the fix to work.
The architecture answers the question. The promoter’s marketing does not.
Three questions. Every product. Every time. The answers tell the operator whether they are buying a tool or funding a funnel.
What You Do Monday Morning
Before the next purchase decision — whatever program, tool, consultant, or platform is next in your queue — run the diagnostic sequence and the three questions.
Name the signal. Not the marketing category. The specific thing your operation is producing that it should not, or not producing that it should. Read it in your building. See it with your own eyes before you name it.
Follow it upstream. Not one step. All the way. Cross domain boundaries as many times as required to reach the environmental cause. Do not stop at the domain the product happens to sell into.
Identify the source. Name it as precisely as you can. Cast development in the lead cohort. Kitchen culture around portioning discipline. Management posture on standard enforcement. Environment default around what gets celebrated and what gets ignored.
Then — and only then — ask whether the product on your desk addresses the source or the symptom. If it addresses the symptom, put it down. Find the upstream fix first. The product that amplifies that fix is a tool. Everything else is a repair.
That process takes an afternoon. It saves the recurring purchase cost of the wrong fix — which is the largest single cost most operators are paying without seeing it.
The Closer
The Hack Roster runs in three more posts. Nine specific product categories. Every one of them run through the diagnostic sequence and the three questions.
The point of the roster is not to name specific products as bad. It is to give the operator the diagnostic that lets them read any product — the ones named here, the ones invented next quarter, the ones they have not encountered yet — against the same test.
The operation is one system. The read has to match the system. Anything else is a repair, and the repair economy has been waiting for you.
Digging Deeper
Positions On The Record
- Hacksterism: The Worldview Underneath — hacksterism.com/
- The Hack Funnel: Four Signatures — hacksterism.com/
- The Hackster Objection — hacksterism.com/
- The Operator’s Read Is The Only Non-Purchasable Asset — jeffreysummers.com
- Every Restaurant Problem Is A Multi-Domain Problem — jeffreysummers.com
Term Definitions From The Knowledge Base
- [The Hack Roster] — kb.jeffreysummers.com/docs/the-hack-roster/
- [Hacksterism] — kb.jeffreysummers.com/docs/hacksterism/
- [The Operator’s Read] — kb.jeffreysummers.com/docs/the-operators-read/
- [Lost Opportunity Tax] — kb.jeffreysummers.com/docs/lost-opportunity-tax/
- [Environment As Default] — kb.jeffreysummers.com/docs/environment-as-default/
- [Earned Trust] — kb.jeffreysummers.com/docs/earned-trust/
