Getting your first customers proves there is something worth building. It does not tell you what to build next, who to build it for, or how the company will carry it.
I help founders decide what deserves focus, turn those choices into measurable action, and build the systems, ownership, and ways of working needed to scale. You stay close to the work where you create the most value. I take ownership of the part getting in the way.
The work lives between strategy and operations (because the problem usually does too).
There are usually two versions of stuck. Many companies are dealing with both.
Different customers are pulling the product in different directions. Every conversation creates another plausible feature. There are more opportunities than time, money, or people.
Too broad, and every customer becomes a market. Too narrow, and you mistake your first customers for the whole opportunity.Find the next betThe process that worked at 10 people is wobbling at 30. Decisions keep finding their way back to the founder. Important work crosses several teams, but nobody owns it end to end.
You do not have to become the operator your next stage needs.Build the operating layerData does not make the decision. It makes the assumptions visible.
You do not have to hire me. But leaving the constraint unresolved has a cost.
Features, customers, and opportunities multiply faster than the evidence. You spend more without getting closer to what is repeatable.
Context, approvals, and difficult decisions keep returning to one person. The company moves only as fast as they can absorb it.
Growth adds rework, delivery cost, and inconsistency because the operating system has not caught up.
They compensate for unclear ownership and broken handoffs until the workaround becomes the process, or they stop compensating.
The risk is rarely one dramatic failure. It is paying for the same friction every week until it becomes normal.
I do not hand strategy to operations. I connect the choices, the work, and the evidence all the way through.
Use customer, financial, and operational evidence to decide which customer, problem, offer, or opportunity deserves focus.
Turn assumptions into attainable goals, measured steps, and clear moments to continue, change course, or stop.
Translate the direction into ownership, decisions, rhythms, processes, and work the team can actually execute.
Customer behaviour, revenue, margin, conversion, retention, and delivery reality keep the choices honest.
A launch unstuck. An operating foundation built for scale. A national partner network aligned around one customer experience.
A vehicle subscription initiative had stalled across insurance, dealer risk, fleet planning, and fragmented ownership.
Processes lived in people’s heads and every new vehicle amplified the exceptions, errors, and cost.
The customer saw one brand. Behind it were several teams, systems, and 21 independent retail partners.
A strategy can make perfect sense in the room where it was decided and still go nowhere.
Somewhere between the 47-slide strategy deck and the Slack message nobody read is the translation that makes a decision relevant to someone's actual work.
Connect it to what they own, how they are measured, and what changes on Monday. That is how direction becomes coordinated action.
When the strategy is not landingThe work is shaped around the problem and the level of ownership it needs. These are starting structures, not off-the-shelf packages.
Explore ways to work togetherFractional COO is useful shorthand, but I do not separate strategy from what it takes to execute. The work may include sharpening the market or customer focus, defining what needs to be proven, building the operating system, or leading the work through its first real version.
Usually after the first signs of traction, when opportunities start multiplying, or later when growth exposes the limits of informal systems. You may need clearer strategic choices, stronger operating foundations, or help finding the constraint underneath a problem that will not go away.
Strategic sparring is for leaders who want an experienced outside brain. Focused projects solve a defined problem or build. Embedded partnerships are for important work that needs hands-on ownership inside the business. The format follows the situation.
Yes. Founder-led companies are the primary focus, but I also work with established organizations launching new ventures or leading cross-functional change. The setting changes. The operating questions around ownership, incentives, handoffs, measures, capacity, and the customer promise are remarkably transferable.
Yes. I work across North America and Europe and bring direct experience translating between the two. I speak fluent German and conversational Italian. Throughout my time at Porsche Canada, part of my role was translating German priorities, expectations, and ways of working into a North American market, then translating local context back the other way. The work can include market strategy, partner models, operating design, launch execution, and cross-cultural alignment.
Start by separating customer requests from repeatable evidence. Look at who gets the clearest value, what they will pay for, which problems repeat, how difficult the work is to deliver, and what the economics could become. The goal is not to choose the smallest possible niche. It is to make the next bet specific enough to test.
Look for the quiet friction everyone has stopped noticing: the workaround that became policy, the process nobody remembers starting, the decision that always returns to the same person, and ownership disappearing at handoffs. One by one, these can look harmless. Together, they are the operating system the company is actually running on.
They usually compound quietly. Runway gets spread across too many bets, decisions keep returning to the founder, more customers create more exceptions and rework, and good people compensate for weak handoffs. The risk is rarely one dramatic failure. It is paying for the same friction every week until it becomes normal.
Because deciding and announcing are not the same as translating. A strategy that made sense to six people in a room still has to become relevant to everyone else's work. That means clear ownership, decision rights, measures, handoffs, and a practical answer to one question: what changes on Monday?
Because the problem rarely stays inside one function. A delayed launch may look like an operations problem and turn out to be about risk. A customer problem may live across product, sales, service, and partners. My breadth helps me follow the problem across those handoffs, bring in specialists where needed, and keep ownership of the whole outcome.
Rarely. It is usually an operating-design problem. Decisions return to the founder because context, authority, measures, or trust have not moved with the work. A cleaner calendar may create temporary relief. Clearer decision rights and ownership change how the company runs.
Both. I can help define the strategy, pressure-test the operating model, and then stay close enough to build, launch, measure, and adjust the first real version. I am most useful when the thinking and the execution cannot be separated neatly.
I use AI for research, synthesis, pressure-testing, and building tools that extend the work. I am also actively building an agent with Claude Code: part coach, Chief of Staff, COO, and truth-telling friend. It is designed to support founders between conversations, not replace human judgment. A model can surface patterns quickly. It cannot read the room, catch the hesitation, or understand every unstated constraint, so human support stays in the loop.
Yes. Mobility, automotive, EV, logistics, fleets, and partner networks are areas where I have useful depth. The broader operating patterns transfer to franchise, dealer, marketplace, multi-location, and technology-enabled businesses where work crosses people, partners, systems, assets, and customer touchpoints.
Strategic sparring is CAD $1,500 per month. Embedded partnerships start at CAD $3,500 per month for one focused mandate. Defined projects are priced around scope. The structure changes with how much ownership and time the situation needs.
We start with what is happening, not a job title or package. If there is a fit, I spend the early work listening, asking questions, reviewing the evidence, and finding the constraint underneath the visible problem before recommending a solution.
You don't need to diagnose the role before getting in touch.