Choosing a Shopify Partner: The Questions That Come Up After You Sign
Every Shopify agency shows you finished work. The differences that matter show up later, in the contract, the process and the handover.

Contents
- Ask what happens when a project goes wrong
- Find out who is actually doing the work
- Check the handover before you need it
- The contract points worth reading properly
- How to read a proposal that is cheaper than the others
- Start with a small paid project, not the whole build
- How agencies price, and what each model does to your project
- Red flags, in rough order of seriousness
- What a good discovery call sounds like
- Certifications tell you less than you would hope
- Two questions that reveal the most
- What to do with all of this
Every Shopify agency will show you a portfolio of finished stores, and they will all look good. That is what portfolios are for.
The differences that actually affect you show up months later, in the contract, in how work gets handed over, and in what happens when something needs fixing urgently. Those are checkable before you sign, and almost nobody checks them.
Ask what happens when a project goes wrong
Not whether it has. It has. Ask what the process is.
You are looking for a specific answer: who tells you, how quickly, and what happens to the timeline and the invoice. An agency with a real answer has been through it and built a process. An agency that says it does not really happen is either new or not being straight with you.
Find out who is actually doing the work
The people in the pitch are frequently not the people who write the code. That is not automatically wrong, agencies have to sell and build at the same time, but you should know before rather than after.
- Who specifically will be on this project?
- Are they employed by you or subcontracted?
- How much of their week do we get?
- What happens if they leave mid-project?
That last question is the one worth pushing on. Every agency loses people. The ones worth hiring have thought about what that means for you.
Check the handover before you need it
Ask to see the handover documentation from a completed project. Not a template. A real one, with the client details removed.
This single request tells you more than any reference call. If they can produce it in a day, they work in a way that assumes you might leave, which is exactly the way you want somebody working. If it takes a week and arrives thin, that is what your handover will look like too.
The contract points worth reading properly
| Clause | What you want | Why |
|---|---|---|
| Intellectual property | Assigns to you on creation | Not on final payment, which leaves a gap |
| Code repository | Yours, access from day one | You should never wait for a zip file |
| Shopify account | In your name, your billing | Otherwise you cannot leave |
| Change requests | Priced method agreed up front | Stops every change becoming a negotiation |
| Notice period | Symmetrical | One-sided notice tells you the relationship |
| Post-launch support | Defined window and response time | Launch week is when you need it most |
None of these are aggressive requests. They are ordinary. Watch how somebody reacts to being asked, because the reaction is the information.
How to read a proposal that is cheaper than the others
A cheaper quote is not automatically worse. Sometimes an agency is faster because it has built your kind of store many times. Sometimes it is cheaper because it left things out.
The way to tell them apart is to check the five things quotes most often exclude:
- Data migration, especially customers, orders and URL redirects.
- Integrations with your accounting, warehouse or ERP systems.
- Content entry. Somebody has to put the products in. Often that somebody is you.
- Post-launch support, and for how long.
- Testing across devices and countries, rather than on the developer's own laptop.
A cheap quote that includes all five is genuinely cheaper. A cheap quote missing three of them is the same price with the difference deferred.
Start with a small paid project, not the whole build
The single most useful thing you can do is buy a small piece of work before committing to a large one. Not a free trial, which attracts the wrong behaviour on both sides. A real, paid, useful job.
A good first project has four properties. It is genuinely needed regardless of who does the rest. It takes one to two weeks. It touches code rather than being pure design. And it has a definition of done you could check yourself.
You are not really buying the fix. You are buying the answer to five questions that no pitch meeting will tell you:
- Do they ask good questions before starting, or start immediately?
- Do they tell you when they hit a problem, or go quiet and hope?
- Does the estimate survive contact with the work?
- Is the handover any good when the stakes are low?
- Is it pleasant? You are potentially doing this for years.
The cost of finding out this way is one small invoice. The cost of finding out during a full build is the build.
How agencies price, and what each model does to your project
| Pricing model | Their incentive | Watch for |
|---|---|---|
| Fixed price | Finish fast, limit scope | Everything becoming a change request |
| Time and materials | No pressure to be quick | Estimates that drift with nobody accountable |
| Monthly retainer | Keep you happy over time | Quiet months where you get little |
| Value or outcome based | Aligned in theory | Arguments over what caused the outcome |
There is no honest model and no dishonest one. Each sets up a different pull, and the useful move is to name it out loud at the start. An agency willing to discuss how its own pricing might distort its choices is showing you something worth knowing.
Red flags, in rough order of seriousness
- They will not name who does the work. The most common source of a bad outcome.
- Everything is possible. Shopify has real limits. Somebody who does not mention any has not hit them.
- Pressure to sign this week. Discounts that expire are a sales tactic, not a scheduling reality.
- No questions about your data. Migration is where projects overrun. Not asking means not having planned it.
- The proposal has another client's name in it. It happens more than you would think, and it tells you how much of this is copy and paste.
- They disparage your current supplier heavily. They will talk about you the same way later.
What a good discovery call sounds like
You should come away from a first call having learned something, even if you never hire them.
The signals worth noticing: they spend most of the call asking rather than presenting. They ask about your business before your website. They raise a risk you had not considered. And at some point they say something is a bad idea, which is the hardest thing for anybody selling to do.
If a first call is forty minutes of slides about their process, that is what working with them will feel like.
Certifications tell you less than you would hope
Shopify has partner tiers, and they mostly reflect volume of business put through the platform rather than the quality of any individual build.
It is a signal that an agency is established. It is not a signal that your project will go well. A small team that has built forty stores in your category is a better bet than a large one that has built four hundred in every category.
Two questions that reveal the most
What kind of project do you turn down? An agency that never says no has no standards, or no work. Either way you find out something.
What would you do differently on the last build you shipped? Anybody who has genuinely shipped has an answer. It is a question people cannot prepare for, and the quality of the answer scales with real experience.
What to do with all of this
You do not need to run every check on every agency. Pick the three that matter most for your situation and apply them consistently to your shortlist, so you are comparing like with like.
For most stores the three highest-value checks are: who is actually doing the work, what the handover looks like, and whether the intellectual property assigns to you on creation.
We answer all of these before anybody signs anything, and we would rather lose the work than discover a mismatch in month three. You can see how we vet developers and our approach to Shopify development.
Have a shortlist already? Send us their proposals and we will tell you what questions we would ask each one. Get a second opinion.

Articles from the Code Elevator team, the engineers and specialists who vet developers, ship client work, and write up what they learn along the way.
More from CodeFour clients, on camera.
Why he brought his development work to Code Elevator.
One useful piece a month, no more than that.
What we learned building and hiring for this work. No newsletter filler.
Reading about it is step one. Building it is step two.
Hire a pre-vetted engineer who has shipped work like this before. Matched within 48 hours.
We reply within an hour during our working day in India and the UAE.


