Case studies

The operating work behind the outcome.

Three enterprise stories showing how revenue policy, finance operations, systems change, training, and cross-functional execution come together under pressure. Each one describes the situation, the work, and what held afterward.

Evidence note: these stories summarize publicly documented corporate roles, not confidential consulting-client claims. Scope measures are included only where the available record supports them.

  1. ENTERPRISE SEPARATION + ASC 606

    Keeping revenue operations coherent while the organization changed around them.

    Pressure
    A major technology-services separation created a new operating organization while revenue teams were also implementing ASC 606 across complex U.S. public-sector contracts.
    Transformation work
    Revenue-recognition leadership connected legacy and new finance operations, coordinated with contracts and operating teams, developed training materials, and supported consistent application through the transition.
    Supported outcome
    Revenue-recognition continuity was maintained through separation and subsequent restructuring, with standardized practices and training supporting the newly formed organization.

    2

    corporate transitions supported

    ASC 606

    implementation environment

    3

    functions aligned

    Discuss the related engagement

  2. U.S. PUBLIC-SECTOR REVENUE OPERATIONS

    Turning technical revenue requirements into repeatable operating work.

    Pressure
    Complex government-contract environments required consistent revenue conclusions while reporting structures, close activities, systems, and ownership were changing.
    Transformation work
    The operating response linked technical accounting, close execution, process documentation, cross-functional coordination, ERP-related change, and practical training for finance professionals.
    Supported outcome
    Revenue and close activities were standardized through significant organizational change, preserving an operating path from technical requirements to reviewable execution.

    7+ years

    public-sector revenue depth

    4

    operating groups connected

    4

    enterprise environments

    Discuss the related engagement

  3. CROSS-MARKET REVENUE CONSISTENCY

    Creating consistency across markets and multiple revenue models.

    Pressure
    International telecommunications operations needed coordinated revenue-recognition treatment across Central and Latin America and across hardware, software, and services transactions.
    Transformation work
    Regional finance coordination addressed complex transaction structures, supported consistent accounting treatment, and connected local execution to a shared technical foundation.
    Supported outcome
    Finance teams across markets worked from a more consistent revenue-recognition approach while retaining the judgment required for varied transaction structures.

    5 years

    regional leadership span

    2

    regions coordinated

    3

    revenue models covered

    Discuss the related engagement

Describe the transformation you are facing.

A short conversation is usually enough to tell whether the work is a diagnostic, a full program, or something you can run yourself.

Discuss a transformation

More writing on this work is in Insights.