Websites, Stores and Search
Generative engine optimization: how to get cited by AI search
What generative engine optimization really is, what the research shows, and a step-by-step plan to get your pages cited by AI search.
Accessibility & UX
UI/UX Design Sprint
See and click through your website, app or portal in Figma before anyone writes a line of code.
Building first and fixing the design later is the slowest way to make software. In this sprint we turn your answers to a written questionnaire into a brief, sketch wireframes and design up to 8 key screens for desktop and mobile. You click through a working Figma prototype, refine it over two revision rounds, and hand your developers designs, a style sheet and a written handover report they can follow.
- Clickable Figma prototype of up to eight screens
- Desktop and mobile layouts for every screen
- Handoff with styles and components developers can follow
$4,225
15–25 working days
What it is
UI/UX Design Sprint is a short design project that produces a clickable Figma prototype of up to 8 screens for your website, app or portal. It includes a written brief on goals and journeys, wireframes, high-fidelity desktop and mobile designs, a style sheet of colors, type and components, two revision rounds and a written handover report.
Why businesses buy it
Changes are cheap in a design file and expensive in code. Yet many teams start building with only a rough brief, then rework screens once real users see them. A short sprint fixes that order. You agree goals and journeys in one written brief, see wireframes, then click through a realistic prototype on desktop and mobile. Colleagues and customers can react to it before any build budget is spent. When you are ready, your developers get designs, styles and a written handover report, so they build what you approved.
Problems this solves
Teams debate a new product without seeing anything concrete
A written brief sets out goals, users and key journeys. Wireframes for up to eight screens then give everyone the same picture to react to.
Building first and fixing the design later is costly
You get high-fidelity desktop and mobile designs and a clickable Figma prototype before any code is written. Changes happen in design, across two revision rounds.
Developers guess at colors, spacing and components
A style sheet sets out the colors, type and components used in the designs. A written handover report walks your developers through the files.
Nobody can click through the idea before committing to a build
The clickable Figma prototype links your screens into real journeys. We click through it on desktop and mobile before handoff, so you can show it to staff or customers.
A good fit if
You are planning a new website, app or portal and want to see it before building.
Your key journeys fit in up to eight screens, such as sign-up, a dashboard and a detail view.
You have a brand guide, or at least a logo and colors.
You have developers ready to build, or plan to hire them, and want clear designs to hand over.
Not the right fit if
You still need to define what a custom app must do and what it will cost. Start with a Discovery Sprint.
You need a logo and brand before any screens. See Logo and Brand Kit.
You want a website designed and built in one go. See Corporate Website or WordPress Business Website.
You need formal user testing with recruited participants. That is quoted through a Change Quote.
How it works
- You answer a written questionnaire on goals, users and key journeys, and we turn it into a brief.
- Wireframes for up to 8 screens map the layout and flow, and you confirm them before visual design starts.
- High-fidelity designs are made for each screen in desktop and mobile layouts, using your brand.
- The screens are linked into a clickable Figma prototype and clicked through on desktop and mobile.
- You review and refine the designs over two revision rounds.
- A style sheet is finished and handed over with a written handover report for your developers.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- Access to your Figma team by invite or a key you control, if you have one.
- Your brand guide, or your logo and colors.
- Your goals, users and the journeys to design.
- Examples of designs you like.
- One person who approves each round.
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Brand material, goals and examples checked, questionnaire answered.
Week 1
Written brief approved, screens and journeys agreed.
Week 1
Wireframes for up to 8 screens shared and confirmed.
Week 2
High-fidelity desktop and mobile designs and the clickable prototype built.
Weeks 2–3
Two revision rounds on the designs.
Week 3
Style sheet finished and handover report sent.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 15–25 working days | $4,225 |
What you receive at handover
- A written brief on goals, users and key journeys
- Wireframes for up to 8 screens
- High-fidelity designs for up to 8 screens, desktop and mobile
- A clickable Figma prototype
- A style sheet with colors, type and components
- A written handover report (building the designs in code is not included)
Expected benefits and how to measure them
- Helps your team agree on the product before money goes into code
- Can give developers a clear reference that cuts back-and-forth during the build
- Makes it easier to show the idea to investors, staff or customers
- Design questions during build
- Count the design questions and change requests developers raise, and compare with your last project.
- Time to sign-off
- Note how long stakeholders take to approve the screens compared with earlier projects.
- Prototype feedback
- When you show the prototype to staff or customers, record how many complete the key journeys without help.
Before you start: Write down how your last build project went: change requests, rework and how long approvals took. Use it as the comparison.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
There are no running costs. The sprint is paid once, and you do not need to buy tools for it. If you want to keep editing the files yourself, Figma has free and paid plans, and that choice is yours.
Ask about running costsCustom requirements
More than 8 screens, recruited user testing, illustrations or building the designs in code? Add a note at checkout for a written Change Quote. Very large projects use the Custom AI enquiry form instead.
Request a custom versionKeep it running
There is nothing to keep running. Once paid in full, the Figma files, prototype and style sheet are yours, and follow-up questions are answered during the support period. To build the designs, compare our website builds, or use a Discovery Sprint to get a fixed quote for a custom app.
How this compares
| Do it yourself | Hire a traditional agency | Upmark Labs | |
|---|---|---|---|
| Price | A design tool subscription and many hours of learning | A design phase priced after discovery | Ours is one fixed price for up to 8 screens, shown before you buy |
| Output | Static mock-ups that are hard to share | Designs, often without a clickable prototype | Ours delivers a clickable Figma prototype for desktop and mobile |
| Revisions | Endless tweaks with no end point | Agreed in the contract | Ours includes two revision rounds |
| Handoff | Screenshots sent to developers | A handoff to the agency's own developers | Ours hands over styles, components and a written handover report for any team |
Questions about this product
What do we get at the end of the UI/UX design sprint?
A clickable Figma prototype of up to 8 screens, with desktop and mobile layouts, plus the wireframes behind it and a style sheet of colors, type and components. You also get a written handover report for your developers. Once paid in full, the Figma files are yours to build from with any team you choose.
Does the design sprint include building the website or app?
No. The sprint ends with designs and a prototype, not code. That keeps it focused and lets you test ideas before paying for a build. To build a website from the designs, compare Corporate Website or WordPress Business Website. For a custom app or portal, a Discovery Sprint turns the designs into a fixed build quote.
Do you test the prototype with real users?
Not with recruited participants; that is outside this scope. We click through the prototype on desktop and mobile before handoff. You can share the prototype link with colleagues or customers for feedback during the revision rounds. If you want formal user testing with recruited participants, note it at checkout for a Change Quote.
How is this different from a Discovery Sprint?
The design sprint is about how screens look and work. The Discovery Sprint is about what a custom app must do, how it connects to your tools and what the build will cost. Discovery ends with wireframes and a fixed quote; the design sprint ends with high-fidelity designs and a clickable prototype. Some projects use both, discovery first.
Do we need a Figma account for the design sprint?
No, but it helps. If your team already uses Figma, we work inside your team by invite, so the files live with you from the start. If not, we build in our workspace and transfer the files to an account in your name at handoff. Anyone can view and comment on the prototype in a browser.
When will the clickable prototype be ready?
The delivery time is shown in the price panel before you order. It starts once your brand material, goals, users and journeys arrive, which should be within 72 hours of ordering. Every day of delay beyond that moves delivery by 3 working days. Quick decisions from the person who approves each round also keep the sprint on schedule.
Can the sprint design screens for a logged-in portal?
Yes. The 8 screens can be any mix of website pages, app screens or portal views, such as a dashboard, a list, a detail page and a settings screen. We agree the screens and journeys in the written brief, so the screens chosen are the ones that matter most to your users.
Guides on this topic
All guides See your product working before you pay to build it.
Order the UI/UX Design Sprint and get a clickable Figma prototype of your key screens, refined with you and handed to your developers ready to build.
Works well with
Accessibility & UX
Accessibility Audit and Fixes
A WCAG 2.2 AA review of up to 10 page templates on your website, with the fixes applied and an accessibility statement…