Fixed Price, Hourly or Retainer for Shopify Development
When you ask for Shopify development work, the quote arrives in one of three shapes: a fixed price, an hourly or daily rate, or a monthly retainer. Merchants usually compare the totals and pick the smallest. The shape of the quote matters more than the number, because it decides who carries the risk when the work turns out bigger than expected. This guide explains how each model works, when each one fits, and how to spot a quote in the wrong shape for your project.
It is written for store owners and founders buying Shopify work, and it uses no price figures, because the right number depends entirely on your scope.
What are the three ways to pay for Shopify development?
- Fixed price. One agreed amount for a defined piece of work. If it takes longer than estimated, the developer absorbs the cost. If the scope changes, the price changes.
- Hourly or daily rate. You pay for the time actually spent. If the work is quicker than expected, you save. If it is harder, you pay more.
- Monthly retainer. A fixed monthly amount for an agreed level of ongoing work, availability or both, usually with a set number of hours or a defined scope of recurring tasks.
None of these is better in general. Each one is the right tool for a different kind of uncertainty.
When does a fixed price make sense?
When the work can be described completely before it starts. A theme migration from a known design, a set of product page changes with approved mockups, a specific integration with a documented system on both sides: these are fixed price work, because a competent developer can see the whole job before quoting.
The advantage for you is certainty. You know the cost, you can approve a budget, and the developer is motivated to finish efficiently because overruns come out of their margin.
The catch is that a fixed price is only as fixed as the scope underneath it. A developer quoting a fixed price on a vague brief has two choices: pad the number to cover the unknowns, or quote low and recover the difference through change requests. Both are rational responses to an unclear brief. Neither is good for you. If you want a fixed price, the work you owe is a scope precise enough to price, which we cover in our guide to reading a Shopify quote.
When is hourly billing the better choice?
When nobody can see the whole job yet. Diagnosing why a store is slow, tracing a bug that only appears with a certain combination of apps, or exploring whether an integration is feasible: the honest answer to "how long will it take" is "we will know once we look."
Forcing a fixed price onto that kind of work usually produces a large, padded number. Hourly billing lets you pay for what the investigation actually takes, and stop when you have the answer you need.
Three protections make hourly work safe:
- A cap. A number of hours after which work stops and you are asked before continuing.
- Regular updates. A short written note of what was done and what is next, at least weekly, so hours do not accumulate unseen.
- A defined first milestone. For example, a diagnosis with a recommended fix, after which the fix itself can be quoted at a fixed price.
That last point is the pattern worth knowing: pay hourly to remove the uncertainty, then switch to a fixed price for the work that follows.
When does a monthly retainer make sense?
When the work is ongoing and the value is in availability as much as output. Stores with customised themes, custom integrations or frequent campaigns generate a steady flow of small changes and checks. Quoting each one separately wastes everybody's time.
A retainer should buy you three things: a defined set of recurring work, a known response time when something breaks, and a developer who already knows your store. The last one is easy to undervalue. A developer who has worked on your theme for six months fixes a problem faster than a new one reading the code for the first time.
What a retainer should not be is a project budget paid in instalments. When a large feature is squeezed into retainer hours, it takes months, the routine checks get skipped, and nobody can tell whether either is on track. We cover where that line sits in our guide to what a maintenance plan should include.
How do you tell if a quote is in the wrong shape?
Look at how the quote handles uncertainty. These are the common mismatches:
- A fixed price for investigation work. "Fix site speed" or "find out why orders are missing" quoted as one number usually means the number includes a large allowance for surprises, or the scope will shrink quietly once work starts.
- Open ended hourly billing for well defined work. If the job can be described completely, you should not be carrying the risk of it taking longer.
- A retainer with no defined deliverables. Hours that roll over, expire or get used without a report are a subscription, not a service.
- A fixed price with no change process. Every project changes. A quote that does not say how changes are priced and approved leaves the most expensive conversation for later.
What should every quote include, whatever the model?
- What is included and what is not, in plain language. The exclusions tell you more than the inclusions.
- What you need to provide: content, designs, access, decisions, and by when.
- How changes are handled: who approves them, how they are priced, and how they affect the timeline.
- What done means: the acceptance test, and how long you have to report problems after delivery.
- What you get at the end: documentation, a list of customisations, and access handed back. Our handover checklist lists what to ask for.
A quote without these is not necessarily dishonest. It is incomplete, and the missing parts will be negotiated later, when you are in a weaker position to say no.
What does Shopify say about briefs and billing?
Shopify's guidance for merchants hiring through its Partner Directory makes the same point about scope from the other side. It asks merchants to "define your budget, timeline, and expected outcomes in detail to allow the Partner to provide an accurate quote." An accurate quote starts with a detailed brief, whichever pricing model you end up choosing.
Two more details from the same page are worth knowing before you agree terms:
- Shopify is not a party to the payment. "The Partner will bill you directly, and these charges don't display on your Shopify bill." Your payment terms, milestones and any dispute are between you and the developer, so put them in writing.
- Access is usually through a collaborator account. Partners may need to access your store through a collaborator account, which you approve and can remove. Agree what permissions the work needs, and remove access when the engagement ends.
The Partner Directory also lets you filter Partners by price range, which is useful for a shortlist but says nothing about how a given Partner prices risk. Two developers in the same range can quote the same job very differently depending on the model they choose, which is the point of this guide.
If you are comparing two quotes in different shapes, convert them into the same terms before comparing totals. Ask the hourly quote for an estimate range and a cap, and ask the fixed price quote what assumptions sit behind it. Only then are the numbers comparable.
Can you combine the models?
Yes, and for most real projects you should. A common and fair structure looks like this:
- A short paid discovery, billed hourly or as a small fixed fee, to understand the store, the problem and the constraints. The output is a written scope.
- The build, at a fixed price against that scope, with a clear change process.
- Ongoing care, on a retainer, once the work is live and needs looking after.
This puts each kind of risk with the party best placed to manage it. You pay for the uncertainty to be removed, the developer commits to a price once they can see the work, and the relationship after launch has its own terms rather than being an afterthought.
If a developer resists paid discovery on a complex project, ask how they will price the unknowns instead. The answer is usually padding, and you pay for it either way.
Want help choosing the right model for your project?
Free scoping call. Get in touch or email hello@exactwhy.com with the subject "Scoping" and a short description of the work. We reply within 4 hours and tell you which parts can be priced now, which need a short discovery first, and what that discovery would cover.
Quote review. If you already have a quote from another developer and want a second opinion on its shape and gaps, send it over. We will tell you what is missing before you sign.