# Discovery Questions to Ask Before Quoting a Shopify Project

> The discovery questions Shopify agencies should ask before quoting, grouped by phase: business, stakeholders, technical, scope, and budget.

_Published: 2026-08-07 · CommerceCopilot_

## Why the specific questions matter more than the number of them

Every agency has a discovery call. Fewer have a discovery call that reliably surfaces the things that change a quote. The difference usually is not effort. It is that the questions asked are generic ("tell me about your project") instead of specific enough to expose the assumption that turns into a change order six weeks later.

A good set of client discovery questions is not a long questionnaire. It is a short, ordered list that matches the shape of a [discovery process](/blog/shopify-agency-client-discovery-process): business context first, then stakeholders, then technical reality, then the edges of scope, then money and time. Ask them in the wrong order and you get a technical conversation before anyone has agreed on the outcome. Ask them in the right order and each answer narrows what the next question needs to cover.

PMI's research on requirements management puts a number on what happens when this goes badly: 47 percent of unsuccessful projects fail to meet their goals because of inaccurate requirements. Discovery questions are the mechanism that catches inaccurate requirements before they become the plan.

## Phase 1: business and outcome questions

These come first because everything downstream, including whether a feature is in scope, gets judged against the answer.

- **"What changes for your business if this project succeeds?"** Forces a concrete outcome instead of a feature list. "We want a faster checkout" is a request. "We're losing 8 percent of mobile carts at the shipping step" is an outcome you can design and measure against.
- **"What's driving the timing of this now?"** A launch tied to a funding round, a seasonal peak, or a contract renewal changes how much risk is acceptable in the plan. A project with no external deadline can absorb a slower, more thorough discovery phase.
- **"What have you already tried, and why didn't it work?"** Surfaces prior agencies, internal attempts, or app-based fixes that failed, along with the reason. Skipping this question means you risk re-proposing something the client already ruled out.
- **"How will you know this worked, three months after launch?"** Gets a success metric on record before the project starts, so "done" has a definition beyond "the client stopped asking for changes."

## Phase 2: stakeholder and decision-making questions

Skipping this phase is how a scope that looked settled reopens in week four, when someone who wasn't in the first call joins a later one with a different opinion.

- **"Who signs off on the final scope and budget?"** Not who is on the call. Who has to say yes. If that person is not in the room, treat everything discussed as provisional until they weigh in.
- **"Is anyone else going to need to approve this who hasn't been part of the conversation so far?"** Legal, brand, or a regional team can appear late in a project and reopen decisions that felt closed. Naming them early does not remove the risk, but it lets you plan around it.
- **"How do you prefer to review and approve work as we go?"** A client who wants to review every ticket needs a different cadence than one who wants a single milestone demo. Mismatched review expectations are a common source of "scope creep" that is really a communication gap.

## Phase 3: technical and platform questions

This is the phase most likely to get compressed or skipped when a quote needs to go out quickly, and it is the one most likely to blow up an estimate when it does.

- **"What's the current tech stack, including every app and any custom code?"** Ask for a list, not a summary. Clients routinely forget to mention an app that turns out to touch the exact area you are rebuilding.
- **"Is there anything in the current build that a developer built one-off and nobody else understands?"** This question catches undocumented custom logic before it becomes a mid-project surprise. Most clients know the answer is "yes, something" even if they cannot say what.
- **"Where does your product, order, and customer data actually live?"** Relevant for any project touching checkout, loyalty, or personalization. A migration or integration quoted without knowing this is a guess with a number attached.
- **"What's your current hosting, domain, and DNS setup, and who has access?"** A launch can stall for days over access, not code, if this is not confirmed before a go-live date is promised.

## Phase 4: scope boundary questions

These questions exist to draw the line between what is in the project and what only sounds like it should be.

- **"If we build exactly what we've discussed and nothing else, is that a win?"** A direct way to test whether the conversation so far has actually captured the full ask, or whether there is an unstated assumption still sitting in the client's head.
- **"What's explicitly out of scope, even if it sounds related?"** Naming the boundary out loud, and writing it into the proposal, gives you something to point to later instead of relitigating scope in a change-request conversation.
- **"Which parts of this are you confident about, and which parts are you still deciding?"** Separates the confirmed scope from the assumed scope before the quote goes out, which is the same distinction that [Shopify project scoping](/blog/shopify-project-scoping) depends on to price accurately.

## Phase 5: budget and timeline questions

Money and time questions go last because an honest answer to either one depends on everything the earlier phases already established.

- **"What's the budget range, not the exact number?"** A range ("$15,000 to $25,000") is more useful than a single figure a client might inflate or deflate, and it lets you flag early if the scope discussed does not fit the range at all.
- **"Is there a hard deadline, or a preferred one?"** These require different plans. A hard deadline (a product launch, a contractual date) should shape which pricing model and which scope decisions make sense; a preferred date has more room to negotiate against.
- **"Would you rather have price certainty or scope flexibility?"** This single question tells you whether fixed price or time and materials fits the engagement better, before you draft the proposal instead of after the client pushes back on it.

## A discovery questions checklist

- Open with outcome and timing questions before anything technical, so scope gets judged against a real goal.
- Confirm who actually signs off, and ask directly whether anyone else will need to approve later.
- Get a full list of apps, custom code, and data locations before pricing anything that touches them.
- Name what's out of scope out loud, not just what's in.
- Separate confirmed answers from assumed ones, and carry that distinction into the proposal.
- Ask for a budget range and a deadline type (hard or preferred) rather than treating both as fixed facts.

## Where this gets harder to sustain as an agency grows

Asking the right questions once is a discipline. Asking them consistently, on every call, for every client, while someone new joins mid-project with a different answer than the one already on record, is an operational problem. That is usually where a documented question list stops getting used: the senior person who wrote it is not the one running every discovery call anymore.

CommerceCopilot's Business Analyst agent is built to hold that consistency. It works from the same discovery structure, business context, stakeholders, technical reality, scope boundaries, and budget, across every connected call, Slack thread, and document, and it flags a gap the moment one of these questions has not actually been answered, instead of letting the project move forward on an assumption. The [discovery project guide](/docs/your-first-discovery-project) covers how it builds that model and turns confirmed answers into sequenced tickets once enough of the picture is settled.

## FAQ

### How many discovery questions should a Shopify agency ask before quoting?

Fewer than most checklists suggest. The goal is not volume, it is covering five areas: business outcome, stakeholders, technical reality, scope boundaries, and budget or timeline. A dozen well-chosen questions across those areas beat forty generic ones that overlap.

### What's the one discovery question agencies skip most often?

"What's explicitly out of scope?" Most discovery conversations establish what is in, and few name what is out loud enough to point back to later. That gap is where a lot of scope disputes start, not from a missing feature but from an unstated assumption about a boundary nobody actually confirmed.

### Should discovery questions change based on project size?

The categories stay the same; the depth changes. A small storefront update might resolve all five phases in one structured call. A larger build, especially with multiple stakeholders or integrations, usually needs the technical and stakeholder phases spread across more than one conversation, which is also where a [documented discovery process](/blog/shopify-agency-client-discovery-process) starts to matter more than a one-time question list.

---
Canonical page: https://www.commercecopilot.ai/blog/shopify-agency-discovery-questions