Jump to content

How To Write A Project Brief That Gets You An Accurate Estimate

From Ecpclio Research & Writing




Begin with the reason this software should exist, not your preferred technology. Which people will use this, how often, and how is the job done today? A vendor who understands the goal can propose an alternative that costs less; one who only sees the requirements as given will price exactly what you asked for.



Define what is included as user stories or scenarios: what the user does and what the system does in response. Equally important, write down what you are not building. An explicit list of exclusions saves more disagreement during acceptance than almost anything else in the document. Also mark which parts are firm and livewire vs inertia which are still open — the difference changes the price, and concealing the open questions helps no one.



Set out your constraints. This means the platforms and services involved, existing databases and their quality, regulatory obligations, traffic expectations, supported browsers or devices and any technology you are committed to. Where a date is genuinely fixed, explain what drives it: mvp development cost an experienced team is usually able to rearrange the plan to hit it, but only if they know it exists.



Define what done means feature by feature. Clear acceptance criteria do not need formal language: a short list describing what a user should be able to do is enough. This one section compresses the sign-off process dramatically and eliminates the usual argument at handover.



To close, ask for a specific format. Require a breakdown by feature or module, a written list of assumptions, the main risks and an optimistic and a pessimistic figure. Treat a wide range as useful information rather than evasion: it usually points to exactly which requirement is unclear. Then clarify that area and request a revised number — the revised figure will be the one worth planning around.