Value-First Data - Apr 14, 2026

Most HubSpot implementations treat pipeline configuration like plumbing. Get the stages roughly right, add a few required fields, connect the automations. Done. The system is live.

Six months later, no one trusts the forecast.

Not because the system failed. Because the foundation was built to track activity instead of commercial reality. The stages describe what salespeople do — Demo Scheduled, Proposal Sent, Contract Out — not where the relationship actually is. Revenue intelligence is impossible when your pipeline is a log of events rather than a map of truth.

This is the central challenge of Part 5 of the Unified Revenue View series on Value-First Data.

In Part 4, Klemen, Casey, and Chris worked through the Scope Decision: choosing which business model drives your HubSpot implementation. That decision establishes your primary commercial object and your revenue cadence. SaaS businesses center on Deal and Subscription. Professional services firms anchor to Deal, Quote, and Order. The model is different; the platform is the same.

Foundation Configuration is where the model becomes architecture.

The foundational question for every pipeline stage isn't "what happens at this step?" It's "what do we know, with confidence, at this point in the relationship?" Those are different questions — and they lead to completely different stage names, different required properties, and different forecast categories.

An activity-based pipeline stage ("Proposal Sent") tells you what occurred. A relationship-based stage ("Terms Under Discussion") tells you where you are. One tracks motion. The other tracks position.

The distinction matters because forecast accuracy depends on position, not motion. You can send 50 proposals and have zero commercial reality in any of them. You can have two relationships under mutual terms discussion and know with confidence what's coming. Foundation Configuration determines which of these your system can see.

Casey Hawkins and Klemen Hrovat bring two perspectives that rarely appear in the same conversation. Casey works at the commercial language layer — helping organizations translate their actual business model into stage names and property configurations instead of copying a generic CRM template. Klemen works at the data architecture layer — building the technical foundation that keeps itself honest.

Together, they expose the configuration gap most implementations never close: the moment where theoretical design meets actual data entry behavior.

Stage gates are the enforcement mechanism. They define what must exist before a deal advances — not as bureaucratic obstacles, but as data quality guarantees. When a deal reaches "Terms Under Discussion" and the associated contact doesn't carry a meaningful engagement signal, the gate surfaces the gap. The foundation doesn't let you lie to it. That's by design.

The Unified Revenue View relies on this. URV's core question — "What's our commercial health, really?" — can only be answered if the foundation reflects reality. A foundation built on activity tells you how busy you are. A foundation built on commercial truth tells you where you stand.

Today, the playbook opens to the build.

Join Klemen, Casey, and Chris as they walk through Foundation Configuration — translating scope decisions into actual HubSpot architecture. You'll see how pipeline stages become commercial truth markers, how stage gates enforce data quality without blocking sales, and how the foundation determines everything the system can tell you downstream.

Live: Tuesday, April 14, 2026 at 2:00 PM CT