Retainer vs Project Pricing for Agencies
Project pricing sells a defined outcome or scope. Retainer pricing sells recurring access, capacity, service, or outcomes under ongoing operating rules.
Recurring coverage, request rules, capacity, priorities, limits, and review cadence.
Separate recurring service from quoted projects and authorized changes.
Use the definition as an operating boundary.
The category becomes useful when each stage has a canonical record, accountable owner, completion evidence, and visible exception path.
Define the current state
Name the source record, owner, required fields, entry condition, and client-visible meaning.
Define the transition
Identify the verified event or authorized decision that moves the relationship or work forward.
Preserve evidence
Keep the date, actor, source object, related records, conditions, and downstream consequences.
Handle exceptions honestly
Leave the last verified state intact, assign recovery, and never record completion without evidence.
Questions that make the category practical.
Use these questions to compare processes and software without relying on category labels alone.
Retainer vs project pricing, answered.
Why does this distinction matter?
Clear category boundaries reduce duplicate records, false automation, unclear ownership, and reporting built from incompatible definitions.
Can one product cover both sides?
Yes. Verify which records are canonical, how permissions work, and whether transitions preserve meaning without duplicate entry.
How should a team apply the definition?
Map one real engagement, identify the source record and owner at each stage, then test the normal workflow and a meaningful exception.
Make the category operational.
Connect each state to a record, owner, evidence rule, and recovery path.