Covenant Intelligence / Data product
Covenant Intelligence: From reviewed research to portfolio-level decisions
A client-facing product for screening agreements, comparing protections, inspecting deals, benchmarking portfolios, and tracing claims to published covenant data.
MVP direction described in the brief; final release status awaits confirmation.
The problem
A library of reviewed reports is not yet a consistent analytical product. Version selection, tranche semantics, missing values, coverage, and permissions must line up.
My responsibility
- — MVP strategy and six-week scope
- — PC Deals screener and comparison
- — Portfolio Benchmark methodology and data disclosures
- — Shared request lifecycle
- — Evidence and entitlement requirements
What we’re connecting
- 1Reviewed reports
- 2Structured facts
- 3Search and comparison
- 4Portfolio context
- 5Decision support
Sanitized representative artifact
Decisions, alternatives, and trade-offs
01 / Strategy
Cut surface area, not coherence
Broad intelligence product, reduced to three two-week sprints.
PC Deals, comparison, Portfolio Benchmark, and Shared Requests.
02 / Data model
One deal, one current view, history underneath
One deal can contain term sheets, preliminary reports, final agreements, and amendments.
Use the latest published report and representative benchmark tranche.
03 / Data model
Do not aggregate tranches when semantics are undefined
Tranches have different covenant semantics.
Show the representative benchmark tranche and its actual name.
07 / AI & trust
Private data boundaries belong in the architecture
Private agreements are client-owned; global AI search can cross boundaries.
Client-scoped sources and anonymized market aggregates.
08 / Data model
Missing is not No
Missing values can silently become negative observations.
10 Yes / (10 Yes + 5 No) = 66.7%; exclude 5 Missing.
14 / Strategy
Prototype to create disagreement while it is cheap
Words hide disagreement about navigation, data density, and semantics.
V1 broad concept → V10 dashboard/screener/benchmark/requests → V14 narrower loop → V15 sharper screening.
Market context with explicit coverage
Sanitized representative artifact · Illustrative data
Amendment — latest published report; powers the current-state screener.
Sanitized representative artifact · Illustrative data
6.50x · anonymized median
No borrower, sponsor, source document, or private deal detail is exposed.
What I learned / what comes next
- Reduce surface area without breaking the customer loop.
- Market context is only meaningful with explicit denominators and exclusions.
Validate launch semantics before adding sponsor intelligence, historical analytics, or broad AI retrieval.
Examples are recreated or sanitized to protect confidential company, client, and legal information. They preserve the product problem, decision logic, and working method without reproducing proprietary content.
Inspect product artifacts