Most organizations approach revenue system configuration backwards. They start with the tool and work through a generic implementation checklist. Every Deal gets the same pipeline. Every company gets the same properties. The assumption is that revenue operations look roughly the same everywhere.
They don't.
A SaaS company with recurring subscriptions has fundamentally different commercial object...
Most organizations approach revenue system configuration backwards. They start with the tool and work through a generic implementation checklist. Every Deal gets the same pipeline. Every company gets the same properties. The assumption is that revenue operations look roughly the same everywhere.
They don't.
A SaaS company with recurring subscriptions has fundamentally different commercial objects than a professional services firm billing by milestone. A manufacturer running CPQ with fulfillment tracking has almost nothing in common with an enterprise sales team managing 18-month deal cycles. Yet most implementations treat them identically — and then wonder why the system doesn't reflect reality.
This is the Scope Decision.
In Part 4 of our Unified Revenue View series on Value-First Data, we walk through the most consequential section of the playbook: choosing which business model drives your implementation. This isn't a preference. It's an architectural decision that determines which HubSpot objects are primary, which are secondary, and which patterns define your commercial rhythm.
The playbook presents four Core B2B Models — SaaS/Subscription, Professional Services, Transactional B2B, and Enterprise Sales — each with specific object priorities. A SaaS business centers on Deal, Subscription, and Quote. Professional Services centers on Deal, Quote, and Order. The objects are the same platform. The emphasis is completely different.
But it doesn't stop at the four core models. We'll explore five Industry-Specific patterns — Manufacturing, Field Service, Healthcare, Education, and Financial Services — where the primary objects may surprise you. Healthcare leads with Contact, Service, and Appointment. Education leads with Contact, Course, and Deal. The platform is flexible enough to serve all of them. The question is whether your implementation reflects your actual commercial reality or someone else's.
And then there are the Hybrid Patterns — because most businesses don't fit neatly into one model. Product + Service. SaaS + Professional Services. Transactional + Recurring. Enterprise + Usage. The playbook helps you name your combination rather than pretending you're purely one thing.
Here's what makes this different from a generic setup guide: the Scope Decision doesn't just categorize you. It cascades forward through the entire remaining playbook. Once you select your model, the Foundation Configuration sections all orient around your specific priorities. You're not implementing every object equally. You're implementing the objects that carry your revenue truth.
Klemen, Casey, and Chris walk through each model live in the playbook, discuss real-world examples from consulting work, and show how the Scope Decision connects to the larger question the Unified Revenue View answers: What's our commercial health, really?
If you've ever felt like your CRM was configured for a business that isn't yours, this episode explains why — and what to do about it.
