Looking for confirmation that this moves from the current deal flow to a contract base flow? Are the objects different from the process of completing a deal? Structure? Naming conventions? How consumers are associated to each other, deal, and/or contracts?
If so how do you create or edit the contracts? If one pushes a quote to be accepted then does HubSpot create the contract and push to the consumer?
What option are available for payment plan creations? How flexible is this option?
Is there a way to integrate forms into the process?
Great questions! Hopefully some folks with hands-on experience can weigh in. While we wait for some more peer input, I believe a good starting point could be this KB article on the matter:
From the current KB, Contracts are a separate object from Deals rather than a replacement for the existing deal flow. It appears that Contracts are intended to be the source of truth for committed revenue and can be associated with the other object types – while deals will still track opportunity.
I’d like to tag in some of our Top Contributors to see if they have any experience with this!!
Contracts are not a rename of Deals. Treat them as a second object that owns committed revenue after the commercial decision is locked.
What usually holds when teams pilot this:
Deals stay the opportunity path (stage, forecast, next step). Contracts become the source of truth for what was actually agreed (amount, term, start/end, status). Associate Contract ↔ Deal ↔ Company ↔ Contact; do not try to make one object do both jobs.
Naming: keep Deal names sales-facing (opportunity). Put legal/commercial identifiers on the Contract (contract number, term label). Mixing those strings on the Deal is what makes reporting ugly later.
Quote accepted → Contract: do not assume every accepted quote auto-spawns a customer-facing Contract push. In pilots, teams usually decide: (a) quote acceptance updates Deal to Closed Won and a Contract is created/associated by workflow or sales action, or (b) Contract is created first and the quote is attached. Confirm the exact beta path in your portal before you promise buyers an auto-push.
Payment plans: model plan terms on the Contract (or related line/schedule), not as a pile of Deal properties. Flexibility is fine until finance needs one place for “what we are collecting.”
Forms: use forms for intake / change requests that create or update Deal or ticket data. Keep signature / acceptance on quote or Contract flows, not a second free-form “I agree” form that never associates cleanly.
Pro limits: check your hub’s Contracts / Commerce entitlements before redesigning pipeline. Beta UI access and full production limits are not always the same conversation.
Practical pilot: one Closed Won Deal + one Contract association + one payment-plan case + one amendment. Confirm associations and reports before opening the beta to the whole sales team.
If you share whether you are Commerce/Payments-heavy or quote-only today, the quote→Contract step gets clearer fast.
Welcome to the Community @HBRichard! While I’m not personally in the beta for contracts, here’s my experience with HubSpot and what I know of its evolution in relation to this new object. HubSpot Contracts is a separate native CRM object, not a replacement for Deals. The intended model is: Deal → Quote → accepted Quote → Contract, with the contract becoming the operational record of committed revenue after the sale.
I found this table breaking down the objects and thought it was helpful:
HubSpot’s designed to have Deals operate as opportunities, and Contracts represent the full customer agreement lifecycle (including amendments and renewals). A contract can be associated with contacts, companies, deals, quotes, invoices, line items, payments, and subscriptions.
I’d say don’t eliminate your existing deal flow. Continue using your normal deal pipeline for new business, then use Contracts as the post-sale commercial record. For cleaner forecasting and reporting, HubSpot recommends distinct pipelines for new business, expansions/change motions, and renewals.
I think most of the rest of your questions are answered in the resource @stassey shared. Hope that helps a bit!
