There's a moment in almost every consulting engagement where you realize you have a choice. You can keep the client dependent on you, or you can teach them how to do what you do. Every incentive in the industry pushes toward the first option. I think the second one is the only version of the job worth doing.
The Business Model Tension
Let's be honest about the economics first, because pretending they don't exist doesn't help anyone. Fractional and advisory work is often billed by the hour, the retainer, or the engagement. If a client no longer needs you, that revenue goes away. There's a real temptation — sometimes not even conscious — to keep the client just dependent enough that the relationship never ends.
I think that temptation is short-sighted, and I've tried to build my practice against it. A client who becomes self-sufficient because of what you taught them doesn't stop being a reference, a referral source, or a future client when their next problem shows up. A client who stays dependent because you never explained your reasoning eventually resents the arrangement, or gets acquired by someone who brings in their own team, or just runs out of budget. Either way, the relationship built on dependency has a shorter half-life than the one built on capability transfer.
Path to Self-Sufficiency, Not Just a Deliverable
When I'm brought in to build a data platform, stand up governance, or fix a broken analytics stack, the deliverable is never really the dashboard or the pipeline. It's whether the internal team understands why the pipeline is built the way it is, so that six months after I'm gone, someone on their side can extend it without calling me in a panic.
That means a few things in practice:
- Documenting the reasoning, not just the result. Anyone can hand over a working system. Fewer people write down why they made the tradeoffs they made — why Snowflake over the alternative, why this schema and not a more "correct" one, what the maintenance burden actually looks like six months out.
- Involving internal people in the build, not just the handoff. If I'm the only one who's touched the thing until the final walkthrough, I've failed at the mentorship part even if the technical part is flawless.
- Being honest about what they don't need anymore. Sometimes the most useful thing I can tell a client is "you don't need a fractional CDO for this next phase, your team can run it." That's a harder sentence to say than it should be, given how the incentives are set up. I say it anyway.
Teaching Mentality, When Time Permits
I want to be careful here, because "teach everything to everyone" isn't realistic advice — deadlines are real, and not every moment on an engagement is a teaching moment. But there's a difference between an engagement where you occasionally pause to explain your thinking, and one where you never do. The first costs you a little time. The second costs the client the ability to think independently about the system you built them.
In practice, "when time permits" tends to show up in small, unglamorous moments:
- Walking someone through why a query is structured a certain way instead of just handing them the finished SQL.
- Spending fifteen minutes in a working session explaining a data governance tradeoff instead of just making the call silently.
- Answering "why" questions fully instead of "just trust me" answers, even when the fuller answer takes longer.
None of that shows up on an invoice. All of it is the difference between a client who grows and a client who stays stuck.
Why This Is Actually the Better Business Strategy
There's a version of this argument that sounds purely idealistic, so let me make the practical case too. Clients talk to each other. A consultant with a reputation for hoarding knowledge gets one engagement per client. A consultant with a reputation for building capability gets referred to the next three companies that client talks to — and gets called back when the next problem shows up, because the relationship wasn't transactional in the first place.
Mentorship isn't in tension with running a sustainable advisory practice. It's the thing that makes the practice sustainable. The goal was never to be indispensable. It was to be trusted enough that when you finish, the door stays open.
Contact me today to see how I can help your business.
I write occasionally about data leadership, fractional CDO work, and building analytics practices that actually stick. More at johnsteinmetz.net.