Consulting vs. Full-Time, Honestly

I’ve been doing fractional and consulting data work for about three years now. In that time I’ve had conversations with clients about coming on full-time, and I’ve thought seriously about what each path costs and what each gives you. These are notes from the middle of the decision.

What consulting gives you

You see more variety faster. Across a few engagements in three years, I’ve worked inside different data architectures, navigated a couple of M&A data integrations, and sat across the table from leaders who all had a slightly different idea of what “data-driven” looks like. Inside one company, that kind of pattern recognition takes longer to build.

Problem selection is the other piece. When a client’s priorities don’t line up with the work I think matters most, I can give them my honest read, try to help them shift the plan, and part ways if it doesn’t land. The engagements that went well were the ones where the problem was interesting and the organization was ready to do the work. That kind of flexibility is something you trade when you go full-time.

What it costs

The feast-or-famine cycle is heavier than I expected going in.

Managing a pipeline of potential projects while delivering for current clients is its own cognitive load. Even when the calendar is full and revenue is stable, part of your brain is always three months out, tracking what comes next. The work itself is usually a good time. Running the business around it is a second job you’re always partly doing.

There’s also something I didn’t fully name until a conversation with Kyle Johnson late last year: the outsider constraint. I was describing how I help clients build teams, set up infrastructure, mentor people, and then step back. And I said something like, “I’m kind of feeling removed.” That was honest. Consulting gives you distance from dysfunction, which is nice. But in the good engagements, the ones where the people are sharp and the problems are genuinely interesting, you’re always slightly on the outside. The conversations can’t go as deep. You’re involved but not fully invested, and that gap is more limiting than it sounds.

A job and a title give you a settled identity. People know what you do. You know what you do. Consulting doesn’t come with that. You’re defining your own identity, which is liberating in some moments and exhausting in others, and the work of articulating what service you actually want to provide never fully stops.

What the full-time path gives you

The thing I think about most is depth. Staying with one company long enough to see whether the decisions you made in month two hold up in month fourteen. In consulting, you often leave before you see the consequences play out. You build the foundation, hand it off, and hear about the results secondhand.

There’s also the team piece. I’ve helped clients build teams, hire across Mexico and India and domestically, train and mentor people. But mentoring someone for six months on a contract is different from building with them over two or three years. The compounding trust, the shared context, the ability to make a call together because you’ve both seen the same failures. That’s hard to get as a contractor.

And honestly, the simplicity. One W-2. One set of priorities. One company’s problems to think about deeply instead of context-switching across three or four. Some weeks the context-switching is fine. Some weeks it’s the thing that limits the quality of what I can do.

What I’d actually want

I’ve been thinking about this more concretely lately. Not as a hypothetical, just as honest reflection on what would make the tradeoff feel right.

A growth-stage company where the data function is either new or in its first generation. Somewhere that needs someone to own the stack and connect data to decisions that move the business, and a leadership team ready to move at the pace the work wants to go.

A consumer-facing or product-led business where customer lifecycle questions are central. The problems I find most interesting are the ones about what customers do over time: where they come from, why they stay, what makes them leave, how you build products and allocate resources against that reality.

And a culture where focused work and personal time aren’t competing. The best work I’ve done, consulting or otherwise, happened when I had the headspace to think clearly.

Where I’m at

I don’t have a clean answer. The consulting path allowed me to see how different organizations work simultaneously, what problems I’m drawn to, and what I’m good at. It also showed me the limits of always being on the outside. Both paths have real costs. I’m paying attention to which costs I’m less willing to keep paying.