Printed briefing sheets on a dark desk, with a pen laid across them, a notepad with empty checkboxes and a closed laptop beside them, under soft blue light

How to write a system scope before asking for a quote

By Leonel Rocha · Product Designer

· 6 min read

Short answerGuide

Write down the problem the system solves, who will use it, the tasks each person does in it, the data that goes in and out, the integrations and what stays out of the first version. You don't need technical language: you need real examples from your operation. An Engprax study of 600 engineers found that projects with clear requirements before development were 97% more likely to succeed.

Short answer

Write down the problem the system solves, who will use it, the tasks each person does in it, the data that goes in and out, the integrations and what stays out of the first version. You don't need technical language: you need real examples from your operation. An Engprax study of 600 engineers found that projects with clear requirements before development were 97% more likely to succeed.

97%
higher chance of success for projects with clear requirements before development, according to Engprax
54%
higher chance of success when requirements start from a real problem
600
software engineers surveyed in the UK and the US in May 2024

Many requests for a system quote fit in one line: “I need a system to manage orders, how much?”. It's an honest question. But the only possible answer is another question, because “manage orders” can mean a screen with five fields or an entire operation with inventory, finance, WhatsApp and invoicing.

When the scope is vague, each company fills in the gaps its own way. One quotes the minimum, another quotes the maximum, and you get three proposals you can't compare. In this guide I show what to write before asking for a quote, without technical language, so you get proposals that talk about the same thing.

Why scope matters more than technology

In May 2024, British consultancy Engprax surveyed 600 software engineers in the UK and the US about the last project they worked on. The result is in the study published in June 2024: projects with clear requirements before development started were 97% more likely to succeed.

Two other numbers from the same survey help explain what “clear” means:

  • Projects with a specification or documented requirements before code were 50% more likely to succeed.
  • Projects whose requirements started from a real problem were 54% more likely to succeed.

The study's author, Junade Ali, expanded the analysis in an academic paper from October 2024. His argument is that the start of a project is the cheapest time to decide, because there's no code to defend yet. Once something has been built, nobody likes to admit it was wrong, and the problem keeps getting pushed down the road.

These are correlations, not proof of cause. But the message for buyers is clear: the document you write before the quote shapes the result more than the choice of language or framework.

AI made scope even more important

Today a large share of code is written with AI help. That speeds up building, but it doesn't guess what you want. In September 2025, GitHub released an open toolkit for spec-driven development and summed up the problem in one sentence: language models are “exceptional at pattern completion, but not at mind reading”, Den Delimarsky wrote on the GitHub blog.

In practice, a vague scope produces fast code that solves the wrong problem. A clear scope produces fast code that solves yours. AI's speed multiplies what you wrote, for better and for worse.

Monitor on a dark desk showing a screen sketch made of gray rectangles linked by thin lines, next to a notebook with hand-drawn boxes
Scope becomes screens later. First, it describes the operation. Image: Studio Responsivo

What to write: 8 blocks that fit in a few pages

