# The Solo Talent Partner's Monthly Portfolio Hiring Cycle

*You will run a monthly cycle that triages every open portfolio role, picks the few worth sourcing by hand, and turns one search into candidates for several companies.*

- Canonical URL: https://www.refolk.ai/guides/solo-talent-partner-portfolio-cycle
- Pillar: Investing and deal sourcing
- Format: Playbook
- Published: 2026-08-01
- Last reviewed: 2026-08-01
- Reading time: 16 min
- Keywords: how to prioritize hiring across a portfolio, vc talent partner sourcing process, shared talent pool across portfolio companies, one recruiter many startups, portfolio hiring triage

## Key takeaways

- Force-rank roles against two documented triggers: the founder spending more than 50% of a week on a function, and searches that would go retained. Only a few roles should pass.
- The market has already priced difficulty for you: 60% of VP of Engineering placements go retained versus 91% for CTOs, so copy that split to decide what to work personally.
- Warm intros pull 3 to 5x the response of cold outreach and cut hiring timelines by 50 to 70%, so a solo partner's scarce resource is intro-worthy hours, not resumes.
- Funds usually already hold 200 to 500 scattered network contacts, so the first monthly win is consolidation and tagging, not new sourcing.
- In Refolk's index, 4,707 professionals carry the title Talent Partner against 1,391 for Head of Talent, a 3.4x ratio that shows how thin most fund talent benches actually are.
- US talent-lead supply is only about 1.33x the UK's (1,773 versus 1,330 profiles), so the one-person model is structurally similar in both markets.

You are the only talent person at a fund, and a dozen founders each want your hours this month. This guide is for that role: the solo talent partner, platform lead, or angel who owns hiring across ten-plus companies and cannot personally source every open seat. It delivers a repeatable monthly cycle that triages every role, picks the few to work by hand, and turns one search into candidates for several companies at once.

Existing guides walk a single search from brief to shortlist. This one sits above them. The scarce resource here is not candidates and not job boards; it is your own attention. So the whole method is built to protect the few hours that only you can spend, and to make everything else run on a repeatable rail.

## Why "one recruiter, many startups" needs an operating system

The job fails without a cycle because founder demand is unbounded and your week is not. A monthly triage-and-batch loop converts a dozen competing asks into a ranked plan you can actually execute solo.

The staffing reality sets the terms. There is no clean published ratio of roles per talent partner, but the anchors are consistent: a private-equity operating partner commonly manages hiring across roughly 10 portfolio companies, funds with 50-plus companies typically staff only 2 to 4 recruiters, and firms like Hustle Fund run one head of talent across the entire portfolio. Meanwhile human capital consumes around 70% of portfolio company budgets, so the stakes on each seat are real. One person cannot hand-source ten simultaneous searches, and the funds that try to force it end up dropping roles silently.

The bench itself is thin, which is exactly why the operating system matters.

**3.4x - Talent Partner profiles per Head of Talent, in Refolk's index**

4,707 professionals carry "Talent Partner" against 1,391 for "Head of Talent" - most funds run a very small talent function.

That thinness is not a US quirk. In Refolk's index there are 1,773 combined talent-lead profiles in the United States against 1,330 in the United Kingdom, a multiple of only about 1.33x. A UK-based solo talent partner is not an outlier; the one-person model is structurally similar on both sides of the Atlantic.

#### What a solo talent desk actually holds

1. **Hands-on searches** - The few roles you personally source this cycle
2. **The monthly cycle** - Intake, triage, batch, route, track
3. **The shared pool** - 200 to 500 tagged, timestamped network contacts
4. **The fund network** - GPs, founders, and past candidates you can reach warm

*The monthly cycle sits on top of a standing pool, and both feed a small set of hands-on searches.*

## The scarce resource is response, not resumes

Your leverage as a solo partner is your relationships, not your sourcing volume. Triage should therefore protect intro-worthy hours, because that is where the returns compound.

The numbers behind this are the spine of the whole method. Warm introductions generate 3 to 5x higher response rates than cold outreach, and a fund's talent network can cut hiring timelines by 50 to 70%, removing a 3 to 4 week sourcing phase entirely. That is the mechanism: a warm path is worth several cold ones, and only you hold most of those paths. If you spend your scarce hours cold-sourcing roles a founder could fill from a job board, you are burning your rarest asset on your most replaceable task.

> Your relationships are the leverage; sourcing volume is the commodity, so protect intro hours and let advisory scale the rest.

This also tells you what to do with the roles you do not personally source. Advisory scales further than intros because process, comp guidance, and org structure are reusable across companies, while a one-off GP intro serves one seat. A head of talent working structure for eight founders creates more total value than the same person hand-sourcing two roles. That is the reason funds hire the role at all, and it is the reason "advise only" is a real answer, not a demotion.

