Talent SummonerFounder Guide to Intake Questionnaires
Use a copyable founder intake questionnaire to expose missing hiring inputs, assign owners and set stop conditions before sourcing one role.
A founder intake questionnaire turns a spoken hiring request into inputs another person can inspect. It is useful when a first hire feels urgent but the role, evidence standard or decision rights are still moving. The output is a versioned record showing what is known, what is unknown, who can answer each question and what must stop until the answer arrives.
Use this questionnaire before searching for one role. It sits between an initial hiring request and an approved hiring brief. A brief records the decisions the team has accepted; an intake questionnaire exposes the gaps and contradictions that need resolving first. It is also different from an interview scorecard, which records evidence from candidate assessment.
What to decide before asking the intake questions
Before asking the questions, define the smallest decision the founder needs to make: launch the search, revise the role, pause for an owner or close the request. Ask for an observable work outcome rather than a title or a description such as "someone senior". Then identify the evidence that could support each essential capability.
Keep unknown separate from absent. If nobody has checked the working pattern, budget input or scope of a past project, record the gap and give it an owner. Do not turn silence in a profile or a founder's uncertainty into an automatic exclusion rule. A questionnaire is working when a second reviewer can see the next question without relying on the founder's memory.
Copyable founder intake questionnaire
Copy the block into the role record and complete one answer at a time. "Unknown" is a valid answer when it is paired with an owner, due point and stop condition. Keep the respondent's observation separate from the decision-maker's interpretation.
FOUNDER HIRING INTAKE QUESTIONNAIRE
Role / team / respondent / date:
Questionnaire version and record owner:
BUSINESS NEED
What work is not being owned today?
What observable outcome should this hire own first?
What remains with the founder or another role?
What is explicitly out of scope?
REQUIREMENTS AND EVIDENCE
Which capabilities are essential, and why are they required?
What source, work sample or job-related question could support each one?
Which preferences are useful but not gates?
Which adjacent backgrounds should be considered?
What is unknown, and who will verify it?
OPERATING BOUNDARIES
What location, working pattern or time-zone constraint is approved?
What compensation and benefits inputs are approved, and in which currency?
Who owns any work-authorisation, employment or specialist question?
Which public or supplied sources are in scope for discovery and review?
PROCESS AND DECISION RIGHTS
Who approves the brief and material changes?
Who reviews evidence and records unknowns?
Who owns candidate contact, assessment, offer hand-off and the final decision?
What is the next gate: launch, revise, pause or close?
What condition stops the next action?
Next action / owner / due point:
Approved brief version / approver / date:How to diagnose intake questionnaire failures
Read the answers as a process check, not as a test of the founder's recruiting knowledge. The table below identifies common failure signals and the smallest correction that makes the record usable.
| Intake signal | Likely input failure | Corrective owner and stop condition |
|---|---|---|
| A title is supplied but no outcome | The request is not tied to work the person would own | The role owner writes an observable outcome; stop discovery until the boundary is approved |
| "Five years" or a title is the only must-have | A proxy has replaced a capability and evidence question | The role owner defines the capability and acceptable evidence; stop using the proxy as a gate |
| "Culture fit" or a personal style is listed | A vague preference may be hiding a job requirement | The decision owner states the job-related behaviour or removes it; pause comparable review until clarified |
| Two people answer the same question differently | Decision rights or the source of truth is unclear | The founder names one accountable owner and records the chosen version; stop material changes in chat |
| Location, schedule or authorisation is unresolved | An operating boundary has no approved input | The authorised operations, HR or specialist owner confirms it; stop actions that depend on the boundary |
| Budget is described only as "market rate" | The team cannot state what has been approved | The budget owner records the actual input, currency and exceptions or marks it unknown; do not promise terms |
| No reviewer can inspect the evidence | More search activity would create an unowned queue | Assign a reviewer or set a bounded batch; stop expanding discovery until review capacity exists |
| Answers change after a favourite profile appears | The brief is drifting in response to a person | The founder versions the change and decides whether earlier records need rechecking; pause the affected decision |
Do not fix every signal by adding more questions. A useful correction names one owner and one release condition. If the owner cannot be reached, preserve the questionnaire version and pause the dependent action. This makes a delay visible without labelling a candidate or treating an incomplete request as a failed person.
How to run the intake questionnaire as a short gate
First, ask the founder to describe the business need and the outcome in plain language. Next, challenge every must-have with "why is this required?" and "what could demonstrate it?" Record acceptable adjacent routes before looking at profiles. This prevents a preferred background from becoming the definition of the role after discovery has started.
Then review operating boundaries with the authorised owner. Location, work authorisation, compensation, benefits and employment administration can depend on the employing entity and relevant jurisdiction; this guide is general process information, not legal or employment advice. Leave specialist decisions with the appropriate qualified person and write the question rather than guessing.
Finally, name the brief approver, evidence reviewer, contact owner, assessment owner and final decision-maker. Freeze the questionnaire version and create the linked brief only when the launch gate passes. If the founder changes an outcome or must-have later, create a new version and decide which earlier work needs a comparable review.
Fictional example: repairing a vague engineering request
Repair a vague request by asking what work the hire will own, what proves the skill and who reviews it, as this fictional example shows. A founder initially writes: "Hire a senior engineer who moves fast." The questionnaire exposes three failures: there is no owned outcome, "senior" has no evidence question and the founder has not named a reviewer. The example is not a market benchmark.
The repaired record says the role should own a defined product workflow through release, with the founder retaining product direction. A must-have becomes "can explain and deliver comparable work," supported by a project source and a consistent technical discussion. An engineering adviser is the evidence reviewer, while the founder approves the brief and final decision. The launch gate is withheld until the adviser confirms capacity. No candidate is rejected because a public profile omits a technology; the gap becomes a verification question.
Where Talent Summoner fits after the intake questionnaire
Talent Summoner is our product for AI candidate sourcing, CV ranking and outreach you confirm before it sends; use it after the questionnaire's stop conditions are resolved and the brief is approved. Its current candidate-sourcing workflow, checked 29 September 2026, starts from a role brief and searches LinkedIn, GitHub and other public professional sources across 200M+ profiles. It returns a ranked shortlist with must-haves, nice-to-haves and plain-English reasoning. Your team still verifies evidence, chooses whom to contact and makes the hiring decision.
Review the live pricing page after the founder approves the role scope, owner and budget input. Pricing is a separate purchasing decision; it does not resolve an incomplete intake.
Founder intake questionnaire FAQ
What is a founder intake questionnaire?
A founder intake questionnaire is a copyable set of questions that turns an early hiring request into recorded outcomes, requirements, evidence questions, constraints, owners and a launch, revise, pause or close decision.
How is it different from a hiring brief?
The questionnaire surfaces missing or conflicting inputs. The hiring brief records the approved outcome, boundaries, evidence standard and decision rule that later sourcing and assessment should use.
What should a founder do when an answer is unknown?
Record the unknown, name the accountable owner and define the condition that releases the next action. Do not guess, silently exclude people or start a dependent step while a material boundary remains unresolved.
Can Talent Summoner complete the questionnaire?
No. Talent Summoner can search public professional sources from an approved role brief and return ranked reasoning. Your team owns intake answers, approvals, verification, contact and the final hiring decision.
Complete the questionnaire for one role, resolve each stop condition and save the approved brief version. Then start candidate sourcing and review pricing as a separate, authorised next step.
