What is a fractional delivery lead — and when do you need one?

Most companies building software hit the same awkward stage: the work is too complex for "the developers will figure it out," but not big enough to justify a full-time delivery executive. The result is usually that delivery leadership lands on whoever has the least room to refuse it — a founder, a department head, or the most senior developer — as a side job. It gets done at the level a side job gets done.

A fractional delivery lead is the direct answer to that stage: senior delivery leadership, part-time, for exactly as long as the work needs it.

What the role owns

Fractional means part-time; it does not mean partial accountability. A delivery lead owns:

• The plan and the date — a roadmap that reflects reality, updated when reality changes, with the trade-offs made explicit rather than discovered late.
• Budget and forecast — what's been spent, what's left, and what the remaining work will actually cost, reviewed against progress monthly.
• Stakeholders — one trustworthy narrative of where things stand, so executives stop pulling engineers into status meetings.
• Cadence — a working rhythm where the team demonstrates real software on a heartbeat and blockers surface in days, not retrospectives.
• Decisions — the open questions that quietly stall projects get named, assigned, and closed.

How it differs from the neighbouring roles

Fractional CTO: owns technology strategy — architecture, stack, security posture, hiring profile. A delivery lead owns execution: the plan, the cadence, the date. Small companies sometimes need both; they're different jobs, and stapling them together usually shortchanges one.

Project manager: a PM tracks and reports; a delivery lead is accountable for the outcome and carries the authority to change how the team works, escalate decisively, and say no to scope. The difference shows up the first time the plan and reality diverge.

Agile coach: a coach improves how the team works and deliberately avoids owning what it delivers. A delivery lead does both — and in a rescue situation, ownership has to come first.

The signs you need one

• The honest answer to "when will it ship?" is a shrug — or a date nobody believes.
• A founder or executive is spending ten-plus hours a week coordinating developers instead of running the business.
• Your development partner is good at building but keeps needing "someone on your side" to decide things.
• A previously healthy project has gone quiet, and nobody inside it can say precisely why.
• You're about to sign a significant build contract and no one on your side of the table has shipped software before.

The economics

A full-time senior delivery or engineering manager in Canada costs roughly $150,000–$220,000 a year plus hiring risk — for a role most small and mid-size initiatives need at one or two days a week. A fractional arrangement buys the same seniority only for the hours the work justifies, typically at a small fraction of the loaded full-time cost, and it scales down gracefully: as the team matures, the engagement shrinks instead of becoming an awkward permanent salary.

The exit matters as much as the entry. A good fractional lead works themselves out of the job — the cadence, the visibility, and the decision-making habits stay with your team after the engagement ends. If an arrangement is designed to make itself permanent, that's a staffing agency, not leadership.

What a sensible engagement looks like

1. A short diagnostic — one to two weeks reading the project honestly: plan versus reality, open decisions, team health, technical drag.
2. A stabilization period — typically one to three months at one or two days a week: cadence established, decisions closed, forecast rebuilt, stakeholders re-engaged.
3. Steady state or hand-off — either a light ongoing rhythm, or a deliberate transfer to someone internal the lead has been coaching all along.

If the middle of this article felt like a description of your current quarter, that's the signal worth acting on early — the difference between a stabilization and a rescue is usually about three months of waiting.