Renewal health tracking — options ranked from least to most effort
| Option | HubSpot Surface | What It Handles | Owner | Effort | Timing | Recommendation |
|---|---|---|---|---|---|---|
| Native CRM config | Properties + Company record + Deals + Tickets | Core architecture: renewal age, last activity, open ticket count — visible on company record | CRM admin / RevOps | Low–Med | Now | ★ Start here first |
| AI-assisted setup | Breeze + Create with Breeze in Properties | Speeds up field design; generates property definitions and calculations | CRM admin / RevOps | Low | Now | Accelerate the native build |
| Workflow orchestration | Workflows | Conditional logic, syncing company fields from associated records, risk-band stamping, automated refresh | RevOps / automation admin | Medium | Later | Second if rollups too blunt |
| AI insight layer | Data Agent | Narrative fields like "renewal risk summary" or account prep insight | Ops admin / AI admin | Medium | Later | Good overlay, not core metric |
| Dataset-based architecture | Datasets + Workflows + Data Studio | Scheduled/batch recalculation across many accounts; advanced record selection | RevOps / data ops | Med–High | Later | Only if scale becomes a problem |
| Custom-code architecture | Custom code actions in Workflows | Complex scoring, candidate-deal selection, fallback logic, custom transformations | Technical RevOps / developer | High | Later | Only if native logic breaks down |
| Agent / MCP architecture | Breeze Studio + MCP Client | Agent-based orchestration, external tool connections, multi-system workflows | AI platform owner / technical admin | High | Later | Only if agentic architecture wanted |
| Developer tooling | Dev MCP server + HubSpot CLI + Development | Custom apps, external AI integrations, code-first implementations | Developer / solutions architect | Highest | Later | Not recommended first |