Your First Hire
The ten decisions that separate a good first hire from the one that costs you a year.
Cold email is the most misunderstood growth channel in SaaS. Most founders who try it write generic outreach, get low response rates, and conclude the channel does not work. The founders who get it right achieve response rates between 15% and 30% because they understand what cold email actually is: a permission request disguised as a message, not a pitch disguised as a message. The difference in framing changes everything about how the message is written and received.
In short
- • Every cold email recipient has the same mental model: this is a stranger asking for something. The first sentence determines whether the recipient reads the second sentence. The second sentence determines whether the recipient reads the third. By the third sentence, the recipient has already decided whether to reply, ignore, or mark as spam. The window is three sentences. Make them count.
- • A 2022 analysis of 12,000 cold email sequences by Apollo.io found that emails mentioning a specific, recent event related to the recipient's company had 3.4x higher response rates than emails that started with a generic compliment. The reason is attention economics. A specific observation signals that the sender did research. A generic compliment signals that the sender did not. People respond to effort.
- • The best cold emails follow a three-sentence structure. Sentence one: acknowledge something specific about the recipient or their company. Sentence two: explain why that observation matters in the context of a problem you solve. Sentence three: make a specific, low-friction ask. 'Would you be open to a 15-minute conversation this week?' is infinitely better than 'I'd love to connect and tell you more about what we do.'
The first hire is an operating decision
A first hire should solve a constraint that the founder can describe in observable terms. “I am overwhelmed” is not enough. The useful question is: what important work is currently constrained because the company does not have a capability, owner, or capacity that it needs?
Common constraints include:
- a capability the team genuinely lacks;
- recurring execution work that is consuming founder time;
- a customer or delivery bottleneck;
- a decision bottleneck;
- a capacity problem already supported by real demand.
If the problem is actually unclear priorities, a broken process, weak demand, or work the founder has not yet learned to do, hiring can add cost without removing the constraint.
Define the outcome before the role
Write the role around what should become different.
Outcome: What should be measurably better after 90 days?
Responsibilities: What work belongs to this person?
Authority: Which decisions can they make without waiting for the founder?
Evidence: What observable results will tell you the role is working?
Dependencies: What must the founder or team provide?
A task list is useful, but an outcome and decision boundary make the role much easier to evaluate.
Test whether the role is real
Before hiring, look at the last four to six weeks of work.
Record:
- recurring tasks;
- founder hours spent;
- delays created by missing capacity;
- customer work that was postponed;
- decisions waiting for the founder;
- work that requires a capability nobody has.
Then ask whether the same constraint is likely to remain after the next quarter.
If the answer is no, consider a temporary contractor, automation, process change, or deliberate deprioritisation before creating a permanent role.
Test the candidate against the actual work
Use a realistic work sample where practical. It should resemble the decisions and outputs the person will actually own.
Evaluate:
- judgment;
- ability to define the problem;
- communication;
- relevant capability;
- handling of ambiguity;
- ability to work within the role's authority.
Do not turn the exercise into unpaid production work. The purpose is to improve the hiring decision, not obtain free labour.
Plan the first 30, 60 and 90 days
First 30 days: understand customers, systems, priorities, relationships and the definition of good work.
By 60 days: own a defined area with decreasing founder intervention.
By 90 days: produce observable outcomes and identify what should change in the role or operating system.
The exact milestones should fit the function. A salesperson, engineer, operator and finance hire should not have identical onboarding tests.
The trade-off
Hiring can increase capacity and remove a founder bottleneck.
It also creates:
- fixed or recurring cost;
- management overhead;
- coordination work;
- onboarding time;
- risk of hiring for a problem that is actually strategic or operational.
The decision should therefore be based on the cost of leaving the constraint unresolved versus the full cost of adding the role.
Decision test
Before opening the role, write one page:
- Constraint: What is blocked today?
- Evidence: How often has it happened and what does it cost?
- Alternative: What happens if we solve it through process, automation, contracting, or focus?
- Role: What capability or capacity is uniquely needed?
- Economics: What must improve for the hire to justify its cost?
- Authority: What will this person own?
- Review point: When will we decide whether the role is working?
A first hire is not a reward for being busy. It is an operating decision.
Research and evidence
Research on decision rights and hiring supports the underlying principles of defining decisions, observable criteria and role clarity. SOE's framework above is editorial synthesis, not a claim that one universal hiring formula works for every company.
Evidence boundary: Replace the framework's assumptions with the economics, workload and customer evidence of the specific business.
Use this on a real decision
Problem: What is happening now?
Evidence: What records or observations support it?
Options: What are the realistic alternatives to hiring?
Trade-off: What does each option cost or make possible?
Next action: What is the smallest step that will improve the evidence?
Review point: When will the decision be revisited?
Take it into your work
Do something with what you just read.
Save it for later, mark the passage that matters, or open your SOE workspace and keep thinking.
Takeaways
What to carry forward
- → The ask must be specific and low-friction. 'Tell me more about your process' is not low-friction. 'Are you using [specific tool] right now?' is specific. 'Would a 15-minute call be useful?' is low-friction. The combination signals that you respect their time and have something concrete to discuss. A 2023 study of 8,000 cold outreach sequences by Reply.io found that specific asks outperformed open-ended asks by 4.1x in response rate.
- → The first cold email gets a 2-5% response rate. The second gets a similar rate. The third gets a similar rate. Cumulatively, a three-email sequence to 100 prospects generates 6-15 responses. A 2021 analysis by Woodpecker.co of 45,000 cold email sequences found that 48% of all responses came from the third or fourth email in the sequence. Most founders send one email and stop. The channel requires sequence thinking, not single-message thinking.
- → Follow-up emails must add value, not just remind. 'Just checking in' is the lowest-value follow-up possible. 'I came across [relevant article/event/data] and thought of our earlier conversation' adds value. 'We just launched [feature] that addresses the problem we discussed' adds value. Each follow-up should give the recipient a reason to reply even if they ignored the previous message.
Cold email works when it is personalized, specific, and sequenced. Write the first email as a permission request, not a pitch. Keep it under 100 words. Send three to five follow-ups over two weeks, each adding value. Track response rate as your primary metric - anything below 5% means your targeting or messaging needs work. A 15% response rate on a cold channel is a superpower. A 2% response rate is a waste of time.