Why fixed scope gets a bad name
Fixed-price projects fail when the scope is vague and changes are argued about instead of priced. Both are fixable.
Dated milestones
We break every project into four to six milestones, each with a date, a demo and a payment. You always know what ships next and what it costs.
A written change process
New ideas are welcome. Each one gets a short estimate, you approve it in writing, and the shared board updates the same day. Nobody argues about whether something was "in scope".
What this looks like in practice
On a 10-week build we typically see two or three approved changes. None of them move the launch date without you choosing to.
