Should we buy wireframes and prototypes together?

Often sequentially, not in parallel: wireframes lock structure, then prototypes validate interaction. We can bundle both in one master SOW with separate acceptance criteria per phase.

Do you also implement the UI in code?

Yes — see Web Design and Web Development hubs. UX / UI leaves can hand off to build engagements with shared Figma libraries and annotated specs.

How fast can a UX / UI engagement start?

Most leaves kick off within two weeks of signed SOW and access to stakeholders. Research and test leaves may need recruit scheduling — we flag that in the quote.

What tools do you use?

Primarily Figma and FigJam; research may use Dovetail or spreadsheets; tests may use Lookback or similar. Tooling is agreed in discovery — we do not force a stack you cannot edit.

Discipline

UX/UI design 11solutions

UX/UI design 22solutions. Research, wireframes, prototypes and creative creative 1creative 1visual work systems that ship.

Discuss your UX / UI scope See design work

UX / UI — choose the right discipline

Wireframes, prototypes, research, systems, and tests are separate scopes — pick the card that removes your current risk.

When UX / UI is bought as a discipline — not a buzzword

UX / UI is not one deliverable. Teams stall when they ask an agency to "do UX" without saying whether the blocker is structure (IA), behaviour (flows), evidence (research), consistency (design system), or validation (usability tests).

This discipline page separates those outcomes. Each card below is its own statement of work, timeline, and price — you can buy wireframes without committing to a full visual redesign.

How to pick between wireframes, prototypes, research, systems, and tests

Choose wireframes when stakeholders disagree on page structure or nav. Choose prototypes when you need to validate flows before dev estimates. Choose research when you lack evidence on what users actually need. Choose a design system when multiple squads ship inconsistent UI. Choose usability testing when you have a live or high-fidelity UI and need a ranked fix list.

Still unsure? Book a 30-minute scoping call. We will recommend a single starting leaf — not a bundle — based on your launch date and risk.

What procurement should see in a UX / UI SOW

Each leaf includes: discovery inputs, revision rounds, acceptance criteria, file formats (Figma/FigJam), and accessibility expectations. We do not lump research and create into one vague "UX phase".

NDAs, GDPR documentation, and vendor onboarding are standard for enterprise buys. Mention procurement requirements in the Start a conversation form.

Outcomes across the UX / UI cards

Shared goal: reduce rework downstream. Wireframes cut visual design churn; prototypes cut dev change orders; research cuts feature guesswork; systems cut UI drift; tests cut post-launch support tickets.

Discuss your UX / UI scope

services in this discipline

5 offerings — click any card to see pricing, features and sample work.

Separate scopes

Buy only wireframes, only tests, or a sequenced bundle — each with its own SOW line items.

Weekly demos

Review FigJam/Figma on a fixed cadence with written change logs — not surprise redesigns.

Handoff to create

Annotated files and acceptance criteria your dev team or our create squad can implement.

Frequently asked

Should we buy wireframes and prototypes together?: Often sequentially, not in parallel: wireframes lock structure, then prototypes validate interaction. We can bundle both in one master SOW with separate acceptance criteria per phase.
Do you also implement the UI in code?: Yes — see Web design and Web Development hubs. UX / UI leaves can hand off to create engagements with shared Figma libraries and annotated specs.
How quick can a UX / UI engagement start?: Most leaves kick off within two weeks of signed SOW and access to stakeholders. Research and test leaves may need recruit scheduling — we flag that in the quote.
What tools do you use?: Primarily Figma and FigJam; research may use Dovetail or spreadsheets; tests may use Lookback or similar. Tooling is agreed in discovery — we do not force a stack you cannot edit.

Not sure which UX / UI card fits?

30-minute scoping call. We map your blocker to one leaf and send a fixed-scope quote within 24 hours.