- 01 Acceptance criteria: what "done" means before we start How to define "done" so there are no surprises at handover. In plain words, for people who pay for development but don't write it themselves.
- 02 The discovery brief: the document that saves us $20K Why a vendor can't quote an honest price without a discovery phase — and how to buy that phase as a small standalone service before signing the big contract.
- 03 The brief for the team (user story): how to read it and know what we're paying for How to tell a well-written task from a bad one. The formula, three signs of a weak story, and the phrase to ask for a rewrite without friction with the team.
- 04 The IT-company estimate: how to read it right, and where the vendor's interests differ from ours 4 signs of a solid estimate, 4 signs of a padded one, and why fixed price isn't always cheaper than hourly. For people who pay for development but don't write code themselves.
- 05 Risk map: how to find what's hidden 6 risk types that show up in 9 out of 10 IT projects, a 3-column table you keep yourself, and the moment it's time to call in a specialist.
- 06 Comparing vendors: oranges against oranges An 8-column table template, a method of asking everyone the same questions, and three red flags visible only in comparison — not in a single proposal.
- 07 The AI feature brief: when AI actually helps, and when it's just trendy Three filter questions, an AI feature brief checklist, and the red flags for when it's better not to add AI at all. For people who hear 'let's add AI' and don't know whether they need it.