# The Founder Commitment Read: All-In, Hedging, or Not Yet

*You will be able to score a founder's commitment across public signals and return a defensible verdict of All-In, Hedging, or Not Yet Committed.*

- Canonical URL: https://www.refolk.ai/guides/founder-commitment-read
- Pillar: Investing and deal sourcing
- Format: Framework
- Published: 2026-10-10
- Last reviewed: 2026-10-10
- Reading time: 16 min
- Keywords: is the founder full time, check if founder left their job, founder commitment due diligence, founder divided attention red flags, verify founder full time commitment

## Key takeaways

- A blank LinkedIn end date is not proof of a concurrent role - people blank it deliberately to stay visible in recruiter searches for a former employer, which systematically over-flags committed founders.
- GitHub silence is high-noise and low-signal: UTC rollover, fork and branch exclusion, a rolling 12-month window, and the private toggle all suppress a genuinely active founder's graph, so contribution timing can only corroborate, never decide.
- The absence of founder vesting is the cheapest high-value flag, because a co-founder who leaves at month six without a repurchase right keeps a full stake and dilutes everyone who stays.
- Dual-commitment is almost never self-declared: only 788 US profiles carry an explicit Founder & Advisor title against 724,534 founders in Refolk's index, so hedging must be inferred from separate overlapping entities.
- The defensible output of a commitment read is a dated transition trigger - a salaried full-time start or a signed resignation written into the memo - not a binary verdict at the table.

Every diligence checklist tells you to ask whether a founder is full-time. Almost none shows you how to answer it yourself, from public data, rather than taking the answer you were given across a table. This guide is for early-stage investors, platform and talent partners, and angels who need to grade a founder's commitment the same way twice. It turns the gut-check into a scored read built from employment end dates, concurrent role listings, contribution timing, and cap-table proxies, and it ends with a defensible verdict: All-In, Hedging, or Not Yet Committed.

The read is worth running because the signals that look most obvious are the ones that lie most often. A blank end date looks like proof someone is still employed; it usually is not. A quiet GitHub graph looks like disengagement; it usually is not. The job here is to know which signal proves what, and what it looks like when it misleads.

## What the commitment read actually decides

The commitment read answers one question before a term sheet: has this founder gone all-in, or are they still hedging, and can you prove it from public signals rather than a meeting. It is a repeated judgement call, so it needs a fixed set of dimensions and a fixed scale, or two partners will grade two founders differently.

The read is not a character assessment and it is not a prediction of success. It is narrower and more useful than that: a structured answer to "is the founder full time" that you can defend in an investment memo. The output is a verdict plus the specific evidence behind each dimension, and for anything short of All-In, a dated condition that converts a soft answer into a hard one.

It fits inside your existing diligence window. Full institutional diligence runs long - a study of 700 venture capital firms found a typical deal once took 83 days, with 118 hours of diligence and 10 reference calls. At the angel and seed stage the process is lighter and conveyed mostly in conversation. The commitment read is a few hours of structured work that slots into either.

**83 days - How long a typical VC deal once took to complete**

With 118 hours of diligence and 10 reference calls on an average deal, per a study of 700 firms. The commitment read is a few hours inside that.

## The five dimensions and what each one proves

Score commitment across five dimensions. Each one proves something specific, and each one has a known way of lying. Do not weight them equally: employment status and cap-table structure carry the verdict, while concurrent roles qualify it and contribution timing only corroborates.

The five dimensions, in order of weight:

1. **Employment end date.** Proves whether the founder has actually left prior work. Lies when the end date is blank, which reads as still employed but often is not.
2. **Concurrent roles.** Proves whether operating attention is split across entities. Lies when a passive advisory seat is read as a side hustle, or a stale profile is read as a live second job.
3. **Cap-table commitment proxies.** Vesting presence and founder ownership band prove structural commitment and predict future dilution damage. Lies when vesting exists on paper but no 83(b) was filed.
4. **Transition timing.** Proves whether a stated move to full-time has a date and a trigger, or is just an intention.
5. **Contribution timing.** For technical founders, proves rough engagement. The noisiest dimension; corroborates, never decides.

