Revenue transformation

The best revenue transformations don't start over.

They build around what already works.

Seven pairings: what you already have, and what gets added

What you already have

What gets added

Why it matters under PE ownership

What this looks like in practice

    Preserve what works. Build what's missing. Scale what matters.

    Preserve

    What should not be lost.

    The selling behaviors, customer relationships, expertise, market knowledge, and cultural strengths that made the business work.

    Build

    What the next stage needs.

    The definitions, data, systems, governance, intelligence, process, and management structure the organization now requires.

    Scale

    What the whole organization can rely on.

    Individual excellence and institutional knowledge, turned into a revenue system that doesn't depend on any one person.

    Seven pairings

    The same logic, applied across the operating model.

    The wheel shows the seven pairings at a glance. Each one below goes deeper — what is preserved, what is added, and the work behind it.

    Relationships plus Visibility

    Preserve relationship-driven selling while making the signals surrounding those relationships visible to the broader organization.

    Human relationships + organizational visibility

    • Customer relationships stay human
    • Seller knowledge stays valuable
    • Important account signals become observable
    • Managers see more without sellers documenting more
    • Customer knowledge depends less on individual memory

    Conversation intelligence

    The situation

    The most important signals in the business — competitor mentions, objections, buying criteria, the language customers used to describe their own problems — lived inside customer conversations. Almost none of it left the call.

    What needed to be added

    Visibility into what customers were actually saying, at scale, without asking sellers to document more or change how they ran a conversation.

    What I built

    Competitive and thematic trackers inside the conversation intelligence platform — keyword tracking and AI theme detection for named competitors — scoped against the platform's own configuration limits so the highest-value signals got the scarce slots. I also designed an approach for analyzing transcripts in bulk to find patterns across hundreds of calls rather than one at a time.

    What it enabled

    Competitive activity became reportable instead of anecdotal. Product and marketing could hear the customer directly. The seller's call didn't change; what the organization learned from it did.

    Explore the work sample

    Expertise plus Repeatability

    Capture what experienced sellers and leaders already know so strong commercial behaviors can be understood and repeated — without turning selling into a script.

    Individual expertise + organizational capability

    • Tribal knowledge, written down
    • Qualification experience
    • Buyer patterns
    • The behaviors behind won deals
    • Playbooks that describe, not dictate
    • Repeatable operating patterns

    Qualification gating

    The situation

    New-logo opportunities that looked identical at the same stage converted very differently. Experienced sellers could usually tell which deals were real. The system couldn't, so neither could anyone relying on it.

    What needed to be added

    A shared standard for what a qualified new-logo opportunity contains — grounded in what had actually closed, not a checklist imported from somewhere else.

    What I built

    A qualification gate with a small set of hard requirements — multiple engaged contacts and confirmed buying authority — and a supporting scoring rubric, both derived from analysis of the organization's own won and lost deals. Expansion opportunities were deliberately exempted because they behave differently. A time-boxed provisional status and a sales-leadership override kept room for judgment on unusual or complex deals.

    What it enabled

    Managers inspected pipeline against one definition. Sellers knew what "qualified" meant before the forecast call, not during it. The pipeline number carried fewer false positives.

    Explore the work sample

    Seller judgment plus Intelligence

    Technology, analytics, scoring, buyer signals, conversation intelligence, and data should augment experienced seller judgment rather than replace it.

    Better decisions, not fewer decisions.

    • Ideal customer intelligence
    • Buyer signals
    • Pipeline intelligence
    • Conversation intelligence
    • Decision support
    • Prioritization
    • Pattern recognition

    ICP scoring model

    The situation

    Sellers and leaders had a shared instinct for which accounts fit. That instinct lived in individual heads, so prioritization varied by rep, and marketing, sales, and success each worked from a slightly different picture of a good customer.

    What needed to be added

    A way to make fit explicit and consistent without discarding what the people closest to the market already knew.

    What I built

    A weighted account scoring model that translated seller and market knowledge into explicit fit criteria — anchored on the platform environment a prospect operates in, operating scale, process standardization, and evidence of manual-process pain — with separate weighting profiles by segment and an interactive control panel so leadership could test how a change in assumptions moved the ranked list. It was built to be used, not admired: scores fed the systems marketing, sales, and success actually work in.

    What it enabled

    One definition of fit across the go-to-market team. Sellers prioritized on evidence and could see the reasoning. Leadership could adjust the model as the market moved instead of waiting for a rebuild.

    Explore the work sample

    Flexibility plus Governance

    Preserve room for judgment and complex selling while creating enough structure that leadership can reliably understand what is happening.

    Structure without rigidity.

    • Shared definitions
    • Opportunity stages and required information
    • Qualification
    • Ownership and handoffs
    • Data standards
    • Exceptions, handled on purpose
    • Thoughtful controls rather than bureaucracy

    Revenue architecture

    The situation

    Systems had accumulated faster than ownership. Handoffs between CRM, quoting, billing, and success tooling broke quietly, and different teams held different versions of the same truth — by design, not by accident.

    What needed to be added

    A map of the revenue machine: processes, systems, data flows, owners, controls, and what happens when something falls outside the standard path.

    What I built

    A revenue architecture connecting the process layer, the system layer, and the data and reporting layer, with named ownership at each handoff and explicit exception handling — including where quote-to-cash synchronization gaps existed, who resolved them, and how. Governance was designed as a small number of controls at the points that mattered, not a rulebook.

    What it enabled

    Leadership could see the whole machine. Changes could be made without breaking something no one was watching. New tools had a place to land instead of a place to pile up.

    Explore the work sample

    Experience plus Evidence

    Leadership experience and intuition remain valuable. Decisions become stronger when they are supported by observable evidence.

    Experience informs the hypothesis. Evidence improves the decision.

    • Forecasting
    • Pipeline analysis
    • Conversion
    • Buyer behavior
    • Revenue signals
    • Historical context
    • Analytical decision support
    • Confidence levels, stated plainly

    Annual revenue planning

    The situation

    Leadership needed to know whether Board-level revenue expectations were achievable — not whether the number looked reasonable, but whether the mechanics of the business supported it.

    What needed to be added

    A model that connected the expectation to the factors that would actually produce the revenue, and that separated what was known from what was assumed.

    What I built

    A planning model connecting the target to segment contribution, contract and program timing, product availability, consumption and volume drivers, pending versus reconciled revenue, conversion assumptions, open pipeline, and sales capacity. It distinguished three layers explicitly — what was known, what was reasonably expected, and what depended on future assumptions — and it named the assumptions that had not yet been validated rather than burying them in a blended number.

    What it enabled

    Planning shifted from historical performance plus management judgment toward the actual mechanics of the business. Leadership could see the gap, see what it was made of, and decide what to do about it.

    Explore the work sample

    Autonomy plus Accountability

    Sellers retain reasonable control over how they sell. Leadership gains enough visibility and consistency to manage performance effectively.

    Freedom to sell. Confidence to manage.

    • Seller autonomy
    • Manager inspection
    • Clear expectations
    • Operating cadence
    • Forecast responsibility
    • Pipeline discipline
    • Measurable outcomes
    • Accountability without micromanagement

    Pipeline playbook — the management layer

    The situation

    Sellers wanted room to run their deals. Managers wanted to know what was really in the pipeline. Without shared expectations, that tension resolved into either micromanagement or blind trust, depending on the manager.

    What needed to be added

    A clear, lightweight operating cadence — what a seller is accountable for, what a manager inspects, and when.

    What I built

    The management layer of the pipeline playbook: forecast categories as explicit commitments, a weekly inspection rhythm focused on a small number of high-signal fields, and readiness tiers that made it obvious which deals warranted attention and which should be left alone. The design goal was to make inspection cheap so that trust could be the default.

    What it enabled

    Managers inspected fewer things, more consistently. Sellers spent less time defending their pipeline and more time working it. Accountability moved from tone to definition.

    Explore the work sample

    Growth ambition plus Revenue architecture

    Translate executive and Board-level expectations into the actual mechanics required to deliver them.

    Ambition connected to operating reality.

    • Revenue targets
    • Capacity and productivity
    • Ideal customer and segmentation
    • Pipeline requirements and conversion
    • Timing and coverage
    • Hiring
    • Consumption
    • Forecast assumptions and revenue realization

    Capacity planning model

    The situation

    Leadership had a growth expectation. The question wasn't simply whether the number looked achievable, but what would actually have to be true operationally for the organization to reach it.

    What needed to be added

    The bridge between a target and the operating variables that produce it.

    What I built

    A model connecting revenue expectations to seller capacity, productivity, pipeline requirements, conversion, timing, hiring assumptions, and other operating variables — so that each assumption could be inspected and changed on its own.

    What it enabled

    Leadership could test ambition against the mechanics of the business rather than relying primarily on historical performance or judgment. A hiring plan became a consequence of the revenue plan instead of a separate conversation.

    Explore the model

    Transformation should add capability, not erase identity.

    The objective is not standardization for its own sake. It is to make strong selling easier to understand, support, manage, and scale.

    The commercial strengths that stay exactly where they are.

    • Customer relationships
    • Seller personality
    • Industry expertise
    • Proven sales techniques
    • Local market knowledge
    • Buyer understanding
    • Human judgment
    • Commercial instinct
    • Cultural strengths
    Career context

    Over the course of my career, I've worked inside organizations navigating growth, investment, operational change, and rising commercial expectations — most of them B2B software and healthcare technology businesses, several of them PE-backed. A recurring challenge has been how to introduce the rigor required for the next stage of growth without stripping away the selling behaviors, customer knowledge, and institutional expertise that helped create the business in the first place.

    My role has often been to build the bridge between those two environments: close enough to the sellers to understand why the motion works, and close enough to leadership and Finance to make it legible, measurable, and scalable.

    Transformation as accumulated capability.

    Each stage adds something. Nothing is taken away. The strength the organization started with stays at the top of the stack the whole way through.

    1 of 5
    1. Seller expertise
    2. Shared qualification
    3. Pipeline visibility
    4. Intelligence
    5. Forecast confidence

    The original strength never leaves the stack.

    What the organization gains.

    • Greater confidence in the forecast
    • Cleaner management decisions
    • More consistent qualification
    • Better pipeline visibility
    • Stronger cross-functional alignment
    • Less dependence on tribal knowledge
    • More useful intelligence for sellers
    • Better accountability
    • A revenue architecture capable of scaling

    They build on what made the business worth investing in.

    Find the commercial strengths that created the value. Preserve them. Then build the operating system capable of taking them further.

    1. Preserve the strengths
    2. Build the system
    3. Create the evidence
    4. Scale what works

    That's the kind of transformation I've spent much of my career operationalizing.

    Explore the work behind the transformation
    Work samples

    The work behind the transformation.

    01 ICP scoring modelAccount prioritization + commercial intelligence 02 Qualification gatingSeller judgment + operating consistency 03 Pipeline playbookShared language + management discipline 04 GTM intelligenceSignals + commercial decision support 05 Conversation intelligenceCustomer interaction + organizational visibility 06 Renewal likelihood modelCustomer signals + structured intelligence 07 Demand-to-revenue frameworkDemand + pipeline + revenue mechanics 08 Capacity planning modelGrowth expectations + operating capacity 09 Annual revenue planningBoard expectations + revenue mechanics 10 Revenue architectureProcesses + systems + governance + intelligence