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
/vortex-tuck-in-analyst: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 (`door-services-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 (door-services-market). Its job is to position the specific target inside that range.
A valuation multiple is not the arithmetic output of a formula. Revenue 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.
The multiple applies to normalized adjusted EBITDA. That figure 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:
door-services-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 Vortex's deal parameters:
Use the box as the reference frame. State plainly whether the target fits it, sits below it, or has quality characteristics that would justify arguing the top of the band or above. The job is a defensible position a deal lead can take into a discussion — not a number that pretends to more precision than the inputs support.
A Nashville commercial door target with FY revenue around $4.3M illustrates the method. The QoE review has already established the normalized adjusted-EBITDA base and its adjustments — the depreciation and interest add-backs, the owner-compensation normalization, the removal of pandemic-relief income, the related-party rent test. Positioning starts from that figure. The owner-stated revenue mix — roughly half service and repair, with the remainder retrofit and a small new-construction tail — is a comparatively high-quality mix that argues for the upper part of the range. The offsetting factors are concentrated owner dependence, since the owner personally holds sales and back-office functions, and the cash-basis accounting without a hard monthly close that the QoE memo flagged; both are diligence items and both pull against the top of the band. The output is a positioned range with that factor-by-factor reasoning — not a single computed multiple.
Provides 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.
npx claudepluginhub zabrisket/vortex-tuck-in-analyst --plugin vortex-tuck-in-analyst