How do I write down what I want built so a developer can quote it?

By Ranjit Bhinge, founder of Blur Studio · Updated · 6 min read

Short answer: Write one page with six parts: the problem, who uses it, how the work is done today, the information involved, the must-haves, and a not-now list. Use plain sentences and one real example. You do not need a formal requirements document. A developer needs enough to quote without guessing, and a short brief does that better than a long one nobody finishes.

Ranjit Bhinge

You want a short brief you can finish in an hour that lets a developer give you a real quote, not a range with a shrug.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Most guides on this topic are written for product teams. They talk about formal specifications, numbered requirements and sign-off. If you run a small business and want a developer to quote a tool, that is too much. What you need is a brief: a short, clear description of the job. This page gives you one you can fill in today. Before you write requirements, read how to scope a small business software project.

Why a short brief beats a long document

A developer quoting your job is trying to answer three questions: how much work is it, how risky is it, and what could surprise us. A good brief answers all three. A long document often hides the answers inside detail, and a vague one forces the developer to guess, which means either a high quote or a bad surprise later.

The UK government's service manual makes a point I agree with. It says to focus on the goal, and that if you cannot write a clear goal for a feature, you should question whether you need it. That is the test for every line of your brief. The same manual says that before you commit to building anything you need to understand the problem, and that you should not start building during its discovery phase. Your brief is the written form of that understanding.

The six parts of the brief

  1. The problem, as one real story. Not "we need a CRM." Write what went wrong last month. Basecamp, the project management company, calls this the problem part of a pitch and says it works best as one specific story showing why today fails.
  2. Who uses it. List each type of user and what they do: owner, office staff, field staff, customers. Note how many of each.
  3. How it is done today. The steps, in order, including the messy ones: where it lives (spreadsheet, inbox, paper), who touches it, where it breaks.
  4. The information involved. What things do you keep track of? Customers, jobs, quotes, photos, documents. For each, what do you need to know? Attach a real spreadsheet or a few real examples.
  5. Must-haves. The few things without which the tool is useless. I suggest five or fewer. Write them as short goal statements.
  6. The not-now list. Things you want eventually but not in version one. This is the most valuable part of the page and the one most people skip.

Basecamp's pitch format also names two parts worth borrowing: an appetite (how much time you want to spend, which constrains the solution) and no-gos (things you are deliberately leaving out). Your budget goes in the brief. A developer who knows your ceiling can design to it, and one who does not will quote against a guess. Once you have requirements, see questions to ask a software development company.

How to write a must-have

Use a simple sentence with three parts: who, what, why. The government's service manual uses the form "As a [user], I need to [do something], so that [reason]." You do not have to use those exact words, but all three parts must be there. Then add one line that says when it is done, such as "done when the office can see every open job on one screen."

Examples of weak and strong:

  • Weak: "Needs a dashboard."
  • Strong: "As the owner, I need to see every open quote and how old it is, so that I can chase the ones going cold. Done when I can see all open quotes sorted by age on one screen."

A filled-in example for a quoting tool

The business and the figures here are made up to show the style.

Problem. Last month we lost a 6,000 dollar job because a quote sat in someone's inbox for nine days. We send about 40 quotes a month. Quotes are built in a spreadsheet, emailed as PDFs, and nobody tracks which are still open.

Users. 1 owner, 2 office staff who write quotes, 4 field staff who only need to see accepted jobs. Customers receive the quote and say yes or no.

How it works today. A customer calls. The office staff copy last quote's spreadsheet, change prices by hand, save as PDF, email it. If the customer replies yes, the office adds a row to the jobs spreadsheet. Nobody follows up on silence.

Information. Customers (name, phone, email, address). Quotes (line items, price, date, status). Price list (about 60 items, attached). Jobs (created from an accepted quote).

