What a Series B operational plan must prove

The plan must connect the investment to the outcome

One of the simplest questions a Series B plan needs to answer is:

What does the next £20 million, £40 million or £80 million actually create?

Hiring people is not an outcome.

Opening an office is not an outcome.

Buying equipment is not an outcome.

Implementing an ERP system is not an outcome.

Those are investments.

The operational plan needs to show what capability those investments create.

For example:

£2 million of manufacturing investment creates a validated production capability of 500 units per month.

A new supply-chain organisation reduces material risk and supports the required production ramp.

A regulatory programme unlocks entry into defined markets.

Additional service capability enables deployment to a significantly larger installed base.

A new ERP and planning process provides the inventory, purchasing and demand controls required to operate at the next scale.

The investor should be able to trace capital to capability and capability to revenue.

It must prove that revenue can actually be delivered

A financial model can show revenue increasing extremely quickly.

Operations needs to demonstrate how the company physically achieves it.

For a hardware company, that means translating sales forecasts into units.

Then units into production capacity.

Then capacity into labour, equipment, test capability, factory space and material.

Then material into supplier capacity, lead times and working capital.

A £100 million revenue forecast is meaningless operationally unless the company understands what £100 million of revenue requires.

If the average selling price is £10,000, that means 10,000 units.

Can the manufacturing system produce 10,000 units?

Can the supply chain provide the components for 10,000?

Can the company test 10,000?

Can it ship 10,000?

Can it install and support 10,000?

Can the suppliers scale with it?

What happens if demand reaches 15,000?

What happens if it reaches only 5,000?

The operational plan should answer those questions.

The forecast needs an operating model behind it

A good Series B plan should connect the commercial forecast to an operational model.

At a minimum, management should understand the relationship between:

demand -> material -> capacity -> production -> inventory -> deployment -> cash

Each stage has constraints.

Demand may be uncertain.

Material may have long lead times.

Factories have finite capacity.

Test processes have cycle times.

Inventory consumes working capital.

Deployment requires people.

Customers have payment terms.

Once these constraints are modelled together, the business begins to understand what growth actually requires.

Without that connection, the company has a sales forecast, not an operational plan.

It must demonstrate that the organisation can scale

Early-stage businesses often work because a relatively small number of capable people hold everything together.

Decisions happen informally.

Information moves through Slack.

The founder knows what every team is doing.

The engineering director remembers why a particular component was selected.

The operations lead personally knows every supplier.

Finance reconciles problems at month end.

That operating model does not scale indefinitely.

A Series B business needs to show how it will move from people-dependent execution towards system-dependent execution without becoming bureaucratic.

That means thinking clearly about organisational design.

Which capabilities need to exist internally?

Which can remain outsourced?

Which leadership positions become necessary?

Where should accountability sit?

What span of control is sensible?

Which functions need specialists rather than generalists?

Where are the organisation's single points of failure?

The answer is rarely to build a large corporate structure immediately.

The objective is to create the minimum structure necessary to operate reliably at the next scale.

The company must understand its capacity

Capacity planning sounds like a manufacturing issue.

It is actually a strategy issue.

If the business succeeds, where does capacity come from?

A good operational plan should show the current capacity, committed capacity and future capacity required to support the growth plan.

For manufacturing businesses this may include:

• Assembly capacity
• Test capacity
• Tooling capacity
• Supplier capacity
• Warehouse capacity
• Engineering support
• Quality resources
• Installation capacity
• Repair and service capability

It should also identify the real bottleneck.

A factory might theoretically assemble 100 products each week while having test capacity for only 30.

The production capacity is therefore 30.

Adding more assembly operators will not solve the problem.

Series B is exactly the stage where identifying these constraints becomes important because capital is about to be deployed against future growth.

Supply-chain risk needs to be visible

Investors do not need to see every component on the BOM.

They do need confidence that management understands the supply risks hidden inside it.

That means knowing where the company is exposed to:

single-source components,

long lead times,

supplier concentration,

geographic risk,

obsolete components,

capacity constraints,

minimum order quantities,

specialist manufacturing processes,

and material requiring significant prepayment.

A mature plan should also explain the mitigation.

That might mean alternate components, alternate suppliers, framework agreements, strategic stock, tooling duplication, redesign, regional sourcing or contractual capacity commitments.

The point is not to eliminate all risk.

That is impossible.

The objective is to demonstrate that the important risks are known, quantified, owned and actively managed.

Unit economics need to survive scale

Many companies assume that higher volume automatically improves margins.

Sometimes it does.

Sometimes scaling reveals costs that were invisible at low volume.

Scrap increases.

Warranty appears.

Freight becomes significant.

Test equipment is required.

Quality headcount grows.

Distributors take margin.

Inventory needs financing.

Field support expands.

Manufacturers add overhead.

Component prices move.

Customers demand different terms.

A Series B plan therefore needs a credible view of landed product economics rather than simply comparing selling price with the engineering BOM.

Depending on the business, this might include:

• Material
• Manufacturing conversion
• Test
• Freight
• Duties
• Packaging
• Warranty
• Repair
• Field service
• Licence costs
• Distribution
• Scrap
• Manufacturing overhead
• Inventory financing

The purpose is not just to calculate today's gross margin.

It is to show how margin behaves as the business scales.

Working capital needs to be taken seriously

One of the most important operational questions in hardware is:

When does cash leave the business compared with when cash comes back?

The answer can be uncomfortable.

A supplier may require payment months before production.

The contract manufacturer may buy long-lead material against forecast.

Products may take weeks to manufacture.

Finished units may spend time in transit.

The customer may then pay 30 or 60 days after delivery.

