Questions Founders Ask

I'm a fractional operator. I work with founders and leadership teams at product companies where the team is heads-down building but nobody is connecting the strategy to what actually ships. That gap is what I call the Operator Vacuum, and I'm the one who owns closing it. Think first officer to the captain, not another task tracker. I call that seat the Operator Seat.

I build them. A lot of my current client work is exactly this: taking an AI product from an idea to something real, making the calls about what it should do and what it shouldn't, and getting it built. It's new enough as a role that it doesn't have a settled title yet. It connects straight back to the Operator Seat, because a build that works turns into something that needs a real team around it, and that transition is where a lot of them stall. I've led that part too, hiring and structuring the team so the thing that got built keeps shipping.

Founders, CEOs, CTOs, and CPOs at product companies under 100 people, usually smaller. Where this page says "founder," read it as whoever is carrying the vision, because that isn't always the founder or the CEO. I've been brought in by CTOs and CPOs just as often. The pattern I look for: the team is genuinely busy and shipping, but someone in that leadership circle is still holding all the connective tissue in their head, and it's starting to cost them.

It's the gap between what a leader has in their head and what actually ships, when nobody owns that translation end to end. The signs I look for: everything is green on the project board right up until delivery, then work bounces back at review. People can describe their own piece but not how it connects to anyone else's. The person at the top still can't step away, even though the team is fully staffed.

It's closer to a first officer than either. A COO runs the business functions. A consultant advises without touching the work. In the Operator Seat I own the outcome, not just the plan for it, and I work directly with the tech leads and the team so what ships matches what was intended. I've used "chief of staff" to describe it, because there isn't one clean industry title for this yet.

Those are both real jobs and neither one is this one. Product management owns the what: stories, backlog, prioritization, requirements. Project management owns the when: sprints, tickets, timelines, status. Both work inside a plan that already exists. The Operator Seat owns whether the outcome actually lands, which makes me accountable for the parts that fall between those two jobs and between everyone's roles. Hiring either one to close an accountability gap is what I call the Hire Trap. You get better tracking and the same gap.

No, and it's the mistake I see most often. Tools don't solve the problem, they enable a solution you've already defined. If the underlying agreement about who owns what is missing, a new tool or a faster AI agent just lets the same gaps move faster. I call this the Tool Trap.

No. I protect and execute the vision, I don't replace it. If something needs to change, I'll push back once, clearly, and explain why. I don't override the call. What I bring is holding the strategy through the execution-level tradeoffs you don't have time to sit in personally, then feeding what I learn back up.

It starts with questions, not conclusions. I ask what's bothering you and what you'd fix first. Usually what comes back is delivery-shaped: things ship late, or on time but not right, or there are disconnects everyone feels and nobody has diagnosed. Then I talk to the people actually doing the work and keep asking why until I hit the real cause instead of the first plausible one. Most of the time goes into defining the problem correctly. Once that's done, the fix is usually obvious.

That's common, and I don't come in swinging. I want the system to work, not to catch anyone out. Most people are already acting in good faith and want to do a good job. Once that's clear, people are a lot more willing to tell you what isn't working.

Alongside. In smaller engagements I've built teams from just myself and the founder or CTO. As things grow, I help you build out the team around the seat. I'm not trying to make myself permanently indispensable.

I have a software engineering background and a computer science degree, and I lead technical teams from a tactical, operational standpoint. I'm not the one making architectural decisions. If what you need is hands-on engineering or architecture leadership, that's not my seat. If what you need is someone who knows the full software development lifecycle well enough to see where things are falling through the cracks and orchestrate the fix, that's exactly it.

AI doesn't create accountability where none existed. It amplifies whatever is already there. A team with real ownership and agreement gets faster with AI. A team without it generates the same gaps at much higher volume, which I've been calling the Agentic Fog. The fix is never more AI. It's making sure a human is still checking that what got built actually matches what was needed.

The mechanical parts, probably, more every year. The judgment part doesn't automate away. Somebody still has to decide what should happen when the plan shifts, and own that decision. That part of the job gets more valuable as the tooling gets faster, not less.

Small, usually under 100 people, often much smaller. The clearest fit: whoever is leading is still close to the actual work but is becoming the bottleneck, because they're the only one holding the full picture together.

Typically 20 hours a week or less. I run two to three clients at a time, never more, because I don't spread myself thin. That works because of how the role is structured: I'm not embedding as a full-time employee doing every task myself. I'm providing direction, keeping an eye on the whole system, and making sure the people who need to be doing things are actually doing them. I can also help hire and build out your team if that's what's needed. Some engagements have grown closer to full-time when the situation genuinely called for it, but that's the exception.

Retainer, paid in advance. I invoice up front to cover the period ahead rather than billing after the work is done. I don't bill by the hour because it creates a conflict of interest I'd rather not have: an hourly relationship gives me an incentive to bill more hours, and gives you a reason to second-guess every ask because it might cost you more. A flat retainer takes that off the table for both of us. I'm focused on the outcome, not the clock. For scale: this is a fee at the level of a senior leadership hire, not a contractor rate.

Yes, and there's no minimum term. If you want to start with a bounded window of two to four weeks, just to see how we work together, that's on the table. I'd rather you find out whether this works than commit to six months on faith. From there my process is deep discovery: understanding your objectives, your team, and what's still unclear, before figuring out what the ongoing shape of the work should be.

A conversation, not a form. The first call is diagnostic: I ask what's bothering you and what you'd fix first, and I'm listening for whether the problem I can solve is the one you actually have. I don't price before that, because the price depends on what you're trying to change and I don't know that yet. If it's a fit, we'll talk about the shape of the work and what it costs. If it isn't, I'll tell you.

The blog publishes weekly, working through the Operator Vacuum and the wrong fixes people try first. The newsletter, Closing the Loop, goes out every other week. You can also follow along on LinkedIn.