THE KIRKWOODCONSORTIUM Put KC on a workstream

Public proof portfolio

Development analysis
built for scrutiny.

These samples show the underwriting discipline John Kirkwood Jr. brings to a deal as an emerging developer — assumptions structured before conclusions, evidence separated from projections, and open conditions named before capital is called.

Inspect both samples Propose a workstream
The Kirkwood Consortium capital stack and funding readiness workbook preview

Work sample 01 · Capital formation

Capital Stack & Funding Readiness

A five-scenario feasibility model that distinguishes planning capacity, program availability, evidence-supported sources, and commitments—then keeps the remaining gap visible.

$15.175MTDC $3.389MDebt cap $4.427MBaseline gap $0Evidence / committed
  • Sources & Uses reconciliation
  • Source-readiness and evidence controls
  • Five capital cases with explicit gap outcomes
Open analysis Excel model
The Kirkwood Consortium 15-year OHFA cash flow and DSCR workbook preview

Work sample 02 · Operating underwriting

15-Year OHFA Cash Flow & DSCR

A hard-debt coverage schedule that separates mechanical DDF capacity from a proven payment waterfall and preserves the Year-16 post-abatement risk.

1.34xYear 1 1.38x15-year avg. Year 11Mechanical DDF 0.43xYear-16 cliff
  • Formula-linked OHFA-style controls
  • Hard-debt coverage and DDF capacity screen
  • Post-abatement stress test
Open analysis Excel model
Inspect Start with the governing question and decision.
Interrogate Trace assumptions, formulas, source status, and open evidence.
Place Apply the method to one bounded workstream on a live transaction.

From proof to participation

Analytical discipline that earns a seat in a live deal.

KC is an emerging developer seeking embedded co-development responsibility on an active affordable-housing or multifamily transaction. The ask is direct: a defined development responsibility, a named project milestone, and an experienced sponsor-side reviewer. KC enters where it can own a bounded portion of execution and demonstrate performance before seeking deeper participation.

A named project or transaction Access to current deal documents and assumptions A bounded execution responsibility with a named milestone Sponsor-side review by the accountable team member Discuss a live deal role
Evidence boundary

Emerging developer disclosure: These are independent, sanitized predevelopment work samples. No completed transaction, controlled site, committed financing, or closed client engagement is represented. These samples demonstrate underwriting methodology and development discipline — not transaction history.