Every request, scorecard, sample, BOM, demo, written into HubSpot as a record with line items, source page and first-touch attribution attached.
Ready-made connections, scoped before we quote a timeline. Integrations are the real driver of a replatform schedule.
The specific answer, because a page that says "seamless integration" tells an evaluator nothing they can act on.
Object | Direction | Sync | Notes |
|---|---|---|---|
Contacts | Write | On submit | Created or updated with progressive profiling, so a known field is never asked for twice. |
Companies | Write | On submit | Resolved by email domain and enriched with detected platform and vertical. |
Deals | Write | On qualification | Created with source page, first-touch offer and the capability gaps named at request time. |
Custom behavioural events | Write | On page view and interaction | One named event per page type, plus search, BOM and sample events. |
Lists and workflows | Read / Write | Continuous | Membership driven by real catalog behaviour rather than form fills alone. |
Line items | Write | On RFQ submit | The BOM as line items on the deal, with quantities and attributes, not pasted into a notes field. |
Field-level mapping is agreed during scoping. Customisation in your instance changes the mapping, not the model.
We run this integration on our own site. The forms you have used on these pages write through it, which is the most honest demonstration we can offer.
Each deal records the first page the buyer landed on, the offer they responded to, and which capabilities scored Missing, so a won deal shows the page that started it.
Present, Partial or Missing, each rating followed by the specific observation behind it. Five business days, and there is no call first.