## The monthly cycle, start to finish

Run the same seven steps every cycle, in order. Intake precedes sourcing, triage precedes effort, and the pool is checked before any cold outreach. This is the procedure a solo partner can execute without a team.

#### The monthly portfolio hiring cycle

1. **Collect open roles** - Send a standard priority form to every portfolio company at cycle start. Done when each company has submitted role, seniority, must-haves, comp band, and urgency. Budget 3 to 5 days.
2. **Triage and score roles** - Rank every role on criticality, founder bandwidth over 50% of the week, and search difficulty. Done when you have a ranked list splitting source-hands-on from advise-only. Budget half a day.
3. **Assign effort** - Pick the few to source personally; route the rest to advisory with a named owner. Done when every role is tagged source or advise. Budget one hour.
4. **Batch the search** - Group roles that share must-have skills and an overlapping seniority band. Done when one shortlist is tagged to multiple companies. Budget 1 to 2 weeks per batch.
5. **Match the pool first** - Run every new role against your tagged pool before cold sourcing. Done when matches are surfaced and availability re-confirmed. Budget hours.
6. **Route via warm intros with consent** - Introduce using the current-warm-path owner rule; get candidate opt-in before any name reaches a founder. Done when no duplicate intros exist and every candidate has consented.
7. **Track and refresh** - Status-track every active role and intro, then feed hires back into the pool with updated, timestamped tags. Done when you have an open-versus-filled dashboard. Budget a weekly touch.

There is a real order disagreement in the field worth knowing. One school leads with a finance-plus-people kickoff meeting before any role scoring, where the finance leader and the talent leader align on headcount goals tied to value-creation initiatives. Another leads with consolidating and cleaning the existing pool first. Both agree on the one rule that matters: intake precedes sourcing. Pick the front end that fits your fund, but never source before you have collected.

> **Rule:** Intake before sourcing, always
>
> Never open a search off a hallway conversation. Every role enters the cycle through the same priority form so triage compares like with like and no company gets sourced ahead of the queue by being loud.

## Triage: which roles you personally source

Force-rank every role against two documented triggers, and expect only a few to pass. Criticality plus founder bandwidth decide whether a role deserves your hours; search difficulty tells you how hard the market thinks it is.

Founder bandwidth is the clearest signal. If a founder is spending more than 50% of their week on a single function, that is the documented sign a senior hire is needed and that the search is worth your personal effort. It is measurable, it is hard for a founder to inflate honestly, and it maps directly to value at risk.

Search difficulty you can read straight off the market, for free. Retained-search share is a difficulty gauge the industry has already priced. Copy that split to decide what to work personally.

### Retained-share as a difficulty signal

| Placement type | Share going retained | Read |
|---|---|---|
| VP of Engineering | 60% | Hard, but often network-fillable |
| CTO | 91% | Retained-grade; work it yourself |

A search that would normally go retained is a search where your warm paths matter most. A role the market fills through networks is a role a founder can run with your advisory support. Retained fees themselves run roughly 25 to 33% of first-year comp, often staged in thirds - which is a useful gut check on how much a hard hire is worth protecting.

#### The source-versus-advise call

Horizontal axis runs from Network-fillable to Retained-grade. Vertical axis runs from Low founder drag to Founder over 50% on this function.

| Quadrant | What it means |
| --- | --- |
| Advise: post, guide comp, move on | Source, but batch it with siblings |
| Advise closely, stay warm | Source hands-on this cycle |
| Advise: lightweight support | Source, batch aggressively |
| Advise, but pre-warm your network | Source hands-on this cycle |

*Two axes decide where your hours go: how critical the role is, and how hard the search is.*

The output of triage is a ranked list with a hard split: a few roles tagged "source hands-on" and the rest tagged "advise only," each with an owner. If everything lands in "source," your triage is broken - see the failure modes below.

## Batch one search across many companies

Group roles that share a candidate profile so one sourcing pass produces a shortlist for several companies at once. This is where a solo partner buys back the most time: the reusable-pool premise means a candidate who is wrong for one startup may be right for another.

The batching rule is strict, because loose grouping produces a shortlist nobody can use. Require both a shared must-have skill set and an overlapping seniority band before you group two roles. "Two startups want a backend engineer" is not a batch if one is a first hire and the other is a director. When the profile genuinely overlaps, one pass of sourcing tags the same candidates to every matching company, and you route from there.

Before you cold-source anything, match against the pool. Funds typically already hold 200 to 500 network members scattered across systems, so the first monthly win is consolidation and tagging, not new outreach. Organize the pool on a documented schema so matching is mechanical.

### Pool schema that survives reuse

