MarketPulse role guide
Ecommerce Consultant Vs Developer
A consultant hands you a decision. A developer hands you working code. This guide shows which of the two your problem needs first, with ten common store problems sorted into the right column.
Advice first when the answer is unknown; building first when it is.
The ecommerce consultant vs developer choice comes down to one thing: whether you already know what needs to change. A consultant works out what to do and why. A developer makes the change happen in the store. Hire a developer for an open question and you pay for code built on a guess; hire a consultant for a clear task and you pay for a report telling you what you already knew.
This page covers what each role produces, a quick test to sort your problem, ten common problems with the role that should go first, and the cases where one person can sensibly do both. If you have settled on the role and now need to decide between one person and a team, go on to agency vs freelancer.
What does each role actually produce?
The fastest way to tell the roles apart is to look at what lands on your desk when the work is finished.
| Ecommerce consultant | Ecommerce developer | |
|---|---|---|
| Main output | A decision, a recommendation report, a ranked list of changes or a written brief | Changed code, a configured store, a working feature, a connection between systems |
| You can check it by | Reading it and asking whether you could act on every point tomorrow | Using the store: placing an order, clicking the new feature, testing on a phone |
| Works from | Your sales data, your goals, your costs, conversations with you and your staff | A written task with clear acceptance criteria |
| Typical billing | Fixed fee per audit or workshop, or a block of advisory hours | Hourly, daily or fixed price per task |
| Typical length | One day to a few weeks | One afternoon to several months |
| Risk if misused | A thick document nobody acts on | A well-built feature that solves the wrong problem |
The Shopify Partner Directory files them in separate groups: “Expert guidance” (business strategy, sales tax, wholesale, international expansion) sits apart from “Development and troubleshooting” (custom apps, troubleshooting, connecting systems). Different skills, different listings.
Is your problem a question or a task?
Write the problem as one sentence and look at how it starts. Here is why that works: developers need instructions they can build and test, so a problem that cannot be phrased as an instruction is not ready for a developer yet.
- “Add a size guide pop-up to every dress product page.” That is a task. Anyone can tell whether it was done. Hire a developer.
- “Work out why people leave at the delivery step.” That is a question. Nobody can build anything until the reason is known. Start with a consultant.
- “Make the store faster.” Half and half. A speed-focused developer can measure and fix the obvious causes, while a consultant is more useful if speed is one symptom of a bigger choice (wrong theme, too many apps, wrong platform).
A second test: can you describe what “done” looks like? If you can write three acceptance criteria (sample: “the pop-up opens on mobile”, “it shows the size table for that product type”, “it closes with one tap”), you have a developer task. If you cannot, the missing piece is thinking, and thinking is what a consultant sells.
Which of these ten problems needs a consultant first, and which a developer?
Ten problems small shops bring to providers, sorted by the role that should go first.
| Problem | Go first | Why |
|---|---|---|
| 1. Choosing between Shopify and WooCommerce for a new shop | Consultant | A decision with long-term costs; a developer tends to recommend the platform they build on |
| 2. Online sales have dropped for three months | Consultant | The cause is unknown: traffic, prices, stock, competition or a broken page |
| 3. Checkout throws an error on one payment method | Developer | A clear fault with a clear test |
| 4. Adding local delivery with three zones and fees | Consultant, briefly | Pricing the zones is a business decision; the set-up afterwards is configuration work |
| 5. Connecting the till to the online stock count | Developer | A defined connection, though check first that the systems you have support it |
| 6. Deciding whether to start selling on a marketplace | Consultant | Fees, stock allocation and margin questions come before any listing work |
| 7. Rebuilding the product page template to a finished design | Developer | The design already answers the “what” |
| 8. Too many apps and rising monthly costs | Consultant | Someone has to decide which apps go; removing them is the easy part |
| 9. Importing 800 products from a supplier spreadsheet | Developer | A data task with a checkable result |
| 10. Planning wholesale prices for trade customers | Consultant | Price rules and account rules are business choices; the build follows them |
Notice how few of these are purely one role. Problem 4 needs an hour of thinking about fees and minimum orders, then a few hours of set-up. Our guide to local delivery zones shows how much of that thinking an owner can do alone.
In which order should you hire them?
When a project needs both roles, the usual order is consultant, then developer, then a short consultant review. Let’s break it down.
- Consultant: decide. They look at the data, talk to you and come back with a recommendation and a written brief the developer can quote on.
- Developer: build. They quote against that brief, build, and test against the acceptance criteria in it.
- Consultant: check. A short review (one or two hours) to confirm the build matches the recommendation and nothing was lost in translation.
Example timeline (invented project, planning figures only): a gift shop wants to add personalised engraving.
| Week | Who | Hours | Output |
|---|---|---|---|
| 1 | Consultant | 6 | Pricing rules for engraving, lead times, which products qualify, a one-page brief |
| 2 to 3 | Developer | 20 | Engraving option on qualifying products, text limit, order note for the workshop |
| 4 | Consultant | 2 | Review against the brief, list of three small fixes |
Total: 28 hours, of which 8 are advice. Skip the first step and the developer has to make the pricing and product decisions on the fly, or stop and wait for you to make them.
The reverse order (developer first) makes sense in one case: something is broken and losing sales today. Fix the fault, then ask the bigger questions.
What does hiring in the wrong order cost?
Two invented examples with the arithmetic shown. Rates are placeholders; use your own quotes.
Developer first, when the question was open. A shop pays a developer for 30 hours at $80 to build a custom bundle feature: $2,400. Three months later, a consultant points out that the platform’s existing discount settings covered most of what was wanted, and customers rarely used bundles anyway. A 3-hour consultant session at $100 ($300) before the build would have saved most of the $2,400 plus the monthly upkeep of custom code.
Consultant first, when the task was clear. A shop with a broken shipping rate hires a consultant for a $1,200 store review. The report’s first finding: the shipping rate is broken, fix it. A developer would have fixed it in 2 hours at $80 ($160). The review had other useful findings, but the urgent fault waited two weeks for them.
The pattern: developer-first mistakes cost more, because code needs maintenance after it is built and a wrong recommendation on paper does not.
When can one person do both jobs well?
Plenty of experienced developers give sound advice, and some consultants still build. One person covering both works when:
- The project is small, with one or two decisions and under about 40 hours of build work.
- The decisions are technical (which app, which theme structure, how to set up a feature) rather than commercial (pricing, channels, product range).
- The person shows you more than one option, including ones they would not build themselves.
Watch the conflict of interest. A developer who recommends work they will then bill for has a reason to recommend more build work. Their advice can still be right. Test it by asking: “What would you do if you were not the one building it?” and “Which part of this could I do in the admin myself?”
For larger or commercial decisions, keep the roles apart. Paying for a few hours of independent advice is cheap insurance on a build worth thousands.
How should you brief each role?
A consultant and a developer need different briefs, and sending the same one to both wastes money on each side.
A consultant brief sets out the question and the context
- The decision you need to make, in one sentence
- Why now, and what happens if you do nothing
- The data you can share: sales export, top products, traffic figures, current monthly costs
- Your limits: budget, staff time, platform you are tied to
- What you want back: a recommendation, two options with costs, or a brief for a developer
A developer brief sets out the task and the test
- What should change, on which pages or screens
- Acceptance criteria, written as checks anyone can run
- Design files or examples, if they exist
- Access needed and who grants it
- Deadline and any dates when nothing may change (sales, busy weekends)
A ready-made layout for the general project brief is on our ecommerce brief template page.
How do you hand work from the consultant to the developer?
Most value lost between the two roles is lost in the handover. A good consultant finishes with a document the developer can quote on without a meeting. Ask for these four parts:
- Decision log. What was decided, what was rejected and why. This stops the developer reopening settled questions.
- Ranked change list. Each change with its expected effect and a rough size (small, medium, large).
- Acceptance criteria. At least for the top three changes.
- Open questions. Anything the consultant could not settle, marked for the developer to answer during quoting.
Then send that document to two or three developers for quotes. If every quote asks the same clarifying question, the handover had a gap; ask the consultant to close it before you pick a developer.
FAQ
Is an ecommerce consultant more expensive than a developer?
Hourly rates vary too much to say. Consultants tend to work fewer hours per project, so the total is smaller even when the rate is higher. Compare the cost of the whole job, including the build the advice leads to.
Can a developer tell me which platform to choose?
They can, and many give honest answers. Most developers specialise in one or two platforms, so ask them to name the case where they would recommend a platform they do not build on. Our Shopify vs WooCommerce guide covers the platform choice for shops with a physical presence.
Do I need a consultant for a small store?
Only when you face a decision you cannot make with your own knowledge and the cost of getting it wrong is higher than the fee. A three-hour session before a platform choice or a big app purchase pays for itself; a full audit of a 20-product shop rarely does.
What should a consultant hand over at the end?
A written recommendation you can act on without them: the decision, the reasons, a ranked list of changes and a brief a developer can quote on. Slides alone are not enough unless they contain all of that.
Should the consultant pick the developer?
They can help you shortlist and read quotes. Make the final choice yourself and ask whether the consultant receives any referral payment from the developers they suggest.
What if the developer disagrees with the consultant’s plan?
Ask the developer to put the disagreement in writing with the reason and the cost difference. Then send it back to the consultant for one reply. Two written positions make the choice clearer than a three-way call.
Is a technical lead the same as a consultant?
No. A technical lead runs the developers on a build and makes technical decisions inside it. A consultant advises on whether and what to build. In small agencies the same person can wear both hats, so ask which one you are paying for.
What should you do next?
Write your problem as one sentence and run the question-or-task test. If it is a task, write three acceptance criteria and find a developer. If it is a question, list the data you can share and book a short consultant session first. Either way, set the next role’s brief before the first one finishes.
If you are unsure which side your problem falls on, describe it to MarketPulse through the contact form and we will help you frame it before you spend money.
Guides for each role
Read the guide for the role you picked, then prepare the brief.