Darren Card, fractional CPTOVancouver · one engagement at a time
Building got cheap for your team too. The judgment did not arrive with the tools.
Fractional product leadership for B2B SaaS teams, delivered as one engagement with a fixed shape: read how calls get made today, wire the loop that feeds them, name the owners, and leave once the rituals run without me.
The engagement worked if the rituals still run a quarter after I stop attending them. Anything else is dependency dressed up as partnership.
One signal says look into it. Two says the operating model is the bottleneck.
None of these are about engineering capacity. Every one of them is about the distance between where work happens and where the call gets made.
You ship more than you can read
Velocity is up and nobody can say which of the last ten launches changed a customer behaviour. That gap is the whole problem, and it is fixable in two quarters.
Agents arrived before the operating model did
Your team has the tools. What is missing is the line: who reads, who drafts, who checks, and who owns the call at the end of it.
The board asks and the answer takes ten minutes
If the honest answer to "did it work" needs a deck and a week of prep, the evidence is not where the decisions are.
The engagement is six slides long, and the last two matter most.
Diagnosis first, because installing a loop on top of an unread quarter just automates the guessing. Then the loop, the owners, and the handover.
- 01Diagnosis
Where the calls are made now
Two weeks reading your last quarter: what got decided, by whom, on what evidence.
- 02Diagnosis
What shipped against what landed
Every launch of the last two quarters, sorted into landed, watch, and stalled.
- 03Agent workInstall
The five-step loop, wired to your tools
Agents read the context, draft the options, and check the rules before the meeting.
- 04The callInstall
One owner per call, written down
Business fit, design quality, technical fit, final approval. Four names, no committees.
- 05Handover
The sixty-second board story
The four questions, answered from the same evidence your team already sees.
- 06Handover
Handover, then out
The rituals run without me, or the engagement did not work. That is the exit test.
Whatever we automate, one person with a name still owns every call.
Clients push back on this line first and rely on it longest. Agents can read, draft, and check without a human in the loop. The approval never happens without one.
- Business fit
- Design quality
- Technical fit
- Final approval
Judgment. Never delegated, never automated.
- Read the context
- Draft the options
- Check the rules
- Propose the next move
Volume. Fast, tireless, and never the owner.
Everything left of the rule has a name attached to it.
One engagement at a time, and a written end date at the start.
- A team that needs someone to run the roadmap permanently. The exit test is the point.
- An organisation where the answer is already chosen and the engagement is cover for it.
- A pure staffing gap. Agents plus judgment is the thesis; more hands is a different problem.
Start with the whitepaper, not with a call.
It is the whole argument in one document: what got cheap, what got scarce, and the operating model that follows. Start there; the email that fetches it is also how a conversation with me starts.