Step 1 Advisory Decision clarity

Advisory for AI adoption: decide what to do before you buy, build, or train

Use this route when the team needs a clear decision: where AI fits, what the first safe pilot should be, and whether the next step is Advisory, Training & Workshops, or Implementation.

Best for founders, operators, school leaders, and programme owners who want a practical decision process before committing budget, tooling, or team time. Fees quoted in GBP, USD, or EUR after scope confirmation.

Clarify priorities, constraints, and ownership before the work turns chaotic.
Choose the smallest useful pilot instead of trying to roll out everything at once.
Leave with a clear recommendation on the next step: more Advisory, Training & Workshops, or Implementation.

Start with the same 30-minute intro call used across the site. We’ll use it to confirm fit, scope, and whether the next step should be a diagnostic, a stress test, or ongoing support.

Quick route summary

Best fit when…

Advisory is usually the right starting point when the team needs a decision, not just more information.

  • You have several AI ideas, but no clear priority order
  • Stakeholders are not aligned on risk, data, ownership, or timing
  • You need a practical first pilot, not a vague brainstorm

You leave with…

The output is built for action: a recommendation, scope boundaries, and a next-step path.

  • A clearer route: Advisory, Training & Workshops, Implementation, or a staged combination
  • Decision notes, guardrails, and a shortlist of realistic next actions
  • Optional follow-up support if the team needs execution rhythm

Choose the right advisory format

Leadership diagnostic

A focused remote session to map the decision, key constraints, and the safest useful next move.

  • Session: 60–90 minutes
  • Output: decision summary, priority map, and next-step recommendation
  • Best for: teams that need clarity this week

Programme / Product Stress Test

A fast paid validation pass for a training concept, internal tool idea, or rollout plan before you commit resources.

  • Inputs: intro call + any draft materials + constraints
  • Output: scorecard, risk notes, and a recommended path
  • Timing: typically 3–5 working days

Advisory sprint / retainer

Ongoing support when the route is clear but the team still needs structure, accountability, and decision support.

  • Weekly rhythm: priorities, blockers, and follow-through
  • Artefacts: decision logs, rollout notes, stakeholder briefs
  • Best for: teams moving from decision to execution

Not sure this is the right route?

That is exactly what the intro call is for. We can quickly redirect you if another route fits better.

What happens after the first conversation

1. We confirm fit

In the intro call we quickly clarify your context, urgency, decision pressure, and what success should look like.

2. We choose the smallest useful step

That may be a diagnostic session, a stress test, or a short advisory sprint — not the biggest package by default.

3. You leave with a route

The output should make the next move obvious: continue with Advisory, move into Training & Workshops, or switch to Implementation.

4. You decide how far to go

You can stop after clarity, continue into delivery, or use ongoing advisory only if the team genuinely needs that rhythm.

Payment & contracting

International payment options can include invoices/card payments (Stripe), bank transfer (Wise), or other procurement-friendly methods. Contracting can be arranged via MVP Lab if preferred.