Fractional Multi-Client Economics

A company at 40 people needs senior data judgment about 2 days a week. Full-time is the wrong container.

The workload at that stage is real but lumpy: architecture decisions, a build sprint, hiring input, then a quieter stretch while the team executes. A full-time senior head fills the quiet stretches with, in the honest cases, busywork. In the less honest ones, reorganizations.

So the fractional math serves both sides. The client pays for the 2 days of judgment they actually need, at a fraction of a full-time senior’s total cost. I stack 2 or 3 such clients, which keeps my week full and my patterns sharp: the migration I designed at one client got debugged at another last quarter. That cross-pollination is part of what’s being bought, though it rarely appears in the contract.

The failure mode is context switching, and the fix is structural: full day-blocks per client, never half days. A day has enough runway to load the context, do deep work, and land it. Two half days deliver about a third of one full day, in my experience.

The model has a ceiling, on purpose. Three retainer clients is full. Past that, someone’s 2 days quietly become responsive instead of proactive, and that’s the thing I’m hired not to be.

What does your company need senior data judgment for this quarter, and how many days is it honestly?