True bidirectional HubSpot integration (deals, contacts, status, dollar values)

Problem

The HubSpot integration today is — at best — a one-way push, and even that is unreliable in practice. For shops running HubSpot as their primary CRM, the missing bidirectional sync means every deal lives in two systems, and salespeople end up updating both by hand on every change. The "integration" stops working as an integration the moment a real workflow tests it.

Required capability

• HubSpot deal ↔ platform opportunity sync, both directions, near real-time.
• Contact and account sync so a deal in HubSpot creates the platform-side client record (and vice versa).
• Common fields propagate: site address, building type, market sector, project type, opportunity owner, total dollar value.
• Status sync: created / presented / signed / lost states translate cleanly between the two systems.
• Conflict resolution rules for the inevitable both-sides-edited case.
• Field-mapping configuration so each tenant can decide how their HubSpot fields line up with the platform's opportunity fields.

Why it matters

Mid-size integrators frequently land on HubSpot as their first real CRM well before they pick a vertical-specific tool. The platform doesn't need to replace HubSpot; it needs to integrate with it well enough that customers don't feel forced to choose. Today they choose — and a HubSpot-using shop either skips the platform's CRM features or skips HubSpot for opportunity tracking. Either path leaves real value on the table.

An equivalent integration to Salesforce is a natural follow-up; the design choices and field-mapping infrastructure carry over.