Sign in

Monthly Retainer

Reserve ongoing senior capacity every month so the work never stalls waiting for a new contract to be signed.

Pro involved Service Offers

What it adds

From your service logs, recurring client requests, and capacity records, the builder produces a subscription-shaped service offer defining what recurring capacity buys, how it is allocated, and how unused capacity is treated. It converts by reframing the purchase from 'a project' to 'a permanently staffed function,' with predictable monthly cost and a clear cancellation path lowering the commitment barrier.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Read the monthly work logs and recurring request records in the source files, and categorize a representative month into the recurring work types and their relative share of capacity.

  2. 2

    Define the unit of capacity explicitly — days per month, concurrent active requests, or a defined workstream — and state which unit this retainer uses and why it fits the work.

  3. 3

    Publish a typical month as a sample allocation: which work types are covered, in what proportion, based on the categorization from step 1. This turns an abstract subscription into an observable service.

  4. 4

    Set the prioritization rule for competing requests, name who at the buyer's organization can submit and approve work, and state the standard turnaround for a routine request.

  5. 5

    State the boundary conditions plainly: what falls outside the retainer, how overflow is handled, whether unused capacity rolls over, and the notice period for cancellation or pausing.

  6. 6

    Explain the pricing model as a monthly fee for reserved capacity, and justify it with the availability guarantee it creates for the buyer rather than with an hourly comparison.

  7. 7

    Implement responsive layout: on mobile present the sample month allocation as a stacked proportion list with a sticky monthly-price bar; on tablet render it as a horizontal bar chart above the boundary rules; on desktop show allocation, boundaries, and turnaround expectations in a three-column dashboard-style panel that stays aligned while the page scrolls.

  8. 8

    Close with a single action — start the first month — and state the notice period for cancellation directly beside it so the commitment feels reversible.

Edge cases it handles

5

The things an agent skips when you only say "build a monthly retainer".
  • Demand in a given month exceeds reserved capacity — publish the overflow policy and how additional capacity is priced.
  • A month passes with little or no work requested — state the rollover or expiry rule explicitly and do not leave it implied.
  • The buyer's request volume is unpredictable — define capacity by workstream rather than by hours and say so.
  • Multiple stakeholders submit conflicting priorities — name the single approver role required.
  • The buyer wants a one-time project instead — direct them to the fixed-scope offer rather than bending the retainer.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • The capacity unit is named and its rationale stated.
  • A sample month allocation derived from real work logs is displayed.
  • Prioritization authority, submission process, and routine turnaround are all specified.
  • Rollover, overflow, and cancellation notice policies are each stated explicitly.
  • Pricing is framed around reserved availability rather than hourly equivalence.
  • Mobile stacked list, tablet bar chart, and desktop three-column panel layouts are implemented.
  • The builder reports which source files informed the allocation and policy decisions, and lists unresolved assumptions.

Related offer files

Service Offers

VIP Day

Clear one stubborn bottleneck in a single dedicated day of undivided expert attention, finished before you log off.

Build This Offer: VIP Day

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this offer type.

  2. 2

    Give it to your builder

    Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.

  3. 3

    It maps, then builds

    Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.