Prepare a software project brief.

Turn your requirements into a one-page brief in eight short steps; arrive prepared for your first conversation or the companies you will ask for a quote. No registration required, and your answers stay in your browser unless you submit them.

Tool

Your brief in eight steps

Takes around 10 minutes. No required fields; anything left blank is omitted from the brief.

You can change your selection; it will be transferred to the inquiry form.

Company and industry

Current situation

Describe how work is done today, rather than the solution.

Where is the work done today? You can select more than one.

Users and roles

How many people, in which roles, on which devices: these factors have the greatest effect on scope.

Who will use it?
Where will it be used?

Must-have functions

The first version would not be useful without these three. The rest can wait for later versions.

Integrations

What will be read from which system, and what will be written where? Simply write “we don't know” for anything you are unsure about.

Systems that need to connect

Success criterion

One measurable sentence is more useful than a long feature list.

Timing

Discovery takes 1–2 weeks; the first release, with scope agreed together, is planned to go live in 6–12 weeks.

When would you like to start?

Budget range

Sharing this is optional. The options help us understand your budget preference; they are not service prices or minimum project fees.

Budget range

The brief generation section uses JavaScript. If it is disabled in your browser, you can use this list for your own notes and enter your answers in the contact form.

Example output

Example: a distributor's dealer ordering brief

X Dağıtım is a fictitious company; the information and targets in the brief are examples. You can see screen designs addressing this need in the Dealer Ordering Platform product concept.

Software project brief

Company
X Dağıtım
Industry
Retail & Distribution

1. Current situation

  • Tools used: Excel, email, phone / messaging, ERP
  • Bottlenecks: Dealers send orders to the field representative by phone or message; the representative enters them manually into the ERP in the evening. Promotions get lost in messaging groups, and dealers call again to check balances and payment terms.

2. Users and roles

  • Who will use it: internal teams, field team, dealers
  • Where it will be used: in the office (computer), in the field (phone / tablet)
  • Roles and approximate user counts: dealers (approximately 6,500, mostly on phones), field sales representatives (40), order operations and accounting (8)

3. Must-have functions

  • Dealers must be able to see their own prices, stock, and promotions, and place their own orders.
  • Orders must reach the ERP without manual entry.
  • Dealers must be able to see their balances, open invoices, and due dates.
  • Can wait: in-app payments, a visit and target dashboard for field representatives

4. Integrations

  • Systems: ERP, payments / banking
  • Details: Stock, prices, and account data will be read from the ERP; orders will be written to the ERP. We will ask our IT team whether the ERP has an API.

5. Success criterion

  • Target: by the end of the first year, more than half of dealer orders should come through the app; calls about balances and due dates should decrease.

6. Timing

  • Start: Within 1–3 months
  • Required deadline: The annual dealer meeting is in early March; the pilot dealer group should be using the app by then.

7. Budget range

  • Not decided yet
  • Note: We would like a quote for the discovery sprint and pilot first.

Why a brief?

What is a brief?

A short, one-page description of the work you want software to address: how work is done today, who will use it, what the first version must include, and which systems it will connect to.

Why does it save time?

When the basic information is available from the start, the first meeting goes beyond introductions; we can discuss scope, risks, and next steps directly. Quotes from companies receiving the same brief also become comparable.

What happens to your data?

The tool runs only in your browser. It does not send your answers to a server or save them in persistent browser storage. Your browser may remember form fields when you go back or restore a tab. Even if you consent to analytics, answer text is not included in measurement. You choose whether to copy, download, or transfer the brief to the contact form and submit it.

Tips

Five tips for a good brief

  1. Describe today, not the solution

    Instead of “we want a mobile app,” write “the field team enters orders into Excel in the evening.” The right solution often emerges from the current workflow.

  2. Limit must-haves to three

    As the list grows, the first release is delayed. Mark the rest as “can wait”; we explain how to choose the first release in our article on MVP scope.

  3. Put numbers against users

    A five-person office team and hundreds of dealers will not use the same screen. Role, user count, and device are the details that change scope the most.

  4. Be explicit about what you don't know

    It is normal not to know whether your ERP has an API. A “we don't know” note shows what needs to be clarified during the discovery sprint.

  5. Define success in measurable terms

    Instead of “make it more efficient,” a statement such as “halve the time spent entering orders” defines when the first release is sufficient.

Related serviceCustom software development