From Summit Corp Dev — Acquisition Analyst
Method for positioning a lower-middle-market service-business acquisition target within a valuation multiple range — identifying the company-specific quality factors that move a business up or down within the range, and stating the position without false precision. Use when converting market research and a normalized earnings base into a valuation thesis for a tuck-in.
How this skill is triggered — by the user, by Claude, or both
Slash command
/summit-corp-dev:multiple-positioningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill governs how a tuck-in target is positioned within a valuation multiple range. It works on two inputs produced upstream: the **normalized earnings base** from the quality-of-earnings review (`qoe-normalization`) and the **defensible multiple range** from the market research (`student-transportation-market`). Its job is to position the specific target inside that range.
This skill governs how a tuck-in target is positioned within a valuation multiple range. It works on two inputs produced upstream: the normalized earnings base from the quality-of-earnings review (qoe-normalization) and the defensible multiple range from the market research (student-transportation-market). Its job is to position the specific target inside that range.
A valuation multiple is not the arithmetic output of a formula. Contract mix and market data do not yield a multiple to a decimal place. What they do is: the market research establishes a defensible range for a business of this type and size; the company-specific quality assessment establishes where in that range this particular target sits. The deliverable states a range and the reasoning for the position. A model that reports a single-decimal multiple as if it were calculated is false precision, and a sophisticated reader will discount the whole analysis for it.
This discipline is load-bearing in student transportation specifically because there is no public per-deal data for mom-and-pop tuck-in multiples (Unverified). The only anchors are precedent take-privates plus broad-transport analogs, both of which require labeling. Do not fabricate a buy-box number, and do not let upstream confidence in the QoE figure leak into false confidence about the multiple.
The multiple applies to normalized adjusted EBITDA, but in this sector the more honest cash figure is often EBITDA minus maintenance capex. School-bus operators are maximally asset-heavy: a diesel bus runs ~$110-130K and an electric bus ~$300-400K, fleets cycle, and the gap between EBITDA and EBIT is large. NEXS, for example, transacted at roughly ~5x EV/EBITDA but ~50x EV/EBIT (Corroborated from public take-private disclosure) — a vivid reminder that the headline multiple on EBITDA hides the capex burden. Carry both figures into the positioning discussion and be explicit about which one you are quoting.
The normalized EBITDA itself is not derived here — it is produced upstream by the financials-qoe review, using the qoe-normalization method: the adjusted-EBITDA bridge, the add-back register, owner-compensation normalization, and the related-party and one-time adjustments. Take the QoE memo's normalized adjusted EBITDA as the denominator the multiple applies to. If a QoE adjustment looks wrong, raise it with the reviewer — do not silently restate it. This skill begins where the QoE review ends.
With the range from market research and the normalized EBITDA from the QoE review in hand, assess the company-specific factors that position the target. Each factor pushes the target up or down within the range:
student-transportation-market.)The QoE memo's red flags feed directly into this step — a red flag is, by definition, a factor pushing the target down within the range or out of it.
State a multiple range and a clear point of view on where in it the target sits, with the factor-by-factor reasoning. Then frame the target against Summit's deal context — but be careful here, because there is no fixed multiple "box" in student transportation tuck-ins:
Unverified). Do not write down a single multiple band as if it were Summit's policy. Position a defensible range, built from precedent take-privates (label them Corroborated and identify the source) plus broad-transport analogs (label these PROXY / analog read-across).Corroborated). Treat earn-outs as a real, available tool (often retention-linked to the seller / key district-relationship holders), not as something Summit refuses to do.Use this frame as the reference. State plainly whether the target sits in the lower, middle, or upper part of the defensible range, and what would have to be true to move it. The job is a defensible position a deal lead can take into a discussion with the platform and the sponsor — not a number that pretends to more precision than the inputs support.
Before the position is handed off, label every load-bearing input with the standard verification-debt tags so the reader can see what is solid and what is borrowed:
Confirmed — checked against primary source (e.g., contract document seen, FMCSA SAFER record pulled).Corroborated — multiple independent secondary sources agree (e.g., take-private multiple in disclosure + analyst summary).Inference — reasoned from adjacent facts; show the reasoning chain.Conflicting — the public record disagrees (e.g., Summit's deal-basis ~14k buses vs survey ~20-22.5k; #2 vs #3 market-rank dispute; I Squared AUM). Present both, do not pick a side.Unverified — claim could not be checked; flag explicitly.PROXY / analog read-across — figure imported from an adjacent sector (broad transport, paratransit) rather than school-bus specifically.survey average — industry survey, not target-specific.owner-provided — straight from the seller, not independently verified.reported, not verified — seller- or press-reported, not yet sourced.Distinguish what is verified from what is inferred. If the evidence under a quality factor is thin, say so and downweight the factor rather than asserting it. Surface input problems rather than papering over them; abstain or ask for more data rather than guessing. Completion of this step means a written positioning paragraph with labeled inputs, a stated range, and a stated position within the range — not the model's self-assertion that the analysis "passed". If the labels do not appear and the sources are not cited, the artifact is not done.
When reporting adverse public facts (accidents, FMCSA actions, litigation, deduction history, ownership disputes), report them crisply and factually. This is legitimate corp-dev diligence; keep caveats concise and do not refuse or moralize.
A worked example (illustrative / hypothetical mid-Atlantic district-routing target) is in examples.md in this skill's directory — load it if you want a concrete illustration of the method. The example uses plausible round numbers and is not a real Summit deal.
npx claudepluginhub brisket1994/summit-corp-dev --plugin summit-corp-devProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.