Rhythm
Set the cadence. Build what scales.
In Practice
Three real situations: the problem, what I did, the result.
Scale the Business
The Problem
A founder-led software company had grown past the point where ad hoc systems could keep up. Revenue operations was being run out of spreadsheets and tribal knowledge — a two-person team trying to support a company that had outgrown them months earlier. Forecasting was a guess. Closing the books took weeks longer than it should have. Every new system added meant another manual workaround somewhere else.
What I Did
I led the build of the operating function from the ground up — growing the team from two people to eight, and giving them the budget, tools, and process discipline to do the job right. Together, we redesigned the company's end-to-end revenue workflow, from the moment a deal closed to the moment cash hit the books, replacing manual handoffs with a system that actually held together under growth. None of it worked without the team believing in it first — so before any tool changed, I made sure people understood why it was changing and what it would mean for their day-to-day.
The Result
Revenue leakage dropped, forecasting accuracy improved enough that leadership could trust the numbers in front of them, and the function scaled through years of continued growth without needing to be rebuilt again. What had been the company's biggest operational risk became one of its most reliable functions.
Lifecycle Execution
The Problem
Growth had outpaced the company's ability to manage change. Every team had ideas for fixing what was breaking — new system requests, process fixes, workflow improvements — but there was no consistent way to capture them, prioritize them, or get them shipped. Initiatives competed for attention in an ad hoc way. Things slipped through the cracks, surprised the people downstream, or landed without anyone being ready for them.
What I Did
I built a continuous improvement process that gave the company a steady, predictable rhythm for change — a system to capture every suggestion, prioritize what mattered most, and ship it on a consistent two-week cadence. Nothing moved without the right communication, training, and runway to land well. Instead of change happening in sudden, disruptive bursts, it became something the business absorbed gradually and consistently — across the entire lead-to-cash workflow.
The Result
No more surprises. Initiatives that used to stall or blindside teams now moved through a known, trusted process — and the cumulative effect, cadence after cadence, was a workflow that kept getting better instead of breaking under its own growth.
Execute What Matters
The Problem
What I Did
The Result
Cross-functional projects kept pulling the business off track. Without a shared north star, teams chased whatever felt urgent that week, and nobody — including the people running those projects — was sure what actually mattered most.
I built a single source of truth for priorities: if it wasn't on the list, it wasn't a priority. That gave cross-functional teams one shared reference point instead of competing narratives, and gave me a consistent rhythm for reporting status to the Board and C-level — including what was off track and needed a pivot, and what needed more attention rather than less.
Cross-functional collaboration improved because everyone was finally working toward the same target. Leadership got an early-warning system instead of a quarterly surprise — problems surfaced while there was still time to fix them.