The product leader who speaks business, IT, and regulator.

In a regulated business, many product problems are really communication problems. Pricing asks for one thing, IT builds another, and compliance hears about it last. I've spent nearly twenty years getting those three to agree, and making sure it doesn't go wrong once the work starts.

The James River running over rocks and driftwood, with the downtown Richmond skyline behind it.
Fig. 1The James at Richmond, Virginia

Who it's for

You don't need to know which service to ask for. Most first conversations start from one of these:

  • You've been asked to launch in more states, or under another brand, and the filing path runs through four teams that each have a different date in mind.
  • Product and IT have stopped trusting each other's estimates, and nobody can say what ships next quarter.
  • The team has outgrown a founder's instinct for what to build, but can't yet justify a full-time head of product.
  • There's a pricing or product decision on the table and you want a second opinion from someone who has no stake in the answer.

What I do

  • Fractional

    Senior product leadership, scoped to what you need

    Acting as the senior product leader for teams that have outgrown a founder's instinct but aren't ready for a full product organization. Roadmap sequencing, prioritization the business trusts, hiring and interviewing, and the process work that makes delivery predictable.

  • Operating model

    When the roadmap stops being a wish list

    Structured intake, clear prioritization, and enough trust between product, IT, and the business that an estimate means something. I rebuilt this process inside an insurance carrier while it was under profitability and regulatory pressure.

  • Domain

    Insurance product, without the headcount

    Rating logic, pricing frameworks, state expansion, regulatory filings, loss ratio, and attrition. I know which of your problems are pricing problems and which only look like them.

How I work

Scoped
Every engagement has an end date written down before it starts. If you want to extend it, that should be a decision you make on purpose.
Direct
You'll hear the version with the bad news in it. If a plan has a problem, I'll say so.
Fluent
I can hold the pricing conversation, the tech conversation, and the compliance conversation without needing a translator. Most of the delay in a regulated business happens in the handoffs between those three.
Independent
No reseller agreements, no referral fees, no vendor I have an incentive to recommend. If I suggest a tool it's because it fits.

Work I turn down

  • Staff augmentation by the month with no defined outcome.
  • Writing a roadmap that's already been decided, so it carries an outside expert's endorsement.
  • Actuarial or statistical modeling — I'll tell you what the pricing question is, not compute the indication.

The rest of that list

How it goes

  1. 01

    A conversation, free

    Half an hour on what you're trying to do and what's in the way. If I'm not the right person you'll leave that call knowing it, and I'll usually have an idea who is.

  2. 02

    A written scope

    What I'll do, what it costs, and when it ends — in writing, before anything starts. No open-ended retainers that quietly become a salary.

  3. 03

    The work

    Weekly written updates, good news or bad. You won't have to ask how it's going, and the invoice won't surprise you.

  4. 04

    A clean handoff

    Documentation your team can act on with or without me. The goal of every engagement is that you need me less at the end of it than at the start.

Next

The first conversation is half an hour and costs nothing. If I'm not the right person, I'll tell you on that call.

Start a conversation