How to Hire a Shopify Plus Agency (2026): RFP, 32 Questions, Red Flags

Hiring a Shopify Plus agency
Hiring a Shopify Plus agency comes down to four things: define the scope before you ask for prices, shortlist three agencies with references in your size band, ask the same 32 questions of each, and require the handover terms in the contract. Most failed builds are visible in the first two calls — a team you cannot name, a process nobody describes, and an estimate with no integrations line.
Key takeaways
- Agencies price ambiguity. A vague brief produces a padded quote.
- Partner tier measures build revenue, not fit for your project.
- Ask for the named team and two references in your size band.
- No integrations line in the estimate means the estimate is incomplete.
A Shopify Plus build is usually a six-figure decision made on the basis of three slide decks and one call. The failure modes are consistent and almost all of them are detectable before you sign: a team you never meet, a process nobody can describe, an estimate with no integration line, and a handover with no contractual definition.
This is the process we would use if we were buying, including the questions that are awkward to ask. If you want the shortlist itself, our guide to the [best Shopify Plus agencies](/blog/best-shopify-plus-agencies) compares the market on published criteria.
Step 1: define the scope before you ask for a price
Agencies estimate against what is written down. If your brief says "replatform to Shopify Plus", the quote is a guess with a margin attached, and every subsequent change is a change order. The scope document does not need to be beautiful — it needs to be specific about the things that actually consume engineering time.
- Catalog size and shape. SKU count, variant count, number of collections, number of images, and whether the data is clean.
- Integrations. ERP, PIM, 3PL, tax, subscriptions, reviews, search, support desk, and anything with a nightly job. This is where budgets go.
- Markets and currencies. How many, in which regions, and whether pricing is localised or converted.
- B2B requirements. Company accounts, price lists, net terms, quote-to-order, ERP sync — or none of it.
- Checkout and customisation. Checkout extensibility, Shopify Functions, post-purchase, and any scripted discounting that was retired with Scripts.
- SEO history. Indexed URL count, top organic pages, redirect requirements, hreflang structure. Omitting this is how migrations lose traffic.
- Content and merchandising. Who is writing product copy, who is loading it, and whether assets exist or need producing.
The cheapest hour you will spend
Export every indexed URL from your current site and hand it to shortlisted agencies. It costs an hour and it separates the agencies that plan migrations from the ones that plan launches. A proposal that ignores your existing URL inventory is a proposal that will lose you traffic.
Step 2: understand what the market actually charges
| Project type | Typical published range | Timeline | What drives the number |
|---|---|---|---|
| Focused replatform, standard theme | $25,000–$60,000 | 8–12 weeks | Data migration, redirects, app parity |
| Custom Plus storefront | $60,000–$150,000 | 3–5 months | Design, custom sections, checkout extensions |
| Enterprise / multi-market Plus | $150,000–$250,000+ | 4–9 months | ERP, B2B, markets, integrations, QA |
| Hydrogen / headless | +30–60% over equivalent Liquid | +2–4 months | CMS, caching, SEO parity, two codebases |
| Ongoing development retainer | $5,000–$20,000/mo | Monthly | Sprint capacity, on-call, roadmap |
| Migration SEO (separate) | $5,000–$15,000/mo or fixed | 3–6 months | URL inventory size, markets, redirect debt |
Two things to read into that table. First, the spread inside each band is real — the same scope can differ by 2× between a boutique and a large agency, and that difference is not quality, it is overhead. Second, migration SEO is frequently excluded from the build quote and then bought separately after the traffic falls, which is the most expensive order to buy it in.
Step 3: shortlist three, and only three
One is not a process. Five wastes a month and stops you comparing on substance. Three gives you a real comparison without exhausting your team.
- Filter on published work that resembles your catalog and market structure, not on portfolio logos.
- Ask for two references in your size band — not your industry, your size band. A 40-SKU DTC brand and a 12,000-SKU multi-market retailer have different problems.
- Send the same scope document to all three and require written responses to the same questions.
- Meet the named team, not the sales team. If the people on the call are not the people on the project, ask why.
- Compare proposals on the assumptions page, not the price page. The assumptions are where the scope quietly shrinks.
Step 4: the 32 questions
Grouped because they reveal different things. Ask all of them of every agency, and take notes on how the answers are given, not only what is said.
Team and continuity
- Who is the named lead on our project, and what else are they running?
- Which of the people on this call will actually work on the build?
- How many Shopify Plus builds did this specific team ship in the last 12 months?
- What happens if our lead leaves mid-project — who inherits, and what is documented?
- Are any roles subcontracted, and which?
Technical capability
- Show us a build that used checkout extensibility or Shopify Functions — what did it do?
- Have you shipped B2B on Plus with company accounts and price lists? Describe the ERP sync.
- What is your position on Hydrogen versus Liquid for our catalog, and why?
- How do you handle multi-market pricing and expansion stores when markets need different catalogs?
- What is your approach to scripts retired in favour of Functions — what replaced them on your last build?
- How do you test a build before launch, and what does the QA checklist contain?
- Who writes the theme code, and is it reviewed by someone else before merge?
Migration and SEO
- How do you build the redirect map, and from what source?
- Who owns hreflang on a multi-market migration?
- How do you verify render parity if we go headless?
- What happens to our indexed URLs that have no Shopify equivalent?
- Who monitors indexation in the 90 days after launch, and what triggers a rollback?
Process
- Describe the process from kickoff to launch in stages, with what we approve at each gate.
- How do we see progress — staging URL, ticket board, weekly demo?
- What is your change-order process, and what triggers one?
- How do you handle a scope discovery in week six?
- What is your definition of done for a sprint?
Commercial and handover
- What exactly is excluded from this quote?
- Who owns the repository, the Shopify partner account access and the app billing at the end?
- What does the handover pack contain, and is it a contractual deliverable?
- What is the warranty period after launch and what does it cover?
- How is the retainer scoped after launch — capacity, or an itemised roadmap?
- What happens if we want to bring development in-house in 12 months?
Judgement
- What would you tell us not to build, and why?
- Where do you think our scope is wrong?
- What has gone wrong on a build you shipped, and what did you change afterwards?
The last three are the most informative. An agency that cannot name something it would cut, or a build that went wrong, is either new or not being candid. Both are useful to know before you sign.
Red flags that predict a failed build
| Red flag | What it predicts |
|---|---|
| No named team on the proposal | You are buying capacity, not expertise. The good people are on someone else's project |
| An estimate with no integrations line | Every integration becomes a change order |
| No migration or redirect plan | Traffic loss in the 90 days after launch |
| Can't name a build that went wrong | Either inexperience or a story being managed |
| Design presented before scope is agreed | The visual will anchor the budget and the engineering will be squeezed |
| References only from brands much larger than you | Your project is a portfolio entry, not a priority |
| Handover not defined in the contract | You will discover the gaps the week your retainer ends |
| Everything is possible, nothing is priced | The proposal is a sales document, not an estimate |
Agency, in-house, or hybrid
In-house makes sense when there is a permanent roadmap and you can hire and keep Shopify engineers. An agency makes sense for a defined launch, a migration, or a capacity gap. Most Plus brands end up hybrid: an agency for the build and migrations, and either a small internal team or a light retainer for iteration.
What does not work is in-house for a one-off enterprise build, because the hiring, ramp and retention cost exceeds the project. Nor an agency on a bare-bones retainer for continuous development, because the context switching costs more than the hours.
Switching without losing traffic
If you are replacing an agency rather than hiring the first one, the handover is the risk. Define it as a deliverable with acceptance criteria, and hold the last payment against it.
- Repository access and full branch history, not just the current theme.
- An app inventory with owner, purpose, billing and whether it is load-bearing.
- The redirect map as it exists today, plus any redirect chains.
- Integration documentation: what talks to what, on what schedule, and who owns the credentials.
- Analytics, tracking, consent and tag configuration, documented.
- A staging environment that matches production, and the steps to deploy.
- An indexation baseline from Search Console captured on the day of handover.
Most post-handover losses come from undocumented changes made directly in the live theme and from a redirect map nobody updated. Both are visible in an audit within a week, and neither is expensive to prevent.
The RFP template
Keep it to four pages. A longer RFP produces longer proposals, not better ones.
- Business context: who you are, revenue band, growth goal for 12 months, and why now.
- Current stack: platform, catalog size, integrations, markets, team structure.
- Scope: what is in, what is explicitly out, and what you are undecided on.
- Constraints: budget band, launch window, blackout periods, internal approvals.
- SEO history: indexed URL count, top organic pages, any previous migrations.
- Success criteria: what must be true 90 days after launch.
- What to submit: named team, two references in your size band, staged estimate, assumptions page, timeline with gates.
- Decision criteria and dates: how you will score proposals, and when you will decide.
The two questions that do the most work are the assumptions page and the named team. Together they convert a sales proposal into something you can hold someone to.
If you are still deciding whether Plus is the right platform at all, start with the [Shopify Plus cost guide](/blog/shopify-plus-pricing-guide). If you already know the build is happening and the risk is SEO, read [Shopify Plus migration SEO](/blog/shopify-plus-migration-seo) before you sign anything.
Want a second opinion on a Plus proposal?
An independent read on scope, estimate and migration risk — including the parts of the proposal that will become change orders.
Book a callFrequently asked questions
How much does a Shopify Plus agency cost?
Published project fees cluster from roughly $25,000 for a focused rebuild or a small Plus launch to $250,000 and beyond for a multi-market enterprise build with ERP integration and B2B. Retainers for ongoing development typically run $5,000 to $20,000 a month. Treat any quote given before someone has looked at your catalog, integrations and market structure as a placeholder rather than a price.
How long does a Shopify Plus build take?
A focused replatform with a standard theme and a handful of integrations typically takes 8 to 14 weeks. Enterprise builds with ERP, B2B, multi-market, custom checkout extensions or headless architecture run 4 to 9 months. The variable is not the storefront, it is integrations and content migration — and every estimate that omits those two is optimistic.
What is the difference between a Shopify Plus Partner and a good agency?
Partner tiers measure build revenue and app adoption, not the quality of your project. A Platinum partner can still be the wrong fit for a mid-market brand with a two-market catalog. Ask for the team who will actually work on the account, the process they use, and two references in your size band rather than a tier badge.
Should we use a Shopify Plus agency or build in-house?
In-house makes sense when you have a permanent roadmap that needs continuous development and you can hire and retain Shopify engineers. Agencies make sense for a defined launch, a migration, or a periodic capacity gap. Most Plus brands end up hybrid: an agency for the build and migrations, in-house or a small retainer for ongoing iteration.
How do we switch Shopify Plus agencies without losing traffic?
Treat the handover as an engineering deliverable with acceptance criteria: repository access, theme branch history, app inventory with billing owners, redirect map, integration documentation, analytics and tracking configuration, and a staging environment that matches production. Most post-handover losses come from undocumented changes made directly in the live theme, not from the switch itself.
What should be in a Shopify Plus RFP?
Business context and goals, current platform and catalog size, integrations and data flows, market and currency structure, B2B requirements, evidence of the SEO history, timeline and budget band, team structure on your side, decision criteria, and a request for the named team and two references in your size band. Agencies price the ambiguity, so ambiguity is expensive.
Do we need a Plus agency or will any Shopify agency do?
If the project involves checkout extensibility, Shopify Functions, B2B company accounts, expansion stores, ERP integration or multi-market pricing, you need Plus-specific experience. If it is a themed DTC storefront, a strong standard Shopify agency is usually better value. Plus capability is expensive and pointless if the project does not use it.
How many agencies should we shortlist?
Three. One is not a process, and five wastes everyone's time because you stop comparing on substance. Shortlist on published work and a reference in your size band, then use the same brief and the same questions for all three so the proposals are comparable.


