Leadership has a shared view of project health
Same format, same language, every week — across all active projects. Not a dashboard nobody looks at. A weekly report that makes project health comparable at a glance.
Fractional delivery leadership
Senior delivery control, without a full-time hire.
Monthly fractional engagement for 50–300 person custom software companies. I work embedded with your PMs — running weekly delivery reviews and surfacing risks before clients do. Leadership gets a consistent view of project health across the portfolio, every week.
The problem
You have PMs. Delivery is still unpredictable.
Projects go sideways without warning. Status reports look fine until they don't. Scope changes quietly eat margin. Each PM runs things their own way — so you can't compare health across projects, and you can't see problems coming until a client is already on the phone.
The issue isn't one bad PM. It's an operating setup that wasn't built for the scale you're at now.
What changes
What's different in the first 30 days
Risks are logged before they reach a client
PMs know how to flag risks, who owns them, and when to escalate. Blockers stop sitting in standups and start getting addressed.
Scope changes go through a consistent review
Small unapproved changes stop stacking up silently. Budget drift becomes visible before it becomes a problem.
You have a delivery rhythm that runs without you
Reviews happen. Reports go out. Risks have owners. The founder or Head of Delivery stops being the person who holds all of this together manually.
Scope
A concrete scope, not an open-ended retainer.
Eight to ten hours a week, structured around your projects and PMs. Here's exactly what that covers:
01
Weekly project health review
All active projects reviewed for status, timeline confidence, budget pressure, and client sentiment — every week, in one consistent format.
02
Risk log with owners
Active risks tracked weekly. Each risk has an owner and status. Leadership knows what's exposed and who's handling it.
03
Scope and budget watch
Unapproved changes flagged as they happen. Budget drift tracked across engagements before it silently eats margin.
04
PM check-ins
Regular sessions with each PM on reporting consistency, risk ownership, and escalation timing. Not performance reviews — operating rhythm.
05
Client communication review
On high-risk projects: reviewing what clients are being told and when. Catching gaps before they become escalations.
06
Monthly leadership summary
What changed this month. What's still risky. What needs a decision from the CEO or Head of Delivery before next month.
07
Async availability
Questions, quick reviews, escalation calls between sessions. Available when something needs attention before the next weekly review.
How it starts
The first two weeks are a diagnostic.
Not onboarding. Not setup time. A full diagnostic — covering your projects, PMs, reporting gaps, and delivery risks. By end of week 2 you have a risk map, PM observations, and specific quick wins to act on.
If the findings aren't useful enough to justify continuing, you stop. No invoice for the rest of the month.
Why this is different
Not a workshop. Not a methodology. Not a report.
What this isn't
- — Agile coaching sessions that stop when the engagement ends
- — A maturity framework delivered as a slide deck
- — An audit with recommendations but no follow-through
- — Generic consulting that doesn't know your projects
What this is
- Weekly operating rhythm inside your existing delivery setup
- Embedded with your PMs, not observing from the outside
- Changes that stick because they happen in the actual work
- Leadership visibility that doesn't require you to chase it
Good fit
This works best when a few things are already in place.
Existing PMs on active client projects
This isn't PM recruitment or replacement. The engagement works with the team you have.
Leadership willing to act on what gets surfaced
The diagnostic will find things. Fixing them requires decisions, not just awareness. If leadership isn't ready to act on the findings, the engagement won't move the needle.
Access to project reporting and PM conversations
I need to see the actual status updates, not a summary of them. The weekly reviews and PM sessions are where the real picture comes from.
50–300 person company where delivery has gotten complex
Informal oversight works at 30 people. It stops working at 150. This engagement is built for that inflection point.
Real engagements
What this looks like in practice.
Three anonymized cases: an escalated project stabilization, a portfolio visibility improvement, and a presales-to-delivery handoff fix. All from custom software companies in the 50–300 person range.
Investment
Senior delivery leadership, without a full-time hire.
Monthly fee
$3k–$4k
Per month, billed monthly
Working model
8–10 hrs
Per week, embedded with your PMs
Best fit
50–300 person custom software firms
With existing PMs and growing delivery complexity
A full-time Head of Delivery typically costs $120k–$180k/year. The fractional model gives you the same delivery leadership function — without the hiring timeline, onboarding risk, or long-term commitment.
Common questions
How is this different from hiring a Head of Delivery?
A full-time Head of Delivery costs $120k–$180k/year, plus recruiting time and onboarding. You also don't know if you'll have enough delivery complexity to justify the role long-term. The fractional engagement gives you the same function — weekly delivery control, PM oversight, leadership visibility — at a fraction of the cost, without the commitment. Start with the 2-week diagnostic. If it doesn't fit, you stop.
What if our PMs push back on the process?
Most don't. The goal isn't to audit them — it's to remove the ambiguity that makes their jobs harder. PMs who've been managing in chaos tend to welcome structure. Where I've seen resistance, it usually comes from unclear framing: PMs worrying this is a performance review in disguise. That gets addressed in the first two weeks.
What do you actually need from us to get started?
A 20-minute fit call. I'll ask about your project load, PM team, and what's been most frustrating about delivery lately. If it's a good fit, we start with the 2-week diagnostic. If it isn't, I'll say so on the call — no follow-up pitch.
Do you work with companies outside the US?
Yes. US, Europe, and GCC. Most of the work is async — status reviews, risk logs, written summaries — with one weekly sync. Two to three hours of timezone overlap is usually enough.
Next step
Delivery control doesn't require a full-time hire — or a big commitment.
Start with a 20-minute fit call. We'll look at your current project load and PM setup. If there's a fit, we run the 2-week diagnostic. If the findings aren't useful by end of week 2, you stop. No invoice for the rest of the month.