Ecommerce consultancy
What to change, what it will cost, and what to leave alone.
That is what a discovery engagement ends with: your operation mapped as a system, and a recommendation you can defend to your board.
Two to four weeks of structured work, ending in a document you can hand to any supplier, including us.
Systems architecture and discovery maps how a business actually works, including the parts held in a few people's experience, and ends in a decision about where to invest. We look at the operation before the software: what the business sells, how an order becomes a delivery, which rules are real and which are habits, and where the complexity has been collected. Ecommerce consulting belongs before a budget is committed, because the cheapest moment to change direction is the one before the contract is signed.
The agency proposes a build, the vendor proposes a license, and your own team divides between the people who keep the current system running and the people who have to sell around it. Each position is honestly held, and each is shaped by what the person holding it has to gain.
The constraint that limits the business most is often missing from all of those proposals: a pricing rule only one person can explain, a supplier who sends data in its own format, or an approval step kept long after the incident that caused it.
Every step from order to delivery, drawn with the people who run it: which systems the data passes through, where it is rekeyed, which exceptions exist and who handles them.
The three or four things that actually limit the business, each with what it costs and what removing it would take. Some turn out to be commercial or organizational, and saying so is part of the job.
Every capability the plan depends on, rated ready, partly ready or absent, with the evidence behind each rating.
A clickable version of the flow being argued about, so the discussion happens over something people can use. When the decision goes ahead, that code is written to be reused in the build.
What to do, in what order, what each phase will take, and what to leave alone for now, with the alternatives and why they were not chosen.
Maxilia was a replatforming project with a wide set of work around it, including interim technical leadership, assembling the delivery team, and the requirements work. The workshops surfaced enough gaps in the existing plan that we recommended rebuilding the requirements before the build started, which pushed back work we would have been paid to deliver. For a retailer weighing a full rebuild, our conclusion was that the money would do more elsewhere, and we said so instead of quoting for it.
Both conclusions came out of mapping the operation first. The reasoning is written down in full, so you can weigh the recommendation against the interest of its authors, ours included.
The decision the engagement has to settle, written down in one sentence with everyone who will act on it. A vague question is what makes a discovery worthless.
Sessions working through real orders, real exceptions and real customers, which is where the documented process and the real one differ.
The assumptions that would be expensive to get wrong get a prototype, a data check, or a conversation with the system's owner, while there is still time for the answer to change the plan.
The recommendation, the alternatives considered, and what would have to be true for each to become the right answer. Written for the board as well as for the team.
If the project is already underway and the question is how to finish it, the right engagement is a review.
Priced on its own
The engagement stands alone rather than being folded into a build, which is what makes the recommendation independent of what happens next.
Fixed scope, weeks rather than months
Long enough to map the operation and test what would be costly to get wrong, short enough that the decision is still live when the report arrives.
Yours to take anywhere
Everything the engagement produces is handed over to you: the map, the recommendation and the reasoning, costed and sequenced. Some of what we recommend is carried out by other suppliers or by your own team, and the document is written so that it can be.
A decision rather than a proposal
Every engagement ends with a recommendation and a reason, addressed to the person who has to sign it off, and it names what to leave alone as clearly as what to start.
The leadership team stops arguing from different pictures. Most of the disagreement turns out to have been about facts, and what remains is the smaller set of questions that genuinely need a decision.
Further out, the saving is a budget spent once, on the constraint that matters most. The decision also holds up once the work starts, because the team that will carry it helped draw the map behind it.
We are worth the money when the decision is large, the stack was assembled in stages over years, and the advice so far has come from people with something to sell.
A business that already knows the problem, the scope, and the answer can skip the discovery and go straight to building, with a nearshore team if it needs the capacity. If a conversation shows that this is your situation, we will say so before you commit to anything.
An ecommerce consultancy worth the fee maps how a business actually operates before recommending anything, then makes a call and stands behind it. The test worth applying to any of them, including us, is whether the engagement is able to conclude against the consultant's own commercial interest.
The operation as it runs today, the constraints that actually limit it, the capabilities the plan would depend on, and whatever is currently being taken on trust. It covers the commercial and organizational side as well as the technical one, because the blocker is often a rule, a channel relationship, or a person's workload. Expect several days of your own team's time, since the useful material comes from them.
A free workshop is funded by the work it is designed to sell, which shapes what it concludes. Charging for the engagement is what lets us recommend less work, a different supplier, or keeping the stack you already run. The fee is fixed and agreed before we start, whatever the engagement concludes.
Then that is the recommendation, with the reasoning and the conditions that would change it. We have delivered that answer to clients who were ready to sign. A decision to wait, taken deliberately and with the map in hand, is worth more than a project started on a hunch.