First 30 Days of a Founder Hiring Plan

The first 30 working days of a founder hiring plan should produce a dated decision record, not a promise of a hire. This calendar is for one approved role. Its outcome may be a focused search, a changed brief, a pause or a close.

The sequence assumes a five-day working week. Adjust the dates to the team's calendar, but keep each gate attached to an owner and a decision. It is a launch cadence, not a general founder hiring workflow.

Start with a Day 1 record

Before the calendar starts, write a one-page record for the role:

• the work outcome, reporting boundary and approved working pattern;
• must-haves, preferences and one evidence question for each must-have;
• founder or role owner, search owner, first reviewer and next review date;
• the decision-maker for a material brief change; and
• the condition that would pause or close the plan.

If the team cannot agree on the outcome, owner or must-haves, the calendar has not started. Do not use the first week to source against a disputed brief.

Follow the 30-working-day calendar

The calendar controls when work is reviewed; it does not require a team to proceed at every gate. A weak first batch may be useful evidence that a requirement, discovery boundary or review capacity needs attention.

Treat the plan as a calendar, not a funnel target

Do not set a profile count, response rate or interview count as the reason to pass a week. Those numbers can describe workload, but they cannot establish that the brief is clear or that a candidate should progress. The useful weekly output is a decision record that another owner could pick up: what was reviewed, what remained unknown, what changed and what happens next.

The calendar also distinguishes three separate clocks. The business clock is the date when the role becomes useful. The team clock is the time available for review and decisions. The candidate clock is the pace at which an individual conversation can be handled with a truthful next step. Do not solve pressure on one clock by skipping a gate on another. If the business date moves closer, the founder may change scope or pause the plan, but should record that decision before changing candidate-facing work.

Keep the same review packet through the first 30 days: the current brief, evidence questions, owner map, decision log and next gate. A new owner should be able to see why work is active, paused or closed without reconstructing it from messages.

Calendar entries should be specific enough to change the next block. "Review candidates" is a meeting note. "The functional reviewer checks the four records marked unknown against the approved ownership question by Thursday" is an owned action. That distinction makes a six-week plan useful when the founder has to step away or the role changes hands.

Use the weekly gate to protect the next block

At the end of each block, ask four questions:

1. Is the role still approved under the same brief version?
2. Can the named owner complete the next action in the next block?
3. Does each record show an observation, an interpretation and any material unknown?
4. Is there a reason to continue, revise, pause or close that another reviewer can understand?

When a must-have, working pattern or outcome changes, create a new brief version. Mark inherited records that need the same relevant recheck before comparing them to new work. Do not apply a changed standard only to the person currently under discussion.

Reset the calendar when a dependency changes

The plan should pause when budget, role authority, review capacity or a material dependency is unresolved. Preserve the current brief version, queue state, open questions and the owner of the restart condition. A restart begins with a current owner and a specific next action; it does not assume that old evidence remains current.

Example: an approved first product-engineer role reaches Day 11, but the functional reviewer becomes unavailable. The founder records the review-capacity pause, keeps the evidence record, names the restart owner and schedules a decision date. The team does not add another batch merely to keep the calendar moving.

Where Talent Summoner fits

Talent Summoner is our product. As verified on 6 September 2026, candidate sourcing supports role-brief discovery and a ranked set of public-source profiles for human review. Use it in the Days 6-10 discovery block only after the Day 1 record is approved. The team owns verification, contact, assessment, offers and all hiring decisions. See pricing for current Role options before purchasing a Role.

Complete the Day 1 record for one approved role, then schedule the first evidence-review gate before beginning discovery.