AICES is the operating method. Five disciplined phases, practiced in order. Each phase has its own rhythm and its own output. Nothing moves forward until the phase before it is documented, discussed, and signed off.
Every engagement starts here. Before we recommend anything, we have to understand what you actually have, not what you wish you had, not what the vendor told you was deployed, not what an organizational chart implies.
Assessment means getting into the environment. Reading your documentation. Talking to the people running it. Looking at the tickets, the dashboards, the change calendar, the audit findings. Understanding the history of decisions that got you here.
Critically, we document against your standard, not an external best-practice framework first. If your organization has its own architecture principles, service management maturity model, or governance expectations, we measure against those. External benchmarks come in the next phase.
The Assess phase is also where we separate the urgent from the important. Every environment has known fires. Part of assessment is triaging, which fires are genuinely burning the building, which are burning but contained, and which are smoke without flame.
Now we look outward. With current state documented, we investigate what peer organizations are doing, what the industry considers current best practice, and, critically, what's actually working in production as opposed to what vendors and analysts claim.
Investigation happens at three layers. First, peer benchmarking: what are organizations of similar size, industry, and maturity actually doing with similar problems. Second, framework alignment: how does the current state and candidate approaches map against relevant standards (NIST, HITRUST, ITIL, specific regulatory regimes). Third, vendor and tool landscape: what's actually available, what's credible, what's marketing.
This is the phase where we pressure-test assumptions. Clients sometimes arrive with a preferred answer already in mind. A disciplined investigation phase ensures the answer is the right one, not just the first one.
The output isn't a survey of the market. It's a defensible shortlist of viable paths forward, with the tradeoffs made explicit for each.
Good recommendations that don't land are worthless. The Communicate phase is where we translate the work of the first two phases into material that decision-makers will actually read, absorb, and act on.
This means different outputs for different audiences. The board needs a two-page narrative, not a fifty-page assessment. The CIO needs a roadmap with phasing and dependencies. Operating leaders need implementation detail. The CFO needs the financial model. We produce one body of analysis, multiple packages, each tuned to how its audience thinks and decides.
We also communicate in person, not just in writing. Every significant recommendation gets a live conversation with the decision-maker. Questions surface. Priorities shift. The recommendation evolves. This is the phase where advisory-only engagements typically conclude.
Most importantly, we communicate what's honest. If the answer is "your environment is in better shape than you think and the biggest risk is elsewhere," we say that. If the answer is "this is going to take longer and cost more than anyone wants to hear," we say that too. You hired us for the outside view.
Execute is the phase that separates AICES from advisory-only firms. When an engagement calls for it, we own delivery, not just the plan that leads to it.
In execution, we run the work. We stand up the project structure, drive vendor selection and management, coordinate internal stakeholders, manage the schedule, own the risk register, and deliver the outcome. We partner with your team where you have capacity and capability, and we bring our own where you don't.
Delivery engagements are typically fixed-scope against a well-defined outcome. Network modernization across X sites. ITSM implementation. HITRUST readiness program. Post-close M&A technology integration. Each engagement is shaped so that "done" is unambiguous.
Not every engagement needs execution. Enterprise clients with strong delivery capabilities often need only the first three phases of AICES. Smaller and mid-market clients often need the full run. We shape the engagement to what you actually need, not to maximize our billable hours.
Engagements end, but the relationship doesn't have to. Support is the phase that says we're still available when you need us, on whatever terms work for both sides.
Support takes several forms. A retainer for ongoing advisory. A standing offer to jump in during major incidents or audits. Quarterly check-ins on strategic progress. Targeted, time-boxed work to address new situations as they arise. Participation in committees or governance forums where your team wants a senior outside voice.
For clients who've completed a delivery engagement, support typically includes post-go-live stabilization, being on call during the first 30 to 90 days after production cutover to handle the unknowns that inevitably emerge. For advisory clients, support is typically a retainer or as-needed structure that keeps us available without a full new engagement.
We don't push Support as an upsell. We offer it as an option, and clients take it or not based on whether it creates value. Many of our longest relationships are with clients who use us for two or three hours a month, not fifty.
Not every engagement needs every phase. Advisory engagements give you the first three moves; delivery engagements run the full five. Pick the model that fits the problem, not the model that maximizes our hours.
Most consulting goes wrong at predictable points: recommendations that don't fit current state, analysis that never reaches decision-makers, implementations that stall after the consultant leaves. AICES is structured specifically to avoid those failure modes.
Most good engagements start with a thirty-minute call. No slides, no pitch, just a conversation about what's on your plate.
Start a conversation →