You don't need a technical template or a diagram. You need to answer eight questions with examples from your company.

  1. The problem. What happens today and what it costs. “We lose orders because they come in through WhatsApp, email and phone, and nobody sees them all together” beats “we want to digitize the operation”.
  2. Who uses it. List the types of people: salesperson, manager, end customer, finance. Say how many of each, today and a year from now.
  3. Each person's tasks. For each type of person, write what they need to do in the system, like a step-by-step of their day. “The salesperson enters the order, picks the customer, attaches the receipt and sends it for approval.”
  4. The data. What goes in (sign-ups, orders, files, photos) and what needs to come out (reports, invoices, alerts, dashboards). If there's a spreadsheet today, attach a copy without sensitive data. It's worth more than any description.
  5. The integrations. Which systems it talks to: ERP, payment gateway, WhatsApp, invoicing software. Name the system you already use.
  6. The business rules. Approvals, limits, exceptions. “Orders over R$10k need manager approval.” This is where a generic system and yours part ways.
  7. Personal data. If the system stores tax IDs, phone numbers, health or financial data, write it down. The LGPD (Brazil's data protection law) requires security measures to be observed “from the product or service design phase” (Art. 46, § 2). That changes the quote and needs to be in it from the start.
  8. What stays out. The list of what's not in the first version. It's the block that best protects your timeline and your money.

How to tell if the scope is good

Run three tests before sending it.

  • The new hire test. Would someone who joined your company yesterday understand what the system does just by reading the document? If they'd need to ask, so will the company quoting it.
  • The example test. Does every task have at least one real case? “Register a customer” is vague. “Register a clinic with three locations and two people responsible for payment” shows the real size of the problem.
  • The cut test. If the quote comes in at twice what you can pay, do you know what to cut? If not, you still need to separate what's essential from what's nice to have.

If you want a starting point, begin with the spreadsheet or process that hurts most today. Many systems start that way, and I explain that path in the guide on how to turn spreadsheets into a system.

Common scope mistakes

  • Describing screens instead of tasks. “I want a blue button in the corner” stalls the conversation on details. Describe what the person needs to get done and leave the design to the designers.
  • Copying a competitor's system. A copied feature comes without the business rule that justifies it. You pay for something you may not use.
  • Hiding the urgency. If there's a date you can't miss, like an event, an audit or the end of a contract with another vendor, write it down. Deadlines change how the project is set up.
  • Leaving “we'll see later” without a list. Everything pushed to later needs to be written down as out of the first version. Otherwise it turns into an argument mid-project.

What the scope doesn't need

You don't need to choose the technology, the database or the hosting. You don't need a flowchart, prototype or schedule. You also don't need to get everything right: the scope you write is the first version, and a good company will come back with questions that improve the document.

What you need is clarity about the problem and honesty about what's essential. The rest gets built together.

How we do it at the Studio

At the Studio, the fixed price comes after discovery. Your scope is where that conversation starts: we read it, come back with questions, cut what can wait and only then set price and timeline, with the deadline written into the contract. Code, files and access stay in the client's name, and the work is done by our in-house dev team.

That's how it went with LCX, a travel company operating in more than 10 South American countries. It had one system per country. The project merged everything into a single system, live in 29 days. With the scope in hand, the next step is understanding what drives the price: I break that down in the guide on how much a custom web system costs, and what needs to go on paper next is in software development contracts.

If your scope is already written, or you want help getting there, see how we work on tailor-made systems and SaaS.

Common questions

Do I need to know how to code to write a system scope?

No. A scope that works is written in the language of your operation: who does what, with which data, and what result needs to come out. Translating that into screens and technology is the builder's job.

How many pages should the scope be before a quote?

Two to five pages are usually enough for a first serious quote. What matters is covering the problem, users, tasks, data, integrations and what stays out. A long document with no real examples helps less than one page with three concrete cases.

Can I send the same scope to several companies?

You can, and you should. With the same document, proposals become comparable: you see who understood the problem, who asked questions and who just sent back a number. Be wary of anyone who quotes without asking anything.

What if the scope changes during the project?

It will change a little, and that's fine. A written scope makes every change a conscious decision, with the impact on timeline and price agreed upfront, not a surprise at the end of the month.

Sources

  1. 268% Higher Failure Rates for Agile Software Projects, Study FindsEngprax · 2024-06-04 · EN
  2. Mitigating Software Project Failure With Loss-Aversion-Aware Development MethodologiesarXiv · Junade Ali · 2024-10-28 · EN
  3. Spec-driven development with AI: Get started with a new open source toolkitGitHub Blog · Den Delimarsky · 2025-09-02 · EN
  4. Law No. 13,709 of August 14, 2018 (LGPD)Planalto

Related service

Systems and apps

Systems, SaaS and iOS and Android apps from diagnosis to launch, with design, code and AI on the same team

View the service

Written by Leonel Rocha, Product Designer and founder of Studio Responsivo

Adobe Certified Expert · Adobe Instructor Design & Layout · Google UX Designer

News Responsivo

Get the next article in your inbox

Cost, timelines, AI and behind the scenes of shipping products. No spam.

Need a custom system?

Reply within 2 hours, during business hours.

Message us on WhatsApp

Prefer to write it out? Send the brief

Newsletter

News Responsivo

New articles in your inbox: cost, timelines and AI. No spam.

New Studio articles in your inbox: cost, timelines, AI and what we've learned shipping products. No spam. Unsubscribe anytime.

Check your email.

Your data stays with the Studio. Privacy