Choose a commercial model that matches how decisions will actually be made. A defined deliverable, an investigative backlog and an ongoing release schedule place different demands on estimating, availability and approval.
Use fixed scope for defined outcomes
Fixed scope works when the outcome, dependencies, acceptance criteria and decision owners are clear enough to estimate responsibly.
- Discovery has reduced major unknowns
- Deliverables and exclusions are explicit
- Approvals can happen on schedule
- Change control is acceptable
Use hours for evolving work
Development hours suit investigation, varied backlogs and smaller releases where the next priority changes as evidence appears.
- Tasks can be prioritized regularly
- Investigation is part of delivery
- The team values visibility over false certainty
- Work can be released in useful increments
Use a retainer for a continuing roadmap
A retainer fits when reserved capacity and a dependable operating cadence matter across campaigns, platform work and integrations.
- There is a maintained backlog
- Monthly priorities have an owner
- Unused or excess capacity rules are clear
- Reporting supports decisions rather than theatre
Protect every model
Commercial structure does not replace delivery discipline. Define environments, communication, QA, approvals, release ownership and escalation in every agreement.
- Name decision owners
- Agree the release process
- Document blockers and dependencies
- Review whether the model still fits
Make the working agreement usable day to day.
Before choosing the label for the engagement, agree how a task enters the backlog, who prioritizes it, what approval means and how a completed change is released. Then record the terms that differ by model.
- Fixed scopeWrite the deliverables, acceptance criteria, exclusions, dependencies and approval dates. Define how a newly discovered requirement affects the estimate and release plan.
- Development hoursAgree the time budget, reporting format and who can reprioritize work. State when investigation should pause for a decision and how remaining time will be communicated.
- Monthly retainerSpecify reserved capacity, scheduling, response expectations and the treatment of unused or additional time. Record what happens during absences and which requests fall outside the agreement.
- Review pointSet a review when the build ends, the backlog changes materially or the team needs a different delivery cadence. The engagement can change as the work becomes more or less predictable.
These are planning considerations, not published pricing or contract terms. Your written proposal defines the agreed scope, fees, capacity and responsibilities.
Compare the available engagement models, development hours and monthly Shopify retainers against the work you need to schedule.
Match the engagement to certainty and cadence.
| Approach | Best fit | Watch carefully |
|---|---|---|
| Fixed scope | Outcome, dependencies, approvals and acceptance criteria are sufficiently clear to estimate responsibly. | Protect the model with explicit exclusions, change control, decision dates and client responsibilities. |
| Development hours | Priorities evolve, investigation is part of the work or varied improvements can ship in useful increments. | Use a visible backlog, time records, review cadence and agreed authority for reprioritization. |
| Monthly retainer | Reserved capacity and a continuing release rhythm matter across a maintained roadmap. | Define capacity, rollover rules, response expectations, meeting load, reporting and work that sits outside the retainer. |
Avoid ambiguity about what the engagement buys.
- Forcing an uncertain technical problem into a fixed price without discovery.
- Buying hours without a prioritized backlog or decision owner.
- Using a retainer as an undefined promise of unlimited availability.
- Measuring progress through meetings and output volume instead of accepted outcomes.
- Keeping the same commercial model after roadmap certainty or operating needs change.
Questions to resolve before implementation.
- Is the outcome clear enough to write useful acceptance criteria?
- Which dependencies and approvals sit with the merchant team?
- How often will priorities change and who can change them?
- Does the work need reserved capacity or only occasional releases?
- How should unused or excess time be handled?
- When will both sides review whether the commercial model still fits?
Questions about this decision.
Which model is best for a new Shopify build?
A defined build may suit fixed scope after discovery. If requirements are still moving, a discovery phase or hours can reduce uncertainty before a larger commitment.
Are development hours the same as staff augmentation?
Not necessarily. Hours can fund a prioritized backlog with senior ownership and defined release practices without placing an unmanaged person inside the team.
What should a retainer guarantee?
It should clearly define reserved capacity, cadence, response expectations, roles and reporting. It should not imply unlimited work.
Can one engagement use more than one model?
Yes. Discovery may be fixed, implementation may use fixed scope or hours, and ongoing work may move to a retainer when a continuing roadmap exists.
How are scope changes handled in fixed-price work?
Assess the effect on outcome, dependencies, timing and price, then approve a change or move the item into a later phase.
When should the model be reviewed?
Review it when certainty, backlog behavior, team ownership, urgency or required capacity changes materially.
Choose the model using the work in front of you.
Send the deliverables you already know, the questions still open and the cadence your team needs. We can propose a working arrangement that makes priorities, approvals and delivery responsibilities explicit.