| Field group | Example values | What it lets you do |
|---|---|---|
| Functional expertise | Engineering, sales, marketing | Match a role to a function fast |
| Experience level | IC, manager, executive | Enforce the seniority band before batching |
| Role preferences | Company stage, geographic flexibility | Route only to companies a candidate would actually join |

Insight Partners' network, for example, auto-recommends candidates to relevant companies based on preferences chosen at sign-up. That is the pattern to aim for: preferences captured once, reused across every company, refreshed each cycle. Tools that hold this vary - Getro for the network layer, TeamOhana, ChartHop, or Anaplan for headcount planning - but the schema matters more than the tool.

The hardest part is finding the right overlapping profiles across a dozen roles without doing a dozen separate searches. That is exactly the friction a plain-English people search removes: describe the shared profile once and pull candidates you can tag to every matching company.

I ran this search: `VP of Engineering candidates open to Series A startups who have scaled teams from 10 to 50 engineers.` - [see the full result list](https://www.refolk.ai/s/9mjvph05zf).

*Returns a batchable shortlist of engineering leaders you can tag to every portfolio company hiring at that stage, so one search feeds several companies.*

When a batch is done, you have a shared shortlist tagged to multiple companies, matched against the pool first, ready to route. [Refolk](/) is where I run that first pass in plain English rather than rebuilding a boolean string per company.

## Route with ownership and consent

Intros collide because two people both believe they may act on the same candidate, not because of bad luck. Assign a single current-warm-path owner per candidate and the collision disappears mechanically.

The ownership rule is precise: the owner is not the most senior person, it is the person whose warm path you are using right now. Log every active intro so no two companies get introduced to the same candidate in the same week. A collision reads to the candidate as either spraying the network or running a disorganized house, and both cost you future response.

Consent is the second guardrail and it is non-negotiable. Decide who a candidate fits, then ask before making any introduction, so they opt in to a specific intro before their name reaches a founder's inbox. The failure this prevents is expensive: the worst thing you can do is push too many low-quality intros, because people stop taking your calls. Your response rate is your whole leverage; consent protects it.

#### The consent-first routing rail

1. **Match** - Decide which company or companies the candidate fits
2. **Assign owner** - Name the single current-warm-path owner for this intro
3. **Ask** - Get the candidate's opt-in to this specific intro
4. **Introduce** - Only now does the name reach the founder's inbox
5. **Log** - Record the active intro so no collision follows

*A candidate is matched, then asked, then named - never named before they opt in.*

> **Watch out:** The advisory hiding place
>
> "Advise only" quietly becomes "ignored," and a role gets zero touches all cycle. Every advised role still gets a job posting, comp guidance, and a status line. If it received nothing, it was dropped, not advised.

## How this goes wrong

The cycle has seven predictable failure modes, and catching them is more valuable than the happy path. Each has a false positive that looks like success and a specific check that exposes it.

| Failure mode | What it looks like | The check |
|---|---|---|
| Triage inflation | 10 "urgent" roles, no source/advise split | Force-rank against the 50%-founder-time and retained-grade tests; only a few pass |
| Batch that isn't comparable | A shortlist no company can use | Require shared must-have skills AND overlapping seniority before grouping |
| Pool decay | A confident match that is wrong | Timestamp every profile; re-confirm availability before any intro |
| Intro collision | Two companies meet one candidate the same week | Enforce single-owner-per-warm-path; log every active intro |
| Consent skipped | A name reaches a founder before opt-in | Opt-in gate before any name is shared |
| Advising as a hiding place | An "advised" role got zero touches | Every advised role gets a posting, comp guidance, and a status line |
| Speed theater | Chasing a 29-day headline on an exec hire | Judge exec searches on retention, not calendar |

Two of these deserve extra weight. **Triage inflation** is the most common: every founder marks their role critical, so nothing is deprioritized and you are back to hand-sourcing ten searches. The fix is the force-rank - the 50%-founder-time trigger and the retained-grade test are deliberately hard to pass, and if most roles clear them, your bar is too low.

**Speed theater** is the subtlest. The public benchmarks tempt you to chase the fastest number on every role, but executive and non-executive searches are not the same game.

### Time-to-fill benchmarks, and why the fast number lies on exec roles

| Benchmark | Days |
|---|---|
| VP of Engineering industry norm | 90 to 120 |
| Korn Ferry / SHRM executive average | 85 to 100 |
| SHRM executive average, all functions | 62 |
| Warm-network specialist average | 29 |

A leadership hire is not where you shave a week. Better ten extra days than a hire that falls apart by month four. The 29-day figure is real for warm-network specialists on the right role, but pinning it to a CTO search is how you ship a fast mistake. For context, SHRM puts non-executive time-to-fill near 52 days against 62 for executive roles - the gap is the point, and it widens for scarce, retained-grade seats.

> **Tip:** Re-confirm before you introduce
>
> Pool decay is silent. A "senior backend, SF" tag from last year reads as a live match. One message re-confirming availability and preferences before an intro prevents the most embarrassing false positive in the whole cycle.

## Close the cycle and keep it current

The cycle only compounds if hires flow back into the pool and the next month starts cleaner than the last. Track every role and intro to status, then refresh tags so today's work is next month's head start.

Run this checklist before you call a cycle done. It is the difference between a triage you ran once and an operating system you can run every month without dropping a role.

#### End-of-cycle check

- [ ] Every portfolio company submitted the priority form this cycle
- [ ] The ranked list has a hard source/advise split, and only a few roles are "source"
- [ ] Every batched shortlist shares must-have skills and an overlapping seniority band
- [ ] Every new role was matched against the pool before any cold sourcing
- [ ] Every candidate named to a founder opted in to that specific intro
- [ ] Every active intro has a single logged current-warm-path owner
- [ ] Every "advise only" role has a posting, comp guidance, and a status line
- [ ] Every hire and every stale match has been re-tagged and timestamped in the pool

Keep the whole thing current with a light standing intake. The priority form template below is the one artifact that makes the cycle repeatable; send it at the start of every cycle and you never have to reconstruct the state of the portfolio from memory.

**Portfolio role priority form**

```
Company:
Role title:
Seniority (IC / manager / executive):
Function (engineering / sales / marketing / other):
Top 3 must-have skills:
Comp band:
Urgency (backfill / growth / first-of-function):
Founder time on this function today (% of week):
Would this normally go to retained search? (yes / no)
Geographic constraints or flexibility:
```

*Send to every founder or hiring manager at cycle start. One row per open role. Keep it to these fields so triage stays comparable.*

For the roles you triage as advise-only, a short standing note keeps them from becoming the hiding place. Reuse the same three touches every cycle so advisory is a service, not a shrug.

**Advise-only role touch log**

```
Posting: link + date posted / refreshed
Comp guidance: band shared + benchmark source + date
Status line: open / interviewing / offer / filled + one-line update
```

*Log these three touches per advised role each cycle. If any line is blank, the role was dropped, not advised.*

Two habits keep the operating system honest over time. First, re-run the retained-share test each cycle rather than trusting last month's tags - which roles the market treats as hard shifts as titles and stages change, so re-check the split rather than assume a fixed value. Second, consolidate the pool before you source, every time, because scattered contacts are the default state a solo partner drifts back into. Do those two things and the cycle described here runs on rails: a dozen companies covered, a few sourced by hand, and nothing quietly dropped.

## Frequently asked questions

### How many portfolio roles can one talent partner realistically cover?

No clean public ratio exists. The anchors: a PE operating partner commonly manages hiring across roughly 10 portfolio companies, funds with 50-plus companies typically staff 2 to 4 recruiters, and firms like Hustle Fund run one head of talent across the whole portfolio. Practically, a solo partner sources a handful of roles hands-on and advises the rest. The split is undocumented publicly, so set it by your own intro-hours, not a headcount target.

### How do I decide which roles to source myself versus advise on?

Use three documented triggers. Score criticality (first-of-function or executive), founder bandwidth (the founder spending more than 50% of a week on that function signals a VP is needed), and search difficulty. For difficulty, copy the market's retained split: 60% of VP of Engineering placements go retained versus 91% for CTOs, so CTO-grade searches are the ones worth your personal hours. Only a few roles should clear all three.

### What is a shared talent pool and how do I tag it?

It is one indexed set of network contacts reusable across every company, because a candidate wrong for one startup may fit another. Tag on functional expertise (engineering, sales, marketing), experience level (IC, manager, executive), and role preferences including company stage and geographic flexibility. Timestamp every profile so a stale match is visible. Funds usually already hold 200 to 500 scattered contacts, so consolidation comes before new sourcing.

### What happens when one candidate fits two portfolio companies?

Resolve it with ownership, not seniority. The owner is not the most senior person; it is whoever's warm path you are using right now. Assign a single current-warm-path owner per candidate and log every active intro so two companies never get introduced the same week. Then apply consent-first routing: decide who the candidate fits, ask them, and get opt-in to that specific intro before their name reaches any founder's inbox.

### How fast should a portfolio executive search actually close?

Slower than the headlines suggest. VP of Engineering industry-norm time-to-fill is 90 to 120 days, SHRM puts executive roles near 62 days, and warm-network specialists report 29-day averages. Chasing the 29-day number on a leadership hire is speed theater. A leadership hire is not where you shave a week; better ten extra days than a hire that falls apart by month four. Judge exec searches on retention, not calendar.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/solo-talent-partner-portfolio-cycle*