After Series A: the first 90 days of your engineering plan

The first 90 days after a Series A are a sequence of decisions, not a hiring spree. Reconcile the money, name the constraint, hire against it, then measure whether the hire moved it. Skip the order and you end up with six open roles and no idea which one unblocks the next milestone.

This plan splits the 90 days into three windows: weeks 1-4, weeks 5-8 and weeks 9-13. Those windows are HighCircl's suggested defaults, not a benchmark. We found no dataset that says how long each stage should take, so treat the boundaries as moveable and the order as the point. The money question (how the round turns into payroll, seats and infra) has its own article, how to size the round into payroll, seats and infra, and this one doesn't redo it.

Window	Decide	Hire	Tell the board
Weeks 1-4	Runway, constraint, role cards, intake owner, employee or contractor	Nobody yet, or one role you already know you need	Day 30: plan reconciled with runway
Weeks 5-8	Who comes first, who waits, and what gates each hire	The first one or two roles	Day 60: starts vs plan, pipeline, one risk
Weeks 9-13	Release, pause or resequence the next roles; commit the next quarter	Next tranche only if the gate is met	Day 90: outcome vs milestone, next tranche

How long does a Series A have to last?

Longer than it used to. Carta data reported by SaaStr, covering 3,365 US startups that raised a Series A, shows 39% of companies took three or more years to get from seed to Series A in Q3 2025, against 19% in Q3 2019. Only 23% raised within 1.5-2 years, down from 41% in 2019.

That's seed-to-A data for US companies. We didn't find an equivalent figure for the step from A to B, so don't read it as a Series B forecast. Read it as direction: the next round isn't guaranteed to arrive on a schedule you set today. Some advisory blogs cite 18-24 months of runway after an A. We found no primary dataset behind that.

The practical consequence is that you plan against runway, not against headcount. A hiring plan that only works if the next raise lands early is a bet, and the board should hear it described as one.

Weeks 1-4: what do you decide before you open a role?

Nothing gets posted in the first month unless you already know it unblocks something. The month is for four decisions.

Reconcile the round

Start from net cash, committed burn and the option pool you assumed, not from the hiring slide in the deck. Venture Capital Careers' (VCC) 90-day hiring plan (August 2026) treats that slide as a hypothesis to check first and authorize second, with separate windows for days 0-15, 15-30, 30-60 and 60-90. The reconcile-then-authorize idea is the useful part. The exact day boundaries aren't, and ours differ.

Put the sizing in one place, using the budget article, and move on. Don't let this step swallow the month.

Name the constraint, then the role

Capability comes before title. Ask what is actually blocking the next milestone, then ask whether that block needs a permanent owner or a spike of work. A flaky deploy pipeline that costs two days a week needs someone who owns delivery. A one-off migration needs a few months of a specialist.

The same VCC page suggests a role card for each hire: problem, milestone, 90-day outcome, decision rights, budget owner, dependencies and stop trigger. Use it. The stop trigger is the field that lets you pause a hire without a fight.

Fix the intake

A headcount budget isn't hiring capacity, which is another point VCC makes. Decide who sources, who screens, who makes offers and who runs the technical vetting. If the CTO is the only person who can judge a senior engineer, the CTO's calendar is your real limit on how fast you can hire, and you should plan around that rather than around the number of open roles.

Decide employee or contractor, role by role

In our judgment, the answer follows the shape of the work. Core ownership of a system you'll run for years leans employee. A bounded spike, or a gap you need covered while a permanent search runs, leans contractor. The cost arithmetic for each is in the budget article. We haven't sourced a rule on contractor classification across European countries, so check it with counsel for each country you hire in rather than assuming the answer.

Day 30 is also your first board checkpoint, covered in the board section below.

Weeks 5-8: who do you hire first, and who can wait?

Two sellers of recruiting give different orders, and they're worth reading side by side as long as you remember what they sell.

Recruiting from Scratch, in its guide to a first engineering team after a seed round, recommends a founding full-stack or product engineer first, then a senior backend or infrastructure engineer in the first quarter, and an engineering manager around the tenth engineer. KORE1, a staffing firm, puts an engineering lead first if you have no strong technical leader, senior engineers as hires two to four, and a manager at roughly 12-15 engineers, with the CTO managing for the first 6-12 months. Both orders are the firms' own experience. KORE1's thresholds aren't sourced to a dataset, and both firms earn money when you hire.

They disagree on the manager threshold, about the tenth engineer versus 12-15. Point Nine's post on scaling an engineering team is about span of control: it says one manager can stretch to 10-15 direct reports but recommends adding a management layer earlier. Our view is that neither number should set your date. Hire a manager when the CTO's calendar stops covering one-to-ones, code review and the roadmap, whatever the headcount is.

Here's a decision table of our own.

