Both words appear on the same kind of website, next to the same kind of promise, at the same kind of price band. Most founders comparing two proposals cannot tell from the documents which model they are looking at, and the difference does not become obvious until roughly four months in, at which point it is expensive to have got wrong.
The distinction is not about quality or seniority. There are excellent consultants and mediocre implementers. It is about where the work stops, and therefore about who is holding the hard part.
Consulting stops at the recommendation. A firm investigates, forms a view, and hands you a diagnosis with a set of changes to make. The thinking is the product. Whether anything changes afterwards depends entirely on your team's capacity to execute it.
Implementation stops when the changes exist. The same investigation happens, but the deliverable is the altered organization: stages that are configured, playbooks that reps have been trained on, a compensation plan that has been through a pay cycle. The thinking is a means to that, not the thing you bought.
The Two Models, Side by Side
Sales consulting
The deliverable is a recommendation
- Two to four weeks of audit and interviews
- A diagnosis, a framework and a prioritised list of changes
- Delivered remotely, with a weekly call
- Your team executes, on top of their existing workload
- Engagement ends at the presentation
- Priced against the analysis
Value depends entirely on whether someone internal has the time and authority to act on it.
Sales implementation
The deliverable is a working system
- A month of analysis before anything is proposed
- A custom scope, priced against what the analysis scored
- Delivered on-site, in the room with your reps
- The firm builds it, then trains your team to run it
- Engagement ends after the system has been observed working
- Priced against what ships
Value depends on whether someone internal can own the system after handover.
Four Questions That Separate Them
Proposals rarely say which model they are. These answers do.
1. What exists on the last day that did not exist on the first?
This is the single most useful question you can ask, and it is uncomfortable enough that the answer tells you a lot. If the honest answer is a document, a framework, a scorecard or a set of recommendations, you are buying consulting. That may be exactly right for you. But you should know it before signing, not in month four.
2. Who does the building, and where do they sit while they do it?
Configuring a CRM, rewriting job descriptions, running training, sitting in on live calls: these are hours of work by someone. Ask whose hours. Ask how many days a month someone will physically be with your team. A firm that intends to build will answer specifically; a firm that intends to advise will answer in terms of workshops and check-ins.
3. What is the end condition?
Consulting ends on a date. Implementation should end on a condition: the system has been running, with your team operating it, long enough to see whether it holds. Those are different commitments. A proposal with a date but no condition is describing a delivery schedule, not an outcome.
4. When is the scope written?
A proposal that arrives before anyone has investigated your organization is a price list with your logo on it. The scope should be produced by the analysis, not before it. If a firm can tell you what they will build in week one, they are describing what they usually build, which is not the same as what you need.
When Consulting Is the Right Answer
This is not an argument that one model is better. Consulting is the right purchase in a set of specific situations, and buying implementation in those situations wastes money.
If you have a capable sales leader with genuine bandwidth, a good consultant is excellent value. The bottleneck in that company is not execution capacity, it is an outside read on a question the people inside are too close to answer. Paying someone to build what your own team could build faster is not a good trade.
If the question is narrow and technical, the same applies. Pricing strategy, a compensation redesign, a territory model: these are bounded problems with clear owners, and they do not need six months of on-site presence.
If a board or an investor needs an independent view before a decision, that is a consulting deliverable by definition, and dressing it up as implementation helps nobody.
Implementation earns its cost in the opposite case: when the changes needed are structural, when they span several parts of the organization at once, and when there is nobody internal with the time and seniority to drive them. That is most companies between roughly five and fifty employees, which is why the model exists.
The Cost of Getting the Choice Wrong
Buying consulting when you needed implementation has a recognisable shape. The analysis is good. The recommendations are sound. Three of the twelve get done, the ones that required no coordination and no difficult conversation. The other nine sit in a folder, and a year later a new firm is hired to produce a strikingly similar list.
The direct cost is the fee. The larger cost is the quarter spent deciding what to do, followed by the quarters spent not doing it, during which the underlying problem compounds. Reps still ramp slowly. The forecast is still wrong. The founder is still in every deal.
Buying implementation when you needed consulting fails differently and less often. You pay for months of building you could have done internally, and your existing sales leader spends the engagement either sidelined or duplicating work. It is expensive, but it usually produces something.
Both failures come from the same place: nobody asked, at the start, which model was on the table.
Signs You Need Implementation, Not Advice
- You already know roughly what is wrong, and it has stayed wrong for two quarters
- There is no one internally whose job is to own the fix end to end
- A previous audit produced recommendations that were never executed
- The problems span sales, technology and organizational structure at once
- Sales still works, but only when the founder is personally in the room
- New reps take months to ramp and nobody can say precisely why
Three or more of these usually means the missing ingredient is execution capacity, not insight. Another diagnosis will confirm what you already suspect and change nothing.
How We Are Structured
One month of analysis, a scored evaluation, a custom scope, then six months minimum.
Growth Frontier is an implementation firm, and the structure reflects it. Every engagement opens with a month of on-site analysis: stakeholder interviews, a pipeline and CRM audit, and a scored review of ten areas of the organization. Nothing is proposed during that month.
The evaluation is then presented, with the scope and price of the full project. That evaluation is yours to keep whether or not you continue - which is the part that most resembles consulting, and it is deliberately the only part.
If you continue, the analysis continues alongside a six-month build: technology first, then the sales organization, then marketing, then a tracking phase, then handover. Six months is a minimum rather than an estimate. We are not changing a procedure, we are installing a way of working, and behaviour settles more slowly than configuration does.
See the full six-month outline, or read where we say no - which is the other half of being an implementation firm.
“Ask what exists on the last day that did not exist on the first. If the answer is a document, you are buying advice, whatever the proposal calls it.”
Common Questions
What is the difference between sales consulting and sales implementation?
Consulting produces a recommendation: an audit, a diagnosis and a set of changes for your team to make. Implementation produces the changes themselves. The consultant's deliverable is the thinking; the implementer's deliverable is a sales organization that runs differently than it did before, with your team already trained on it.
How do I tell which one a firm is actually selling?
Ask what exists on the last day that did not exist on the first, and who built it. If the answer is a document, a framework or a set of recommendations, it is consulting regardless of the word on the proposal. Ask also where the work happens and how often someone is physically with your team.
Is sales implementation more expensive than sales consulting?
Per engagement, usually yes, because it covers months of building rather than weeks of analysis. Per outcome the comparison is different: a recommendation only produces value if your team has the time, seniority and appetite to execute it, and the cost of a plan that never gets implemented is the whole fee plus the quarter it took to decide not to act.
How long should a sales implementation engagement take?
Ours runs a minimum of six months, opening with a month of analysis before anything is proposed. Shorter is possible for a single system, but a full sales organization involves changing how people work, and behaviour takes longer to settle than configuration does. Anything promising a rebuilt sales function in a few weeks is selling a document.
When is sales consulting the better choice?
When you already have a capable sales leader with the bandwidth to execute, and what is missing is an outside read on a specific question. A strong internal team with a narrow blind spot is well served by a good consultant. Implementation is for companies with no one inside who can own the build.
Is a fractional sales leader the same as sales implementation?
Related but not the same. A fractional leader occupies a seat and runs the function part-time, often indefinitely. Implementation is finite by design: it builds the system, trains the team on it, and hands it over. If an implementation engagement has no end condition, it has quietly become a fractional arrangement.
Not Sure Which One You Need?
Tell us where your sales stands today. If advice would serve you better than a build, we will say so on the first call.