The One-Page Project Charter for Startup Founders
A startup-grade project charter built for founders who need scope clarity in an hour, not a week — with three signals that catch expansion early.
The four lines that keep an early-stage project honest
The startup charter isn't shorter because startups need less rigor. It's shorter because longer ones don't get re-read.
Founders don't need a thirty-page charter. They need a one-pager that gets re-read every Monday. The version below is built for that — four lines that fit on a sticky note, plus three early-warning signals you can spot before the project quietly doubles in scope.
This sits in the detective part of the lifecycle: the goal isn't to prevent expansion (you can't, in a startup), it's to see it within a week of it starting. That's the difference between a recoverable detour and a blown quarter.
The four-line charter
0 / 4- Why — one sentence on the customer outcome. Not the feature, the outcome.
- By when — a single date you'd be embarrassed to miss. No ranges.
- Done means — three observable criteria. If you can't tell from the outside whether they're met, rewrite them.
- Not this — three things this project will not include. The exclusions list is the whole charter, in a sense; everything else can be reconstructed.
The detective charter — five questions, one page
The instinct in a startup is to skip the charter because everything is changing. That's exactly backwards. Things change fast; that's why you need a written reference point that's cheap to re-read. A one-page charter takes 45 minutes to write, costs you nothing if it never changes, and saves a quarter the first time it catches drift.