What is the most flexible way to fund continuous product development?

Use one-off quotes, planned releases, monthly capacity, or a dedicated team according to actual demand. Wavesteam analyzes normal and peak workload, role mix, readiness, and waiting cost: intermittent work usually suits one-off pricing; a continuing prioritized queue may suit release or monthly capacity; a dedicated team makes sense only when several roles remain close to fully occupied. A monthly retainer is not inherently cheaper.

First separate warranty defects, technical operations such as monitoring and security updates, routine business changes, and new modules. They have different responsibilities and pricing. “Long-term maintenance” without these boundaries invites the client to expect unlimited changes while the provider expects only server continuity.

Model	Best demand shape	Commercial pattern	Main risk
One-off quote	A few independent changes per year	Scope and fixed price each time	Repeated startup and queue delay
Planned release cycle	A group of priorities can form each period	One goal and accepted increment per cycle	Interruptions fragment the release
Monthly capacity	Continuing small/medium work with changing order	Buy specified roles and capacity; queue controls scope	Idle time, unclear units, and rollover
Dedicated/joint product team	Sustained multi-role product operation	Team and period pricing with strong continuity	Highest fixed cost and waste without direction

Wavesteam reviews a historical period that covers ordinary work, peaks, and seasonality: request, start, release, effort, priority, category, lead time, urgent work, readiness, acceptance wait, rework, and role distribution. When evidence is limited, assumptions are explicit. The client confirms business peaks and priorities; Wavesteam builds the capacity model.

Compare total cost, not hourly rate. Include fixed fee, unused capacity, expedite, meetings and management, providers and cloud, and business cost of waiting. Ten purchased days with four used can be dearer despite a lower nominal rate; repeated two-week waits for a critical one-off change can cost more than reserved capacity.

A monthly agreement defines roles and capacity units, whether meetings/test/release count, rollover and expiry, readiness and priority authority, incident versus enhancement response, defect and debt classification, overage, monthly artifacts and time evidence, and exit transfer of code, accounts, documents, and backlog. Priority access becomes measurable response and evaluation windows, not “everything starts immediately.” Capacity caps effort; it does not guarantee a fixed number of features.

The Scrum Guide combines a Sprint Goal, selected backlog, and delivery plan and allows learning to refine the plan. It does not support unlimited interruption or treating velocity as the outcome. Review business results, lead-time distribution, commitment completion, production defects, recovery, rework, utilization, and next priority each month. Reduce capacity when unused, expand or cut low-value work when persistently overloaded, and stop building when outcomes are absent.

Our cooperation guide and operations packages describe available models but not unlimited development or a universal discount. The quote governs roles, capacity, response, rollover, and price.