Underwrite · PCT-003 · Published note
Who else holds this borrower
A deal team pricing a new loan to a sponsor-backed software company wants to know which BDCs already lend to it and at what marks.
Today vs automated
- Open 10+ 10-QsAssociate · manual
- Ctrl-F the borrower nameAssociate · manual
- Paste marks into ExcelVP / counsel · manual, re-keying
- Email / meeting hand-offAssociate → VP / counsel
- A new deal enters the pipelineTrigger: starts on its own
- Match names across filingsAutomated · Document parser
- List holders and marksAutomated · LLM
- Flag mark gapsAI draft, human review · Model template
- Issuer names are not standardizedApprove / override · VP / counsel
AutomatedAI draft, human reviewHuman onlyTools: Data room, Document parser, LLM, Model template
Verified example
- Lender / BDC
- Borrower
- Filing
Before: scattered rows
| Where it sits | Row text (as filed) | FV ÷ cost |
|---|---|---|
| ARCC 10-Q, Schedule of Investments | Hyland Software, Inc. | First lien senior secured loan | 100.8% |
| OBDC 10-Q, Schedule of Investments | Hyland Software, Inc | First lien senior secured loan | Non-Affiliated | 97.0% |
| GBDC 10-Q, Schedule of Investments | Hyland Software, Inc. | One stop 1 | Non-Affiliated Issuer | 96.3% |
Three filings, name strings that don’t match exactly, two different tranche labels. Nothing in the rows says they are the same company.
Question the graph answers
Which lenders share this borrower, and who marks it lowest?
One hop from Hyland Software: ARCC, OBDC and GBDC. Lowest mark: GBDC at 96.3% of cost. Two hops: the filing behind each mark.
Estimated valueestimate
70–1,160 analyst hours a year
$10k–$290k of time, vs an assumed $20k–$100k tool cost
Net: −$90k to $270k a year net of tool cost; at the low end of the assumptions it does not cover the tool cost.
Assumptions
- 1–3 analyst hours per lookup today; 0.1–0.3 hours with an agent, including review
- 100–400 lookups a year for one team
- $150–250 per hour loaded cost
- Tool or build cost $20,000–100,000 a year (both)
Estimate, based on the assumptions shown; your numbers will differ. How we estimate
What else it can do for the team
- Find co-lenders before an amendment call
- Check your mark against peers each quarter
- Spot crowded names across managers
- Support the valuation committee pack
- Track position size changes by holder
How you get thereFour steps from prompting to an agentic workflow; most teams start at step 4.
Needs: an approved AI tool, a confidentiality policy.
Risk: unchecked answers, data pasted outside policy.
Needs: field definitions, a template, document parsing.
Risk: breaks silently when formats change.
Needs: inbox/doc-store access, system write-back, logging.
Risk: acting on a misread; needs review gates.
The automated lane above
Needs: shared data model, permissions, audit trail, exception queue.
Risk: errors compound across steps; needs monitoring.
Typical starting point
Solution optionsBuy (3 vendors listed), build or hybrid, with the trade-offs of each.
Octus, The LoanEdge, Canoe Intelligence
Fastest start; you adapt to the product's data model and pricing.
An LLM API, a document parser, a vector or document store, your data warehouse, and a review queue.
Fits your definitions exactly; you own maintenance and controls.
Vendor extraction feeding your own checks, templates and systems.
Common middle path; two things to integrate and govern.
Listing is not endorsement.
What changes for the team1–3 h → 0.1–0.3 h per lookup (estimate); coverage goes from the sections someone had time to read to every clause and schedule checked against the term sheet.
How it works
Full title: Same loan, different marks: who else holds your borrower, how they value it, and who might sell
“Same loan, several lenders, different marks. Every number links to the 10-Q.”
This card now includes former PCT-015 (Find the forced sellers: which lenders hold a stressed name, and at what mark?).
Scenario
Public: a deal team pricing a new loan to a sponsor-backed software company wants to know which BDCs already lend to it and at what marks.
What the human still decides
Issuer names are not standardized. Treat every match as a possible match and confirm the entity and tranche in each filing before quoting it.
Why it matters
The SEC staff statement asks valuation teams to calibrate to available market information. Other BDCs' marks on the same loan are public evidence your valuation committee will be asked about.
Before and after
Before
- Search several 10-Qs by hand for the borrower name
- Reconcile different legal-entity names
- Copy cost and fair value into a comparison sheet, or pay for a BDC research tool
After (agent first draft)
- Agent normalizes issuer names across all SOI rows for a quarter
- Returns every BDC holding a matching name with tranche, cost, fair value and FV/cost
- Highlights where marks on the same name differ
Agent pattern: normalize names → join across filers → compare marks → label matches 'possible'
Tools
- SEC BDC SOI data set
- Fuzzy-match script
- Static JSON on this site
Try it: prompt and data
Across all SOI rows for quarter {q}, find holdings whose issuer name matches '{name}' (show match confidence), and table BDC, tranche, cost, fair value, FV/cost. Highlight where marks differ by >5 points.Data
Public data. Issuer-name matching is approximate; different tranches and entities can share a name.
Who uses it, vendors and build
- Segments
- BDCs, Direct lending, Research & ratings
- Who uses it
- Deal team (pricing a new deal), Credit analyst, LP / credit research
- Build
- Vendor + in-house
- In-house
- This site's SOI pipeline + fuzzy name matching. Estimate: 1 week.
- Last verified
- 2026-10-15
Vendors that claim this capability
- The LoanEdge: cross-holder-overlap, fair-value-benchmarking
- Octus: private-credit-comps
- Canoe Intelligence: cross-holder-overlap
Tags reflect each vendor's own public claims at the linked page (checked 2026-10-15). Not tested, ranked or endorsed.
Sources and related
Next step
Related use cases
Get new walk-throughs
Not investment advice. Names marked SAMPLE are fictional. Found an error? See the corrections log.