Perspectives

Field notes on computational revenue

On this page

Written by the authors

How companies design revenue around each offer, and run it as one system that learns and improves each cycle.

  • July 2026

    The Continuum

    Where each offer sits on the continuum — and what breaks when it moves

    Every offer sits somewhere across five positions — and most are quietly moving. A diagnostic for knowing an offer's position, its direction, and what each shift breaks.

  • June 2026

    On the Podium, Not in the Loop

    Why the Revenue Motion Stays Human — and How the Operating System Holds the Balance

    Human-in-the-loop makes people approvers of work they no longer author. But the revenue motion is a human motion. The Revenue Architecture Operating System (RAOS) is the balance — judgment and empathy on the podium, AI doing much of the work.

  • May 2026

    The Entropy of Human Heuristics

    Why Revenue Strategy Fails at Scale — and What Replaces It

    The half-life of a methodology engagement is about 90 days. Why revenue strategy decays after the consultant exits, and the operating-system model that replaces it.

  • April 2026

    The Agentic Inflection

    When the Buyer Arrives as an Agent, the Manual Sales Motion Has Already Lost

    Buyers are arriving as agents, and the manual sales motion can't answer them. The agentic inflection is the shift from manual persuasion to orchestrated revenue.

  • March 2026

    Beyond the Franken-Stack

    Where the Operating System Sits in Your AI Stack — and Why the Tools Don't Replace It

    Which layer governs, which tools execute, how they connect — where the Revenue Architecture Operating System fits, and why point tools can't replace the layer that makes them cohere.

  • February 2026

    Beyond Strategy Drift

    Why the Distance Between Your Strategy and Your Frontline Is an Architecture Problem

    Strategy drift isn't a talent gap or a discipline gap. It's an architecture gap — strategy treated as a document, execution as behavior. An operating system closes it.

  • January 2026

    The Methodology Trap

    Why You Keep Buying Training and Keep Drifting Back

    Sales methodologies are manual, and all of them decay. Why training is a patch, not a system, and what an operating system does instead.

  • December 2025

    Value Architecture

    The Four-Level Cascade That Replaces Messaging — BVP to CVP

    Messaging is creative copy that drifts. Value Architecture is an engineered cascade — Brand, Offer, Audience, and Customer Value Propositions — that stays coherent end to end.

  • November 2025

    The FACT Model

    Why Qualification in Considered Sales Is a Collaboration, Not an Interrogation

    BANT qualifies the seller's way. FACT — Fit, Authority, Criteria, Timeline — qualifies the way considered deals are actually won — as a two-way collaboration.

  • September 2025

    The Close Is the Midpoint

    Why the Funnel Has to Run Past the Close in High-Consideration Revenue

    The vertical funnel treats the close as the finish line. In high-consideration revenue the close is the midpoint, with acquisition and expansion designed as one motion across the full lifecycle.

  • August 2025

    The CRO as Architect

    Why the Average CRO Lasts Eighteen Months — and What the Ones Who Stay Build Instead

    CROs don't fail for lack of talent. They fail for lack of a system. The shift from leading sales from the front to architecting a revenue operating system that produces the number.

  • July 2025

    The Outside-In Rule

    Wherever You Sit on the Continuum, Lead With Their Problem — Not Your Capabilities

    The strongest temptation in any sale is to lead with what you do. The outside-in rule inverts it — engage from the buyer's urgent and visible problems, at every position on the continuum.

  • June 2025

    The Wholesaler as Architect

    Why Distribution in Asset Management Stopped Rewarding the Pitch

    Advisors do most of their evaluation before the call, and content is everywhere. What they still can't get is judgment. The case for the wholesaler as architect, not pitcher.

Subscribe to Perspectives

New pieces on the shift from human heuristics to computational revenue, when they publish. No spam; unsubscribe anytime.

Questions about a piece, or how it applies to your company?

Write to John Stone and Sherwin Uretsky. They read every note.