UX/UI freelance project scope: what to clarify before quoting

“Design ten screens” is rarely enough to estimate a UX/UI freelance project. Ten polished screens based on an approved flow are different from discovering the flow, testing it with users and documenting every state. Before quoting, separate research, interaction design, visual design and handoff. This guide helps a freelance designer turn a vague request into a reviewable scope.

Identify the starting point

Ask whether the client has an existing product, research findings, a design system or only an idea. Confirm who the users are and which problem the project is meant to address. If there is no evidence about the problem, do not present a preferred visual direction as a validated UX solution. Agree whether discovery is part of the paid assignment.

• Which user role and journey are in scope?
• What exists today, and what must stay unchanged?
• Who approves product decisions and visual design?
• Which technical or accessibility requirements constrain the work?

Count flows and states, not just screens

A sign-up screen can include empty, invalid, submitting and successful states. A dashboard may need loading, no-data, restricted-access and error views. List the important states with the client. Clarify whether mobile and desktop layouts are both required, and whether a tablet adaptation is a separate deliverable or follows agreed responsive rules.

State how reusable components will be handled. Using an existing component library is different from creating a new design system. Define which components, variants and documentation are included rather than allowing “make it consistent” to become an unlimited systems project.

Separate research from production

If research or usability testing is included, define the method, recruitment responsibility, participant costs and output. A prototype alone is not a completed user test. Likewise, a visual review is not evidence that users can complete a task. Make clear which conclusions will be based on observation and which remain design assumptions.

Write down the handoff

• Editable design files and ownership or access arrangements.
• Agreed flows, responsive layouts and important states.
• Components and interaction notes needed by developers.
• Prototype depth: which paths work and which are illustrative.
• Exportable assets and any licensed fonts or images.
• Whether implementation review is included after handoff.

Do not silently include production code, copywriting or a formal accessibility audit in a design-only fee. They may be useful additional services, but they need their own scope and an appropriately qualified person. Record the accessibility requirements the design should support without claiming the entire product is compliant from static mock-ups alone.

Example: a checkout redesign

An illustrative first scope could cover the cart-to-confirmation flow on desktop and mobile, including empty cart, validation errors and payment failure. Deliverables could include a flow diagram, reviewed wireframes, final UI and a clickable prototype of the main path. The client provides product rules, approved copy and access to the existing design system.

In that example, customer interviews, payment integration code, new brand identity and ongoing development support are excluded unless separately agreed. Review rounds and acceptance criteria should be specified. This is a scoping example, not a universal package or a price recommendation.

Questions to send before a quote

Ask which flow matters most, what evidence already exists, which devices need designs, who supplies content and who signs off. Then ask what “done” means: approved design files, a tested prototype or implementation-ready documentation. A concise written answer is more useful than an impressive screen count with undefined boundaries.

When browsing assignments, distinguish a one-off design project from an ongoing job vacancy. On Vibe Work, use the One-off section for project work and check the original brief of external listings. Neither a listing category nor a design title guarantees that the scope, budget or current availability meets your needs.