Most platforms help manage workflow. Capital Refinery helps determine whether the output deserves to move forward.
That means the practical question is not whether Capital Refinery replaces every system around it. It is where it replaces brittle manual work, where it complements neighboring systems, and where it becomes the operating layer for decision discipline.
Replace spreadsheet monitoring. Keep spreadsheet inputs.
Capital Refinery does not replace DealCloud, iLevel, Allvue, your data room, or the QoE workbook your TS firm just delivered. It sits above them as the monitoring and evidence layer.
It does replace the spreadsheet-based monitoring patterns most credit and PE teams have grown out of. Borrower models, covenant trackers, and add-back schedules come in as inputs — reconciled, stress-tested, and converted into a governed monitoring record with covenant pressure detection, breach forecasting, KPI drift, evidence lineage, and decision-ready outputs that survive beyond the model owner.
Excel remains a welcome evidence source. It stops being the system of record.
Replaces, complements, anchors.
Capital Refinery replaces
The brittle repair loop most firms run outside the official stack.
Spreadsheet rebuilds that recreate the same downside, pressure, and memo logic repeatedly. Disconnected post-close tracking where the underwriting story dies after close. Static IC, board, and lender packs rebuilt from memory instead of live context. Threshold-only monitoring that shows movement without clarifying what the numbers justify.
Capital Refinery complements
The rest of the stack stays in place. The decision layer sits above it.
Data rooms such as Datasite and Intralinks. CRM and pipeline systems such as DealCloud and Affinity. Administrative and ownership systems such as Carta and Juniper Square. Portfolio monitoring infrastructure such as iLEVEL, Allvue, Chronograph. Accounting feeds (NetSuite, Sage Intacct, QuickBooks). Reference data providers such as PitchBook and Capital IQ. AI analyst tools that accelerate reading, search, and drafting. Capital Refinery is not trying to replace any of those — it is the layer that determines whether their output deserves to move forward.
Capital Refinery becomes central when
The question on the table is decision-grade, not workflow-grade.
The issue is whether the downside is decision-grade. The team needs continuity from diligence through ownership. Pressure must be tied to evidence, timing, and action path. Output needs to survive committee, board, lender, or intervention scrutiny. Once the question is what to do next — not where the file is — Capital Refinery is the operating surface.
The stack stores, moves, and accelerates. Capital Refinery determines whether the output deserves to move forward.
| Layer | What it does |
|---|---|
| Data rooms, CRM, admin systems, AI analyst tools | Help store files, move workflow, or accelerate work. |
| Capital Refinery | Helps determine whether the output deserves to move forward. |
Most firms do not have a single system to replace. They have a chain of manual repairs.
The repair loop
What actually happens between the official systems today.
Reworking downside cases outside the original workflow. Rebuilding the investment story after close. Comparing pressure in separate spreadsheets and dashboards. Rewriting the same narrative for IC, the board, lenders, and operators. That is the repair loop. It is expensive, it drifts, and it does not leave an inspectable record.
What replaces it
One operating layer, five primitives.
The Decision Ledger preserves the chain from pressure through approval to outcome. The Continuous IC Memo surfaces drift against the IC anchor — what changed since approval, in human-readable language. Risk Signals renders observed values against firm-policy thresholds on every memo, every export, every portfolio rollup. Anchored Exports carry a deterministic fingerprint and (when issued) a public verification URL at /p/<token>. The Decision Timeline preserves every decision-commit anchor per position — original IC, drift evidence, reopen, execution, outcome — inspectable rather than reconstructed.
When buyers start with us
The same five patterns, again and again.
A downside case looked finished but was not. The underwriting story disappeared post-close. Pressure surfaced too late to intervene cleanly. Committee or board material had to be rebuilt from static files. Polished output was being mistaken for trustworthy output. Any one of those is enough — most firms have all five.
The thinking behind this.
- Same engine, five readersOne record. Five readers — operator, banker, buyer, lender, LP. Five evidence levels. The unifying architecture.
- Verified Financial ArtifactsFingerprint + public verification URL + engine-graded refusal discipline. The primitive that makes the artifact portable across counterparties.
- The decision integrity categoryWhy no incumbent occupies the decision layer above the stack — and why the category had to be named.
- The decision integrity gapThe full landscape analysis — 48 sources, 14 vendors, and the missing 7th layer.
- When decisions breakDrift means conditions changed. A broken decision means the approval basis no longer holds.
The buy-side stack above is one application of the engine. The sell-side IRA is another.
The Decision Ledger, Continuous IC Memo, Risk Signals, and Anchored Exports primitives above all serve buy-side investment teams. The same engine grades businesses against the same 10-axis framework on the seller side — producing the Institutional Readiness Assessment artifact that buyers, lenders, and LPs read against their own firm-policy thresholds. Sellers run the $750 Self-Assessment as the operator-attested entry; the formal IRA is the document-verified counterparty-credible artifact. Same engine, both sides of the conversation.
See the same-engine architecture for the unifying framing across all five readers.
Keep your stack. Add the layer that governs it.
If your stack is already paid for, good — you do not have to rip it out. The next question is what sits above it. Bring us a deal. We will show you on real data.