Quick Takes
from the Field.

If you can't pull up your key metrics in under sixty seconds, you're flying blind.

I've been saying this to every founder I work with for years, and it never stops being relevant. The startups that execute best measure relentlessly. Not vanity metrics. Not whatever the last investor asked about. The metrics that actually tell you whether the business is healthy, whether it's improving, and where it's about to break.

Pick the right ones for your stage and business type. Build the infrastructure to capture the underlying data — not just the headline KPI, but the raw transactions, pipeline snapshots, and cohort data that feed it. Forecast every one of them in your financial model. Display them in a near-real-time dashboard.

Then run a monthly AVF — Actual vs. Forecast — and dig into every meaningful variance. Positive variance: understand why something is outperforming. Negative variance: debug it before it compounds.

Do this and a few things change at once.

Board prep stops being a fire drill, because the slides are the same data you already see every day.

You catch problems early — three months before they show up in revenue or churn.

And investors evaluating execution risk see a founder who knows their own business cold.

This is one of the highest-leverage things a startup can do, and almost nobody does it well at the seed stage. Which is exactly when it matters most.

I wrote up the full playbook.

The first two posts in this series argued the funding bar has moved up — and moved up further for hardware.

This one is about what that means for your runway.

The median wait between funding rounds is now 696 days. Whatever round-to-round timeline you modeled last year, you most likely need longer than that.

Carta puts the Series A → Series B median at 2.8 years — the longest on record. Seed to Series A is 616 days. About 40% of seed-stage rounds are now bridge rounds, because the bar has moved higher and most companies cannot clear it on the original timeline.

Two cues founders can use to size the gap.

First, bridges typically run six to twelve months. If 40% of companies are taking one, plan as if you might be one of them.

Second — for hardware founders especially — your own prototype cycle. Hardware prototype cycles can run six to nine months. If you need to ship more units to more customers at higher quality to clear the next bar, you are likely looking at one more prototype cycle before scaling — six to nine more months on top of what you planned.

You will need more runway than your plan currently shows.

The financing levers are limited. Bridges are getting raised, but at terms most founders would rather not accept. Spend cuts have a floor. Revenue acceleration has a slope.

The lever with the most room to move is operational. And the timing matters.

Bring in experienced operations help early — fractional or full-time — to lead the burn-cutting, the planning discipline, the reporting cadence, the supply chain tightening. Done early, the savings and productivity gains pay for the help and extend the runway. Done late, you can’t afford the help when you need it most.

In this market, operations isn’t back-office hygiene.

It extends the runway.

I keep meeting hardware founders who've decided their product is now "as a service."

Press them on why and the answer is almost always the same: SaaS companies get better valuations, and they want in.

That's not a strategy. That's envy dressed up as a business model.

Calling yourself HaaS doesn't make you a SaaS company. It just hides the fact that you're running a hardware company with an awkward payment plan — and you'll pay for it in working capital, gross margin, and customer trust.

SaaS valuations are high because the underlying business has four attributes at once: very high gross margin, low and easily scalable distribution cost, high LTV, and the ability to improve the product without rolling a truck.

Hardware-as-a-service loses on three of those four. Stickiness is the only one it can win on, and that alone won't close the valuation gap.

There are real HaaS businesses. Rolls-Royce sells thrust by the hour because airlines don't want engine maintenance risk. HP sells printing as a service because customers don't want to manage ink. Some robotics companies sell outcomes because the customer can't operate the gear themselves.

Those are the right reasons.

"I want a higher valuation" isn't on that list.

If you're drawn to HaaS because your customers genuinely can't operate the technology, build the model around that reality. If you're drawn to it because recurring revenue trades at a premium, stop.

Build a hardware-enabled SaaS company instead. Charge for the hardware honestly. Earn your multiple on the software layer where it's actually warranted.

That's the job.

Not "part-time" but "part of the team."
Not one project one time, rather a function, indefinitely.
Deep experience on the bench before you can afford it.

That's what a Fractional COO is.

Done right, your team doesn't see a fractional COO. They see a second-in-command. Your board sees credibility. You have an integrated sounding board that isn't part-time, but answers a call any time.

Own and do, vs advise.

Shoulder to shoulder in BOD meetings and investor pitches, if you want.

30yrs of experience at the price of a new-hire. Get your Company OS built right the first time, because it isn't their first time.

Land that next round at a higher valuation because your operations are that good.

Earlier this week I posted about how the funding bar has moved up.

Going from less than $1M ARR to $5-10M ARR is an order-of-magnitude jump — neither easy nor low-risk for any startup.

The thing is, most hardware startups don’t have ARR, they just have revenue, recognized one-time when the unit ships. For a SaaS company, revenue from existing customers remains constant as long as customers continue to use the service they subscribed to in the past. But for a hardware company, constant revenue this quarter vs. last implies shipping as many new widgets this quarter as last. That doubles the installed base just to keep revenue growth flat. You have to ship twice as many units to double revenue, tripling the installed base. The math keeps biting quarter after quarter.

