UI/UX Design Sprint Statement of Work Template

Count everything. A deliverable a client cannot count is a deliverable a client can expand.

1. 2.1A facilitated kickoff and mapping workshop (up to 4 hours, up to 6 client participants) producing an agreed sprint question and target user.
2. 2.2Lightning demos and solution sketches consolidated into one storyboard covering up to 2 user flows.
3. 2.3A clickable high-fidelity Figma prototype of up to 12 screens covering the storyboarded flows.
4. 2.4Five moderated remote usability sessions (45 minutes each) with participants recruited to the agreed screener.
5. 2.5A findings readout: session highlights, issue severity table and recommended next steps, delivered as a Figma page and a 45-minute presentation.

Name what the engagement does not include. These are the lines your PMs will cite most often.

1. 3.1A design system, component library or production-ready UI specifications.
2. 3.2Screens or flows beyond the two storyboarded flows.
3. 3.3Participant incentives and recruitment platform fees, which are passed through at cost.
4. 3.4Brand identity, illustration, motion design and copywriting beyond interface microcopy.
5. 3.5Development, technical feasibility studies and engineering estimates.
6. 3.6Additional rounds of user testing after the findings readout.

The storyboard includes one consolidated revision round before prototyping begins. The prototype includes one round of changes after internal review and before user testing. Changes after testing are captured as recommendations in the readout rather than applied to the prototype.

Acceptance needs a measurable test and a window. Without both, delivery never formally ends.

1. 5.1The sprint question and target user are agreed in writing at the end of the kickoff workshop.
2. 5.2The prototype covers every step of the approved storyboard and runs in Figma's presentation mode without broken links.
3. 5.3Five sessions are completed, or rescheduled within the sprint window if a participant does not attend.
4. 5.4Delivery of the readout completes the engagement.

Tie each dependency to a date so a late input has a known effect on the schedule.

1. 6.1A client decision maker attends the kickoff and storyboard sessions and can approve direction on the spot.
2. 6.2The client shares existing research, analytics and brand assets before kickoff.
3. 6.3Recruitment criteria are agreed within two business days of kickoff so sessions can be booked in time.
4. 6.4Feedback is consolidated by one named client contact.

Adding a flow, screens beyond 12, extra test sessions, a second sprint question or production UI work is a change. The studio will propose a change order within one business day stating the added work, hours, cost and effect on the sprint calendar. Because sprint calendars are tight, approved changes may extend the sprint by whole days.