Must-haves.

  • As office staff, I need to build a quote from the price list, so that I stop retyping prices. Done when a 5-line quote takes under 3 minutes.
  • As the owner, I need to see all open quotes by age, so that I can chase the cold ones. Done when I see them on one screen.
  • As a customer, I need to accept a quote with one click from the email, so that I do not have to reply. Done when acceptance creates a job automatically.
  • As the system, send a reminder to the office after 3 days without an answer.

Not now. Invoicing, payments, a customer portal, a phone app, accounting sync, stock tracking.

Budget and timing. We want to spend under a stated amount, and would like a working version in 6 weeks. We can give 30 minutes twice a week for feedback.

That is under 400 words, and a developer can quote it. It names the one risk worth flagging, which is the price list, because price rules are where quoting tools get complicated.

What to leave out

  • Technology choices. Do not say "use React" or "use WordPress." Describe the need and let the developer propose how.
  • Screen designs from your head. A rough sketch is useful. Pixel-perfect mockups are not, yet. GOV.UK's guidance on early prototypes says to build things just complex enough to test ideas, not production quality, and to expect to throw most of them away.
  • Everything you may ever want. That is what the not-now list is for.
  • Jargon you picked up from sales pages. Say "customers can log in and see their jobs," not "a multi-tenant portal."

Things developers need that owners forget

  • Volume. How many customers, jobs or quotes per month, now and in two years.
  • Connections. Which tools it must talk to: email, calendar, accounting, your website forms.
  • Who owns the data and the code. Say you expect to own both.
  • Who decides. One name, with authority to say yes.
  • Sensitive data. If you store customer personal details, say so. It changes how the tool must be built.

Finally, read the brief as a stranger would. Could someone who has never seen your business explain back to you what the tool does and who uses it? If not, add the missing sentence now. Ten minutes here saves a week of back and forth later.

Red flags in the replies

  • A fixed price with no questions asked. They did not read the brief, or they plan to charge for changes.
  • No questions about your data. The messiest part of the job is invisible to them.
  • Nothing in writing about who owns the code.
  • No mention of testing or of how you will see progress before the end.

For the contract side, a statement of work spells out scope, dates and payment. See the SOW template and example. If you are choosing who to brief, read hiring a Lovable, Bolt, Replit or Cursor developer.

Do you need a developer at all

Writing the brief often answers that. If your must-haves fit a ready-made tool, buy it. The question is covered in how to choose between buying a tool and building custom software. If it is a simple internal tool, you may be able to build it yourself with AI help, see building an internal tool without a developer. For rough cost expectations, read custom software development cost, and for timing, how long custom software takes to build.

How I'd approach this

I would write the brief in one sitting, then read it aloud to someone on your team and ask what is missing. The not-now list is the part I would spend the most time on. If you are unsure, send me the brief as it stands. I would rather get a rough page and ask good questions than receive a 40-page document. The better the not-now list, the more accurate the quote. You can see how I take on this kind of work on the business page.

Questions people ask

How long should a software requirements brief be?

One page is enough to get a real quote for a small project. The filled-in example above is under 400 words. Add attachments (a spreadsheet, a few real examples) instead of more prose.

Do I need a formal software requirements document?

Not for a small business tool. A formal document can help on large projects with many teams. For one process, a plain brief with a must-have list and a not-now list does the job.

What is the difference between a brief and a statement of work?

The brief describes the need. The statement of work is the agreement: scope, dates, payments and who owns what. Start with the brief, then see the SOW template.

Should I include my budget in the brief?

Yes. A time or money ceiling constrains the solution, and Basecamp calls the time version an appetite. A developer who knows it can design to it. Read custom software development cost to set a realistic number.

What if I do not know what I want yet?

Write down what goes wrong today and how the work is done, and leave the solution open. A short paid first step to map the process is better than guessing at features.

Can AI tools write my requirements for me?

They can help you tidy a draft or ask you questions, but you still supply the facts: your steps, your data, your must-haves. Do not let a tool invent requirements you do not have.

More in this topic: Problem solving: custom software (22 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…