Configure6–8 weeks focused
Product UX/UI
For a team with a decided direction and blocked developers, because a build without an interface specification becomes an argument conducted in code.
- “We are rebuilding the app and need the design.”
- “Our developers are blocked waiting for screens.”
- “We need an app, a rebrand, a website.”
What you get
- 01IA, sitemap and user flows agreed before a pixel is drawn
- 02Wireframes with real content structure, interaction notes and every state
- 03Full UI: component variants, all states, responsive breakpoints, RTL mirror
- 04Clickable prototype of the critical journeys
- 05Annotated specs, tokens, assets and interaction documentation
- 06QA checklist your engineers sign against at build
Not included
- Front-end or back-end implementation
- Research — either attached as a phase or signed off as assumption risk
- Brand identity creation
- Content production or copywriting beyond interface text
- Unlimited revision rounds — revisions are capped and named in the scope
What you bring
- A named decision-maker with authority to approve, not just to comment
- Technical constraints and platform decisions already made
- A review cadence with a named response time
What should change
Developers stop waiting
Measured by
Screens delivered against sprint plan
Rework falls
Measured by
Defects raised post-handoff
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
- Product Designer (lead), UX Researcher, UI Designer, UX Writer · 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
Design Systems, once the same components start being rebuilt by a second team.
Configure12–20 weeks, then a maintenance retainer
Design System Build
For an organisation buying the same design repeatedly.
SAR 118,100–168,800· Indicative