What Implementation Consulting Actually Covers

Implementation consulting is part architecture, part program management, part senior engineering, and part political work. The consultant owns the question: "what has to be true for the first AI feature to be live, valuable, and maintainable in 90 days, and what has to be true for the second one to be cheaper than the first?" That question survives every project review.

• Translate the strategy doc into a sequenced delivery plan with named owners, milestones, and exit criteria per phase
• Pick the first feature scope so it is narrow enough to ship in 8-12 weeks but valuable enough to defend in a board update
• Make the architecture decisions that protect later phases: model routing, evaluation harness, retrieval, observability, secrets, billing instrumentation
• Choose vendors and tooling where the contract terms are reversible and the lock-in is bounded
• Stand alongside the internal team during build, reviewing PRs on the critical path, unblocking integration questions, killing scope creep
• Define done in measurable terms so the project actually closes rather than sliding into a permanent maintenance phase
• Instrument the second initiative while the first is shipping, so there is no flat-footed delay between waves
• Write the program review, the board update, and the post-mortem so the leadership team has clean artifacts after launch

When You Need Implementation Help, Not More Strategy

The trigger is a roadmap that is stuck. If the deck has been blessed and the team still cannot decide where to start; if a vendor was bought six months ago and nothing has been integrated; if a pilot is technically live but nobody uses it; if the head of engineering keeps adding AI to the next quarter and never the current one, the missing ingredient is implementation leadership, not more analysis.

• You already have a strategy document but the engineering org cannot tell you what they would build first
• You have bought a vendor or platform whose integration has stalled past its planned go-live
• A pilot is in production but adoption is under 10% of the target user base and no one owns fixing that
• Your team is shipping prompt-engineered demos, but nothing has an evaluation harness, observability, or a cost ceiling
• You are about to engage a Big Four implementation partner and want an independent senior on your side of the table
• You have three AI features in flight, no shared architecture, and the cost-per-call is climbing without anyone noticing
• The first phase of a transformation program shipped slowly, expensively, and you need a senior practitioner to diagnose why before phase two starts
• A regulated launch is coming and the engineering team has no plan for evaluation, audit trail, or red-teaming

How Implementation Consulting Differs From Strategy and From Engineering Hire

Strategy consultants leave at the roadmap. Engineering hires take 4-6 months to source and 3-6 months to ramp. Implementation consultants own the period between those two states. The clear separation matters because each of the three has different incentives, different deliverables, and different risk shapes.

• Strategy consultant deliverable: a deck, an opportunity matrix, an ROI model, and a roadmap. Exit at signoff
• Implementation consultant deliverable: a live AI feature in production, an evaluation harness, a runbook, and a trained team. Exit at launch plus stabilization
• Engineering hire: hands-on building, full-time, 2+ year horizon, line management as team scales. Right answer once the implementation pattern is proven
• Big Four implementation partner: 15-50 staff, $1M-$5M for the first wave, brand cover, slow internal handoff
• Independent implementation consultant: one to three senior practitioners, $150K-$500K for the first wave, fast turnaround, native handoff to internal team
• Pick strategy work when the question is what to do; pick implementation when the question is why the doing has not started
• Pick a Big Four when the scope is genuinely 18+ months across business units; pick an independent when the scope is one to three quarters and ship-focused

Pricing and Engagement Shapes in 2026

Implementation engagements are usually structured as a monthly retainer with a defined hour or day band, sometimes with a fixed-fee delivery milestone bonus. Pure day rate is rare for implementation because the consultant needs reserved capacity to be reliable for the team. Pure fixed-fee is rare because the scope is too dynamic in the first weeks.

• US day rate: $2,500-$5,500/day for senior implementation work, with AI-specific delivery clustering at $3,500-$5,000
• US monthly retainer (2-3 days/week): $35,000-$70,000, plus expense pass-through for travel and tools
• US monthly retainer (4-5 days/week, embedded interim mode): $60,000-$120,000
• UK day rate: GBP 1,200-2,000/day for senior implementation in London and Manchester
• UK monthly retainer (2-3 days/week): GBP 18,000-32,000
• EU day rate: EUR 1,500-2,500/day in major hubs
• Fixed-fee 90-day delivery sprint with one feature in production: $120K-$280K total in the US, scoped tightly with milestone payments
• Project costs that show up in vendor proposals: production RAG application $75K-$250K over 8-16 weeks; full MLOps platform build $200K-$600K over 3-6 months. An implementation consultant either replaces or sits on top of these engagements depending on the team
• Red flag: a quote that does not name the deliverable, the elapsed time, the percentage of consultant time on critical-path versus standby, or the exit criteria