Your situation	First hire	Employee or contractor
No strong technical leader	Engineering lead, or a CTO-level hire	Employee
CTO is strong but the product is half-built	Senior product or full-stack engineer	Employee, or contractor to start sooner
Product works, delivery is slow	Senior backend or infrastructure engineer	Either, based on how long you'll need the work
Launch deadline inside the quarter	Senior engineer who can start in days	Contractor, with a permanent search in parallel

Whatever you choose, gate each hire behind a milestone, as VCC does: release, pause or resequence the next roles on observable evidence, not on the calendar.

The same Point Nine post (Olly Headey, January 2022) adds two habits for the start itself: fixed start dates every two weeks, and written onboarding goals for week one, month one and quarter one. Fixed dates limit inductions to one every two weeks, so new hires start together. If your first hires are contractors, a 14-day contractor onboarding plan covers the ramp.

Weeks 9-13: what do you measure and commit?

This window is for deciding what to release, pause or resequence. VCC's days 60-90 do the same: compare planned against actual start dates, and ask whether the bottleneck you named in week 2 has moved. If it hasn't, another hire in the same lane is the wrong answer.

Then commit the next 90 days. How to build that roadmap is a separate job, not covered here. Here, the only rule is that it exists in writing before the day-90 board update.

Watch velocity. Point Nine's author expects a short-term hit while the team standardises equipment and hiring processes, which he calls a necessary investment. That's one author's view, so don't treat it as a law, but plan for a possible dip. A dip in week 6 shouldn't make you cancel the plan, and a dip that lasts all quarter is a signal the onboarding isn't working.

What do you tell the board at day 30, 60 and 90?

Three short messages, three or four bullets each.

Day 30:

The plan reconciled against net cash and runway.
The roles you'll open, each with its milestone gate.
Who owns intake, and any CTO-time constraint.
The employee or contractor call per role.

Day 60:

Hires started against hires planned.
Pipeline health: candidates at each stage, time since the role opened.
Whether the bottleneck has moved.
One risk, named, with an owner.

Day 90:

Outcome against the milestone you set in week 1.
What was released, paused or resequenced, and why.
The committed next 90 days.
The decision you want on the next tranche.

None of this needs a new layout. If you don't have a standard update yet, the one-page board layout covers the format.

What this means for your next 90 days

The decision in front of you is the shape of the team and the order of the hires, set against runway. That's yours as CTO, and for a non-technical founder it's the decision to get a technical lead to own.

Two facts should shape it. Seed-to-A timing for US startups is slower than it was, so plan to the cash you have. And the hire orders on offer come from sellers of recruiting who disagree with each other on the manager threshold. Neither is a reason to follow them or ignore them. Use the situation table above, gate each hire on a milestone, and write the stop trigger before you post the role.

For the wider set of decisions around a raise, the startup CTO guides cover leadership, diligence and the first hires. Your first approval will probably be a single senior hire, and it needs a business case your CEO and CFO will accept. Making the case for the first senior hire compares the routes by cost, time to start and exit.

Hiring senior engineers through HighCircl

HighCircl places senior engineers from seven European countries: Poland, Hungary, Slovakia, Serbia, Slovenia, Romania and Spain. Rates are €45-105/hr ($50-115/hr), with a 20% margin, capped and applied on top of what the engineer earns. About 1 in 10 applicants pass vetting, and a shortlist of three to five arrives within 72 hours. There's no subscription and no minimum hours. A deposit of one month's estimated cost is applied to your first invoice, and a replacement comes at no additional recruitment cost if an engagement isn't working.

FAQ

What should a startup do first after raising a Series A?

Reconcile the round against net cash, committed burn and runway before opening any role. Then name what's blocking the next milestone and write a role card for each hire that answers it. Hiring comes after both steps, not alongside them.

Who should the first engineering hire be after Series A?

It depends on what's missing. Recruiting from Scratch suggests a founding full-stack or product engineer, and KORE1 suggests an engineering lead if you have no strong technical leader. Both are sellers of recruiting, so use their orders as inputs. Our judgment is to hire for the constraint that blocks the next milestone.

How many engineers does a Series A startup need?

We found no sourced figure. KORE1 cites a team of 8-20, but that's the firm's own experience, not data. Size the team from your runway and your milestones, and the budget article shows the arithmetic.

When should you hire an engineering manager?

The two vendors differ. Recruiting from Scratch says around the tenth engineer, and KORE1 says roughly 12-15. Both are the firms' own experience. We'd hire when the CTO can no longer cover one-to-ones, review and roadmap, whatever the headcount is.

How long should a Series A last?

Some advisory blogs cite 18-24 months of runway after an A. We found no primary dataset behind that. Carta data reported by SaaStr shows 39% of US startups took three or more years from seed to A in Q3 2025, so plan against runway and not against an expected next raise.