| |
| writing_a_technical_brief_that_gets_you_an_accurate_estimate [2026/09/20 08:50] – created eltonoliva | writing_a_technical_brief_that_gets_you_an_accurate_estimate [2026/09/22 00:20] (current) – created michalhofmann |
|---|
| |
| |
| Open with the business problem, not a list of screens. Which people will use the system, how many times a day, and how is the job done today? An experienced team who understands the goal often proposes a cheaper route to it; a team that receives only a feature list can only price the list as written. | Open with the problem you are solving, not a list of screens. What kind of user will use it day to day, with what frequency, and what happens today? An experienced team who grasps the purpose will suggest a cheaper route to it; someone handed only a feature list will price exactly what you asked for. |
| |
| |
| |
| Define what is included as short scenarios: a walk through each important path. Equally important, write down what the first release deliberately excludes. An explicit list of exclusions prevents more argument at delivery time than any other single page. Mark too which decisions are settled and which may still change — honest teams price those differently, and hiding it helps no one. | Describe the scope as user stories or scenarios: what the user does and what the system does in response. Just as important, write down what you are not building. An explicit exclusion list removes more disagreement later than any other single page. Mark too which parts are firm and which may still change — honest teams price those differently, and hiding it only hurts you. |
| |
| |
| |
| Write down the hard constraints. These include the platforms and [[https://webparadox.com/blog/laravel-vs-nodejs-2026/|choosing between laravel and node js]] services involved, the data you have and where it lives, security and [[https://webparadox.com/hire/angular-developers/|hire angular audit experts]] compliance rules, expected load, supported browsers or devices and stacks you cannot change. Where a date is genuinely fixed, say why: a good team can often resequence the work to meet it, but only if they know it exists. | Write down the hard constraints. This means existing systems the [[https://webparadox.com/blog/dedicated-team-vs-outsourcing/|dedicated vs outsourced software development team]] has to talk to, the data you already hold and its condition, security and compliance rules, [[https://webparadox.com/technologies/kubernetes/|kubernetes consulting services]] traffic expectations, target platforms and infrastructure that is already decided. Where a date is genuinely fixed, say why: a team is usually able to cut the right scope to protect it, provided they hear about it early. |
| |
| |
| |
| Say what done means [[https://webparadox.com/services/seo/|seo agency for software factories]] each item. Testable acceptance criteria do not need formal language: a plain-language note setting out what must be true when the feature works will do. This one section shortens acceptance testing dramatically and closes off the usual argument at handover. | Define what completion means for each item. Acceptance criteria do not require any formal notation: a short paragraph setting out what a user should be able to do will do. This single habit reduces acceptance testing by a surprising margin and removes the most common source of disputes. |
| |
| |
| |
| Finally, say what you expect back. Require an itemised estimate, the assumptions behind each number, the main risks and a range rather than a single figure. Take a broad range as useful information rather than evasion: [[https://webparadox.com/technologies/ai-development/|ai developers for hire]] it usually points to where your description is thin. Then tighten that section and ask again — the second estimate is far closer to reality. | Finally, state what you want in the response. Ask for a task-level breakdown, the assumptions used, the risks the team sees and an optimistic and a pessimistic figure. Take a broad range as useful information rather than evasion: it tells you the part of the brief that needs work. Then clarify that area and ask again — the revised figure tends to be much more reliable. |
| |
| |
