AI Scoping

Know what you're building before you build

The bridge between Audit and Build. A structured investigation in 6 to 36 weeks to anchor each feature in a real use case.

Need a diagnostic first? Discover our AI Audit.

45%

average budget overrun on IT projects

4

investigation tracks

6-36

weeks of scoping

Scoping is won in business workshops

A structured investigation across 3 dimensions to anchor each feature in a real use case

Business need

  • Explore real workflows and the client's business processes
  • Identify operational constraints that condition scenarios
  • Prioritize high-impact use cases

Validated user journeys, prioritized expectations

UX

  • Confront interface hypotheses with concrete scenarios
  • Identify friction points and adoption conditions
  • Produce wireframes tested with users

Validated UX/UI mockups, optimized journeys

Technical

  • Map existing tools, databases and systems
  • Assess API availability and data quality
  • Define target architecture and identify risks

Documented ecosystem, prioritized API scenarios

Why scope before building

Avoid 45% budget overrun

Scoping identifies traps before they cost. Each block is costed, each risk anticipated.

Specify, don't guess

User stories, mockups and architecture validated with users. No bad surprises at delivery.

Align all stakeholders

Business, technical and management share the same vision. The specifications document builds consensus.

Ready for Build or tender

At the end of scoping, you have everything to launch development or consult service providers.

4 investigation tracks

Track 1

Functional scoping

  • Field interviews
  • Functional mapping
  • Wireframes & UX/UI mockups
PPT

Track 2

Technical feasibility

  • Ecosystem & API
  • Data sources
  • Architecture & risks
PPT

Track 3

Cost determination

  • Costed functional blocks
  • Realistic MVP phasing
  • Development schedule
Excel

Track 4

Specifications document

  • User stories
  • Technical specifications
  • Ready for Build or tender
Word

Typical schedule & deliverables

Indicative duration: 6 to 36 weeks depending on scope complexity

W1
W2
W3
W4
W5
W6
W7
W8

T1 - Functional scoping

W1-W4

T2 - Technical feasibility

W2-W5

T3 - Cost determination

W6-W7

T4 - Specifications document

W7-W8
Delivery

At the end of scoping, the client has:

Functional mapping & validated UX/UI mockups

PPT

Technical architecture & feasibility analysis

PPT

Block costing & development schedule

Excel

Specifications document ready for Build or tender

Word

Need a diagnostic first?

Discover our AI Audit

3 audit formats to diagnose your opportunities and prioritize your AI investments.