Choose a package when
- The deliverable is already a known shape
- You want the scope, the round count and the file list visible before you commit
- Your timeline is tight and you would rather not spend a week defining scope
Choose a commission when
- The output does not fit a standard shape
- The work needs research, exploration, or an unusual technical constraint
- You want the scope written specifically around your problem
The honest difference
A package trades flexibility for certainty. A commission trades certainty for fit. Neither is the premium option — they are different tools.
Switching mid-way
If a package brief turns out to be a commission in disguise, we say so before starting rather than quietly stretching the package. Any difference in scope is written down and agreed before production continues.