What to launch with.
WHAT IT SHOULD DO
Solve the core problem completely for one kind of user.
WHAT IT NEED NOT HAVE
Every feature discussed Configuration options Multiple user roles Integrations An interface for everything
WHAT CAN BE MANUAL AT FIRST
Account creation Billing Data import Reporting Anything infrequent
WHY MANUAL IS ACCEPTABLE EARLY
It delays engineering until you know what is actually needed, and customers rarely notice or mind.
WHAT MUST NOT BE MANUAL
Anything a customer does daily.
WHAT TO CUT WHEN THE SCOPE GROWS
Anything not on the path from signing up to receiving value.
WHAT THAT PATH IS CALLED
The core loop of the product.
WHAT TO PROTECT
That path working reliably.
WHAT TO RESIST
Building for imagined future customers Building for the largest customer you hope for Configurability before you know what varies
WHY CONFIGURABILITY SPECIFICALLY
Every option multiplies testing and support, and most are never used.
WHAT TO SET AS A RULE
One opinionated way of working, until customers prove otherwise.
WHAT TO MEASURE AT LAUNCH
Whether anyone reaches the value.
