Key Milestones
Definition
Container handle for the field-array of named fundraising milestones the board should track to the close — each entry tracks milestone name, type (e.g. term-sheet signing, IC presentation, close), target date, status (upcoming / in-progress / completed / at-risk), responsible party, and notes. The "what has to happen, by when, and who owns it" surface that turns the round narrative into a tracked plan. Renders via the CollapsibleFormItemCardGallery widget (the reused gallery pattern shared with sales pipeline deals and HR key hires / openings). Common pitfall: milestones carried forward from prior packs without status updates — these should be refreshed each period so the board sees real progress, not a stale wishlist.
Why it matters
Converts the round narrative into a tracked plan with owners and dates — the board can see at a glance which milestones are slipping and who to press. Without named-milestone visibility, the board only learns of a stalled round when the close date slips.
How it's calculated
Container — field-array of milestone items (name, type, status, targetDate, responsibleParty, notes). No aggregate calculation; the surface makes individual milestones and their owners visible at the board level. How to interpret it
Watch for milestones that have been "in-progress" across multiple quarterly packs without resolving, and for an at-risk or blocked milestone on the critical path to close (term sheet, lead commitment, IC presentation). Pair with `fundraising.round_status` and `fundraising.planned_close_date` — a clean milestone list alongside a slipping close date usually means the milestones are being optimistically maintained.
Source
imboard Editorial
Stage relevance
Typically owned by
Related KPIs
Current phase of the active fundraising round on a coarse state machine (e.g. not-started, in-progress, term-sheet, closing, closed). The board reads this to know which playbook applies — pipeline-building, diligence, closing, or post-close communications. Common pitfall: the field drifts when a round stalls or pivots, so treat each phase change as a board-update trigger. The PhasePlaybook widget binds to this enum and surfaces the appropriate phase guidance read-only beside the editor.
Calendar date by which the round is expected to close (final wires received, definitive documents signed). Compared against `finance.runway_months` to detect a fundraising-against-the-clock situation. Common pitfall: planned close dates routinely slip 30–90 days in practice (collected founder postmortems on First Round Review) — boards should ask for both an "expected" and a "no-deal" date and watch the gap to actual runway exhaustion.
Target gross capital the company intends to raise in the currently active round (the "ask"). This is the headline number the CEO walks investors through and the board uses to sanity-check dilution and runway implications. Note the distinction from `total_round_size` (which can include third-party participation beyond the company-led ask) and from `minimum_close_amount` (the floor at which the round can close). Common pitfall: the target is updated mid-process when investor demand or strategy shifts — every change deserves a board note.
Capital that investors have agreed to invest — including both soft commitments (verbal / handshake / IOI) and hard commitments (signed term sheet or executed subscription docs). Treat this as the round-progress odometer. Common pitfall: soft commitments are notoriously squishy — every published fundraising postmortem (per First Round Review and Bessemer founder essays) warns that founders over-count soft commits. Board-best-practice is to track soft vs hard separately or to define a haircut convention (e.g. 50% of soft) at the start of the round.
Named risks that could prevent the round from closing as targeted — market conditions (general venture sentiment, sector-specific freeze), investor-side risk (anchor investor wobble, partner-meeting drop-off), company-side risk (a metric trending wrong direction, customer concentration concern surfaced in diligence), and timing risk (runway versus close date). Common pitfall: optimistic CEOs under-report risk factors. Boards should expect at least 2–3 named risks even in a healthy round — "no risks" is itself a risk signal.
Track these KPIs with your board
I'mBoard helps startup CEOs report the metrics that matter, track resolutions, and run better board meetings.