30 MAR 2026
David noticed: Phased rollout is the wrong default for a startup product
David's standing position is that implementation plans should not include phased rollout language — everything should be built and shipped in full, now, not spread across time for caution's sake.
When reviewing the implementation plan for Kerra's Canvas file metadata heal and external source recovery, David caught boilerplate phased-rollout language and rejected it:
i hope youve not put some phased rollout language in here? we need to do it all now. if the plan includes any wording like that, change it to be that we need to do it all now.
This is a recurring position David holds when reviewing AI-generated implementation plans: agents default to cautious, time-spread rollouts that make sense for large engineering teams but are inappropriate for a fast-moving startup that needs features live immediately. The plan became the bible for execution, not a staged proposal.