trade-vocabulary

Use when writing any report finding, mailer, or sales copy for a business in a trade with its own operator language — names the problem or lever in the operator's own KPI/metric term (beverage attach

SKILL.md

GitHub

Trade Vocabulary

The reader of a report is the operator. To them, "your beverage attach rate" is plainer and sharper than "how often guests order a drink." Naming a problem or lever in the trade's own metric signals you understand their business — the way a mechanic using the right part name signals they know cars.

Assume plain, hook-first, short writing is already your default. This skill governs which word you reach for when the trade has a precise one, on top of that.

Core rule: when the trade has a precise term for a metric or lever in this finding, use it in place of the generic phrase — but only when it is genuinely sharper, and never to claim something the evidence doesn't show.


This is about their metrics, not their slang

The value is in the KPI/lever names operators actually manage by:

Generic (weaker) Operator term (sharper)
how often guests order a drink beverage attach rate
customers who don't come back your rebook rate / losing regulars
a repeat service call for the same problem a callback
how many guests you serve covers (guests) / turns (reseats per table)
whether the problem is service or food FOH vs BOH
average spend per guest PPA / check average

Reach for the metric. Do not sprinkle in-group slang ("in the weeds," "slammed") for flavor — it reads as trying too hard, and a stranger using a trade's social slang lands as pandering, not competence. Naming the number they manage by is the opposite: it's respect.


The guardrail (this is the whole skill)

Use the term for what the evidence shows. Never to assert a cause the evidence doesn't.

The failure mode is real. Given a review that says "our drinks come watered down":

Works — names the lever, stays in evidence:

"The lever is your beverage attach rate. No five-star review names a drink; the only mention is 'watered down.'"

Fails — the term drags in an invented operator-side cause:

"The well is slow and the pour quality reads as watered down."

The review says the drink was weak. It does not say the well (the bar's speed rail) is slow — that's a cause you made up because the vocabulary was available. A trade term used to smuggle in an unsupported claim is worse than plain English: it's confident and wrong, and an operator catches it instantly.


How to apply — three tests per term

Before swapping in a trade term, all three must be yes:

  1. Sharper? Is the term genuinely tighter than the plain phrase — or already in the finding data? If the plain words are just as clear, or the term's already there, leave it. (Swapping "LTO" in where "LTO" already sits adds nothing.)
  2. Fits? Does this exact business use this term? "Covers/turns" is full-service; a coffee shop has neither. Scope to the sub-sector.
  3. Inside the evidence? Does the term describe only what a review, benchmark, or count actually shows — no invented cause, no assumed mechanism?

One good swap that names the operator's real lever beats five slang drop-ins.


Where the terms live

Curated KPI/lever vocabulary for several sub-sectors (restaurants and bars, salons, HVAC/plumbing, cafes): references/lexicons.md. It also carries the recipe for building one for a new sub-sector (mine operator forums and trade press, then curate down to metric/lever names only; drop the aphorisms).

If a sub-sector has no lexicon yet, don't invent trade terms on the fly — a term you're unsure of fails test 2. Write it plain, and add the sub-sector to the reference when you've confirmed the vocabulary.


When NOT to use

  • Plain-language / no-jargon deliverables. A self-serve product for a buyer who asked for zero consultant-speak should strip trade terms. Do not apply this skill there.
  • A different audience than the operator. Broker, lender and enterprise briefs speak valuation/deal language, not the operator's KPIs. A term only helps when the reader manages by it. If you're unsure the reader is the operator, write plain.

Common mistakes

  • Slang for flavor. "Your kitchen's in the weeds" — cut it. Name the metric (ticket times), not the mood.
  • Cause-smuggling. The guardrail failure above. The term must not carry a claim the evidence doesn't.
  • Forcing a term that half-fits. If you're reaching, the plain phrase is safer.
  • Term already in the data. No credit for re-stating "LTO" — the swap has to add precision.