Five platforms, one source of truth.
Protege runs compliant data exchange for AI training — a sophisticated product with an equally complex delivery process spread across five tools. We made HubSpot the operational core and orchestrated the rest around it, sales conversation through to delivery.
HubSpot as the nerve centre of a multi-platform operation.
The situation
Sales, operations and delivery each worked in their own tool — HubSpot, Make, ClickUp, Slack and Linear — with no unified view of where a project stood. Coordination was manual, handoffs were where things broke, and reporting across the whole lifecycle was not possible at all.
The work
We mapped the sales-to-delivery lifecycle across every department and tool, then designed HubSpot as the operational core the other four would orbit. Each stage in the pipeline triggers coordinated actions in ClickUp, Slack and Linear through Make; custom Data Hub endpoints listen for events from those platforms and write status back, so the CRM stays current without anyone updating it by hand.
The handover
Leadership sees every project end to end from one place — first sales conversation through delivery completion — across all five platforms, on reports that were impossible while the tooling stayed fragmented.
Map, centre, orchestrate, report.
Process mapping and tool audit
Mapped the full sales-to-delivery lifecycle across every department and tool: where handoffs broke down, where data sat in silos, and which manual steps were ready to automate.
Hub architecture design
Designed HubSpot as the single source of truth — what data had to flow in and out, and which pipeline events should trigger action elsewhere.
Cross-platform automation
Built the automation chains in Make so each pipeline stage coordinates ClickUp, Slack and Linear, with custom Data Hub endpoints listening for events coming back.
Reporting and visibility
Built the dashboards that give leadership oversight of every project across all five platforms, from first conversation to delivery.
The pieces the team now owns.
HubSpot core
Pipeline architecture from sales through delivery, custom properties for AI project tracking, deal stage automation triggers, and the source-of-truth configuration underneath.
Cross-platform orchestration
Make scenarios driving ClickUp project and task creation, Slack notifications and alerts, and Linear issue sync for engineering.
Inbound data hub
Custom API endpoints for external events, listeners for platform status changes, and bi-directional flow that keeps HubSpot aware of what happens outside it.
Reporting and oversight
End-to-end project status dashboards, pipeline velocity and conversion analytics, cross-department reports, and delivery milestone tracking.
What the team runs now.
- One source of truth unifying HubSpot, Make, ClickUp, Slack and Linear.
- A pipeline where each deal stage triggers coordinated action across every tool.
- Bi-directional flow: HubSpot stays aware of external events through custom Data Hub endpoints.
- Full project visibility from the first sales conversation through delivery completion.
- Cross-department coordination without manual handoffs or status meetings.
- Reporting that was not possible while the tooling stayed fragmented.