Overview

Service retainer plans reserve recurring service capacity for a client and track usage against an agreed-upon allocation. They follow the same pattern as Stripe's Product → Price model: a group is your offering ("Software Development Plans"), each plan is a tier inside it (Support, Starter, Growth, Scale, Enterprise), and a version is an immutable snapshot of that tier's terms at a point in time.

A contract attaches one plan version to a client and tracks periods month by month. Each period records included hours, rollover, used hours, and overage — the billable artifacts your invoices come from.

Mental model: Plan groups are the catalog. Plans are the tiers. Versions are the price book at a point in time. Contracts are the customer instances. Periods are the monthly buckets that get billed.

How it fits together

EntityWhat it representsLives in
Plan groupA product family — e.g. "Web Design Plans".Contracts → Retainers
PlanOne tier inside a group — e.g. "Growth (75 hrs/mo)".Contracts → Retainers
Plan versionFrozen terms (price, rollover, overage). New version on each edit.Automatic
ContractOne client's instance of a plan version.Contracts
PeriodThe recurring billing bucket with usage and overage tracked.Contract → Billing & retainer → Retainer

What a typical month looks like

  1. The current period follows the contract's start-date anniversary. For example, a contract starting on the 15th has periods anchored on the 15th, not the first of each calendar month.
  2. As the team logs billable time on the contract's project or entity, those hours roll into the period via the time-entry aggregator (see how time becomes usage).
  3. If usage approaches the limit, you'll see warning chips and notifications (75% / 90% / overage / projected overage).
  4. At period end you Close period, generate Draft invoices for the recurring retainer fee and any billable overage, and review them in Invoices before sending.
  5. Unused hours within the rollover cap carry to the next period; anything beyond the cap or the expiry window quietly expires.

What can change without breaking existing contracts

Plans use immutable versions, so editing a plan creates a new version that only new contracts use. Existing contracts keep the version they were created on until you explicitly switch them. See plan versions and contract safety.

Next steps

  • Build your catalog in Contracts → Retainers.
  • Create plan groups for each product line, then add tiers inside each group.
  • Configure rollover, overage, and term discounts on each tier.
  • Attach a plan version when creating a contract from Contracts.