Skip to content
dvnt.io

Resources · glossary

Brief

A document in which the client describes the goal, scope and constraints of a project before anyone starts quoting. Its quality translates directly into how far apart the quotes are.

Also called
  • brief
  • project brief
  • request for proposal
  • RFP
  1. 01

    Why quotes cannot be compared without one

    Three companies get one sentence and quote three different projects. A spread from PLN 8,000 to PLN 60,000 then says nothing about the vendors; it says each one guessed differently. A brief turns guesses into comparable assumptions.

  2. 02

    What it must contain

    The business goal (what should change, not how it should look), who will use it, what already exists and must be connected, the deadline and the budget, even as a range. Leaving out the budget does not protect you from an inflated quote; it only makes the talks longer.

  3. 03

    What it does not need

    A technical solution. Naming a technology in the brief closes the door on a cheaper or faster option you may not have known about. Describe the problem; choosing the tool is part of the offer.

  4. 04

    How to make it quicker

    We have a brief builder that walks you through these questions step by step and gives you a file at the end that you can send to any vendor, not just us.

In practice

Related terms

  • Project estimateAn estimate of a project’s effort and cost made before it starts, based on what is known about the scope at that moment. It is not a price promise — the less is known, the wider its range should be.
  • Cost breakdownA price split into line items with hours and rates, instead of one amount at the bottom of the page. It lets you see what you are paying for and cut what you do not need.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.