REVENUE OPERATIONS CONSULTING
Unblock the decisions holding back your revenue transformation.
CRM and CPQ projects can stall when commercial rules, ownership and cross-functional requirements remain unresolved. I help B2B organizations and implementation partners clarify those decisions and translate them into actionable operating requirements.
From inherited transformation challenges to pricing approvals and customer handoffs, the starting point is the business problem - not another software configuration.
Available for select Revenue Operations consulting engagements.
AREAS OF work
Where I help resolve operating problems
Common starting points include stalled CRM or CPQ implementations, inherited transformations with unclear decision ownership, and revenue handoffs that break across teams.
WAYS TO BEGIN
What a first engagement could deliver.
You do not need to commission an entire transformation to resolve a specific blocker. A focused engagement can clarify the decisions, operating requirements and next actions before a wider commitment.
CRM AND CPQ
Unblock a CRM or CPQ implementation
When pricing logic, approvals, ownership or cross-functional requirements are unresolved and delivery cannot proceed confidently.
POSSIBLE OUTPUTS
Decision register, requirements specification, ownership and approval matrix, implementation acceptance criteria.
TRANSFORMATION RECOVERY
Assess a troubled transformation
When an inherited initiative has unclear progress, unresolved dependencies or a gap between technical rollout and operational adoption.
POSSIBLE OUTPUTS
Current-state findings, risk and dependency map, decision owners, prioritized recovery options.
REVENUE OPERATING MODEL
Define how revenue work should operate
When systems, team responsibilities and handoffs have become fragmented across the customer lifecycle.
POSSIBLE OUTPUTS
Lifecycle and handoff maps, decision-rights model, governance structure, target operating requirements.
Illustrative starting points, not fixed packages. Deliverables and scope are agreed based on the problem, stakeholders and available information.
Implementation partner? I can help resolve the client-side decisions holding up your CRM or CPQ delivery.
POINT OF VIEW
Better technology cannot compensate
for an operating model
that was never designed.
Organizations rarely struggle because a platform lacks features. They struggle because strategic choices were never translated into clear ownership, decision rights, processes, information flows and governance.
Adding automation or AI to that environment may increase speed, but it rarely creates alignment. It can make unclear ownership harder to see, inconsistent processes faster to repeat and poor information easier to scale.
My work begins with the operating model, then determines how data and technology should reinforce it.
Technology should enable - not create - business strategy.

OPERATING PRINCIPLES
Six principles for designing systems that remain useful as organizations change.

FRAMEWORKS
Principles explain how I think. Frameworks make that thinking usable.
ROMA assesses the current Revenue Operating System across process, reporting, ownership, data and systems, identifying maturity gaps, root causes and where intervention or deeper design is required.
BIOS translates strategic intent into an enterprise-wide target operating system across ownership, value flows, context, governance, people and technology, designed to execute consistently and adapt as the business changes.



