Learn how to approach pre-seed hiring by defining the problem first, screening for ownership, and choosing builders over job titles.
You have funding, but you also have a long list of problems.
Your first instinct may be to hire a marketer, designer, or salesperson. That can be the wrong first move.
Pre-seed hiring works better when you start with the business problem, define the outcome, and then find the person who can own it.
Position-Thinking vs. Problem-Thinking
Position-thinking starts with a title:
“We need a content writer.”
Problem-thinking starts with the result:
“We need someone who can help customers understand why our product matters and turn that interest into qualified conversations.”
At the pre-seed stage, the right hire is not always the person with the right title. It is the person who can solve the problem.
| Position-thinking | Problem-thinking |
| “We need a social media manager.” | “We need someone who can build an engaged early-adopter community.” |
| “We need a salesperson.” | “We need someone who can help us convert qualified prospects into customers.” |
| “We need a UX designer.” | “We need someone who can make the product easier to understand and use.” |
| Screen for tools, titles, years of experience | Screen for ownership, learning speed, and results |
Before hiring, define the outcome clearly. Tinova’s Business Foundation approach follows the same principle: diagnose the real problem before deciding what needs to be built.
Why First Hires Fail
A founder may hire a designer because the brand looks weak. But the real issue may be positioning.
A founder may hire a salesperson because revenue is low. But the real problem may be that customers do not trust the offer yet.
The hire is not necessarily bad. The diagnosis was incomplete.
Tinova has diagnosed 200 startups, and its current process starts with diagnosis because the deliverable a founder asks for is not always the real business leak.
That gives founders a useful hiring rule:
Do not ask, “Who should I hire?” before asking, “What result do I need?”
What Should You Screen For?
A strong resume can show experience. It does not tell you how someone will behave when the plan changes.
For a pre-seed hire, look for four things:
1. Ownership
Can they explain what they personally decided, built, or changed?
2. Speed of learning
Can they learn a new market, tool, or process without needing constant direction?
3. Ability to ship
Have they finished real work and produced a measurable result? Paul Graham makes a similar point in his essay on doing things that do not scale: early startups need founders and teams who take direct action rather than waiting for a perfect system.
Paul Graham: Do Things That Don’t Scale
4. Comfort with uncertainty
Can they make a sensible decision when the answer is not obvious?
At this stage, proof of work can tell you more than a polished resume.
The 30-Minute Brain Test
Give the candidate the problem you need solved and ask:
“Based on what you know today, how would you approach this in your first 60 days? What would you do first, and how would you measure success?”
You are not looking for a perfect answer.
Look for:
| Strong signal | Weak signal |
| Asks clarifying questions | Starts prescribing tactics immediately |
| Breaks the problem into steps | Jumps straight to tools |
| Defines a measurable outcome | Describes effort instead of results |
| Works within your budget and constraints | Assumes more resources will solve the problem |
A good answer should make you think, “This person knows how to figure things out.”
Generalist or Specialist: Which Should You Hire?
There is no universal answer.
A generalist can make sense when the startup is still discovering the best path and one person needs to cover several connected problems.
A specialist makes sense when the problem requires expertise your current team cannot develop fast enough. Think regulatory work, advanced engineering, security, or another high-risk technical area.
Research discussed by the World Economic Forum found that broader experience can be valuable in hiring, while specialization remains important in fields where deep expertise is critical. The right choice depends on the work the person needs to do.
World Economic Forum: Generalists or Specialists?
The simple rule: hire a generalist when you are still solving for the path. Hire a specialist when the problem itself demands deep expertise.
What About Hiring a Salesperson?
Be careful with hiring sales simply because you have funding.
Before handing customer discovery to a sales hire, founders should understand the buyer, the objections, and the buying process themselves. Tinova’s 30-Prospect Test uses a two-week customer research process to help founders learn what is working before they try to scale it.
That same principle applies to hiring:
Do not hire someone to discover a process you have not started to understand.
A Better Pre-Seed Hiring Process
Before posting a job, answer four questions:
What problem are we solving?
Define the business problem, not the department.
What outcome should this person own?
Give the result a number, deadline, or clear state.
What proof would show they can do it?
Ask for real examples, not just job descriptions.
Does this need a specialist?
Choose depth only when the problem requires it.
This approach keeps hiring tied to the startup’s actual needs instead of filling seats because a title seems necessary.
Hire for Outcomes
Your first hires can shape how quickly the company learns and executes.
At pre-seed, hire for the problem, not the job title.
Define the outcome first. Screen for ownership and learning speed. Ask candidates how they would solve the actual problem. Then decide whether you need a generalist or specialist.
And remember the core test:
Can this person take a real problem and move it forward with the resources we have today?
That question is more useful than asking whether their title matches your job description.
Ready to Build a Stronger Early Team?
Tinova’s Investor-Ready in 21 Days program helps pre-seed and seed founders build their positioning, commercial foundation, website, pipeline, and investor assets before a raise. The program is designed for startups with an MVP or first customers preparing to raise within two quarters.
See Tinova’s Investor-Ready in 21 Days program
FAQs
Who should a startup hire first?
Hire for the biggest business problem, not the most obvious job title. Define the outcome first, then find someone who can own it.
What should I look for in a first startup hire?
Look for ownership, learning speed, ability to ship, and comfort with uncertainty. Real examples of completed work can be more useful than job titles alone.
Should a pre-seed startup hire a generalist or specialist?
Use a generalist when the startup is still figuring out the best path. Hire a specialist when the problem requires deep expertise your current team cannot develop quickly.
What is the Brain Test for hiring?
Give the candidate a real business problem and ask how they would approach it in their first 60 days. Look for clear thinking, useful questions, constraints, and measurable outcomes.
Why is hiring by job title a mistake at the pre-seed stage?
Job titles describe a role. Outcomes describe what the business actually needs. At pre-seed, that distinction can prevent a costly mis-hire.