What the First 90 Days Looks Like

The 90-day window is the industry standard because it is the shortest period in which you can land one working AI feature, build the evaluation and observability backbone reusable by the next four, and produce the board update that funds phase two. A serious implementation engagement is structured around hitting that window, not around extending the consultant relationship indefinitely.

• Week 1-2: delivery diagnostic. Read the strategy doc, audit the existing data, models, and vendor contracts, interview the engineers, identify the integration bottleneck
• Week 2-3: scope the first feature to fit a 60-day build window, define the evaluation contract, name the launch metric and the kill criterion
• Week 3-4: architecture decisions documented in writing: model choice, retrieval pattern, observability stack, secrets handling, billing instrumentation, fallback policy
• Week 4-8: build. Consultant is in the standups, reviewing critical-path PRs, killing scope creep, unblocking vendor and infra questions
• Week 6-8: evaluation harness running on a real dataset, with regression alerts wired to the team Slack
• Week 8-10: limited beta to a controlled user segment, instrumentation reading green, cost-per-call within the planned envelope
• Week 10-12: launch, post-launch monitoring, a documented runbook, and a written program update for the board
• Week 12+: optional stabilization tail at reduced hours; phase two scope confirmed and either handed to the internal team or extended into a second retainer

Concrete Deliverables From an Implementation Engagement

Insist on the artifacts being named in the engagement letter. Implementation engagements that lack a written deliverable list drift into ongoing advice and never close.

• One AI feature live in production, with measurable business outcome verified against the agreed launch metric
• Evaluation harness running on a real dataset, with regression and drift alerts wired to the team
• Architecture decision record covering model, retrieval, observability, evaluation, secrets, billing, and fallback policy
• Runbook covering on-call, incident triage, retraining or prompt-version rollback, vendor escalation paths
• Integration documentation for upstream and downstream systems, written for the engineer who joins after the consultant has left
• Cost model with actual cost-per-call measured, projected at planned and worst-case usage
• Vendor scorecard updated with how the chosen vendor performed in delivery versus the sales promise
• Hiring plan if the next wave requires headcount, with job descriptions and target compensation
• Phase-two scope document scoped to the next two quarters with phase gates
• Post-launch board update written and reviewed with leadership

Common Implementation Failure Modes

Most failed implementations are diagnosable in the first 30 days and predictable in the first 30 minutes of the sales call. The patterns repeat across companies and across consultants. Use the list as a checklist before signing and again 30 days in.

• Scope creep that turns a 6-week build into a 6-month one because no kill criterion was set up front
• Architecture decisions that lock in the wrong vendor: long-term contracts signed before the evaluation harness was running
• No evaluation harness, so quality drift is invisible and the model regressions are discovered by the customer
• Demo-driven development: features built to impress in a board meeting but never tested against real user workflows
• Production handoff without docs, leaving the internal team unable to maintain the feature within 30 days
• Pilot trap: the AI feature ships to a controlled cohort and never expands because nobody owns the rollout plan
• Cost surprise: the model and infra bill outpaces the value because there is no billing instrumentation tied to the feature
• Vendor capture: the implementation consultant has a referral fee with the vendor, so the architecture quietly entrenches lock-in
• Integration paralysis: the AI works in isolation but the connection to CRM, billing, or auth was never scoped
• No second wave: the consultant leaves after launch, the team has no phase-two scope, and momentum collapses

How Mahmoud Runs an Implementation Engagement

The work is hands-on by design. The point of hiring a senior independent for implementation is that the consultant is in the codebase, in the standups, and in the architecture reviews, not coordinating from a distance. Engagements are structured around a named feature shipping in 90 days, with the engineering team learning the patterns that make the second feature cheaper.

• Embedded with the engineering team for the duration: standups, PR review on the critical path, architecture decision records co-authored with the tech lead
• No vendor relationships, no resale, no commission, every tool choice is purely a fit call against the engagement evaluation criteria
• Capped at three concurrent implementation engagements so reserved capacity for your team is real
• Written deliverables shared incrementally throughout the engagement, not stockpiled for a final readout
• Engagement letter names the feature, the launch metric, the kill criterion, the exit date, and the optional stabilization tail
• Comfortable handing the system to your team and walking out at 90 days. The handoff is the product

FAQ