The company can therefore finance several months of the operating cycle before receiving the revenue.

Rapid growth magnifies this effect.

The business may become more successful commercially while simultaneously consuming more cash operationally.

A credible Series B plan should therefore include working-capital requirements alongside operating expenditure.

Ignoring this is one of the fastest ways for a successful hardware company to find itself unexpectedly constrained by cash.

Product maturity must match the commercial plan

A Series B company may still have significant product development underway.

That is normal.

What matters is understanding the relationship between technical maturity and commercial commitments.

The plan should show what has been demonstrated and what remains unproven.

For a hardware business that might include:

engineering validation,

design validation,

production validation,

reliability,

regulatory approval,

manufacturing process qualification,

production test,

field validation,

and software maturity.

Each major commercial milestone should have corresponding technical and operational evidence.

The company should not commit to a production ramp simply because the forecast requires one.

Production should increase because the evidence justifies increasing it.

Regulatory and quality requirements need ownership

Regulation can easily become a milestone on a project plan:

"Obtain certification."

That is rarely sufficient.

Leadership needs to understand what regulatory strategy supports the intended markets, which entity holds the approvals, what testing is required, how design changes will be controlled and what obligations continue after the product reaches the market.

Quality requires similar clarity.

Who owns supplier quality?

Who controls design changes?

How are non-conformances handled?

What traceability is required?

How are field failures investigated?

How are corrective actions closed?

What records need to exist?

These things become increasingly important as volumes and customer exposure increase.

The operational plan should make ownership unambiguous.

Systems should follow the operating model

Series B businesses are frequently told that they need enterprise systems.

ERP.

CRM.

PLM.

QMS.

Planning tools.

Business intelligence.

Potentially all of them are justified.

But software does not fix an undefined process.

The company first needs to decide how it intends to operate.

What is the source of truth for the BOM?

Who can release a product revision?

Where is demand captured?

How does demand become a purchase requirement?

Who approves suppliers?

How is inventory valued?

How are serial numbers tracked?

How is a customer issue connected to a manufacturing batch?

Once the operating model is understood, systems can support it.

Implementing software before answering those questions often results in expensive digital versions of poorly designed processes.

The plan must show who owns execution

One of the most important features of an operational plan is accountability.

Every major workstream should have a clear owner.

Not a department.

Not a committee.

A person.

Manufacturing readiness.

Supply-chain scale.

Quality.

Regulatory.

Systems.

Hiring.

Capacity.

Cost reduction.

Service.

Each needs somebody accountable for delivering the result.

Cross-functional collaboration is essential, but collective ownership frequently becomes no ownership.

The board should be able to see who is accountable for each major part of the scale-up.

Milestones need evidence, not percentages

"Manufacturing readiness: 80% complete" tells a board almost nothing.

Operational milestones should be evidence based.

For example:

Production design released.

Critical suppliers approved.

Long-lead purchase orders placed.

Production line commissioned.

Production test validated.

Pilot build completed.

First-pass yield above target.

Regulatory testing completed.

Production capacity demonstrated.

Service process operational.

The benefit of evidence-based milestones is that they make progress harder to disguise.

A programme is either ready to pass the gate or it is not.

The plan must show what happens when reality differs from the forecast

Every Series B plan will be wrong.

Demand will differ from forecast.

Hiring will take longer.

A supplier will slip.

A certification test may fail.

A product issue will be discovered.

A customer deployment will move.

The quality of the plan is therefore not determined by whether the assumptions prove perfectly accurate.

It is determined partly by whether management understands what it will do when they are not.

A good operational plan includes scenarios.

What happens if demand doubles?

What happens if it is 50% below plan?

Which expenditure is committed?

Which can be delayed?

What is the production constraint?

Which components create inventory exposure?

What hiring is critical?

What is the minimum viable operating structure?

Scenario planning demonstrates something important to investors:

management understands the mechanics of its own business.

Risk needs to be connected to decisions

A risk register containing 100 rows does not necessarily indicate good risk management.

The board needs to understand the relatively small number of risks that could materially prevent the company achieving its plan.

For each one, management should understand:

the probability,

the impact,

the mitigation,

the owner,

the trigger,

and the decision required.

Operational risk management should therefore support decisions rather than becoming an administrative exercise.

The strongest Series B plan tells one coherent story

The commercial plan says what the company expects to sell.

The product plan says what needs to be developed.

The manufacturing plan says how it will be produced.

The supply-chain plan says how material will arrive.

The hiring plan says who will make it happen.

The systems plan says how it will be controlled.

The financial model says what it will cost.

The funding plan says how it will be financed.

These should not be independent documents.

They should describe the same company.

If commercial forecasts assume rapid growth but the hiring plan does not support it, there is a problem.

If manufacturing requires long-lead inventory but the cash model does not include it, there is a problem.

If the product roadmap adds multiple variants while operations assumes a stable BOM, there is a problem.

If revenue assumes entry into a new geography while regulatory approval is not funded, there is a problem.

Operational planning is partly the process of finding these contradictions before the company discovers them in reality.

What the board should ultimately be able to see

A strong Series B operational plan should allow a board or investor to answer five fundamental questions.

Can the company deliver what it is selling?

Can it scale that delivery without losing control of quality, cost or cash?

Does management understand the major constraints and risks?

Is there a credible organisation capable of executing the plan?

Does the proposed investment create the capability required for the next stage of the company?

If the answer to those questions is clear, operations strengthens the investment case.

If it is not, a polished financial model will not compensate for it indefinitely.

Because at Series B, investors are no longer only financing the possibility that a product could become successful.

They are increasingly financing the company's ability to turn that possibility into a repeatable operating business.