Qualify first7–10 weeks
Experience Strategy
For leadership funding five roadmaps that contradict each other, because the wrong roadmap is more expensive than a slow one.
- “We have five products and they feel like five different companies.”
- “Every department is building its own app.”
What you get
- 01Current-state and future-state ecosystem maps
- 02Experience diagnostic report with prioritised gaps
- 03Problem statement and opportunity framework
- 04Prioritised portfolio roadmap — including what you will deliberately not build
Not included
- Interface design
- Implementation of any recommendation
- Decisions we are not given the authority to influence
What you bring
- A sponsor with decision rights, confirmed in the Diagnose phase
- Leadership in the room at each gate — this is not a document engagement
- The business metric the strategy is expected to move
What should change
The roadmap stops being a wish list
Measured by
Initiatives killed on evidence
Departments stop duplicating
Measured by
Overlapping builds consolidated
How it works
- 1
Fit check
Seven questions: the problem, who approves, budget, access to users, timeline, sector, and what it could lead to.
- 2
Your result
You see it straight away. A good fit: send it and we reply by email to arrange a first conversation. If not, it names what needs to change first, or a smaller fixed-scope start.
- 3
Priced, then started
Priced after the fit check, in a written proposal you approve before anything is charged. Kickoff is days 1–2.
- Who’s on it
- Experience Strategist (lead), UX Researcher, Service Designer, partner oversight at every gate · Experience squad
Your first 14 days
- Days 1–2Kickoff: objectives, success criteria, decision-maker map, escalation pathKickoff document, signed
- Days 3–5Access: data, analytics, systems, stakeholders, existing researchAccess log with owners and dates
- Days 5–7Working agreement: cadence, review protocol, approval authority, response times both waysWorking agreement
- Days 7–10Immersion: context absorption, constraint capture, assumption registerAssumption register
- Days 10–14First checkpoint: early observations, confirmed scope boundary, risks raisedCheckpoint note, acknowledged in writing
Why can’t I buy this online?
This work affects decisions above any single project, so we check fit first. It’s never sold through checkout.
After this
Service Design or Product UX/UI, when the gates are run with the client in the room.
Qualify first8–14 weeks for one service line
Service Design
For an organisation whose app is fine and whose customers still complain.
Priced after the fit check
Configure6–8 weeks focused
Product UX/UI
For a team with a decided direction and blocked developers.
SAR 63,000–90,000· Indicative