Revenue Foundations · Research

Applied research on revenue systems and operations.

Field notes from the work — HubSpot architecture, integration design, and the trade-offs that only show up at production volume. Written for the people who have to build it, and the people who have to sell it.

3Papers
45Pages
FreePDF downloads

The Library

3 titles

Case Studies

6 studies
No. C1Revenue Systems Architecture

Migrating a wealth-advisory firm off Redtail to HubSpot

A wealth-advisory firm standardized on HubSpot — but an advisory firm’s value lives in households, accounts, a web of relationships, and provable compliance, not in contacts. A first-principles account of a platform migration: mapping the source model to HubSpot objects, finding what has no native home (accounts, households) and what that forces, parsing a decade of encoded fields into typed properties, and rebuilding 60+ adviser-run compliance workflows as team-assignable ticket pipelines.

HubSpot · Migration · Custom Objects · Wealth / RIA

Jul 20269 minRead
No. C2Revenue Systems Architecture

Stopping a Stripe–HubSpot sync from splitting 5,000 members

A multi-location membership business wired Stripe into HubSpot with the off-the-shelf connector. It worked until members cancelled and returned — the billing platform re-issued a new customer ID each time, the 1:1 sync treated each as a new human, and ~5,000 contacts fractured. A first-principles look at identity resolution: why native connectors can’t solve it, the bridge-object model that collapses many billing IDs into one person, the custom objects a non-deal business needs, and the Custom-Code-vs-middleware decision.

HubSpot · Integration · Identity Resolution · Middleware

Jul 20268 minRead
No. C3Revenue Systems Architecture

Modeling a dealer channel in HubSpot for an equipment manufacturer

An equipment manufacturer sells serial-numbered machines through independent dealers while marketing to the operators who use them. HubSpot’s contact–company–deal default assumes you sell to the buyer, so at the point of sale the end customer disappears. A first-principles look at modeling a channel: dealer/employee/customer on one account via association labels, the install base as an Equipment custom object, a warranty-capture loop to recover the operator, and the Orders object as the ERP bridge.

HubSpot · Custom Objects · Channel · Manufacturing

Jul 20268 minRead
No. C4GTM Operations

Migrating a custom fabricator off a legacy PSA to HubSpot

A bid-driven fabrication studio migrated to HubSpot and carried its pipeline across one-to-one — dozens of stages mixing sales progression with production approvals, so forecasting meant nothing. A project business has two lifecycles: winning the work and doing it. A first-principles account of separating them without a Project custom object: a streamlined deal pipeline, the native Ticket object as the project record, a change-order pipeline of child deals, and stage requirements as hard gates.

HubSpot · Tickets · Pipelines · Project-based

Jul 20268 minRead
No. C5GTM Operations

Scaling consult intake in HubSpot for a consumer law firm

A high-volume, multi-office consumer law firm ran on speed-to-lead and consult booking, but its scheduler didn’t write meeting outcomes or associations back to HubSpot — so intake lived in spreadsheets. A first-principles account of treating the intake layer as a data contract: what a booking system must return, the post-sale lifecycle as a ticket pipeline, scoring on case economics not engagement, and activity-based recycling to enforce follow-up at scale.

HubSpot · Intake · Routing · Tickets

Jul 20268 minRead
No. C6Commercial Strategy

Splitting B2B leasing from D2C in one HubSpot Commerce portal

A hardware company leases devices to institutions on multi-year contracts and sells kits through a D2C web store — two motions in one Commerce Hub portal. Invoices generated blank, e-commerce orders duplicated by lease term and shipped wrong quantities, web-only products leaked into institutional quotes. A first-principles account of separating transactional and contractual sales: custom-coded workflow actions to reshape order data, validation as an integrity gate, catalog visibility, and fulfillment-aware stages.

HubSpot · Commerce Hub · CPQ · E-commerce

Jul 20268 minRead

Series

5 standing lines of inquiry
  • IRevenue Systems ArchitectureHow revenue data actually moves.2 papers
  • IIAttribution & MeasurementWhat marketing spend actually returns.1 paper
  • IIIGTM OperationsThe machinery between a lead and a booking.Forthcoming
  • IVRevenue IntelligenceSignal over noise in the pipeline.Forthcoming
  • VCommercial StrategyPricing, packaging, and the shape of the deal.Forthcoming