#### The commitment read, outermost signal to innermost proof

1. **Employment end date** - Has the founder left prior work, or is the field blank and unresolved
2. **Concurrent roles** - Operating entities that split attention, versus passive advisory seats
3. **Cap-table proxies** - Vesting present or absent, and founder ownership against stage benchmarks
4. **Transition timing** - A dated trigger for going full-time, versus a vague intention
5. **Contribution timing** - GitHub activity as a corroborating signal only, never deciding

*Weight falls as you move down the stack - end date and cap table carry the verdict, GitHub only corroborates.*

### What proves commitment, and what it looks like when it lies

A signal is only useful if you know its failure mode. The table below is the core of the read: for each public signal, what breaks it.

#### Classifying a concurrent role

Horizontal axis runs from Passive or beneficial role to Active operating role. Vertical axis runs from Low equity or time to High equity or time.

| Quadrant | What it means |
| --- | --- |
| Advisory seat, small stake | Yellow - normal, note it and move on |
| Research or partner role aiding the startup | Yellow - a potential strategic asset, confirm scope |
| Named advisor at scale | Probe - confirm it is not operational |
| Second operating company, full-time elsewhere | Red - the hard flag investors avoid |

*The test is operating versus passive, not present versus absent on the profile.*

## How each public signal misleads

No single public field is reliable on its own. LinkedIn end dates are routinely wrong, overlapping listings are often stale, and GitHub graphs are suppressed by four unrelated mechanics. This is the section to internalise, because the false positives here are what produce wrong verdicts.

| Signal | Failure cause | What it looks like when it lies |
|---|---|---|
| LinkedIn end date | Left blank to stay in recruiter search pools | Blank date shows as "current employee," flagging a committed founder as Hedging |
| Overlapping listings | Outdated or abandoned profiles are common | Two current roles read as divided attention when one is stale |
| GitHub graph gaps | UTC, fork and branch, 12-month window, private toggle | A quiet graph reads as disengagement on a genuinely active founder |

Three facts set the ceiling on how much any public field can prove. First, 92% of LinkedIn profiles carry no verification. Second, LinkedIn's place-of-work verification does nothing by default when an employee leaves, and the platform is not checking revocation status, so even a verified badge can be stale. Third, GitHub contributions are timestamped in UTC rather than local time, so late-night commits shift a day, and the graph shows only a rolling 12-month window, dropping older activity entirely.

> **Watch out:** The blank end date trap
>
> A blank LinkedIn end date carries the opposite signal from what it looks like. People leave it blank so a recruiter typing the old employer's name still sees them as current. Reading blank as "still employed" systematically over-flags committed founders. Mark it unknown and resolve it directly.

GitHub silence deserves the same caution in the other direction. Commits on feature branches or forks do not count until merged into the default branch. Private-repo activity counts only if the user enabled the toggle, and even then GitHub shows only that a contribution was made that day, never the repository name, commit message, or code. Four separate mechanics suppress a genuinely active founder's graph, which is why contribution timing is a corroborating dimension, never a deciding one.

> Read a blank end date as unknown and a quiet GitHub graph as unreadable, not as proof of anything.

## Reading commitment at scale with one query

When you need to find hedging founders across a market rather than grade one in front of you, the inference problem flips: dual-commitment is almost never self-declared. In Refolk's index, only 788 US profiles carry an explicit "Founder & Advisor" or "Founder and Angel Investor" style title, against 724,534 US profiles with a Founder or Co-Founder title. That is about 0.11 percent. Hedging does not show up as one honest label. It shows up as separate overlapping entities, concurrent operating roles, and unresolved end dates.

| Segment | Count | Derived |
|---|---|---|
| US Founder or Co-Founder | 724,534 | baseline |
| UK Founder or Co-Founder | 179,237 | 0.25x of US |
| US founders tagged "stealth" | 9,791 | 1.35% of US |
| US explicit "Founder & Advisor" dual-title | 788 | 0.11% of US |

