Senior team or first hires? The first 90 days after a round

The round closes and the plan says hire. It should: a company needs its own team. But a senior engineer takes months to find, and the first hires still need someone to set the foundations. Meanwhile the clock that matters, the one to the next round, is already running.

What the first 90 days are for

The next round will not ask how many people you hired. It will ask what customers can do today, and what the numbers say. The first 90 days should produce exactly that: a product people use and measurement you can trust.

When a senior team makes sense first

• You have a method, a mockup or a pilot and it has to become a product, not another prototype.
• The product needs AI that works, which takes engineering experience, not only enthusiasm.
• You cannot afford a slow start. On a recent build, a working AI product was done in 8 weeks, as planned, running on the client’s own accounts from the fifth week.

What “handover-ready” should mean

A team that builds before your hires arrive has one more job: leaving something your team can take over. That means:

1. Your repository, your accounts. Nothing lives on the vendor’s side.
2. Automated tests. On that same build, the first weeks had none; we fixed that, because untested code is a trap for whoever comes next.
3. A written record. Weekly reports and a log of decisions, so your first engineer can read why things are the way they are.
4. Small, reviewed changes. A history someone can follow, not one giant commit.

Both, in order

It is rarely senior team or hires. It is a senior team now, so the product and the numbers exist, and hires who join something that already works.