The Reward for Good Work Is More Work

There's a pattern I keep noticing when I work with clients. You close a task, you tell them it's done, and they light up. Something clicks for them, mostly without them noticing it click: this person solves problems.

And the natural result of that is not relief. It's more work. Founders in particular tend to already have more ideas than they have time — that's close to the job description. The moment they see execution actually happening, the volume doesn't go down. It goes up.

The reward for good work is more work.

That would be a fine problem to have, except for one complication. People like me — and I'd guess most people who are good at this kind of work — also say what they won't do. We size things honestly. We ask what a task is actually going to cost before agreeing to it.

Clients who are used to handing off responsibility and having it disappear don't love that. So you end up with two options, and neither one is popular: ask a lot of clarifying questions, which reads as friction, or say part of the request isn't happening, which reads as a no. Either way, the founder feels a little less delighted than they did after the last "done."

Prioritization is the actual bottleneck

This is where it gets interesting. Ambitious founders with weak prioritization are one of the harder combinations to work with — and also exactly where someone with a strategic, systematic approach earns their keep.

What I actually do, in practice, is fairly simple. I agree that an idea matters. I don't argue it away. Then I park it — put it into a roadmap, with real implementation steps and enough detail that "we're doing this" has a shape, not just a name.

If the founder pushes to add something on top, I ask a version of the same question every time: do you have more budget, more people, more time? Almost always, the answer is no. And that single question tends to do more for how a founder engages with priorities than any argument I could make. The absence of that discipline is often the real gap inside the company — not a lack of ideas.

We overestimate the day and underestimate the quarter

The part I find most interesting is almost philosophical. We consistently overestimate what we can do today and underestimate what we can do in a quarter. A founder will insist they have far too many ideas for their team to ever get through.

Then you sit down and actually lay those ideas out — week by week, month by month, three months at a time. And it turns out one of two things is true. Either there's less real, concrete work than three months' worth. Or most of it is vague enough — wishes with no shape yet — that the founder needs to sit and think before it can even go on the map.

Once that happens, though, something shifts. What looked like chaos becomes a roadmap that actually holds together.

Holding the edges of the roadmap

The job doesn't end once the roadmap exists. Ambitious founders will keep testing its edges — that's not a flaw, it's what makes them ambitious. The roadmap has to stay genuinely flexible: one thing can trade for another. What it can't become is a container you just keep adding to, on top of everything already agreed.

Holding that line, quarter after quarter, without turning rigid and without turning into a dumping ground — that ongoing discipline is most of what a systematic, strategic partner actually does. Not more ideas. A place for the ones that are already there to become real.

Ambition was never the constraint. An unprotected roadmap is.