So you cannot screen for hedging by filtering on a title. You have to screen on the structural pattern - a current operating role at one company sitting alongside a stated founder role at another. That is a query you can run in plain English rather than a filter you build by hand.

Ask me this: `Founders in San Francisco who list a current full-time operating role at another company alongside their startup` - [run the search](https://www.refolk.ai/start?q=Founders%20in%20San%20Francisco%20who%20list%20a%20current%20full-time%20operating%20role%20at%20another%20company%20alongside%20their%20startup).

*Returns founders whose public profile shows an active operating role elsewhere running in parallel with their startup, the first structural pattern to probe for hedging.*

Running the pattern across a whole segment with [Refolk](/) turns a one-by-one profile read into a ranked queue of founders who declare the overlap themselves - which, given that only 788 use an explicit dual title, is the honest minority worth looking at first. The stealth population matters here too: 9,791 US founders self-tag stealth, and absence of a public footprint is not evidence of Not Yet Committed, it is often a deliberate choice.

## The cap-table signal that predicts future damage

The absence of founder vesting is the load-bearing commitment flag, because it is both a signal about today's attention and a prediction of tomorrow's dilution. Founder vesting is one of the first things sophisticated investors look for in a cap table, and its absence is one of the fastest ways to stall a term sheet.

Standard vesting is a four-year schedule with a one-year cliff: during the first year no equity vests, 25 percent vests at the one-year mark, and the remainder vests monthly over the next three years. Skipping it turns a departed co-founder into dead equity. Without a repurchase right, a co-founder who leaves at month six keeps a full stake that dilutes everyone who stays. That is why vesting absence predicts cap-table damage, not just present attention.

Ownership bands give you the second proxy. Place estimated founder ownership against the stage benchmark below. Post-seed founder ownership below 50 percent is rated poor; below 40 percent before product-market fit, motivation and governance both suffer. Early hedging compounds here: median seed founder ownership is already 56.2 percent, so a part-time founder entering later rounds from a weaker base converts a soft commitment question into a hard dilution one.

| Stage | Median founder ownership | This-round dilution |
|---|---|---|
| Pre-Seed | ~77% | 10-15% + ESOP |
| Seed | 56.2% | ~19.5% |
| Series A | ~36% | ~22% |
| Series B | ~23% | ~17% |

> **Rule:** Vesting present is necessary, not sufficient
>
> Confirm vesting exists, then confirm the 83(b) election was filed within its 30-day window. Vesting can sit on paper with no election filed, which creates tax and diligence cleanup. Vesting present without a filed 83(b) is still a flag.

## The procedure: footprint to verdict

Run the read in seven steps, roughly three to four hours of work. The first five gather and resolve evidence, the sixth classifies, and the seventh writes the condition that makes any non-All-In verdict investable.

#### Scoring a founder's commitment from public signals

1. **Pull the public footprint** - Collect the LinkedIn experience section, GitHub profile, company registry record, and any advisory or board listings. Capture every current role and its dates in one place.
2. **Resolve employment end dates** - Check whether the prior employer role shows an end date. Treat a blank end date as unknown, not as still employed, because the field is gamed. Mark each prior role ended, ambiguous, or clearly current.
3. **Map concurrent roles** - List every parallel operating role, board seat, advisory seat, and consulting entity. Tag each one operating (red) or passive and beneficial (yellow).
4. **Read contribution timing** - For technical founders, inspect the GitHub graph while accounting for UTC, merge and fork exclusions, the 12-month window, and the private toggle. Score activity consistent, sporadic, or unreadable.
5. **Check cap-table commitment proxies** - Confirm whether vesting exists and place estimated founder ownership in a band against the stage benchmark. Confirm the 83(b) was filed.
6. **Score and classify** - Combine the dimensions into All-In, Hedging, or Not Yet Committed, citing the specific evidence per dimension.
7. **Set the conditional trigger** - For Hedging or Not Yet, require a dated transition commitment - a salaried full-time start or a signed resignation - as a close condition, written into the memo.

A note on order, because sources disagree. Allied Venture Partners requires all co-founders to work full-time before investing, which makes step seven a gate rather than a condition. Kingscrowd treats part-time as a yellow flag and allows a documented post-raise transition. Decide which policy your fund runs before you start, because it changes whether a Hedging verdict is a pass or a workable deal.

## Turning the verdict into a dated trigger

The defensible output of this read is not a binary at the table, it is a dated transition trigger. The "quit your job" bar is an accelerator-manufactured norm, not a law. Y Combinator operationalises it by directing founders to pay themselves a salary from the investment so they can work full-time. That makes a salaried full-time start a verifiable post-close condition, not a promise.

A wait needs a specific trigger - a signed pilot, a reconciled cap table, a specialist opinion, or a founder commitment. For commitment specifically, the trigger is a last day at the current job or a dated start on a founder salary. Write it into the memo so it is checkable, and remember that verification should not rest on the profile alone: funds run background checks and verify LinkedIn claims against employer records.

**Commitment verdict and trigger block for the memo**

```
COMMITMENT READ

Employment end date: [ended / ambiguous / current] - evidence:
Concurrent roles: [none / passive only / active operating] - entities:
Cap-table proxies: vesting [present/absent], 83(b) [filed/unconfirmed], ownership band:
Transition timing: [transitioned / dated plan / vague intention]
Contribution timing (if technical): [consistent / sporadic / unreadable]

VERDICT: [All-In / Hedging / Not Yet Committed]

TRIGGER (required unless All-In):
Condition: [signed resignation dated / salaried full-time start dated]
Close gate or post-close covenant: [gate / covenant]
Verification: [background check against employer records]
```

*Fill each dimension with the evidence you found, then state the verdict and, for anything short of All-In, the dated trigger.*

A clean All-In looks like this: a resolved end date, no active operating roles elsewhere, vesting present with an 83(b) on file, and either a transition already made or a dated commitment. A Hedging verdict has one load-bearing flag, usually an active second operating role or absent vesting, and is investable only with the trigger. Not Yet Committed has multiple unresolved flags and no dated plan to resolve them.

## How this read goes wrong

The failure modes below are the most valuable part of the standard, because every one of them produces a confident but wrong verdict. Each is a false positive: a signal that looks like evidence of hedging or disengagement but is not. For each, the check that clears it.

- **Blank end date read as still employed.** Scores a committed founder as Hedging. The field is deliberately gamed. Check: ask directly and require a resignation or last-day date.
- **Overlapping current roles read as divided attention.** The profile is often stale, not live. Check: look for the newest role's activity, not the old role's missing end date.
- **Quiet GitHub graph read as disengagement.** Work is in private repos with the toggle off, on forks, or on non-default branches. Check: treat the graph as unreadable, not as evidence.
- **Busy GitHub graph read as full-time focus.** Commits can be padding, or from a prior employer still inside the 12-month roll. Check: timestamps and repo ownership.
- **Vesting present read as commitment.** Vesting can exist with no 83(b) filed, creating cleanup risk. Check: confirm the election was filed within 30 days.
- **Advisor title read as a side hustle.** Passive advisory at 0.2 to 1 percent is normal, not divided operating attention. Pools rarely exceed 2 percent. Check: confirm the stake and that the role is not operational.
- **Stealth or no public footprint read as Not Yet.** Stealth is often deliberate - 9,791 US founders self-tag it. Check: require private confirmation rather than returning a public verdict.

> **Tip:** Corroborate, never decide, on GitHub
>
> Let contribution timing confirm a verdict the other dimensions already point to. If end date, concurrent roles, and cap table all say All-In, a consistent graph supports it. If they disagree, a graph cannot break the tie - it is too easy to suppress or pad.

The common thread across all seven is the same discipline: no single public field is proof. The end date, the overlapping listing, and the GitHub graph each carry one failure mode that flips its apparent meaning. The read works because it triangulates five dimensions and lets the structural ones - end date and cap table - carry weight the noisy ones cannot.

## Before you call the verdict

Run this check before you write the memo. It catches the false positives from the section above and confirms you resolved rather than assumed.

#### Clear before writing the verdict

- [ ] Every prior role is marked ended, ambiguous, or current - no blank end date was read as still employed
- [ ] Each concurrent role is tagged operating (red) or passive and beneficial (yellow)
- [ ] Any active second operating company is confirmed live, not inferred from a stale profile
- [ ] Vesting is confirmed present or absent, and the 83(b) filing status is checked
- [ ] Estimated founder ownership is placed in a band against the stage benchmark
- [ ] GitHub timing, if used, is scored as corroborating only and not as a deciding signal
- [ ] For Hedging or Not Yet, a dated transition trigger is written into the memo
- [ ] The plan to verify LinkedIn claims against employer records is noted

## Keeping the read current

The mechanics behind these signals change, so re-check them rather than trusting a past read. GitHub's contribution rules, LinkedIn's verification behaviour, and the ownership benchmarks all drift. When you run a read months after a prior one, confirm the GitHub window still covers the period you care about - it rolls forward 12 months and drops older activity - and re-pull the end date, since a founder may have resolved a blank field or added a new concurrent role since.

The ownership bands move with each new dilution dataset; treat the figures here as the shape of the curve, not fixed values, and refresh them against the current benchmark report before quoting a number in a memo. The one thing that does not drift is the method: resolve the structural dimensions first, let the noisy ones corroborate, and convert any soft answer into a dated condition. That is what separates a verdict you can defend from a gut-check you cannot.

## Frequently asked questions

### How do I check if a founder actually left their job?

Do not rely on the LinkedIn end date. The field is deliberately gamed, and a blank end date keeps a person visible in recruiter searches for the old employer, so it reads as still employed even when they have left. Treat a blank date as unknown, then require a signed resignation or last-day date directly from the founder, and expect your fund to verify LinkedIn claims against employer records in background checks.

### Is a founder with a second company always a red flag?

No. A concurrent operating role that draws attention away is a hard flag, but a passive advisory or board seat at 0.2 to 1 percent equity is normal and does not signal divided operating attention. The test is whether the parallel role is operating or passive, and whether it is beneficial to the startup, such as research or partner work. Tag each role before you score, and never let one overlapping listing on a possibly stale profile decide the verdict.

### What does missing founder vesting tell me?

It is the cheapest high-value flag in a commitment read. The absence of founder vesting is one of the fastest ways to stall a term sheet, because without it a co-founder who leaves at month six keeps a full stake and dilutes everyone who stays. Standard is four years with a one-year cliff: no equity vests in year one, 25 percent vests at the cliff, then monthly over 36 months. Confirm it is present and that an 83(b) election was filed.

### Can I trust a quiet GitHub graph as a sign the founder is disengaged?

No. GitHub silence is high-noise and low-signal. Four separate mechanics suppress a genuinely active founder's graph: contributions are timestamped in UTC not local time, commits on forks and non-default branches do not count until merged, the graph shows only a rolling 12-month window, and private activity appears only if the user enabled the toggle. Use contribution timing to corroborate other signals, never to decide.

### Should I require a founder to be full-time before investing?

Sources disagree, so pick a policy and state it. Allied Venture Partners requires all co-founders to work full-time before investing, which makes full-time a gate. Kingscrowd treats part-time as a yellow flag and allows a documented post-raise transition. The practical middle ground is a dated transition trigger: Y Combinator funds founder salaries so they can work full-time, which makes a salaried full-time start a verifiable close condition.

### Why do so few founders list themselves as part-time or dual-role?

Because dual-commitment is almost never self-declared. In Refolk's index, only 788 US profiles carry an explicit Founder and Advisor style title against 724,534 founders, about 0.11 percent. Hedging rarely shows up as one honest title. You have to infer it from separate overlapping entities, concurrent operating roles, and unresolved end dates, not from a label the founder chose to publish.

---

*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/founder-commitment-read*