Working with an Ecommerce Consultant: Process and Expectations

The First Month: Diagnosis and Road Map

The relationship starts with diagnosis, not sales; that is the first month’s work.

The discovery meetings: the week of questions

In the first meetings the side doing most of the talking is you: product, cost structure, existing channels — home-market and Turkish — team, goals. You hear no recommendations at this stage; if you do, be suspicious. A prescription without diagnosis is the same mistake in every sector. The first weeks’ job is listening; the speaking turn comes later.

Data access and the current-state photograph

Store panels, sales reports, advertising accounts: read access is granted, the photograph is taken — a step that works identically from any country, which is exactly why it anchors a cross-border engagement. Narrative without numbers misleads; even in settled businesses a gap appears between the account given and the data found, and that gap is the diagnosis itself. The photograph sometimes stings; treatment starts with the photograph.

The diagnosis report and road-map presentation

The first month’s output is written: where you stand (in numbers), the problems in priority order, a three-to-six-month road map, each step’s owner and measure — delivered in English, with the Turkish market’s specifics translated into decisions, not left as local folklore. The report is debated in the presentation meeting; objections are spoken at the table, and the map is finalised together. A plan accepted without objection is a plan not yet owned.

The expectations contract

Alongside the road map, the division of labour is written: which work sits with us, which with you, who holds which decision rights — including who answers Turkish-language questions in daily operations. This document is the relationship’s constitution; when a “who was supposed to do this” debate arises later, it is opened, read, and the debate ends. Writing is the relationship’s cheapest referee — and across a time zone, its only reliable one.

The Division of Labour: Who Does What?

The table gathers the typical division; details calibrate per project.

The consultant gives reasoning, not instructions

Every recommendation arrives with its why: why this channel, why this tool, why the alternatives fell away. A business that understood the reasoning decides correctly without the consultant present; that is precisely the aim — and for a foreign owner, the written reasoning is also the audit trail across the language line. Instructions teach memorisation; reasoning teaches.

Daily operations sit outside the scope

Order fulfilment, customer messages, cargo tracking: the business’s daily life, and not consultancy’s scope. This border is drawn upfront, because an unlimited-scope promise exhausts both sides — and for a cross-border client, the Turkish-language service question inside that border is settled in writing on day one. A sharp border is the long relationship’s condition.

Your share: data, decisions, follow-through

Consultancy runs on the business’s hours too: requested data flowing on time, attendance at decision meetings, implementation of what was decided. An unimplemented recommendation produces the same result as one never given; the only difference is the invoice. Consultancy is not an archive of unapplied reports.

The common language: a written communication order

Instead of scattered call traffic, an order: a weekly short status note, a monthly report-card meeting, one channel for questions in between — an order that neutralises most of the time-zone gap, since writing waits patiently in any inbox. Writing is memory, for both sides.

The Monthly Rhythm: The Report-Card Loop

From month two the relationship settles into rhythm; the rhythm’s centre is the report-card meeting.

The monthly report-card meeting

The agenda is fixed: last month’s numbers against target, the working and the faltering steps, this month’s priorities. The meeting stays under an hour, because the preparation was written — and a written agenda is what lets one good hour bridge two countries’ calendars. A long meeting is the penalty of an unprepared one.

Numbers are spoken, not feelings

“It seems to be going well” is invalid at the card table; channel profitability, order cost and return rate are spoken. Feeling produces hypotheses; decisions come from numbers — numbers, usefully, that read identically in every language. The measurement routine was built in month one precisely for this table; the card forces both sides to look at the same reality.

The road map is a living document

Data corrects the plan: the working step deepens, the faltering one is revised. Blind loyalty to a three-month-old plan is no virtue; loyalty belongs to the goal, not the map. The map is the tool; the goal is fixed. Every revision is written with its reasoning — so whoever looks back six months later sees what changed and why.

The quarterly review: the big picture

Every three months the agenda widens: progress toward the goal, scope needs, the collaboration itself. Continue, narrow, widen or end — spoken openly at this table; consultancy need not be an endless subscription, and an honest consultant says so unprompted. Need sets the relationship’s lifespan; habit does not.

Signs of a Healthy Relationship — and the Red Flags

Two lists; both apply to both sides.

The healthy signs

Written outputs accumulate, decisions carry reasoning, numbers are spoken openly, faltering steps reach the table rather than hiding, and the team grows more competent over time. The last item matters most: good consultancy makes itself gradually unnecessary. A relationship able to say goodbye is a healthy one.

Red flag: the dependence architecture

Knowledge unshared, access held by the consultant, reasoning waved off as “experience” — a pattern that grows dependence, not service; and a foreign client, watching from a distance, is its easiest audience. If your questions do not earn patient answers, you have in fact received your answer; its name is dependence.

Red flag: unaccounted optimism

Everything wonderful every month, but the profit number never spoken; presentations shine, the card stays empty. Consultancy’s job is not morale; it is making reality manageable. The consultant who brings bad news on time is a good consultant; bad news arriving late is bad twice.

Red flag: ownerlessness on your side

Honesty runs both ways: if data does not flow, meetings go unattended, decisions hang and nothing is implemented, the problem is not the consultant. In that picture the honest consultant’s duty is not to prolong the relationship but to say so plainly; we say so.

The Process in One Visual

The visual gathers the collaboration’s timeline.

The right to leave runs both ways

If the fit fails, a civil parting beats a bad marriage; the quarterly table is its natural address. The accumulated written outputs stay with you; consultancy is not a hostage arrangement. The reason to stay must be value, not obligation.

The cost reads from the card

The fee’s justification reads not from presentation shine but from the card: are channel profitability, order cost and team competence moving the right way? The fee frame opens separately in the fees guide.

If you want to sit down prepared

Arriving at the discovery meeting with your current numbers accelerates everything; for a preliminary photograph of your setup, a digital audit, and for our working order’s whole, the e-commerce consultancy page stand by.

Frequently Asked Questions