One engagement. Done well.
From $8,500. Fixed fee. One week.
Core Engagement
The Catalyst Advisory Assessment.
One structured interview with your team. One to three stakeholder conversations. Four deliverables and a findings presentation — all within the week.
Covers all 14 dimensions of delivery maturity — including AI readiness, security posture, and team governance.
A findings brief for the executive.
A plan for the delivery lead.
A starting point for the team.
A jump-start for your developers.
And thirty days later — I come back.
Get in touch →Want to go further?
Present to leadership with confidence.
— $2,500
Scott prepares you for every question before you walk in the room.
Introduce the changes to your team.
— $1,500
A facilitated session so you don't have to have that conversation alone.
Ongoing advisory.
— By arrangement.
A senior peer available when you need one. No retainer until you're ready.
All three are optional. Most clients start with just the assessment.
Fixed fee. No surprises.
Every engagement is scoped and priced before work begins. If you are not sure where to start, get in touch and we will figure it out in one conversation.
Get in touch →FOR THE EXECUTIVE
A findings brief for the executive.
A complete presentation ready to deliver to your board, your CTO, or your leadership team — without a single edit. Every finding translated into business language. Every risk connected to a commercial consequence. Speaker notes on every slide so you walk in fully prepared for the questions you will be asked.
It does not read like a consulting report. It reads like a confident advisor who knows your organization and has a clear point of view. Because it is.
FOR THE DELIVERY LEAD
A plan for the delivery lead.
Twenty-five pages written for the person who has to act on it — not present it. Root cause analysis that names what actually happened and why. A week-by-week 100-day plan with named owners, specific deadlines, and a success indicator for every action. A complete risk register. And a conversation guide for every difficult conversation you need to have with your team.
This is the document you read before the board presentation — not after. It is where you decide whether you agree with the findings before anyone else sees them.
FOR THE TEAM
A starting point for the team.
A structured presentation designed for you to deliver directly to your team — with full speaker notes for every moment where it gets hard. Leads with what the team is genuinely good at, because that has to come first. Names what has slipped without assigning blame. Introduces the first three changes with enough specificity that nobody leaves the room wondering what happens next.
It tells you exactly what to say when someone pushes back. Because someone always does.
FOR YOUR DEVELOPERS
A jump-start for your developers.
Every action from the 100-day plan structured as Epics, Stories, and Tasks — organized by phase, with acceptance criteria and effort estimates. Your developers pick it up without a briefing. No translation required. No backlog grooming session needed to make it usable.
Import it directly into your project management tool and the first sprint of re-engagement is already planned.
Day one with your team and your stakeholders. Days two through four building everything. Day five presenting the findings. Thirty days later — I come back.
What a finding looks like
This is the level of specificity you should expect.
Every finding cites actual assessment evidence. Every recommendation has a named owner and a deadline. This is a representative example — anonymized from a real engagement.
Finding 02 · Critical
This platform's September deadline cannot be delivered at current resource allocation. This requires a leadership decision — not a delivery team workaround.
Business Impact
The back-end architect is allocated at 10% of their time. The AI engineer role is not yet hired. Three parallel workstreams are competing for the same fractional capacity. This is not a delivery risk in the conventional sense. It is a structural impossibility that leadership needs to name explicitly and resolve with decisions, not delivery pressure.
Evidence
Portfolio governance score: 0%. Developer allocation confirmed at 5-10% across three workstreams. Critical-path engineering role unfilled. External client commitment in September with no resource model to support it.
The Three Options
Option A — hire and increase allocation — full delivery. Option B — re-sequence the deadline proactively before it becomes a crisis. Option C — descope to a demonstrable proof of concept. Silence is not an option. Carrying the commitment without resolving the resource gap is the worst outcome.
Finding 03 · High
Leadership has committed to an AI roadmap. The team has no named AI owner, no proof of concept, and no framework for validating AI outputs before they reach clients.
The roadmap and the delivery capability are twelve months apart. This is not a technology problem. It is a resourcing and governance problem — and it requires a leadership decision before the next board presentation commits to another milestone.
Names, platforms, and figures have been changed. Finding structure and specificity are representative of real engagement output.
$8,500. Everything included.
One week. Four deliverables.
A findings presentation.
And thirty days later — I come back.
No retainer to start.
No ongoing obligation.
No proposal before a conversation.
Half on signing. Half when I present the findings.
Fixed fee. No surprises.