Consulting vs Staff Augmentation
In staff augmentation, the client is primarily buying capacity.
In consulting, the client is primarily buying an outcome, judgment, or expertise.
A useful test is:
If the client already knew exactly what needed to be done and how to do it, would they still need you?
If yes, because they simply need another competent person to execute the work, that is usually staff augmentation.
If no, because a major part of your value is figuring out what should be done, reducing ambiguity, making tradeoffs, designing the approach, negotiating scope, or guiding the customer, that is consulting.
For example, these can use exactly the same AWS technologies.
Staff augmentation:
The customer needs another Terraform/AWS engineer for six months. Here is the backlog. Join the standups, pick up tickets, follow our architecture and processes.
Consulting:
The customer wants to modernize this application and move it to AWS. They have business goals but the technical path is unclear. Determine the target architecture, uncover constraints, decide what can fit in the engagement, get stakeholders aligned, and deliver it.
Both people might spend Tuesday writing Terraform.
The difference is that the second person’s job includes deciding whether Terraform should be written, what it should create, why, in what sequence, with what compromises, and whether that actually solves the customer’s problem.
| Dimension | Staff augmentation | Consulting |
|---|---|---|
| Client buys | Labor/capacity | Expertise/outcome |
| Problem definition | Mostly supplied | Often incomplete/ambiguous |
| Work prioritization | Client directs | Consultant materially shapes |
| Architecture | Usually inherited | Often proposed/owned |
| Scope | Backlog/team assignment | Negotiated against goals/time/budget |
| Success | Productive team member | Customer outcome/deliverable |
| Management | Embedded in client’s machinery | Greater delivery autonomy |
| Technology | Often specified | A tool selected to solve the problem |
| Communication | Mainly team coordination | Often executives, stakeholders, sales, customer teams |
| Judgment | Needed, but bounded | Central part of what is being sold |
There is also a continuum.
A company can call someone a “consultant” while effectively renting them out as a Java developer for twelve months. Conversely, an independent contractor can perform genuine consulting.
That is why “I learned AWS service X” does not really distinguish consulting. A staff-augmentation engineer can learn ten AWS services.
The stronger description is:
Consulting means being accountable for turning an incompletely specified business problem into a technically feasible, bounded solution, while managing the tradeoffs among requirements, time, cost, risk, and stakeholders.
The technology is implementation substrate.
The product being sold is judgment plus delivery.