For hardware startups, the bar didn’t move up by just inches, more like feet.

Getting to the new bar means putting many more units in the field, and warranty (and reputation) exposure scales with that — the cost of a hardware bug climbs fast when there are hundreds or thousands of units out there to recall, repair, or replace.

The version of the product that satisfied the first ten customers usually isn’t ready for the next hundred. Before scaling deployment, you almost always need at least one more prototype cycle to lift quality. That could be six to nine months.

And we haven’t even mentioned the working capital required to ship order of magnitude more units.

The Series A bar moved up in absolute terms. For hardware, it also moved up in units shipped, quality required, capital deployed, calendar time, and operational complexity — all at once.

If you are a hardware founder, your fundraising plan needs to absorb this. The operational lift to clear the new bar starts long before the next round is on the calendar.

Bring in experienced operations help early — fractional or full-time. Done early, the savings and productivity gains pay for the help and extend the runway. Done late, you can’t afford the help when you need it most.

In this market, operations isn’t back-office hygiene.

It’s the runway.

Q1 2026 set a venture funding record: $300 billion in a single quarter.

But one company took more than one third of that — OpenAI — and four companies took 65% of it.

The funding market for the thousands of other startups is a different story — it’s harder than it has ever been.

Deal count is down. Carta tracked just 1,122 new rounds in Q1 2025, the lowest Q1 since 2018.

The wait between rounds is the longest on record. 696 days median across all stages. 2.8 years from Series A to Series B.

The seed-to-Series A pipeline is clogged with bridges — about 40% of seed rounds are now bridge rounds.

And the Series A bar moved up. One investor told Carta the new expectation is $5M to $10M ARR. A few years ago, less than $1M sometimes got you there.

Now for most hardware startups, ARR is a proxy — the bulk of their revenue is recognized one-time when units ship. The bar translated: more revenue, more units shipped to more customers, more PMF risk retired before the next round.

If you are planning your 2026 fundraise on 2022 assumptions, you are facing a funding shortfall.

You cannot move the market, so you need to move your operations.

Automation. Forecasting. Reporting. Governance. Compliance.

These are the inputs to fundability you control end-to-end — to extend the runway and shorten the diligence.

In this market, operations is fundraising infrastructure.

Sometimes compliance feels like a nuisance.

Startups have limited time, limited cash, and seemingly unlimited pulls on both. The founder is right to focus on product, customers, and the next fundraise. But the founder and the leadership team need to resist perceived compliance shortcuts.

You've heard about Delve — the $300M startup expelled from Y Combinator earlier this month. Possibly some founders were looking for a shortcut when they signed up with Delve. Possibly not. I don't know.

What I do know: I applaud the incorporation of modern apps and tools in the tech stack. Eliminate manual work. Automate extensively. Use agentic tools with care and within guardrails. But Delve is a cautionary tale in that sense — your tech stack needs to feature reputable, proven apps and tools. Vet the vendor as hard as you'd vet a hire.

And to the extent any founders saw Delve as an info sec compliance shortcut: info security isn't optional, and you shouldn't be looking for shortcuts. Company-building includes many things that need to be done properly — not always fun, perhaps not an obvious use of the company's scarce resources. But they are. Bad on you if you forgot the compliance line item in your budget. It isn't optional, no more than insurance.

You need to avoid a hack or a breach at all costs. Partner and customer trust takes years to earn, but can be destroyed in an hour. So actually put the controls in place — not to pass the audit, but to avoid the breach.

If you need help figuring out which controls to put in place, or how to implement them, find a consultant who specializes in this. SeriesOps can hook you up. There are also good tools that help collect and organize the evidence — they really do make the audit go more smoothly.

With the controls in place, you'll pass the audit easily. More importantly, you'll sleep better at night — because you'll have reduced the chance of an event that will kill your company.

Controls, not certificates.

Do the work.

The difference between a promising startup and an investable one is whose name is on the paperwork.

Founders claim durability with pitches. Investors verify it via signatures.

Audited books carry the name of your accountant. A SOC 2 Type II report is adjudicated by an accredited third party and issued under their name, not yours. A penetration test report carries the name of an accredited security firm. Each one is independent verification that the business is real, the controls work, and the numbers survive scrutiny.

Start collecting them earlier than feels necessary.

SOC 2 Type II is the one that matters. It requires months of operational evidence that your controls actually work — and enterprise buyers know exactly what the report says. Retain a consultant who does Type II prep full-time; they'll get you audit-ready faster than you could alone.

What most founders miss: large enterprise customers will send you security questionnaires regardless. The cert doesn't make the questionnaires go away. It means every answer is backed by an accredited auditor's opinion — and that turns a stalled procurement cycle into a signed contract.

