Working capital peg calculator

Purpose

Convert a target company's historical working capital cycles into a defensible normalized peg and a fully specified true-up mechanism — so buyers don't overpay for a seasonal high point and sellers don't get penalized for a temporary trough. Produces the peg number, the reasoning behind it, and the deal-document mechanics needed to operationalize it at close.

When to Use

Invoke this skill when the user asks to:

• Set or validate a normalized working capital peg (target) for an acquisition
• Analyze whether a seller's proposed peg is inflated or understated
• Adjust a working capital baseline for seasonality before pricing a deal
• Design the post-close working capital true-up and collar mechanism
• Normalize historical working capital for one-time or non-recurring items
• Prepare a working capital position for negotiation or a quality-of-earnings discussion

Inputs Required

Before starting, collect:

• Historical working capital data: Monthly or quarterly balances for the trailing 12-36 months — accounts receivable, accounts payable, inventory, and any other included/excluded current items
• Revenue by period: Monthly or quarterly revenue matching the WC periods, to compute ratios and detect seasonality
• Deal structure basics: Enterprise value or purchase price, expected close date, and whether the deal is cash-free/debt-free
• WC definition scope: Which balance-sheet lines are in vs. out of the target working capital definition (e.g., cash, deferred revenue, income tax, related-party items)
• Known one-time items: Any non-recurring events in the historical period — large one-off orders, bulk inventory buys, delayed collections, temporary payment-term changes
• Business seasonality context: Peak/trough months if known, or major seasonal drivers (holiday, harvest, fiscal-year buying, etc.)
• Negotiation posture: Buy-side or sell-side, and whether a counterparty peg has already been proposed

If monthly granularity is unavailable, use quarterly data and flag that seasonality precision is reduced. If close date is unknown, model the peg at the most recent quarter-end.

Instructions

Step 1: Define and Reconcile the Working Capital Base

Establish exactly what counts as working capital for this deal before computing anything.

• Build the WC bridge: Current Assets (in scope) − Current Liabilities (in scope)
• Standard inclusions: trade receivables, inventory, prepaid expenses, trade payables, accrued expenses
• Standard exclusions in a cash-free/debt-free deal: cash, short-term debt, current portion of long-term debt, deferred revenue (often disputed), income taxes payable, related-party balances
• Confirm each disputed line's treatment with the user; note that deferred revenue and accrued interest are the most common negotiation flashpoints
• Produce a clean, period-by-period WC series using the agreed definition

Step 2: Compute the Cash Conversion Cycle Metrics

For each period, calculate and trend the three drivers:

• DSO (Days Sales Outstanding) = (AR / Revenue) × days in period
• DIO (Days Inventory Outstanding) = (Inventory / COGS) × days in period
• DPO (Days Payable Outstanding) = (AP / COGS) × days in period
• Cash Conversion Cycle = DSO + DIO − DPO
• Flag any trend: rising DSO signals collection deterioration (or channel stuffing before sale); rising DIO signals stale inventory; falling DPO signals suppliers tightening terms
• Note whether recent-period metrics diverge from the trailing average — sellers often stretch payables and accelerate collections in the months before close to depress WC

Step 3: Detect and Adjust for Seasonality

Isolate the seasonal swing so the peg reflects a true operating level, not a calendar accident.

• Plot WC as a percentage of trailing revenue by month to normalize for growth
• Identify peak and trough months and quantify the swing (peak WC − trough WC)
• Choice of averaging method — select and justify:
• 12-month trailing average: neutralizes full seasonal cycle; default for most businesses
• Same-month-prior-years average: use when close date lands on a known seasonal point
• Revenue-weighted average: use when WC scales tightly with sales volume
• If the deal closes at a seasonal peak, the peg must reflect that peak — otherwise the buyer inherits an underfunded balance sheet on day one

Step 4: Normalize for One-Time and Non-Recurring Items

Strip out distortions so the peg reflects the ongoing business.

• Remove one-off inventory builds, abnormal single-customer receivable spikes, temporary supplier prepayments, and any WC impact of discontinued lines
• Adjust for any pre-close WC manipulation identified in Step 2 (aggressive collections, stretched payables)
• Add back items artificially suppressed and remove items artificially inflated
• Document each adjustment with the amount and the rationale — this is the schedule that survives negotiation

Step 5: Derive the Peg and a Defensible Range

• Calculate the recommended peg from the normalized, seasonally-adjusted series
• Present it as a point estimate plus a range (low / recommended / high) reflecting method sensitivity
• Show what the peg implies for the balance sheet at close and the purchase-price impact of a 1-day move in DSO/DIO/DPO (sensitivity table)
• State the buy-side vs. sell-side framing: buyers argue for a higher peg (more delivered WC), sellers for a lower one

Step 6: Design the True-Up Mechanism

Specify the post-close adjustment mechanics as deal-document-ready terms:

• Measurement date & method: closing-date balance sheet prepared on the same accounting policies as the peg (consistency clause is essential)
• Adjustment direction: dollar-for-dollar increase/decrease to purchase price for the difference between closing WC and the peg
• Collar/dead-band: recommend a collar (e.g., no adjustment within ±1-2% of the peg) to avoid disputes over immaterial swings; size it to the business's normal noise
• Preparation & review timeline: who prepares the closing statement, review window (typically 30-60 days), and estimated-then-final true-up sequence
• Dispute resolution: escalation to an independent accounting firm, cost allocation, and binding-determination language
• Sample terms: provide 3-5 drafted clauses the user can hand to counsel

Output Format

• Structure: Analytical report followed by a mechanism-design section and drafted clauses
• Length: 1,000-1,400 words plus supporting tables
• Format: Structured document with narrative reasoning, at least two tables (period-by-period WC/CCC metrics; peg sensitivity), and a bulleted true-up clause list
• Sections: WC Definition & Reconciliation → Cash Conversion Cycle Metrics → Seasonality Analysis → Normalization Adjustments → Recommended Peg & Range → Sensitivity → True-Up Mechanism → Sample Clauses
• Tone: M&A financial advisor — precise, evidence-first, negotiation-aware; every number tied to a defensible rationale

Quality Checklist

Before delivering output, verify:

• [ ] Every WC line item is explicitly classified as included or excluded, with disputed items flagged
• [ ] DSO, DIO, DPO, and cash conversion cycle are computed for each period and trended, not just averaged
• [ ] A specific averaging method is chosen and justified against the deal's seasonality and close date
• [ ] Each normalization adjustment shows an amount and a documented rationale
• [ ] The peg is presented as a range with a purchase-price sensitivity table, not a single unexplained number
• [ ] The true-up section specifies a collar, a measurement-consistency clause, a review timeline, and dispute resolution
• [ ] At least 3 drafted true-up clauses are provided

Notes

• The single most common dispute source is inconsistent accounting policies between the peg and the closing statement — the consistency clause matters more than the peg itself
• Watch for pre-close working capital "dressing": accelerated collections, delayed vendor payments, and inventory drawdowns that make the closing balance look artificially lean
• Deferred revenue treatment can swing the peg materially and is almost always negotiated separately — surface it explicitly rather than folding it silently into the base
• For high-growth targets, a trailing average understates the peg because WC scales with revenue; consider a revenue-weighted or forward-adjusted approach and state the assumption

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

• ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
• <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

1. Drag this file into a new chat, or copy and paste its contents
2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills