Backed by Y CombinatorThree documents and three sheets that close every support request on a recorded outcome, not on the introduction or the candidate slate being sent.
Free download · No account needed
What you get
Pack of 6 files: 3 documents, 3 spreadsheets
VC Portfolio Company Support TemplateSupport Delivered Log
Every delivered request gets an outcome status before it counts as closed, not before the action happens.
| Company | Category | Outcome Status | Outcome |
|---|---|---|---|
| — | — | — | — |
| — | — | Unknown | — |
Delivered and outcome unknown are not the same state as declined. The action happened. Nobody has checked back since.
Kestrel Ventures logged twenty-four support requests from its twelve portfolio companies in the first quarter of 2026: enterprise BD introductions, engineering hiring help, follow-on introductions, PR and launch support, and technical advisory. Eighteen were delivered, four declined, two still open. Split the eighteen delivered requests by outcome and the number that matters drops again: eleven have a recorded result, a signed contract, a hire, a term sheet. The other seven are introductions made and candidate slates sent, with no update logged since either happened.
Hiring support shows the widest gap of the five categories: five requests delivered, one with a recorded outcome. Enterprise BD and follow-on introductions look almost as strong as technical advisory and PR on delivery alone, six and two delivered, but fall once an outcome is required too. An introduction depends on a third party's own hiring or fundraising timeline. A technical review or a placed story usually resolves inside one conversation. A portfolio-wide "value-add" number that folds all five categories together, the way most funds report it beside the quarterly cash position, buries that difference.
Limited partners already ask for the evidence this log produces. ILPA's Due Diligence Questionnaire asks a GP directly to provide case studies illustrating the firm's value creation capabilities, a request a register with no outcome column cannot answer. A survey of venture capitalists found seventy-two per cent report helping companies connect with future investors, and sixty-nine per cent report customer introductions. The survey measures what a VC says it does, not what got recorded when one specific introduction closed or died.
Request RegisterKestrel Ventures, illustrative, Q1 2026. 10 of 24 rows shown. Every request is logged the day it is raised, including the ones that get declined or are still open.
| Company | Category | Date raised | Status |
|---|---|---|---|
| Oakcastle Health | Enterprise BD intro | 2026-01-12 | Delivered |
| Thornfield Analytics | Hiring support | 2026-01-20 | Delivered |
| Hazelwick Systems | Follow-on intro | 2026-01-22 | Delivered |
| Stonebridge Freight | Technical advisory | 2026-01-28 | Delivered |
| Corvid Analytics | Enterprise BD intro | 2026-02-05 | Delivered |
| Fenrose Systems | Hiring support | 2026-02-14 | Delivered |
| Elsmere Health | Enterprise BD intro | 2026-03-13 | Declined |
| Gantry Logistics | PR / launch support | 2026-03-16 | Declined |
| Fenrose Systems | Enterprise BD intro | 2026-03-24 | Open |
| Corvid Analytics | Follow-on intro | 2026-03-27 | Open |
24 requests, 18 delivered, 4 declined, 2 still open at the end of the quarter. Declined always carries a stated reason, not a general "unable to help."
Support Delivered LogThe 18 delivered requests from the register above. 10 of 18 rows shown. Outcome Status is Recorded or Unknown, never left blank.
| Company | Category | Outcome status | Outcome |
|---|---|---|---|
| Oakcastle Health | Enterprise BD intro | Recorded | Signed, $185,000 ARR, 6 weeks |
| Millbrook Logistics | Enterprise BD intro | Recorded | Signed, $95,000 ARR, 10 weeks |
| Thornfield Analytics | Hiring support | Recorded | Hired, 9 weeks from first candidate |
| Hazelwick Systems | Follow-on intro | Recorded | Term sheet issued, 14 weeks later |
| Corvid Analytics | Enterprise BD intro | Unknown | Intro made, no update since |
| Duncastle Freight | Enterprise BD intro | Unknown | Intro made, no update since |
| Fenrose Systems | Hiring support | Unknown | 2 candidates sent, no word |
| Gantry Logistics | Hiring support | Unknown | 1 candidate sent, no word |
| Harrowgate Data | Hiring support | Unknown | 3 candidates sent, no word |
| Millbrook Logistics | Hiring support | Unknown | 1 candidate sent, no word |
11 of 18 delivered requests have a recorded outcome. 7 do not. Hiring support is the widest gap: 5 delivered, 1 recorded, and all 4 unrecorded rows are shown above rather than folded into an aggregate rate.
Introduction TrackerThe BD, hiring and follow-on rows from the delivered log, all 13 shown, isolated because "did the introduction work" is usually the first question anyone asks.
| Company | Introduction type | Outcome status |
|---|---|---|
| Oakcastle Health | Enterprise BD intro | Recorded |
| Millbrook Logistics | Enterprise BD intro | Recorded |
| Bramwell Robotics | Enterprise BD intro | Recorded |
| Corvid Analytics | Enterprise BD intro | Unknown |
| Duncastle Freight | Enterprise BD intro | Unknown |
| Elsmere Health | Enterprise BD intro | Recorded |
| Thornfield Analytics | Hiring support | Recorded |
| Fenrose Systems | Hiring support | Unknown |
| Gantry Logistics | Hiring support | Unknown |
| Harrowgate Data | Hiring support | Unknown |
| Millbrook Logistics | Hiring support | Unknown |
| Hazelwick Systems | Follow-on intro | Recorded |
| Oakcastle Health | Follow-on intro | Recorded |
7 of 13 introductions have a recorded outcome, 53.8 percent, against 80 percent for technical advisory and PR combined. An introduction depends on a third party’s own timeline; a review or a placed story resolves in one conversation.
Support OfferingWhat the fund tells a company on the day it joins, including this period’s real numbers rather than a capability list alone.
Enterprise BD introductions, engineering hiring support, follow-on fundraise introductions, PR and launch support, technical advisory, and international expansion help where the fund has a relationship.
| Category | Delivered | Recorded outcome |
|---|---|---|
| Enterprise BD intro | 6 | 4 |
| Hiring support | 5 | 1 |
| Follow-on intro | 2 | 2 |
| PR / launch support | 2 | 1 |
| Technical advisory | 3 | 3 |
Hiring support’s recorded rate is stated here on purpose. A low rate is a reason to tighten the check-back, not a reason to drop the category from the offering or hide the number.
Every incoming request logged the day it is raised, company, category and status, including declined and still-open ones
The delivered subset, with an Outcome Status of Recorded or Unknown on every row, never left blank
BD, hiring and follow-on introductions isolated from technical and PR support, because an introduction resolves on someone else's timeline
What the fund tells a company on the day it joins, refreshed quarterly with that period's delivered and recorded counts
How a request becomes a logged introduction, who owns the check-back and on what schedule, and what closes an outcome
Per-category playbooks defining what counts as an outcome for BD, hiring, follow-on, PR and technical requests before the quarter starts
Company, category and the date it was raised, the day it comes in. Delivered, declined or open, and a declined request always carries a stated reason.
A delivered request gets an owner and a date to check back, matched to the category's playbook: weeks for a technical review, a full quarter for a follow-on introduction.
Every delivered request closes with an outcome status, never a blank cell. Recorded means a specific result. Unknown means the action happened and nobody has confirmed what it led to since.
Compare the recorded rate for introductions against technical and PR support separately, because a category-wide number is what a single blended rate always hides.
Because delivered only means the action happened, an introduction sent or a candidate slate forwarded. Whether it led anywhere is a separate fact that nobody logs by default. In the worked example eighteen of twenty-four requests are delivered, but only eleven of those eighteen carry a recorded result.
Because they resolve on different clocks. A technical review or a placed story is usually answered in one conversation, which is why both record at a high rate here. A BD or follow-on introduction depends on a third party's own hiring or fundraising timeline, and can sit at Unknown for months without anyone having failed at anything.
Board prep reads one company's pack against its own prior minutes ahead of a single meeting. This tracks a different document entirely, every support request across the whole portfolio, and stays open between meetings rather than resetting each cycle. The board meeting prep pack is the per-company, per-meeting complement to this portfolio-wide log.
It is an input, not the decision. A company whose BD introductions keep converting is a different reserve conversation than one where five hiring requests went out and one came back with a result. Follow-on and reserve analysis is where that gets modelled against ownership and remaining capital.
Yes, that is usually where a recorded outcome gets used. A specific instance, a named company and a checkable result, is what a founder reference can confirm and what a claim with no record cannot survive. Competitive round and allocation checks exactly that claim before it goes in front of a syndicate.
No. The memo carries the thesis and the definitions a position was taken on, at entry. This pack tracks what the fund actually did for the company afterward and whether it worked, which is a different question the investment committee memo was never built to answer.
Word documents for the support offering, the introduction protocol and the playbook set, and CSV for the three sheets. The documents open in Word, Pages and Google Docs. The sheets open in Excel, Numbers and Sheets with the columns intact, and no conversion step in between.
Written by
Co-founder & CEO, River
Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.
Send this quarter's request log, however you track it today. The first pass separates delivered from recorded and flags every request still open.
Log this quarter's support