1. Titles - Title 1 | Rebuilt Marketing Automation in 30 Days | Transformation | Score: 8 | Rationale: Clear outcome, strong timeline, and highly relevant to operators actively considering a migration. - Title 2 | We Quit HubSpot Enterprise. Here’s the Playbook | Contrarian | Score: 9 | Rationale: Taps into a real frustration while promising a practical, non-ranty breakdown. - Title 3 | The Hidden Cost of HubSpot Enterprise | Curiosity | Score: 8 | Rationale: Strong pain-point hook for budget owners who suspect the invoice is only part of the problem. - Title 4 | 3 Automations That Paid for Our Migration | Listicle | Score: 8 | Rationale: Specific and benefit-driven, with a clear payoff tied to revenue and ROI. - Title 5 | HubSpot Wasn’t the Expensive Part | Contrarian | Score: 9 | Rationale: Creates an immediate curiosity gap and reframes the buyer’s existing complaint. Recommended winner: We Quit HubSpot Enterprise. Here’s the Playbook This title has the best mix of emotional pull and practical promise. It signals a real story, not a generic software comparison, while attracting both HubSpot-frustrated buyers and marketing ops leaders looking for a migration framework. 2. Thumbnail Concepts - Thumbnail A: Split-screen composition. Left side shows a blurred HubSpot-style invoice with a large red “$128K” stamped over it; right side shows a clean automation flow diagram with green checkmarks. Overlay text: “WE MIGRATED”. Facial expression: skeptical half-smirk, eyebrows raised. Color scheme: orange, black, and green. Psychological trigger: cost shock plus transformation. Paired title: We Quit HubSpot Enterprise. Here’s the Playbook - Thumbnail B: Presenter holding two sheets of paper: one labeled “LICENSE” and one labeled “CONTRACTORS,” with the contractor sheet visibly larger. Background includes faint workflow spaghetti lines. Overlay text: “HIDDEN BILL”. Facial expression: dry disbelief, slight grimace. Color scheme: white, charcoal, HubSpot orange accent. Psychological trigger: hidden cost reveal. Paired title: HubSpot Wasn’t the Expensive Part - Thumbnail C: A 30-day calendar visual with Week 1, Week 2, Week 3 checked off, and a bold arrow pointing to “PAID BACK.” Add small icons for email, routing, attribution, and CRM sync. Overlay text: “30 DAY REBUILD”. Facial expression: focused, confident, slightly tired. Color scheme: navy, electric blue, lime green. Psychological trigger: speed, structure, and ROI. Paired title: Rebuilt Marketing Automation in 30 Days 3. Full Script A. HOOK <<0:00 - 0:30>> - Hook type: Shocking stat - Open loop: HubSpot wasn’t the expensive part — the hidden contractor layer was. - Value preview: Exact cost breakdown, why we picked Customer.io, the 30-day migration plan, three automations that paid back the move, and audit results after launch. - Pattern interrupt at ~0:15: Hard cut from clean dashboard to a blurred contractor invoice with a cash register sound. - Spoken script: We rebuilt our marketing automation in 30 days. Not “we cleaned up a few workflows.” We ripped out HubSpot Marketing Enterprise, rebuilt the lifecycle engine in Customer.io, reconnected Salesforce, and shipped three revenue automations before month-end. And the weird part? HubSpot wasn’t the expensive part. <<QUICK CUT. CASH REGISTER SOUND. BLURRED CONTRACTOR INVOICE FILLS SCREEN.>> The expensive part was the human layer we needed just to keep it usable. I’ll show you the real cost, the migration plan, the three automations that paid it back, and the audit results after the dust settled. (B-roll: screen recording of messy workflow folders, blurred invoice, calendar flipping 30 days, Customer.io journey canvas, Salesforce campaign screen) B. INTRO / CONTEXT <<0:30 - 1:30>> - Spoken script: Quick context. We run marketing ops and demand-gen rebuilds for B2B SaaS teams. Mostly companies between 50 and 500 people. Usually on HubSpot or Marketo. Usually with one very tired demand-gen lead, one ops person if they’re lucky, and about 47 workflows nobody wants to touch. This was one of those. The company had Salesforce as the CRM, HubSpot Marketing Enterprise for automation, Chili Piper for routing, Clearbit for enrichment, Dreamdata for attribution, and a pile of Zapier jobs nobody trusted. On paper, the stack looked normal. In practice, every campaign needed a workaround. Every scoring change needed QA. Every lifecycle update became a “let’s ask the contractor” moment. That’s the part nobody budgets for. If this is the kind of teardown you want more of, subscribe when the math starts feeling uncomfortably familiar. That’s usually the signal you’re in the right room. And keep one number in your head: 30 days. Because the migration didn’t work because we moved fast. It worked because we refused to migrate the mess. (B-roll: SaaS stack logos, blurred Slack thread saying “can we update the workflow?”, Asana migration board, close-up of workflow map with crossed-out branches) C. MAIN BODY Segment 1 -- The Invoice Wasn’t the Cost <<1:30 - 4:05>> Here’s the actual cost. Their HubSpot Marketing Hub Enterprise contract was $4,800 a month after discount. That included the contact tier they were on, around 82,000 marketable contacts. Then Ops Hub Pro added another $800 a month. A few paid seats, dedicated IP, and reporting add-ons brought the annual platform number to about $76,800. Annoying? Yes. But survivable. The hidden bill was the contractor layer. They had a part-time HubSpot admin on retainer for $3,500 a month. Then another $12,000 in one-off cleanup work across the year. Workflow fixes, scoring edits, deduping, campaign attribution patches, form routing bugs. So the all-in number wasn’t seventy-six grand. It was $130,800. For a system the team still described as “fine, as long as we don’t touch it.” (B-roll: blurred invoice stack, calculator showing $76,800 then $130,800, workflow with red warning icons) <<RETENTION BEAT at ~2:45: Cut to a mock “SaaS Budget Crime Scene” board with red string connecting license, contractor, sync errors, and campaign delays.>> And that’s the first lesson. Don’t compare software cost to software cost. Compare operating cost to operating cost. <<EASTER EGG>> A quick test: pull the last 90 days of Slack messages mentioning “HubSpot,” “workflow,” “sync,” or “can you fix.” If that thread has more than 25 real requests, you don’t have a platform cost problem. You have an operations drag problem. The transition was obvious. But the replacement couldn’t just be cheaper. It had to make fewer things require a specialist. So we narrowed the decision down fast. Segment 2 -- Why Customer.io, and Weeks One-Two <<4:05 - 6:55>> We picked Customer.io for one main reason. It treats behavior and data as first-class citizens. Not lists first. Not forms first. Events first. For this company, that mattered because their best buying signals weren’t form fills. They were product usage, pricing page revisits, integration page views, G2 intent, and sales activity in Salesforce. The alternative stack became pretty simple. Customer.io for journeys and email. Salesforce as the source of truth for accounts, opportunities, owners, and lifecycle. Segment for product events. Census to sync modeled account data from BigQuery. Chili Piper for routing. Dreamdata for attribution. Week one was not migration. Week one was demolition. We exported every HubSpot workflow, form, list, property, score, and campaign. Then we tagged each asset as keep, kill, merge, or rebuild. Out of 137 workflows, only 31 survived. That was the whole ballgame. (B-roll: workflow export spreadsheet, columns labeled keep/kill/merge/rebuild, giant red “KILL” stamp) <<RETENTION BEAT at ~5:25: Screen goes black for one second, then text appears: “Most migrations fail because they migrate nostalgia.”>> Week two was the data contract. We defined the fields Customer.io could write back to Salesforce. Not everything. Just the useful stuff. Lifecycle stage. Last meaningful touch. Active journey. MQL date. Hand-raise source. And disqualification reason. Concrete example: instead of syncing every email click as a Salesforce task, we synced one clean field: “current buying signal.” Much less noise. Much more useful. And by the end of week two, the scary part was done. The system could send, listen, route, and report. Now it needed to make money. Segment 3 -- Three Automations Paid It Back <<6:55 - 10:45>> Week three is where the migration stopped being a project and started being a business case. The migration cost was $18,000 in services and internal time. We needed payback fast. Automation one was speed-to-lead for demo hand-raisers. If someone requested a demo, Customer.io enriched the person, checked account fit, looked up territory in Salesforce, triggered Chili Piper, and posted to Slack if no meeting was booked within five minutes. Before, median routing time was 42 minutes. After, it was under 90 seconds. That produced nine extra meetings in the first month. At their historical conversion rate, that was about $31,000 in expected pipeline. (B-roll: timer dropping from 42:00 to 1:28, Slack alert, Chili Piper booking screen) <<RETENTION BEAT at ~8:20: Quick fake courtroom graphic: “Objection: pipeline is not revenue.” Speaker nods and says, “Correct. Which is why we used conservative math.”>> Automation two was the “warm but not ready” recycle path. Closed-lost no-decision opps went into a 60-day education journey. But only if they showed new intent — pricing page, competitor page, G2 category visit, or product docs. That created four re-opened opps in 30 days. Automation three was account expansion. When three or more users from the same customer account hit an integration or security page, Customer.io notified the CSM and enrolled the champion in a relevant sequence. That produced two expansion conversations that would have been invisible before. <<EASTER EGG>> Here’s the underrated move: name your automations after the business outcome, not the tactic. “Demo Speed-to-Lead.” “Closed-Lost Revival.” “Expansion Intent.” Nobody funds “Workflow 17B.” By day 30, we had $54,000 in influenced pipeline tied to automations shipped in week three. Not magic. Just fewer leaks. But the audit is where the story got more interesting. Segment 4 -- The Audit After the Dust Settled <<10:45 - 13:35>> Thirty days after launch, we ran the audit. Not vibes. The boring stuff. Deliverability, engagement, attribution, routing, sync health, and team time. Open rate went from 28.4% to 36.9%. Now, open rate is a messy metric. Apple Mail Privacy made sure of that. But the improvement still mattered because it moved alongside better click quality and fewer spam complaints. The main reason wasn’t subject lines. It was segmentation. We killed batch sends to the bloated database and rebuilt around lifecycle, account stage, product usage, and declared interest. (B-roll: email performance dashboard, segment builder, before/after chart) <<RETENTION BEAT at ~12:00: Cut to a giant fake trophy labeled “Best Subject Line” being thrown into a trash can.>> Attribution got cleaner too. Before migration, 41% of sourced pipeline was sitting in “unknown,” “direct,” or “manual campaign.” After 30 days, that dropped to 17%. Not perfect. But finally useful. The biggest internal win was time. The demand-gen lead had been spending six to eight hours a week checking workflows, fixing list logic, or asking the contractor to explain why something fired. After migration, that dropped to about 90 minutes. And the contractor retainer went away. There were still issues. Two Salesforce sync errors. One broken suppression rule. One email that should have excluded open opportunities and didn’t. Normal migration bruises. But the team had something they didn’t have before. Confidence to edit their own system. That’s the real unlock. And it brings us back to the open loop. D. CLIMAX / KEY REVELATION <<13:35 - 14:45>> The reason this worked wasn’t because Customer.io is magically better than HubSpot. That’s the lazy take. The reason it worked is because we stopped treating marketing automation like a campaign tool. It’s not. For a B2B SaaS team, marketing automation is the operating layer between demand, sales, customer data, and revenue motion. If that layer is full of old lists, mystery workflows, fake MQL math, and contractor-only logic, the software almost doesn’t matter. You’ll recreate the same mess in a new UI. So the open loop is this. HubSpot wasn’t the expensive part. The expensive part was renting clarity from someone outside the team every time the business changed. The migration paid back because it made the system understandable again. That is the playbook. Kill the mess. Define the data contract. Ship the money workflows first. Then optimize. E. CTA SECTION If you’re looking at your HubSpot or Marketo renewal and wondering whether the number on the quote is the real number, we can help you pressure-test it. There’s a link in the description to book a 30-minute migration audit call with our team. We’ll look at your current stack, your hidden ops cost, and whether migration actually makes sense. Sometimes the answer is rebuild. Sometimes it’s stay put and clean house. And if you want the next layer, watch the video on how to design lifecycle stages that sales will actually use. F. OUTRO A clean automation system should not require a séance, a contractor, and three Slack threads to change one rule. If it does, the invoice is lying to you. The platform is only part of the cost. The operating drag is the part that compounds. [END SCREEN: “Lifecycle Stages Sales Will Actually Use” on left, “Book a Migration Audit” visual prompt on right] 4. Retention Strategy Map - Techniques used: - <<0:00>> Shock claim: “HubSpot wasn’t the expensive part.” - <<0:15>> Pattern interrupt with blurred contractor invoice and cash register sound. - <<1:30>> Specific cost breakdown to build trust and reward early attention. - <<2:45>> Visual metaphor: SaaS Budget Crime Scene board. - <<4:05>> Reset with tool choice and migration structure. - <<5:25>> Contrarian line: “Most migrations fail because they migrate nostalgia.” - <<6:55>> ROI section begins with clear payback target. - <<8:20>> Objection handling pattern interrupt: pipeline is not revenue. - <<10:45>> Audit results to deliver measurable payoff. - <<13:35>> Key revelation reframes the whole story around operating clarity. - Predicted retention curve shape: Expect a strong initial hold because the hook combines a specific timeline, a recognizable platform, and a hidden-cost curiosity gap. Retention should dip slightly during context, recover during the cost breakdown, spike at the three automations section, and hold through the audit because the payoff is quantitative. - Highest-risk drop-off points: - Risk 1 -- mitigation: Around <<0:45>>, viewers may leave if the setup feels too broad; the script quickly grounds the story with named tools and a recognizable messy-stack scenario. - Risk 2 -- mitigation: Around <<4:30>>, migration details can feel operationally dense; the “keep, kill, merge, rebuild” framework and the “migrate nostalgia” interruption simplify the section and reset attention. 5. Video Description - First 2 lines: We rebuilt our B2B SaaS marketing automation in 30 days — and the HubSpot Enterprise license wasn’t the real cost. Here’s the migration playbook, the hidden contractor bill, and the automations that paid it back. - Timestamps / chapters: <<0:00>> The hidden cost of marketing automation <<0:30>> Why this migration happened <<1:30>> Segment 1 — The real HubSpot Enterprise cost <<4:05>> Segment 2 — Why we picked Customer.io and weeks 1-2 <<6:55>> Segment 3 — Three automations that paid back the migration <<10:45>> Segment 4 — Post-migration audit results <<13:35>> The key revelation <<14:45>> Book a migration audit - Links block: Book a 30-minute migration audit: [INSERT LINK] Download the migration checklist: [INSERT LINK] Customer.io: [INSERT LINK] Dreamdata: [INSERT LINK] Chili Piper: [INSERT LINK] - Summary: Most B2B SaaS teams look at marketing automation cost as a software line item. But the real cost often sits in the operating layer: contractors, cleanup work, brittle workflows, unclear attribution, and campaign delays. In this video, we break down a 30-day marketing automation migration from HubSpot Marketing Enterprise to Customer.io. You’ll see the actual all-in cost, including the hidden contractor bill, why we chose the alternative stack, how we handled weeks one and two of migration, and the three automations that paid back the project in week three. We also share the post-migration audit results, including open rate improvement, attribution cleanup, and team time saved. - Social media links: Website: [INSERT LINK] LinkedIn: [INSERT LINK] Newsletter: [INSERT LINK] Podcast: [INSERT LINK] Contact: [INSERT LINK] 6. Tags marketing automation, HubSpot Enterprise, Customer.io, B2B SaaS marketing, demand generation, marketing operations, HubSpot migration, Marketo alternative, SaaS demand gen, lifecycle marketing, Salesforce marketing automation, marketing attribution, revenue operations, martech stack, lead routing automation, B2B email automation, marketing automation migration, HubSpot hidden costs 7. Pinned Comment Hot take: most teams don’t need a new marketing automation platform — they need fewer mystery workflows. Are you staying on HubSpot or Marketo this year, or actively looking for an alternative?