Hiring before you have an HR team is not a temporary workaround. It is the default state for most first-time founders, and the decisions made in this window shape company culture, team performance, and operational health for years. The first 90 days of building a team are less about filling seats and more about creating a repeatable process from scratch, often while also shipping product, closing customers, and managing runway. Done well, this period sets the foundation for every hire that follows. Done poorly, it produces a team misaligned on expectations, roles, and culture.
TL;DR
- The first 90 days of hiring without HR requires structure, not improvisation.
- A 30-60-90-day framework helps founders sequence decisions by urgency, learning, and system-building.
- Defining role expectations before posting is the highest-leverage activity most founders skip.
- Fractional HR for startups is a practical middle ground between going it alone and hiring a full-time People lead.
- Hiring infrastructure, not just individual hires, is what enables a team to scale.
About the Author: High Five is an AI-powered hiring platform purpose-built for founders and operators hiring across Southeast Asia. With a client base spanning fast-growing startups and product-led companies, High Five has direct experience helping teams without HR functions build scalable hiring processes from day one.
Why Do the First 90 Days of Hiring Matter So Much?
The first 90 days are not arbitrary. Research into leadership and role transitions consistently shows that early structure dramatically increases the likelihood of long-term success, for both the hires and the founder doing the hiring [alumni.hbs.edu]. Every norm, process, and cultural signal you establish in this window becomes the default template your company inherits.
For a first-time founder, this period typically involves making three to eight hires with no dedicated recruiter, no standardized interview process, and no documented role expectations. The decisions are consequential and the process is improvised. That combination is where most early-stage hiring mistakes are born.
The risk is not just a bad hire. It is a bad hiring habit that scales.
What Should a Founder Actually Do in the First 30 Days?
The first 30 days are for learning before deciding [cornerstoneondemand.com]. Most founders invert this and start posting roles before they have clarity on what those roles need to accomplish.
The 30-day priority list:
- Write a one-page “team thesis” covering what the company needs to be true about its first five hires
- Map your immediate execution gaps, not your ideal org chart
- Define what “good” looks like for each role before you write a job description
- Establish a simple scoring rubric for interviews so you are not evaluating candidates on gut feel alone
- Identify which roles are blocking product or revenue, and sequence accordingly
A useful discipline here is separating the “what” from the “who.” Before you think about candidates, you need clarity on what the role must accomplish in its first 90 days, why that work cannot wait, and how you will measure whether the hire is succeeding [alumni.hbs.edu]. Founders who skip this step tend to hire for personality rather than output, which feels right early and causes problems later.
How Should Hiring Decisions Evolve in Days 31 to 60?
Building on the clarity established in the first month, days 31 to 60 are where you shift from learning to deciding. This is when your first hires are onboarding and your hiring process needs to become repeatable, not just functional.
What to build between day 31 and 60:
- A basic candidate evaluation template that every interviewer uses
- A written offer framework so compensation conversations are consistent
- A simple onboarding checklist covering week one logistics, key meetings, and initial deliverables [codeoftalent.com]
- A short document per role defining the first 30, 60, and 90 days of expectations for each new hire [cornerstoneondemand.com]
The onboarding piece is underrated. Many founders spend significant effort sourcing and interviewing candidates, then provide almost no structure once someone accepts. A new hire left without a clear first week plan loses momentum immediately [codestory.co]. The cost is not just their first week. It is the trust and engagement they bring into month two.
A practical analog: think of onboarding as the product experience for your new hire. If your product had no user flow after signup, you would fix it immediately. The same logic applies to the joining experience.
What Does “Hiring Infrastructure” Actually Mean for a Startup?
This is where the thinking needs to shift from transactional to structural. Most founders treat each hire as a one-off event. You write a job description, post it somewhere, interview a few people, and make a call. That works for hire one. It breaks down at hire five.
Hiring infrastructure means treating your recruitment process the same way you treat your product infrastructure: something that runs continuously, improves over time, and does not require you to rebuild it from scratch every time you need it.
Core elements of early hiring infrastructure:
| Component | What It Looks Like at Startup Stage |
|---|---|
| Role definition process | A repeatable template for translating business need into a role brief |
| Candidate sourcing | A consistent channel strategy, not ad hoc posting |
| Screening criteria | Written criteria applied consistently across candidates |
| Interview structure | A fixed set of questions per role type, evaluated against a rubric |
| Offer and compensation framework | A simple band structure with documented rationale |
| Onboarding checklist | A week-one plan every new hire receives before they start |
Building this does not require an HR team. It requires about two to three hours of deliberate setup per role type, done once, and then refined as you learn.
When Should a Founder Consider Fractional HR for Startups?
Fractional HR for startups is not a compromise. It is often the right answer for companies between five and twenty-five employees who need People infrastructure but cannot yet justify a full-time hire.
A fractional HR professional typically works across multiple companies at once, providing access to genuine expertise at a fraction of the cost of a permanent hire. They are particularly useful for:
- Drafting employment contracts and offer letter templates
- Building a compensation framework and leveling structure
- Establishing compliant onboarding and offboarding processes
- Advising on early-stage culture and values documentation
The alternative, using a founder’s time for all of this, carries a real opportunity cost. Every hour a founder spends untangling a contractor classification issue or building a performance review template is an hour not spent on product or customers.
A good rule of thumb: if HR-adjacent tasks are consuming more than four hours per week of a founder’s time, the economics of fractional HR almost always work in the company’s favor.
Frequently Asked Questions
Q: Do I need a job description before I start sourcing candidates? A clear role brief is more useful than a formal job description. It should define the outputs expected in the first 90 days, the non-negotiable skills, and the team context. This takes less time to write and produces better candidates than a generic job description.
Q: How many hires should a founder expect to make in the first 90 days? This varies widely depending on funding, runway, and business needs. There is no standard range that applies across seed-stage companies. Prioritize roles that unblock your highest-risk execution gaps.
Q: What is the biggest onboarding mistake first-time founders make? Not planning the first week before the hire starts. New employees should receive a structured first-week agenda before their start date [codestory.co].
Q: When should I hire a Head of People or HR lead full-time? Most companies bring in a dedicated People leader around the twenty to thirty employee mark. Before that, fractional HR for startups or a strong operations hire with People responsibilities usually covers the need.
Q: How do I evaluate candidates consistently without a formal process? Create a simple scoring rubric with four to six criteria per role. Every interviewer scores each candidate independently before the debrief. This takes thirty minutes to build and significantly improves decision quality.
Q: Can I use the same hiring process for technical and non-technical roles? The evaluation framework should differ by role type, but the structure, role brief, sourcing approach, scoring rubric, and onboarding checklist can and should be standardized across all roles.
Q: How does AI-assisted sourcing help founders without HR support? Platforms that run candidate sourcing continuously mean founders are not starting from scratch each time a role opens. The pipeline stays warm, the search criteria are already defined, and qualified candidates arrive without the founder spending time on manual outreach.
About High Five
High Five is an AI-powered hiring platform that helps founders and operators build teams across Southeast Asia without paying agency fees or success fees. The platform uses AI-assisted sourcing combined with human expert review to surface qualified candidates on a flat monthly subscription, making it particularly well-suited to companies without a dedicated HR function. High Five covers a broad range of roles across tech, product, finance, marketing, and operations, and is designed to function as always-on hiring infrastructure rather than a transactional service. Clients include PayMongo, Nafas, Agridence, and SkinSeoul, among others.
If you are a founder building your team in Southeast Asia and want a hiring process that works without a full HR team behind it, visit highfive.global to learn how High Five can support your hiring process from day one.
