G.04Guides · Decision brief
Hire a consultant or build in-house?
Every outside engagement is implicitly a decision not to build the capability yourself. Sometimes that is exactly right, sometimes it is a slow leak of competence out of your company, and the difference is predictable in advance: it turns on frequency, urgency, and who has to own the answer once it exists.
The distinction
What is actually being compared?
Praxis sells consulting, so read this with that interest declared. The discipline that keeps the advice honest is simple and it is the same one used in scoping: recurring capabilities belong in-house, and an advisor who builds a dependency where a capability should grow is farming you, not serving you.
The in-house case is strongest for anything you will do monthly forever: the analytics your operations run on, the hiring engine, the customer pipeline. Building is slower and costs more up front, but each repetition compounds inside your walls. The consulting case is strongest for decisions that are rare, heavy, and urgent: a market entry, a repositioning, a build-versus-buy call, a turnaround. You will not face them often enough to justify the standing capacity, the stakes punish learning on the job, and speed matters because a 6 month internal learning curve can cost the window itself.
The three questions that decide it
Frequency: will you face this problem repeatedly? Recurring means build; rare means rent. Urgency: does the decision have a window? A closing window argues for renting proven judgment now and building later. Ownership: who must live with the answer? If operating the answer requires deep internal context every week, the capability has to end up inside regardless of who starts it, and the engagement should be designed as a transfer from day one.
Most real situations resolve into a hybrid: rent the judgment for the rare, heavy decision, and let the engagement deliberately leave capability behind, in the form of the frameworks, the trained people, and the operating cadence that persist after the advisor leaves. That transfer clause is the single strongest predictor of whether outside spend compounds or evaporates.
The failure modes on each side
The consulting failure mode is dependency: quarterly re-engagements for work your own team should have absorbed after the first one, and strategy revisited annually because it was never owned internally. The in-house failure mode is the expensive apprenticeship: assigning a first-time problem to a smart internal team, spending 9 months and a market window learning what an experienced outsider knew in week 2, and calling the tuition an investment. Both failures are avoidable at scoping time, not delivery time.
Side by side
Rent or build, by the shape of the problem.
| Hire outside judgment | Build the capability in-house | |
|---|---|---|
| Frequency | Rare: entries, exits, repositioning, turnarounds | Recurring: analytics, hiring, pipeline, operations |
| Urgency | A window that punishes a learning curve | Time to grow the muscle before it is critical |
| Ownership after | Decision transfers cleanly once made | Operating the answer needs weekly internal context |
| Cost shape | Concentrated fee against a heavy decision | Salary and time, compounding with each repetition |
| Failure mode | Dependency and repeat billing | Expensive apprenticeship on a live problem |
The call
How do you make the call this week?
- 01
Count the repetitions.
Honestly estimate how many times in 3 years you will face this exact class of problem. One or two: rent. Twelve: build, even if it is slower.
- 02
Price the window, not just the fee.
Compare the consulting fee to the cost of deciding 6 months later, not to the salary equivalent. Heavy decisions are usually mispriced in the buyer's head by ignoring the delay.
- 03
Write the transfer clause.
Whatever you rent, name in the scope what stays behind: the model, the playbook, the trained owner. An advisor who resists that clause has told you their business model.
A note on interest. Praxis sells consulting, so treat this page as an informed party’s brief, not a referee’s ruling. The discipline we hold ourselves to is written down: category-level comparisons only, no named competitors, and a public page on when we are not the right fit.
Questions
Asked before scoping.
- Is it not always cheaper long-term to build in-house?
- For recurring capabilities, usually yes, and this page says so plainly. For rare, heavy decisions the arithmetic inverts: standing capacity you use once every few years is the most expensive way to buy judgment, and the internal learning curve consumes exactly the window that made the decision urgent.
- How does Praxis handle the dependency risk?
- By scoping engagements to end: defined-scope work with a finish line, deliverables designed to be owned by your team, and a stated preference for building your capability where the problem recurs. The engagement models page describes those shapes and where each fits.
Where this leads on the site
Other decision guides
- G.01Strategy vs management
- G.02Consultant vs contractor vs fractional
- G.03Boutique vs Big Four
- G.05Change vs transformation
- G.06Fractional vs retainer
- G.07AI consultant vs implementation partner
- G.08Data strategy vs engineering
- G.09Consulting vs coaching
- G.10Interim vs consultant
- G.11SEO consultant vs agency
- G.12Transformation vs modernization
- G.13What drives cost
- G.14Fee structures
- G.15Fixed vs T&M
- G.16First-engagement budget
- G.17Questions to ask
- G.18Red flags
- G.19Writing an RFP
- G.20Evaluating proposals
- G.21Do you need one?
- G.22Getting the value
- G.23When to hire strategy
- G.24SEO for construction
- G.25Board vs advisory board
- G.26Marketing consultant vs agency
- G.27Piloting an advisor
- G.28AI implementation cost
- G.29Strategy vs ESG reporting
Decided what kind of help you need?
Then the next conversation is about fit and scope. Tell us what you are deciding, and we will tell you honestly whether we are the right resource for it.
No obligation · a scoping conversation first