Stage 01
Map Contact States
Defined campaign tags, role fields, hot-lead status, monthly-drip state, deal conditions, and the transitions connecting each lifecycle path.
Output / Lifecycle state map
Back to portfolio
Draft case study2025–2026
Lifecycle Automation
HVAC Lifecycle Automation.
Built an HVAC lifecycle system spanning nurture, hot-lead routing, deal suppression, win-back, monthly drip, calling, and cross-platform handoffs across connected marketing tools.
HubSpotZapierInstantlyAircallAutomation
Explore the rebuild
Main Track
Multi-touch nurture
Champion
Role-based sequence
Win-back
Delayed re-entry
Properties
Campaign state fields
The System Problem
A CRM rebuild starts by identifying the connected failures underneath the visible symptoms.
Root cause / 01
A campaign needed one lifecycle instead of disconnected automation islands
The campaign crossed HubSpot, Zapier, Instantly, Aircall, Slack, and Meta-related workflows. Without shared state, one contact could enter overlapping sequences, receive follow-up after creating a deal, or reappear in win-back without the controls needed to stop duplicate outreach.
The project became a lifecycle design problem rather than a simple nurture build. Each system needed clear ownership, suppression logic, campaign tagging, reply behavior, and handoff rules so sales activity could interrupt marketing automation cleanly instead of competing with it.
Audit signals
What the system was telling us.
01
Main nurture required coordination
02
Role-based track needed separate logic
03
Deals had to suppress outreach
04
Win-back required delayed re-entry
05
Monthly drip required no open deal
Rebuild Sequence
The work moved from diagnosis to architecture, implementation, and governance—in that order.
Stage 02
Build Nurture Paths
Implemented the main and champion sequences, hot-lead bypass logic, reply handling, and one-sequence-at-a-time safeguards reliably across connected tools.
Output / Automated nurture tracks
Stage 03
Wire Sales Handoffs
Connected deal creation, Slack alerts, Aircall events, and suppression logic so sales activity could immediately change marketing behavior.
Output / Sales handoff system
Stage 04
Add Recovery Loops
Built win-back, nurture completion, monthly drip, re-engagement, and rollback safeguards so long-term follow-up remained controlled after primary sequences ended.
Output / Recovery automation layer
Target System Architecture
Four connected layers turned the portal from a collection of tools into an operating system.
System spine
Target-state sequence
Good automation and reporting sit on top of a governed data and process model—not the other way around.
Layer 01
Campaign State
Persistent campaign properties identified audience, role, urgency, win-back status, and monthly-drip membership consistently across the entire lifecycle system.
Layer 02
Sequence Control
Automation enforced the correct nurture path while preventing hot leads, replies, and active deals from receiving conflicting outreach.
Layer 03
Sales Signals
Deal creation, calls, and engagement events updated CRM state and triggered suppression, alerts, or follow-up across connected systems.
Layer 04
Long-Term Followup
Win-back and monthly-drip logic created controlled re-engagement paths after the initial nurture ended without reopening every contact blindly.
Qualitative Outcomes
The engagement focused on structural improvement, so the strongest results are clearer operations—not invented vanity percentages.
SystemBeforeAfter rebuild
Nurture
Disconnected sequence behavior across tools
One coordinated lifecycle system
Suppression
Deals could coexist with outreach
Deal activity stopped sequences
Routing
Hot leads risked standard nurture
Hot leads bypassed nurture
Re-engagement
Follow-up lacked durable state
Win-back and drip controlled
What Was Delivered
A reusable case study should make the work tangible without exposing confidential client data.
Deliverable 01
Lifecycle architecture map
Deliverable 02
Eleven-touch nurture build
Deliverable 03
Eight-touch champion track
Deliverable 04
Deal suppression automation
Deliverable 05
Win-back and drip logic
Deliverable 06
Aircall and Slack handoffs
System note / final
Architecture before automation.
The durable part was not any single workflow. It was the shared state between systems. Once campaign tags, deal conditions, replies, calls, and nurture status all meant the same thing across tools, automation stopped behaving like six coworkers forwarding the same email to each other.
Client identity, campaign content, phone data, and internal routing rules remain confidential.