# Fixed Price vs. Time and Materials for Shopify Builds > Fixed price vs time and materials for Shopify projects: how to pick the right model, and why scoping accuracy decides it more than preference does. _Published: 2026-08-12 ยท CommerceCopilot_ ## The real question behind fixed price vs. time and materials Ask a room of agency owners whether they prefer fixed price or time and materials and you'll get strong opinions on both sides, usually shaped by whichever one burned them last. That's the wrong way to pick. Fixed price vs. time and materials isn't a matter of taste or which side has more negotiating power. It's a question of how well you actually know what you're building, and picking the model that doesn't match your scope confidence is how a reasonable project turns into a fight about money. Both models are just different answers to one question: who absorbs the cost if the estimate turns out wrong? Fixed price puts that risk on your agency. Time and materials puts it on the client. Neither is safer in the abstract. Each is safer under different conditions, and most agencies pick based on habit rather than checking which condition they're actually in. ## What each model is actually asking of you **Fixed price** sets the deliverables, timeline, and total cost before work starts. The client gets budget certainty; your agency gets the job of absorbing anything the estimate got wrong. That only works if the scope going in is genuinely well-bounded: a defined migration, a checkout redesign, a store launch with a fixed feature list. Quote fixed price against a scope that's still fuzzy and every gap between what you assumed and what the client actually needs comes straight out of your margin. **Time and materials** bills for actual hours and costs as the work happens. The client keeps the flexibility to change direction, add scope, or drop something that isn't working, and your agency isn't stuck absorbing a bad estimate. The tradeoff shifts the other way: the client is now trusting your team's efficiency and your reporting, and a project without regular check-ins and a running total can drift on both sides, cost and confidence, well past what either party expected. Neither model removes risk. They just decide who's holding it when the estimate is wrong, and estimates are wrong more often than anyone likes to admit. Client requirements evolve mid-project even when everyone starts out aligned, which is exactly why the model you pick needs to account for how likely that drift is on a given project, not just this quarter's cash flow preference. ## The deciding factor: how settled is the scope, not how big the project is Agency owners tend to sort projects by size when picking a pricing model: small projects get fixed price, big ones get time and materials. Size is the wrong axis. A small project with an unclear brief is a worse fixed-price candidate than a large project with a fully resolved scope. The question that actually predicts which model will hold up is the same one that drives [Shopify project scoping](/blog/shopify-project-scoping): has discovery resolved the platform, the pages and flows in scope, the integrations, and the client's definition of done, or is meaningful ground still unconfirmed? If the technical check is done, the client has signed off on specific deliverables, and the remaining unknowns are small enough to price as a contingency line rather than a structural risk, fixed price is a reasonable trade: you're pricing something you actually understand. If discovery surfaced open questions that won't resolve before work starts, or if the client is still deciding between approaches, time and materials is the honest model, because a fixed number against an unsettled scope isn't really an estimate. It's a guess wearing a decimal point. This is also why the same client relationship often uses both models over time. A first engagement with an unfamiliar client and an ambiguous brief is a stronger time and materials case. A second or third project, once your team understands the client's stack and the brief is specific because you've done this kind of build with them before, is a stronger fixed price case. The model should track what you know, not what worked last time. ## A hybrid pattern worth using more often The pattern that avoids most of the friction on both sides is running discovery and scoping as its own fixed-price or flat-fee phase, separate from the build, and only committing to a build-phase pricing model once that phase is done. This solves the core problem with picking a model too early: you're being asked to choose your risk exposure before you know enough to choose it well. A short, paid discovery phase gives you the information a real pricing decision needs, the platform, the technical constraints, the confirmed vs. assumed scope, without betting the whole project on an estimate made before any of that was known. Once discovery is done, the choice gets easier because it's based on what you actually found. A tightly scoped, well-understood build can go fixed price with real confidence. A build where discovery turned up dependencies or stakeholder disagreement that didn't fully resolve can go time and materials, with the discovery findings as the shared reference point for what's already agreed versus what's still open. ## Where agencies get this wrong **Choosing the model before scoping instead of after.** The pricing model gets picked in the sales conversation, often before anyone has checked the client's current theme, apps, or integrations. Whatever gets agreed to at that point is locked in regardless of what discovery later reveals, which means the model was chosen on vibes rather than information. **Running time and materials without a budget ceiling.** Time and materials without a not-to-exceed number or a regular reporting cadence puts the client in the position of writing a blank check, and clients who feel that way stop trusting the relationship even if the billing is completely fair. A T&M engagement with weekly hours reported against a running estimate and a client-agreed ceiling for check-ins avoids this without giving up the model's flexibility. **Running fixed price without a documented change process.** Scope will move on a fixed-price project too. The agencies that keep their margin are the ones with a defined way to evaluate and price a new request when it shows up, agreed with the client before work starts. Without that, every legitimate new requirement becomes an argument about whether it was "supposed to be included." ## A quick decision checklist - Is the technical environment (theme, apps, integrations) checked, or still assumed? Unchecked favors time and materials. - Has the client signed off on specific deliverables, or just a goal? A goal favors time and materials until it's translated into a concrete scope. - Are there open questions that could change the shape of the build, not just its size? Open structural questions favor time and materials. - Is this a repeat client on a stack your team already knows? Familiarity favors fixed price. - Would a short, paid discovery phase resolve most of the uncertainty before you have to commit to a build-phase model? If yes, run it first and decide after. ## Where the decision actually gets made The fixed price vs. time and materials decision is only as good as the scope information it's based on, and that information usually lives across a handful of client calls, a Slack thread, and a stack of half-answered emails by the time someone has to make the call. CommerceCopilot's Business Analyst agent treats discovery as a continuous process rather than a single pre-quote conversation: it keeps a living model of what's confirmed and what's still assumed across every connected call, Slack channel, and document, and flags a gap the moment something is unclear instead of letting it slide into "probably fine." That's the same distinction [good discovery questions](/blog/shopify-agency-discovery-questions) are designed to surface, applied continuously instead of only in the kickoff call. When it's time to price a project, that running model of confirmed versus assumed scope is exactly what tells you whether the scope is settled enough for fixed price or still open enough that time and materials is the honest call. The [discovery project guide](/docs/your-first-discovery-project) covers how that model gets built before a single ticket is written. ## FAQ ### Can you switch pricing models partway through a project? Yes, and it's often the right move when discovery keeps running after the quote goes out. A project that started fixed price because the brief looked settled, but turned up major open questions once work began, is better served by renegotiating to time and materials for the unresolved portion than by absorbing an open-ended risk under a number that no longer reflects reality. The renegotiation is easier if the client already knows, from the original proposal, that scope changes trigger a pricing conversation rather than a silent absorption of extra work. ### Does time and materials mean the client has no cost certainty at all? No. A well-run time and materials engagement includes a not-to-exceed ceiling or a phase-by-phase budget, agreed before work starts, plus regular reporting against it. The client gets the flexibility of T&M without an open-ended bill, and your agency gets a documented checkpoint if the work is trending toward the ceiling before it becomes a surprise. ### Is fixed price ever right for an unclear scope? Only if you price in enough contingency to cover the specific unknowns you've identified, and you're honest with the client that the number includes that buffer. That's a narrower, riskier version of fixed price than most agencies mean when they use the term, and it's usually better handled by running a short discovery or scoping phase first and pricing the build once the scope is actually settled. ### How does this decision change for retainer or ongoing work? It mostly doesn't apply the same way. Retainers are typically priced as a recurring block of capacity rather than against a fixed deliverable list, which makes them closer to time and materials in spirit, capacity for hire rather than a fixed outcome purchased. The fixed price vs. time and materials choice matters most for discrete projects with a defined start and end. --- Canonical page: https://www.commercecopilot.ai/fr/blog/fixed-price-vs-time-and-materials-shopify