Contracts API

This is the one to plan around, and it is not close. The gap it closes is the one every admin has been hacking around for years: today, managing a customer's changing commitment means closing a deal won, spinning up a new deal in a renewal pipeline, and opening a ticket in a support pipeline to track the relationship. Nobody chose that architecture. It is what you do when the platform has no object for the actual agreement.

The motion this unlocks is the interesting part. At an upgrade moment, pull the customer's current contract into a quote, show them what they have, let them add or remove what they are paying for, layer in recommendations for what else is available, and write the change back into the contract when they sign or pay. The lifecycle is then managed natively, and anyone can open the contract and see everything that customer bought over time.

One flag before you get excited. This is built for recurring-revenue moments and change management over time. If you are expecting it to behave like general contract-management software, check that assumption first, because it is designed to shade toward the merchant-style functionality the naming implies.

Speaking of which: if you adopt contracts, HubSpot now calls you a merchant. Plenty of businesses will benefit from contract functionality and approximately none of them describe themselves that way. Read it as "company" and move on.