Ask Kilby.
2021–Early 2022: Peak. Software median EV/Revenue peaked at 6.7× on abundant liquidity and ultra-low rates. EV/EBITDA for software peaked at 39.9× in H2 2022. PE buyers paid an average 11.7× that year; strategics paid 8.5×.
Late 2022–2023: Sharp Compression. As rates rose, multiples fell below 3× EV/Revenue and 15–18× EV/EBITDA. Roughly one-third of private-target deals in 2023 included earnout provisions — up from 21% in 2022 — a clear sign buyers and sellers couldn't agree on price.
2023–2024: Stabilization. EV/Revenue settled around 2.6×; EV/EBITDA anchored at 17–22× for software. 59% of advisors reported flat purchase multiples year-over-year. FinTech averaged 10.1× EV/EBITDA in 2024.
2025: Early Recovery, PE Driving It. Global median EV/EBITDA stands at 9.3× as of mid-2025. PE buyers reached 12.8× in the US vs. 9.9× for corporate acquirers. Software EV/Revenue ticked up to 3.1× in H2 2025. Deal values rose 36% while volumes rose just 1% — concentrated in megadeals, which climbed from 63 in 2024 to 111 in 2025.
Bottom line: About 60–70% recovered from the 2022 peak. The recovery is K-shaped — megadeals and PE-backed transactions are driving multiple expansion while mid-market remains subdued. Recurring, visible revenue is the single biggest multiple driver right now.
Start with the professional lens.
This is Kilby's core differentiator. Choose from 17 professional experience lenses across Financial Services Operations, Capital Markets, and Technology & Business, and Kilby will reason through that domain-specific context instead of defaulting to generic AI output.
Then choose how Kilby shows up.
Pair that experience with differentiated personalities like Strategist, Operator, Confidant, Socratic, or Performer, then choose custom voices, accents, and delivery styles so the same judgment can arrive sharper, warmer, more probing, more direct, or more personal based on how you work.
Use a voice that fits the role.
Kilby supports user-selected voices, accents, delivery styles, voice input, and spoken responses so the agent can sound like part of your workflow instead of a generic text-to-speech layer.
Keep the same working context alive.
Return to the exact thread, context, and attachments you were already working through instead of restarting the job every time.
Kilby remembers you.
Kilby retains facts across sessions — your role, portfolio context, preferences, and working history — so every conversation picks up where the last one left off instead of starting from zero.
Kilby works while you sleep.
Set price alerts that auto-clear when triggered, schedule recurring Python analysis, or ask Kilby to monitor a metric and report back. Results arrive in your thread — no polling required.
Operate across your real tools.
Kilby currently integrates with Google Workspace and related applications. Over time, Kilby will make additional horizontal as well as vertical application integrations.
Work directly in your files.
Run the kilby binary on your machine to give Kilby full access to local files, folders, spreadsheets, PDFs, and Python execution — no upload required.
curl -fsSL https://agentkilby.com/install.sh | bash
curl -fsSL https://agentkilby.com/install.sh | bash
powershell -ExecutionPolicy Bypass -Command "irm https://agentkilby.com/install.ps1 | iex"
cd into any folder, and run kilby. Your browser opens once to approve — after that it's just kilby.Front office to back office.
AM04 is "insufficient funds" — the counterparty's account didn't have enough cash to cover the delivery. That's a liquidity or funding problem on their side, or possibly a booking/allocation mismatch causing the wrong account to be debited.
AC04 is "closed account" — the cash leg is hitting an account that no longer exists. That's an SSI problem. Either your standing settlement instructions are stale, or the counterparty's bank account changed and your records weren't updated.
The AC04 is actually the more urgent fix — a payment routing to a closed account won't settle regardless of how much liquidity exists. You need to get correct cash settlement instructions from the counterparty or their custodian before anything else moves.
On the Reg T Extension:
For a DTC fail on a US equity where you're unable to make delivery due to the settlement break, the applicable reason codes depend on what's actually blocking you:
The most direct fit here is Reason Code 15 (COD-Fail 35 days) — but only if you're at or past the 35th calendar day from trade date. That gives you up to 14 calendar days, does not count toward the 5-extension limit, and is marked final on the transaction.
If you're before T+35, then look at Reason Code 21 (Exceptional Circumstance) — because a failed DTC delivery driven by an SSI/account defect (AC04) and counterparty funding failure (AM04) isn't cleanly covered by the standard codes. Code 21 gives you up to 14 calendar days, does not count toward the 5-extension limit, and is not final, meaning you can come back again if needed. However, it should only be used when no other code squarely fits.
If the root cause resolves to securities not yet received on your side (a fail-to-receive feeding a fail-to-deliver), Reason Code 5 is worth considering — but that's a 7-calendar-day, final extension that does count toward the 5-extension limit, so use it only if it's genuinely the right characterization.
My recommendation: Fix the AC04 SSI problem first — that's your actual blocker. Get updated cash settlement instructions confirmed in writing from the counterparty, correct your SSI record, and retry the cash leg. Meanwhile, file the Reg T extension to protect yourself on the regulatory clock. If you're pre-T+35, Code 21 gives you the most flexibility. If you've crossed T+35, Code 15 is your vehicle.
What's the trade date? That'll let me confirm which code is actually in scope for you right now.
No subscription. Pay as you go.
| Model | Input / 1M tokens | Output / 1M tokens |
|---|---|---|
| Claude Haiku 4.5 · Fastest | $1.00 | $5.00 |
| Claude Sonnet 4.6 · Recommended | $3.75 | $18.75 |
| Claude Opus 4.6 · Most Powerful | $18.75 | $93.75 |