04

Blog · November 19, 2026 · 6 min read

How We Scope a Product Design Project Before We Quote a Price

Most design projects that go wrong were scoped wrong. The usual culprit is a scope written as a list of screens, priced before anyone looked at the live product, with no line that said where the project ends. Six weeks later the team has forty polished frames, a growing list of "while you're in there" requests, and the same conversion problem they started with.

We scope every engagement the same way, and we do it before we name a price. This post walks through that process step by step, and explains why each step exists. If you are a founder or product lead about to hire design help, you can use the same checklist on any studio, freelancer, or internal team.

Step 1: Name the one decision the work has to support

Every scope starts with a single sentence: what decision will your team make differently once this work is done?

Good answers sound like "decide whether to cut the second onboarding step," "decide which of two pricing page structures to build," or "decide what the approval screen shows before a manager clicks approve." Weak answers sound like "refresh the app," "make it modern," or "improve the UX."

We push on this in the first call because a decision gives the project an edge and a natural finish line. Once the decision is made with good evidence, the project has done its job.

If a team cannot name a decision yet, that is useful information too. It usually means the first piece of work is a short teardown to find one, and we say so plainly instead of quoting a large project on a vague goal.

Step 2: Look at the live product before we write a word of scope

We scope from the product people actually use, so a pitch deck, a Figma file, or a verbal description is never enough on its own.

Before a quote, a senior designer walks the real flows: signup, the core task, the paywall or checkout, the settings page nobody has touched in a year, and the error states. For complex or regulated products, such as fintech, health, insurance, and B2B SaaS, we also look at the moments where trust breaks: verification, consent, payment status, and anything that touches money or personal data.

This step changes the scope more often than any conversation does. A team asks for a new dashboard, and the walk shows that people never reach the dashboard because the import step fails quietly. A team asks for a landing page refresh, and the walk shows the page is fine but the signup form asks for a company size field that stops a lot of visitors. Scoping without this step means pricing the wrong project.

We use AI here for the mechanical parts: capturing screens, listing every field and state, and flagging inconsistencies across flows. A senior person decides what matters and what goes in the scope, because knowing which field is costing you customers in your market takes judgment about your users, your regulators, and your business model.

Step 3: Write the scope as outcomes, artifacts, and a reject list

Our written scope has three parts, and each one is short.

Outcomes. One to three statements of what will be true at the end, tied to the decision from step 1. For example: "The team has a tested, coded version of the new approval screen and evidence on whether approvers understand it in under ten seconds."

Artifacts. Exactly what you will receive. We name the format, because the format decides how useful the work is after we leave. Our default is working software: a coded prototype or production ready components your engineers can run, with the reasoning written next to them. Static mockups appear when a specific decision needs them.

The reject list. This is the part most scopes skip, and it is the part that protects the project. We write down, in plain language, what we will not do inside this engagement. Typical lines:

  • No full visual rebrand inside a flow redesign.
  • No new features beyond the flows named above.
  • No pixel polish on screens outside the decision path.
  • No design system build unless the decision depends on it.
  • No open ended rounds of revision after the review in step 5.

A reject list feels blunt. It is also the most honest page in the document. It tells both sides where the edges are before anyone is tired or frustrated.

Step 4: Set a fixed end point and a review moment

Every scope we write has a calendar end date and one named review moment before it. The review is where the team sees the work in working form, tests it against the decision, and tells us what to cut.

We plan for cutting. A good engagement ends with fewer screens than it started with, because the review shows which parts did not earn their place. If a scope has no review moment, revisions drift into a slow second project nobody agreed to.

The end point also protects the team's time. Founders at early stage companies are running sales, hiring, and fundraising at the same time. A project with a clear finish line is much easier to give attention to than one that might run another month.

Step 5: Price the scope, then stop adding to it

Only after the first four steps do we price the work. The price reflects the decision, the artifacts, and the time senior people will spend. Because the reject list exists, the price can stay put.

When a new request comes up mid project, and one always does, we write it down and hold it for a separate conversation after the end point. Sometimes it becomes the next engagement. Often the review shows it was never needed. Either way, the original project finishes on time and answers the question it was hired to answer.

Why we scope this way

Three reasons shape the whole process.

Senior time is the expensive part, so it should go where the risk is. We staff engagements with senior people only. That makes their hours valuable, and a tight scope makes sure those hours land on the flows that carry business risk, instead of on screens that look nice in a portfolio.

Working software exposes scope problems early. When the deliverable is code, gaps show up fast. A missing error state or an unclear permission rule surfaces the moment someone clicks through it. That keeps the scope honest in a way a static file never does.

AI makes the busy work cheap, which makes judgment the bottleneck. We use AI to move quickly on capture, variants, and documentation. That speed only helps if a senior person has already decided what is worth building. Scoping is where that decision happens.

What we reject in a scoping conversation

We turn down, or reshape, projects that arrive in these forms:

  • "Redesign everything." We will scope the one flow that matters most first.
  • Pricing by screen count. Screens are a poor measure of value, since a single approval screen can carry more risk than twenty marketing pages.
  • Scoping from Figma alone. If the live product exists, we look at it first.
  • A deadline with no decision. A launch date tells us when, and we still need to know what the work has to prove.
  • Unlimited revisions. One structured review, then cuts. Anything else turns into a second project.

A scoping checklist you can use on anyone

Before you sign any design proposal, from us or anyone else, check that it answers these questions:

  1. What single decision will this work help us make?
  2. Did the designer look at our live product before writing the scope?
  3. What exactly will we receive, and in what format?
  4. What is explicitly out of scope?
  5. When does the project end, and when is the review?
  6. What happens to new requests that come up mid project?

If a proposal cannot answer all six, the price on it is a guess.

Work with us

If you have a flow that is costing you customers and you are not sure how big the fix is, we will help you scope it properly before you commit to anything. We work with complex and regulated products in fintech, health, insurance, AI, marketplaces, and B2B SaaS, with senior people on every call and working software as the default deliverable.

Book a discovery call or email ash@uxsignalstudio.com.

Let’s talk about your next step

Have a question or a project in mind?

Tell us where you are and what you want to figure out. We’ll review your message and reply within two business days.

Contact UX Signal Studio

We’ll use your details to respond to your inquiry. This form does not subscribe you to a mailing list. Privacy policy.

Prefer to talk? Book a discovery call

Get the next essay in your inbox

One practical piece on UX and product design, every week or two. No noise.