What the engine actually produces — on real cases, and on the patterns that recur.
Two named cases (Cedarbrook Foods Q1 2026 and Falcon Services Q1 2026) anchor the methodology end-to-end on real-shaped data. Four pattern examples — one per active vertical — illustrate sub-lane engine output without claiming customer engagements we haven't earned. Refusal discipline applies to the marketing surface as much as to the engine itself.
How to read this gallery
Capital Refinery distinguishes named cases from pattern examples:
The two-section structure is structural, not editorial — a sophisticated reviewer should be able to tell at a glance which artifacts are real customer engagements (none, currently) versus methodology fixtures versus pattern examples.
Named cases
Methodology fixtures used to validate the engine end-to-end on real-shaped data. Real KPIs, real covenants, real stress runs. Disclosed as fixtures rather than customers.
- corp.distribution · Sell-side IRA walkthroughCedarbrook Foods Q1 2026
A corporate private-credit deal with strong data infrastructure (89.7% provenance coverage, 58 promoted KPIs) and unreconciled financial conflicts that gate the verdict at Not Ready. Six steps of real engine output: initial verdict, conflicts, strengths, consultant playbook, Re-IRA delta in outcome language, and the public verification URL.
Open the walkthrough → - corp.services (buy-side) · Buy-side IC dossier + monitoringFalcon Services Q1 2026
A corporate services deal — closed, financed, monitored quarter over quarter. Real KPIs ($228.4M revenue, 18.6% margin, DSCR 2.95x, FCCR 1.35x, leverage 4.78x, total debt $210.5M). Four canonical entry surfaces: the video walkthrough, the seven-artifact buy-side proof pack (/sample-falcon), the same-day diagnostic sample (/sample-diagnostic), and the IC memo engine deep dive. APPROVE WITH CONDITIONS recommendation with What Must Be True / What Would Change / Likely Pushback triptych and a standalone Decision Record.
Open the walkthrough →
Pattern examples by industry
Fictional but specific. Each pattern example illustrates engine output for a representative business in its sub-lane. Inline-labeled illustrative on each page. The structural-blocker patterns, named-buyer ecosystem, and partner-handoff brief shapes are accurate to the sub-lane; the operator is invented.
- corp.hvac_services · pattern exampleHartwell HVAC (HVAC services pattern)
Regional HVAC platform, $27M revenue across 4 Texas locations. Single service manager owns 35% of revenue relationships. Reviewed-not-audited financials. The engine flags key-person dependency as the gating blocker; remediation horizon 9-12 months of structured handoff. Material multiple compression avoided by remediating before going to market.
Open the sub-lane page → - corp.dentistry · pattern exampleMaple Grove Dental (dental DSO pattern)
5-doctor multi-location dental practice, $12M revenue across 6 offices. Recall completion at 71% vs DSO-acquirer threshold of 85%+. Hygiene mix healthy at 38%. The engine flags recall completion as the leading-indicator gating blocker; remediation horizon 4-6 months of recall-system overhaul. Material multiple preservation when remediated before going to market.
Open the sub-lane page → - re.multifamily · pattern exampleCypress Pointe Apartments (multi-family pattern)
Texas garden-style multifamily portfolio, 4 properties / 1,200 units / ~$180M GAV. Acquired 2021-2022 at peak. Floating-rate debt with rate caps expiring Q2 2026. Interest reserve depletes Q1 2026. The engine flags debt-service runway with time-to-consequence on every named blocker; remediation path is structured lender engagement, not transaction prep.
Open the sub-lane page →
Why the gallery doesn’t have a customer-logo wall
Most early-stage products at this stage would assemble a customer-logo wall and call it the proof gallery. Capital Refinery doesn’t — for two structural reasons. First, customer engagements are protected under the same NDA discipline that makes the buy-side institutional pricing private. Second, the IRA’s portability claim depends on the artifact carrying institutional weight without requiring customer logos to ratify it; a fingerprint and a public verification URL stand alone.
When customer logos earn their place on the page — disclosed with the customer’s permission, alongside the actual artifact they ran — they’ll be added. Until then, the gallery is honest about what it is: a methodology fixture, two pattern examples per industry, and the structural argument that the engine produces credible evidence whether or not marketing has decorated it.
Bring your own deal — that’s the only proof that matters.
The named cases and pattern examples exist so you can inspect the engine before committing. Once you've inspected, the next step is running the engine on a deal you bring us. No demo data.