03Engagements
Three engagement shapes, designed to be entered at whichever point matches where the business actually is. Most clients start with a Blueprint. Some already know what they need built. A few need the senior capability more than they need another project.
A fixed-scope diagnostic and design engagement.
Most transformation programs fail before anyone writes code, because the organization commits to a set of tools before it has agreed on how it wants to operate. The Blueprint exists to make that agreement explicit, in writing, with the trade-offs visible and the sequence argued through.
We work across leadership, operations, engineering, finance, and the field, because the gap between how a business believes it operates and how it actually operates is usually where the money is. The output is a document leadership can act on and a roadmap a delivery team can start from.
Best when
Systems have multiplied, ownership is unclear, or leadership needs a credible transformation plan it can fund and defend.
You leave with
A target operating model, systems and data architecture, risk register, AI opportunity map, and a prioritized 90-day roadmap set inside a twelve-month arc.
Structured interviews from the executive floor to the field. Full system, integration, and license inventory. Data flow and ownership mapping. Access and security review.
Where the operating model and the systems disagree. What the status quo costs in time, risk, rework, and forgone capacity. What is genuinely urgent versus merely annoying.
Target operating model. Systems and data architecture. Identity and governance model. AI opportunity map scored on value and feasibility. Build, buy, and consolidate calls with reasoning.
A sequenced plan with owners, dependencies, and investment ranges. An executive readout built to survive questions from the people who will fund it.
Four to six weeks
Fixed fee, fixed scope
Access to people, systems, and numbers
A build, or a plan you run yourselves
A senior delivery team, working in increments that stand alone.
This is the work. Integrations, data foundations, custom applications, automated workflows, executive reporting, and applied AI, all built into production, adopted by the people who have to use them, and handed over in a state someone else can operate.
We work in increments that each deliver something usable on their own, so the business is never holding a half-finished platform waiting on a distant go-live. Adoption is part of delivery rather than a phase that happens afterward, because a system nobody uses is indistinguishable from a system that was never built.
Best when
The direction is clear, but the business needs senior builders who can work across platforms, data, operations, and the field at the same time.
You leave with
Integrated systems in production, governed data, custom applications, automated workflows, executive visibility, documentation and runbooks, and an adopted way of working.
Identity, environments, the canonical data model, and the integration backbone. Unglamorous, and the reason everything after it goes quickly.
Systems joined to the backbone in dependency order. Data reconciled and remediated as it moves. Manual handoffs replaced with instrumented ones.
Custom applications and automation for the work no platform covers. Reporting and metric governance. Applied AI where it has been shown to earn its place.
Training with the people doing the work, not just their managers. Runbooks, monitoring, named internal owners, and a handover that assumes we leave.
Sized to the program
Increment-based, scoped per phase
Senior practitioners across the needed disciplines
Documented, monitored, and operable without us
An ongoing senior capability, retained monthly.
Growing capital-program firms reach a point where technology decisions need a consistent owner, and the two available answers are both bad: let decisions accumulate without one, or hire a full internal function years before the business can justify it.
The Fractional Transformation Office is the third answer. Senior technology leadership, architecture, platform stewardship, applied-AI delivery, vendor management, and roadmap governance, held by people who already know your systems because they helped build them, at a fraction of the cost of the department it replaces.
Best when
Growth is outpacing internal capacity and technology decisions need a consistent senior owner who is accountable for outcomes rather than tickets.
You leave with
Technology leadership, platform stewardship, applied-AI delivery, vendor and contract management, security and compliance liaison, and continuous roadmap execution.
Working sessions with the teams. Delivery on the active roadmap. Decisions made and recorded rather than deferred.
Executive review against the roadmap. Spend, vendor, and license position. Risk and security posture. What changed and what it cost.
Roadmap reset against where the business is actually going. Architecture review. Build, buy, and consolidate decisions revisited with real usage data.
A named senior owner for technology decisions, reachable when something breaks or a client asks a question nobody internally can answer.
Ongoing, reviewed quarterly
Monthly retainer
Leadership, architecture, delivery, governance
Hand off to an internal team when you are ready
How we price and staff
Transformation work has a reputation for open-ended scope and open-ended invoices. We work against that reputation deliberately.
Diagnostic and design work is fixed fee, because we know what it takes. Build work is scoped per increment, because pretending to price a long, discovery-dependent delivery up front is how both sides end up unhappy.
The people in the room during the pitch are the people doing the work. We do not staff engagements with juniors learning the industry at your expense, and we do not sell a partner and deliver an analyst.
Some engagements need depth we do not carry: a specific platform, a regulatory domain, a hardware environment. We bring in a specialist from our network and say so, rather than learning it slowly on the invoice.
Every increment delivers something the business can use whether or not the next one is funded. You are never holding a half-built platform waiting on a distant go-live to get value.
Documentation, runbooks, monitoring, and named internal owners are part of the deliverable rather than a phase that gets cut. An engagement that leaves you dependent on us is a failed engagement.
The Transformation Office is explicitly designed to hand off to an internal team when the business is ready to carry it. We will tell you when we think that point has arrived.
Tell us where the business is, and we will tell you which of these it needs.
Book a working session