Hi @saidkadaoui3 , this is a classic SaaS setup question, and in 2025 there’s a much clearer pattern emerging now that HubSpot has matured its objects and reporting.
The cleanest mental model is to separate meeting qualification from deal creation. Bookings alone should not create deals. Whether the meeting is booked by an SDR or an AE, the deal should only exist once there’s real sales intent. Practically, that means demos get booked first, meetings get completed, and only then does a deal get created. This avoids bloated pipelines and keeps your close rates meaningful.
On ownership, I’ve seen the least friction when Contacts (and Leads, if you’re using the new Leads object) stay owned by whoever sourced and qualified the meeting. That can be an SDR or an AE. Deals, however, should almost always be owned by the AE from the moment they’re created. If SDR attribution matters for comp, store the SDR in a separate “SDR Owner” user property on the deal rather than via ownership. That makes reporting far easier and avoids reassigning records later.
For the handoff moment, make it explicit and operational. The handoff happens when the demo is completed and qualified. At that point, either the AE creates the deal manually or a workflow creates it once a “Qualified after demo” flag is set. That’s your clean boundary between SDR motion and AE motion, regardless of who booked the meeting.
Pipeline-wise, keep it simple. One pre-deal motion (lead or contact lifecycle), one sales pipeline owned by AEs
only. Stages like Discovery Complete, Evaluation, Decision, Negotiation still work well for SaaS. Round robin stays at the meeting level, not the deal level.
One quick clarifying question: are you already using the Leads object, or are you still modeling everything directly on Contacts? That choice slightly changes how clean your reporting will be, especially for SDR compensation.
Hope this helps.