Practical Guide

Most AI transformation timelines look like this: three months to select a consulting firm, six months for the strategy engagement, three months to select an implementation partner, six to twelve months for the first build. Total: 18–24 months before anyone in the organisation uses AI-powered software.

This playbook compresses that to 90 days. Not by cutting corners — by eliminating the structural handoffs that waste time. Here's the week-by-week plan.

Phase 1: Assessment (Days 1–14)

Week 1: Internal Audit

Start with what you already know but haven't documented. This week is about creating an honest inventory of where your organisation actually stands.

Catalogue every SaaS subscription in your organisation — CRM, ERP, HR, analytics, project management, communication. Most mid-market companies are spending $50K–$200K per month on subscriptions, many underutilised. Pull the billing data. You'll find tools nobody uses, overlapping capabilities, and integrations that don't exist.

Identify the top five operational pain points that consume the most manual effort. Not the ones your team complains about loudest — the ones that cost the most in hours, errors, or missed revenue. Talk to department heads. Ask a specific question: "What takes your team the most time that a machine could do better?"

List the decisions your leadership team makes quarterly that should be made weekly — or continuously. Pricing adjustments based on market conditions. Inventory rebalancing based on demand signals. Customer risk scoring based on behavioural patterns. These are the decisions that AI transforms from periodic guesswork into continuous, data-driven action.

Document which processes still run on spreadsheets, email, or manual handoffs. Every spreadsheet-driven process is a candidate for automation. Every email-based approval workflow is a candidate for a system. Every manual handoff between departments is a candidate for integration.

Week 2: External Intelligence

Research 2–3 platforms that combine business intelligence with software delivery capability. Evaluate based on: time to first value, ongoing intelligence, and total cost of ownership. This is a new category — most vendors offer one or the other, not both in a closed loop.

See XI running on a live demo company. Go to xts.xamun.ai — it's free and self-serve. Understand what continuous business intelligence looks like before you commit to anything. See how XI reads market signals, competitive movements, and operational data in real time. This isn't a demo video. It's a live system running on real data.

Schedule a Discovery session — $2,500, half a day, in your city or online. This is the single most important step in the entire playbook, because it replaces months of traditional consulting assessment with a concentrated, AI-powered diagnostic.

Before the Discovery: XI reads your business — market position, competitors, operational signals. It arrives at the meeting having already done the analysis that a consulting firm would take six weeks to produce.

During the Discovery: review the Opportunity Map, Found Budget, and Transformation Roadmap preview with your leadership team. This is the moment where abstract "AI potential" becomes specific, quantified opportunities tied to your actual business.

Phase 2: Strategy Lock (Days 15–45)

Weeks 3–4: AI CXO Certification

Engage a certified Xamun partner for a structured programme scoped to your organisation. This isn't generic AI training — it's a working session that produces deliverables your board can act on.

Full XI diagnostic runs against your business data. The system analyses your market position, competitive landscape, operational efficiency, and technology stack against industry benchmarks. The output is specific: here's where you're losing money, here's where AI creates value, here's the sequence.

Objectives confirmed with your leadership team. Not aspirational objectives — measurable ones. "Reduce customer onboarding time from 14 days to 3 days." "Automate 60% of compliance reporting." "Surface pricing opportunities that generate $500K in annual margin improvement." These become the governance metrics tracked after deployment.

Transformation Roadmap built, pressure-tested, and signed. The Roadmap sequences every build over 6–12 months, ordered by ROI. The highest-value item goes first. Every item has estimated story points, timeline, and expected business outcome.

First 45 days of XI access included — so by the time you subscribe, you already know the platform. You've seen what it surfaces. You've validated whether its intelligence is actionable. No vendor lock-in surprise.

Weeks 5–6: Subscription Scoped

Match story point allocation to your roadmap and appetite:

First sprint planned: the highest-ROI item from your Roadmap goes first. Not the easiest. Not the most politically convenient. The one that delivers the most measurable value — because early wins create organisational momentum.

Phase 3: First Build (Days 46–75)

Weeks 7–8: Specification and Design

XAMI (Xamun's AI) interviews stakeholders about the first build target. Not a requirements-gathering workshop that produces a 60-page document nobody reads — a structured conversation that produces a precise specification.

DesignStudio generates workflow diagrams, page designs, and user stories with acceptance criteria. Your team sees exactly what will be built — every screen, every interaction, every data flow — before a single line of code is written.

Your team reviews and approves the specification. Nothing is built until the spec is signed off. This is where scope creep dies: the spec IS the scope. Changes after approval are tracked, estimated, and explicitly agreed to. No surprises.

Weeks 9–10: Build and QA

Claude Code generates 70–80% of boilerplate and scaffolding code from the approved specification. This is not a prototype or a proof-of-concept — it's production-grade code generated from the signed-off specification.

Expert human engineers handle architecture, business logic, integrations, and edge cases. The AI accelerates the predictable parts. Humans handle the parts that require judgement, domain expertise, and the kind of systems thinking that makes software work in the real world.

SonarQube quality gates run on every module. Code quality, security vulnerabilities, and technical debt are measured and enforced automatically. Nothing ships that doesn't pass.

Human QA engineers test against acceptance criteria. The same acceptance criteria your team approved in the specification. Working software deployed to your infrastructure. Not a staging environment. Not a sandbox. Your infrastructure.

Phase 4: Governance and Loop (Days 76–90)

Weeks 11–12: Outcomes and Next Cycle

The Objective Governance Dashboard goes live — tracking whether the software achieved its business metric. Not vanity metrics like "user adoption" or "feature completion." The actual objective: did onboarding time drop from 14 days to 3? Did compliance reporting automation hit 60%? Did the pricing engine surface the projected margin improvement?

XI continues running: market signals, competitor moves, and operational data surfaced continuously. The intelligence doesn't stop when the first build ships. It accelerates, because now XI has deployment data to analyse alongside market data.

Second sprint planned based on what XI identifies plus what governance reveals. The loop is now running: intelligence → build → deploy → govern → intelligence.

This is the structural advantage. Traditional consulting is linear: assess, recommend, hand off, build, hope. The closed loop is continuous: every deployment generates data that improves the next decision.

What You Have at Day 90

Compare That to Day 90 with Traditional Consulting

The difference isn't marginal. It's structural. One approach is designed to deliver working software. The other is designed to deliver consulting engagements.

Common Objections

The Question Is Simple

The 90-day playbook isn't theoretical. It maps directly to Xamun's engagement model because the engagement model was designed to compress transformation timelines. Discovery replaces months of assessment. AI CXO Certification replaces the strategy engagement. The Software Factory replaces the implementation partner search and build phase. Objective Governance replaces the hope that deployed software actually delivers results.

Every step exists because the traditional alternative wastes time, money, or both.