Same logic on the financial side. I've seen VCs skip their own financial diligence audit when the company handed them books already audited by an independent accountant.

But the real signal isn't any one cert. It's the stack of professionals standing behind the company.

A fractional COO running operations. An experienced startup lawyer on retainer. An accountant whose name is on your audit. An accredited auditor whose name is on your SOC 2 report.

Four professional signatures on your business before Series A.

That's a formidable company from day one.

The founder stays on product, customers, and the next round. The signatures take care of the rest.

I've seen two kinds of patent filing at seed-stage startups.

Reactive — when someone remembers.

Deliberate — through an actual program.

The gap between them compounds. Fast.

If your company creates IP — and if you're building anything technical, it does — you need the second kind. Not a patent attorney on speed-dial. A process.

Here's what it looks like:

A one-page invention disclosure form every engineer and designer knows how to fill out. Training on it during onboarding, so submitting a disclosure feels like logging a ticket, not a legal production.

A patent committee that meets every quarter for an hour. Fractional outside IP counsel in the room. Your CTO. Your fractional COO running the agenda. The founder on the committee, but not running it.

Every disclosure from the last ninety days gets reviewed. Each gets a verdict — file provisional now, revisit next quarter, or pass. A handful of provisionals a year, at a few thousand dollars each, locks in priority dates and buys you twelve months to decide on a non-provisional.

Reward participation. A modest amount per disclosure. A larger one when a patent is granted. The amounts matter less than the signal — the company takes IP seriously, and engineers who create it get recognized.

And every employee and contractor has signed your CIIAA. It was your first contract template — and it's been used without exception. Nothing else you build matters if that foundation is missing.

The founder's job is product, customers, and the next round. Not running the patent committee.

But an IP moat with multiple concentric circles makes the next round a little easier.

Compliance isn't a chore. It's fundraising infrastructure.

I've watched deals die in diligence.

Not because the product was weak. Not because the market was small.

Because a consulting contract from year one assigned IP in the wrong direction. Because a contractor built the prototype before signing a CIIAA. Because the "executed" vendor agreement only existed as a vague memory.

The pitch doesn't fail. The data room does.

The fix starts with clean templates — an employment agreement, a CIIAA, an NDA, a pilot contract, a sales contract — drafted by a corporate lawyer who specializes in venture-backed startups. Not your uncle's real estate attorney. And not an AI copilot that still generates legal slop on the subtle stuff.

The right lawyer is a boardroom advisor, not a billable-hour machine. You might only talk to them a handful of times between rounds. But you're not buying hours — you're buying pattern recognition, and the quiet judgment of someone who's watched a thousand cap tables survive or implode. Their counsel is worth many multiples of their fee.

The routine — redlining vendor contracts, tracking signatures, enforcing a signing authority chart — belongs with your fractional COO. The founder shouldn't be in this at all. Every hour spent on contracts is an hour not on product, customers, or the next round.

And every signed contract lives in a contract management tool — e-signed, timestamped, searchable. Not a folder in Google Drive. Not "I think we executed that." One archive, ready when diligence asks.

The companies that close rounds fast don't have the best decks.

They have their house in order.

"Most winning plays start way deep in your zone. Those are the spectacular ones that change the course of the game."

My friend Martin — who's been VP or SVP of Operations at various companies — left that comment on one of last week's posts - it stuck with me.

He's right. And it applies directly to hardware startups.

Engineering usually thinks they're in the red zone when Manufacturing starts producing a new product. In reality, they're at midfield. There are still dozens of problems and loose ends to sort out before that product ships in volume with high yield and low cost.

And I agree with Martin, the most successful product launches I've seen don't start at midfield. They start deep in the team's own zone — with Manufacturing, Fulfillment, Field Ops, and Customer Support, even Sales and Marketing, involved from the earliest stages of product development.

Choose your CM early. Include their manufacturing engineers in your design reviews. Build your support systems before you need them - test them alongside the product during your field trials. The handoff from engineering to production shouldn't be a handoff at all — it should be a play the whole team has been running from the opening snap.

I wrote about this in detail — the five handoffs that kill hardware startups, and how to get them right.

Your product isn't just the thing you ship. Your product is your whole company.

Great hardware with buggy software delivers a poor customer experience. So does great software on defective hardware. So does late fulfillment, inaccurate documentation, difficult installation or slow customer support.

The customer doesn't care which department dropped the ball. They just feel let down. And customer trust takes a long time to earn but can be lost in an instant.

The entire operations stack has to be ready and aligned — engineering, manufacturing, fulfillment, support, documentation. Every touchpoint either builds trust or erodes it.

Repeat purchases happen when customers are satisfied. Price premiums are earned when customers are delighted. And the best thing that can happen to your business? Your existing customers become product evangelists - new customers find you rather than the other way around.

That doesn't happen just because you built a great widget. It happens because every part of the company delivered.

Operations isn't back-office support. Operations is product.

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.