Case Study:
When the Platform Is Fine but the Operations Are Not: Rebuilding Email Marketing in HubSpot for the Michigan Chamber of Commerce
Client: Michigan Chamber of Commerce
Engagement: May 2025 – January 2026
HubSpot Hubs: Marketing Hub Enterprise – Content Hub Pro – Data Hub Enterprise
Type of Engagement: HubSpot Fractional Admin Support
The Short Version
Sometimes a HubSpot portal isn’t broken. The operations around it are.
That was the situation with the Michigan Chamber of Commerce — a statewide membership organization that had been running email marketing in HubSpot for some time. The platform worked. But the governance didn’t. Workflows were unstable. Subscription management was unclear. Reporting existed but no one trusted it. And the internal team was making decisions based on assumptions rather than documented process.
By the time the engagement ended, they had a functioning email marketing framework, stabilized workflow architecture, cleaner contact management, dashboards leadership could actually use, and — maybe most importantly — a team that understood why HubSpot was behaving the way it was.
That last part took as much work as everything else combined.
The Challenge
Fragmented email operations with no clear owner
The organization had accumulated campaigns, workflows, and email sends without a coherent structure underneath them. No naming conventions. No clear enrollment logic. No documented ownership. The result: confusion about who should receive what, when, and why — and no reliable way to audit it after the fact.
Workflow instability that nobody could explain
Several workflows were producing unexpected behavior. Contacts were re-entering sequences they’d already completed. Suppression logic was inconsistent across different sends. Branching paths overlapped in ways that created downstream problems. When things went wrong, there was no documentation to troubleshoot from.
Subscription and compliance fog
The organization wasn’t sure how their subscription types mapped to actual send behavior. What happened when a contact unsubscribed? How should legacy subscription categories be handled? What was the difference between an operational email and a marketing one inside HubSpot? These weren’t edge-case questions — they were creating real compliance uncertainty.
Reporting that existed but wasn’t usable
Leadership wanted visibility into campaign performance and engagement trends. Reports had been built. But they were either incomplete, structured in ways that made interpretation difficult, or producing numbers the team didn’t know how to read. The dashboards existed. The confidence didn’t.
A team making decisions from assumptions
Across every area of the project, the same pattern appeared: internal staff had developed mental models of how HubSpot worked that didn’t match how HubSpot actually worked. That gap was producing everything from bad workflow decisions to inflated contact counts to deliverability risk.
What I Did
Built a structured email marketing framework from scratch
The first priority was creating a repeatable operational structure — not just fixing individual problems, but establishing the system that would prevent them from recurring.
That meant:
- Naming conventions for campaigns, workflows, and email assets
- Clear categorization of campaign types (newsletter, nurture, workflow-triggered, one-off)
- Enrollment governance that documented who enters what, and when
- Asset organization that made future audits possible in under ten minutes
Rebuilt workflow architecture for predictability
Existing workflows were audited against their original intent. Where enrollment logic was unclear, it was rewritten with explicit criteria and documented suppression rules. Where branching paths overlapped, they were separated. Where resend logic was creating loops, the timing and re-enrollment conditions were rebuilt.
The goal wasn’t elegance — it was predictability. A workflow that behaves consistently and can be explained in plain language is more valuable than a clever one nobody can troubleshoot.
Simplified subscription management without losing compliance visibility
Rather than adding more subscription types to handle the confusion, the engagement moved in the opposite direction: consolidating where possible, clarifying the purpose of what remained, and documenting what happens at each stage of the opt-in/unsubscribe lifecycle.
The team walked away understanding the difference between operational and marketing communications in HubSpot — and why that distinction matters for both deliverability and legal compliance.
Created re-engagement infrastructure for stale contacts
Continuing to email cold audiences indefinitely is a deliverability problem, not just a list hygiene problem. This engagement built a scalable re-engagement framework:
- Defined segments for low-engagement and inactive contacts
- Built suppression logic for contacts who hadn’t engaged in defined windows
- Designed re-engagement sequences with clear exit criteria
- Established rules for when a contact should stop receiving promotional emails altogether
This reduced unnecessary send volume, protected sender reputation, and gave the organization a long-term audience health strategy rather than a one-time cleanup.
Built dashboards leadership could actually use
Four reporting areas were addressed:
- Cumulative email engagement — baseline performance across all sends
- 2-day and 7-day engagement windows — shorter-term activity monitoring
- Workflow performance — automation activity and completion rates
- Campaign activity summaries — send-level visibility by initiative
A substantial part of this work was translation: taking what HubSpot reports and explaining what it means, where the platform’s native reporting has limits, and how to interpret numbers that look confusing but aren’t wrong.
Invested heavily in team education
This project had an unusual amount of overlap between technical configuration and internal alignment work. The same questions surfaced repeatedly across different sessions — around workflow behavior, marketing contact definitions, deliverability implications, reporting interpretation.
That pattern wasn’t a sign of a slow team. It was a sign that HubSpot’s logic isn’t always intuitive, especially for organizations that grew into the platform rather than being onboarded intentionally. Converting technical HubSpot concepts into operationally understandable processes became as central to the engagement as the build work itself.
The Callout Worth Noting
One workflow setting changed by a developer. A large portion of the contact database reclassified overnight. No one knew it had happened.
Contact governance isn’t a one-time setup task. It requires documented logic, change management, and someone who understands the downstream effects of what looks like a small configuration decision. That’s the difference between a HubSpot portal that works in the short term and one that scales reliably.
The Outcomes
By the end of the engagement, the organization had:
More predictable email operations. A structured framework replaced the patchwork of one-off decisions. Campaigns had a consistent home, workflows had documented logic, and the team knew where to look when something behaved unexpectedly.
Stabilized automation. Workflow behavior became reliable enough that troubleshooting shifted from “why is this happening” to “let me check the documented logic.” That’s a different kind of problem — a much better one.
Cleaner contact management. Marketing contact counts reflected actual audience intent rather than accumulated noise. Re-engagement infrastructure meant the list would continue improving over time rather than degrading.
Dashboards leadership used regularly. Not just built — adopted. The difference came down to explanation: once the team understood what the numbers represented and where HubSpot’s reporting limitations lived, the data became trustworthy enough to act on.
A team that understood the platform better. This is the outcome that’s hardest to quantify and easiest to underestimate. Organizations that understand why their HubSpot behaves the way it does make better decisions, create fewer problems, and don’t require emergency intervention every time something changes.
What Made This Engagement Different
Most HubSpot projects focus on building. This one focused equally on explaining.
That’s not unusual in my experience — especially for organizations that have grown into HubSpot without formal onboarding or documentation. The platform has deep capability, but capability without context creates problems over time. The gaps show up in deliverability, in reporting trust, in workflows that nobody will touch because nobody knows what they do.
The technical work here was meaningful. But the translation work — converting HubSpot logic into plain operational language the team could actually act on — was what made the technical work stick.
Email Marketing Framework
Naming conventions, campaign categorization, asset organization, and enrollment governance built from the ground up
Workflow Architecture
Full workflow audit, enrollment logic rebuild, suppression rule standardization, loop and overlap resolution
Subscription Management
Subscription type consolidation, opt-in/unsubscribe lifecycle documentation, operational vs. marketing email compliance clarity
Marketing Contact Governance
Inactive contact segmentation, suppression logic, re-engagement infrastructure, marketing contact cost reduction
Reporting & Dashboards
Cumulative engagement reporting, 2-day and 7-day activity windows, workflow performance monitoring, campaign summaries
Team Enablement
HubSpot behavior translated into operational process; internal documentation, meeting recaps, and decision-making frameworks delivered throughout