Configure4–6 weeks
Research Sprint
For a team about to fund a build on assumptions, because research is the cheapest way to find out you were about to solve the wrong problem.
TanweelUX/UI case study · 2024See the case study - “The board wants proof before we fund the redesign.”
- “We think we know the problem but cannot prove it.”
- “We are about to commit budget and nobody has spoken to a user.”
What you get
- 01Research plan with questions, hypotheses and method rationale
- 02Discussion guides and test protocols in Arabic and English
- 03Moderated sessions with recruited participants, recorded and transcribed
- 04Findings report with severity-ranked issues and a full evidence trail
- 05Personas or behavioural segments with JTBD statements
- 06A working readout that produces the next scope, not a presentation
Not included
- Design or wireframes of any kind
- Participant incentives (passed through at cost)
- Quantitative survey work at statistical significance
- Ongoing research operations
What you bring
- Access to real users, or written agreement that Pixilated recruits with budget
- Existing data: analytics, support tickets, prior research, complaint logs
- The business metric this research is expected to move
What should change
Decisions stop being opinion
Measured by
Recommendations adopted per release
The next scope writes itself
Measured by
Readout converts to a defined brief
How it works
- 1
Configure it
Set it up here and add it to your plan.
- 2
Written scope
Within 48 hours: tasks, milestones, named roles and a delivery date.
- 3
Approve, then start
You approve the scope and price before anything is charged.
- Who’s on it
- UX Researcher (lead), synthesis researcher, Arabic-native moderator where required · 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
Is the price final?
Not yet. Our prices are indicative while we finalise them. You get the confirmed price in writing before you pay anything.
When do we pay?
Your written scope states the price and the deposit. Nothing is charged until you approve it.
After this
Product UX/UI or Experience Strategy — the readout is designed to produce the next scope.
Configure6–8 weeks focused
Product UX/UI
For a team with a decided direction and blocked developers.
SAR 63,000–90,000· Indicative
Qualify first7–10 weeks
Experience Strategy
For leadership funding five roadmaps that contradict each other.
Priced after the fit check