The seven sections every software scope needs — and the three everyone skips
Assumptions, risks and exclusions are the cheapest insurance in software procurement. What each of the seven sections of a scope should say.
Notes
Written for the person signing the contract.
No listicles, no vendor-neutral fence-sitting. What we know about scoping, choosing a development partner, and the clauses that decide who pays when a project slips.
Five questions that separate a studio from a sales team
Ask about code review, not awards; about who is free next month, not headcount. Five questions for a first call with a development partner.
Escrow for software projects, explained without the jargon
What acceptance criteria must say for escrow to mean anything, how to size milestones, and what escrow does and does not protect you from.
Inheriting a codebase: the two-week audit that saves six months
What to check first in an inherited codebase, which findings justify a rewrite, and how to recover access when the previous vendor goes quiet.
When AI is the wrong answer to a document problem
A short test for whether a document workflow needs a language model, a template or a better form — and what to settle before any model spend.
Why two quotes for the same project differ by 3×
It is rarely hourly rates. It is what each team assumed you meant. How to read and compare software development quotes properly.
One weekly meeting is enough — if it is the right one
The 30-minute agenda for running an outsourced software build, the written update that makes it work, and what belongs outside that call.
Have a question these notes do not answer? Ask it — we reply to your specific case, not with a link to an article.
Ask a question