01 · Queue
Designjoy Primary
“One request at a time”
Boundary: define one request and complexity.
Executive synthesis · 33-source research base · 25 August 2026
Translate hours into a promise.
Keep hours for capacity and margin. Let the client evaluate the service they receive.
#01 The answer in one view Synthesis
Inside the studio
Hours
Capacity · utilization · cost · margin
What the client buys
A reliable working relationship
QueuePaceOutputsAccessBudgetHybrid
Lead with 120 hoursBuyer evaluates labour
- Hourly rate
- Unused time
- Timesheet policing
Lead with the promiseBuyer evaluates reliability
- Will work keep moving?
- What is included?
- What happens at peak?
Why: the first number defines the comparison. This is a proposal-design inference—not a universal law of buyer behaviour. See the evidence and counterpoint →
#02 Choose by the shape of demand
Prepaid labour is the product
→
Hour bank
Work arrives continuously
→
Queue or daily pace
Outputs repeat each month
→
Deliverables
Senior decisions are the bottleneck
→
Access / advisory
Discipline mix changes
→
Flexible budget
Routine support + large launches
→
Hybrid
Six real offers Primary
The captures prove these models are sold publicly. Prices and terms are dated snapshots; Primary Research carries the caveats.
02 · Daily capacity
Flocksy Primary
“Pick the pace that fits.”
Boundary: hours must explain pace, not dominate value.
03 · Deliverables
DBL Design Agency Primary
“5 designs per month”
Boundary: define one design, revisions and overages.
04 · Access / advisory
Maura Reminga Primary
“A strategic partner in your corner”
Boundary: define access, meetings and production.
05 · Flexible budget
Superside Primary
“unused budget that rolls over month to month”
Boundary: define burn, rollover, expiry and fees.
06 · Hybrid
Studio Nate Primary
“Ongoing design partner”
Boundary: define what leaves the base retainer.
#03 Recommended proposal
Client sees
The service promise
- Active priorities
- Response and review cadence
- Typical turnaround
- Overflow rule
Studio tracks
The capacity model
- Hours
- Utilization
- Delivery cost
- Margin
Monthly design partnership
“[One/two] priorities move at once, reviewed weekly; larger launches become separate sprints.”
Validate before promising: concurrency, turnaround, revisions, overflow and margin.
#04 Keep hours visible when…
- Procurement requires utilization records.
- The client is buying prepaid production.
- The work is too unpredictable for a credible throughput promise.
The lesson is hierarchy, not secrecy. If hours remain, place the service promise first and explain capacity second.
#05 Go deeper
- Primary research33 sources · benchmark · contracts · 7 YouTube clips · counterevidence