Quick Takes
from the Field.

If you're running an early-stage startup in 2026, you can automate more of your operations than ever before.

Close your books? Autopilot. Draft your NDAs? Autopilot. Screen candidates? Autopilot. These aren't demos — they're shipping products handling real work.

So here's the question every founder should be asking: what's left?

Julien Bek at Sequoia published a framework that nails it. Every function has an intelligence component — complex but rule-based, automatable — and a judgment component — experience, instinct, taste. The autopilots are eating the intelligence work. Fast.

But judgment doesn't automate. Deciding when your company is ready to scale. Selecting the best CM to manufacture your product and negotiating the contract. Determining how much cash you'll need to get to the next major value inflection point (and then raising one-third more). Choosing which of five urgent things actually matters this week.

That's operational leadership. And as AI takes over the routine, that judgment work becomes the highest-leverage activity in your company.

The tools are getting better every quarter. The need for someone who knows what to do with them is only increasing.

Clearly defined roles and responsibilities are essential.

At one startup I worked for, there was a time when we asked the VP of Product Management to also serve as VP of Engineering — we'd lost our Engineering leader and filling the role was taking a long time.

With no disrespect for the people involved at the time, here's why that wasn't a great idea.

There must be a healthy tension between those two roles. Engineering needs firm, unambiguous requirements. And Product Management needs those requirements fully met and the product delivered on budget and on time.

When one person holds both roles, accountability disappears. It's too easy for the engineer to forgive incomplete requirements when the engineer is also the overworked product manager. It's too easy for the product manager to forgive schedule slips when the product manager is also the overworked engineer.

The same applies to Engineering and Manufacturing. If the head of Manufacturing is also the head of Engineering being graded on finishing on time, it's too easy to declare the product "done" before it's truly ready for production.

You're on the same team, but the person throwing the football shouldn't also be catching it.

At the earliest stages, everyone wears multiple hats — that's unavoidable. But as the company grows, the founder needs to formalize clear handoffs. VP Engineering holds the PM's feet to the fire. VP Ops holds Engineering's feet to the fire.

Good corporate hygiene requires well-defined roles and responsibilities, with a champion in each seat who owns the outcome.

Many founders think culture is something you think about at 50 people, maybe after you've brought on your HR Director.

It's not. It's being established right now, by your first five hires — how decisions get made, how conflicts get resolved, whether people tell you the truth or what you want to hear.

If you're not deliberate about it, you end up with a culture shaped by accident. And culture is hard to change later.

Culture is how work gets done when you are not watching. It's also why your best employees decide to stay or leave.

You want a high-performance team. Its impossible without strong, intentional culture.

I wrote about how to make culture operational — not a poster on the wall, but actual infrastructure that drives how your team executes.

Huge congratulations to the Alcatraz team on closing $50M in Series B funding. This didn't happen overnight — it's the result of years of steadfast commitment to a vision by a founder and the team he inspired.

In a few years, in workplaces around the world, the ubiquitous badge reader will have been replaced by an Alcatraz Rock. The future is here today.

Tina, Vince, and the entire team earned this one.

One founder signs up for Notion. Another starts using Airtable. Someone drops a spreadsheet in Google Drive. Someone else emails an Excel file.

Six months later, the same data lives in four places and nobody knows which version is current.

That's not a tech stack. That's a mess.

The mistake most startups make with their operational tools isn't choosing the wrong ones. It's not choosing deliberately at all. The tools are cheap, mature, and well-integrated. The problem is that nobody sat down and designed the system — which tool owns which data, how information flows between them, and where the single source of truth lives.

I wrote about this: how to think about your Company OS as a deliberate design, not an accident.

You can make operations your company's hidden superpower.

The most important role in a hardware startup isn't the CEO. It isn't the CTO, the VP of Engineering, or the head of Sales.

It's the Product Manager.

If a startup is fortunate, it has a crackerjack engineering team that will design the product exactly to the requirements, on time, at the target cost point. But most of those engineers rarely talk to customers. They build what the PRD tells them to build.

And in hardware, the PRD has to be right.

SaaS companies can implement continuous deployment — ship fast, get feedback, iterate overnight. That doesn't exist when PCBs need to be redesigned, laid out, fabricated, assembled, and tested. When packaging needs to be retooled. When software integration has to catch up to a new board revision. Hardware development cycles are measured in quarters, not days.

Startups have short runways. Their capital is the most expensive they will ever raise. A wrong PRD doesn't just mean a pivot — it can mean a very expensive delay or outright failure.

That PRD is the single most important job of the Product Manager. And in an early-stage startup, the founder is usually the Product Manager.

Which is exactly why the founder has to keep her eye on the ball. Stay maniacally focused on the customer. And as the company grows, she cannot afford the distraction of building the operational machine around the product.

That part needs to be delegated.

Every hardware startup hits the same inflection point.

A prototype exists that proves the technology works. There's a lead customer lined up to test it, and seed investors have taken interest. The founder has been doing everything right, hired only engineers to this point, and handled everything else — planning, hiring, accounting, board reporting — alone. All the non-technical chairs in the company are empty.

But now field trials need to run. The fundraise is coming. The prototype needs to become a product. All those chairs can't stay empty.

This is the moment founders get wrong. They burn out trying to do it all. Or hire junior people who are learning on the job even though the startup can't afford mistakes. Or cobble together unpaid advisors who each give a few hours a month — fragmented advice, nobody owning anything.

The better answer? Hire one experienced operator who can sit in any of those chairs and get it right the first time, because it isn't their first time.

I'm starting something new.

I'm launching SeriesOps — a fractional COO for early-stage startups, from pre-seed or seed to Series A and beyond.

Here's the thesis:

Building a startup from scratch doesn't just require an innovative idea. It requires establishing all of the support systems every company needs. And the technical founder cannot spend her time on it. The opportunity cost is too high.

There's a task trio that needs to be the founding team's singular focus: developing the product, landing the initial customers, and fundraising. Every moment founders spend doing anything else delays progress and decreases the probability of success.

SeriesOps enables the founding team to focus on that trio while the rest of the company is designed and built by an experienced second-in-command — 30 years in tech, six startups, two exits.

What that looks like in practice: I embed in your company, attend your leadership meetings, present to your Board, and build the operational machine — your Company OS — systems, processes, financial modeling, KPI dashboards, AI-powered automation, and corporate governance. And if yours is a hardware startup, where operational complexity is considerably higher, that's my specialty — supply chain, hardware NPI, manufacturing, fulfillment, field support.

Operations becomes your startup's hidden superpower.

I'm writing regularly about startup operations at seriesops.com/insights — tactical, opinionated articles on topics from financial modeling to board reporting to why your ops stack is probably already obsolete.

If you're a founder at an early-stage startup, I'd love to talk. If you know an early-stage founder, I'd be grateful for the introduction.