Every engagement follows the same four-stage rhythm. Documented, defensible, and designed to make the work depend on the method rather than the heroics.
Most boutique advisory firms run engagements as bespoke processes shaped by the lead partner's preferences. The result is brilliant when the partner is in form and inconsistent when they are not. Bodenhamer & Co. takes a different view: the method is the firm's most important asset, because the method is what allows a deliberately small senior team to deliver work at the standard a much larger firm would require.
Each stage below has documented inputs, defined deliverables, and explicit acceptance criteria. The same method runs a Strategy Sprint, structures the diagnostic phase of a Build Engagement, and shapes the rhythm of a Fractional Advisor retainer. Operators see the method working from the first conversation onward.
Most consulting engagements waste the first week on briefings, deck-reading, and orientation calls that produce surface familiarity rather than operational understanding. The firm runs the operational read differently. The first week is structured access to the operation itself — the systems, the data, the people doing the work.
Direct conversations with operations, finance, sustainability, IT, and field leadership. Review of current systems documentation, vendor contracts, recent operational reports, and live operational data samples under NDA. Where geography permits, time on site at one or two representative properties or assets. The objective is to understand the operation as the people running it understand it, before forming any diagnostic position.
A working operational map — not yet a roadmap — covering the systems landscape, the data architecture (such as it exists), the operational workflows in use, the regulatory pressure points, and the team capability and constraints. This map is the foundation for everything that follows. It is also shared with the client at the end of the week, so the diagnostic stage starts with shared facts rather than divergent assumptions.
The diagnostic stage is where the firm produces its actual point of view on the operation. It is the part operators are paying for — the synthesis of operational reality, technical possibility, and honest constraints into a defensible position on what the operator should and should not do.
The firm's senior team works through the operational map produced in Stage 01 and identifies, for each operational pain point: whether AI or connected systems will produce real value, what value (quantified where possible), what the data foundation requirements are, what the realistic time-to-value is, what the implementation risks are, and whether the operator's current organisational capability can absorb the change.
Crucially, this stage explicitly identifies what the operator should not do — vendor pitches that should be declined, AI applications that are marketing rather than substance, and integrations that should wait until prerequisite data foundation is repaired.
A draft diagnostic position covering the firm's reading of the operation, the categorised list of opportunities, and the explicit list of false trails. This draft is reviewed with the client before becoming a roadmap, because the diagnostic must reflect operational reality the client recognises.
The roadmap is the deliverable operators take to their boards, their CFOs, their existing vendors, and their internal teams. It must be defensible without the firm in the room to interpret it. That requirement shapes how the firm builds it.
Each prioritised initiative is documented with: a plain-language description, the operational outcome it delivers, the data foundation prerequisites, the technology and vendor decisions implied (with build / buy / integrate calls), realistic cost ranges and complexity estimates, time-to-value windows, and explicit dependencies on other initiatives. Initiatives are sequenced into phases — typically a 90-day, 12-month, and 24-month horizon — with clear gating criteria between phases.
Visionary multi-year transformation narratives. Speculative AI applications without operational grounding. Vendor recommendations the firm benefits from financially — the firm has no reseller relationships and no vendor commission structure. Generic best-practice content that could appear in any consultant deck.
Written document, typically 18–28 pages depending on portfolio complexity. 90-minute walkthrough call with key stakeholders, recorded for distribution to internal teams who could not attend. 30 days of email follow-up access for clarification questions. The roadmap is the operator's property and can be shared with internal teams, vendors, and advisors without restriction.
The end of a Strategy Sprint is not necessarily the beginning of a Build Engagement. The firm is structurally indifferent to which path the operator chooses, because the firm's pricing model does not depend on follow-on work to make the initial engagement profitable.
The priority initiative from the roadmap converts into a Build Engagement with fixed scope, fixed price, and fixed timeline. Stage 01 work is not repeated — the operational read carries forward, and the engagement starts in the implementation phase. Build Engagements run six to ten weeks typically, with weekly written progress updates and a mid-engagement review checkpoint.
The roadmap is structured so internal teams or external vendors can execute against it without further dependence on the firm. Build, buy, and integrate decisions are documented with enough specificity that the operator can run a vendor procurement directly. This is the deliberate design — the roadmap must work as a standalone artefact, not as a teaser for follow-on engagement.
Conversion to a Fractional Advisor retainer is the most common path for operators with good internal execution capability who want continued senior strategic support. The retainer relationship typically begins within 30–60 days of sprint completion, allowing the operator to evaluate internal capacity before committing.
Working document produced in Stage 01 covering systems, data, workflows, regulatory pressure, and team capability. Shared with client at end of week one.
Draft synthesis covering opportunities, false trails, and prerequisite work. Reviewed with client before becoming the roadmap.
Final 18–28 page deliverable with sequenced initiatives, build / buy / integrate calls, and honest cost and complexity estimates.
90-minute final session recorded for distribution to internal stakeholders who could not attend live. Operator owns the recording outright.
A short fit call is enough to determine whether the firm's method matches the operational reality you are working in. The firm will be candid about fit either way.