Est. reading time: 7 minutes

This case study covers the email infrastructure layer of the Soleil Floors engagement. The full system story, including paid media, conversion testing, and content infrastructure, is here.

The Situation

Soleil Floors came into the engagement with 20 years of customer relationships and no way to email any of them.

Customer history lived in four tools. Pipedrive held the deals. QuickBooks held the transactions. Calendly held the appointments. Typeform held the inquiries. None of them talked to each other, and none of them connected to an email platform.

A Mailchimp account existed, but it was dormant. It had never sent an email, carried no reputation with any mailbox provider, and had none of the structural safeguards that protect a domain once sending starts.

That dormant account was the highest-stakes asset in the engagement, because the decisions made before it sent anything would shape how email performed for Soleil for years.

Key Outcomes

• Cold Mailchimp account authenticated, warmed, and monitored without damaging sender reputation
• Custom Pipedrive-to-Mailchimp sync built in Zapier, including future-use fields the sales process had not activated yet
• Direct Calendly and Typeform integrations firing welcome emails at peak intent instead of waiting on CRM passthrough
• Subscriber eligibility logic separating new leads, past clients, and contacts with mixed deal histories before a single legacy import
• A Mailchimp Preferences Center giving subscribers control over frequency and content type
• A lifecycle program spanning welcome, post-consultation, re-engagement, and project content, still operating after handoff

The Primary Challenge

The tempting move with a 20-year customer base and a fresh email platform is to import everything and start sending.

That move burns domains. Mailbox providers read sudden volume from an account with no history as spam behavior, and the damage lands fast. A domain hurt in its first month of sending can take months to recover, and the business feels it as silence. Campaigns go out, land in spam folders or nowhere at all, and no dashboard makes the cause obvious.

The four disconnected data sources raised the stakes further. An import without careful field mapping and validated update logic produces duplicate subscribers, mismatched records, and a list the team can never fully trust again.

Before email could work as a channel, it had to exist as infrastructure.

The Goal

Configure Mailchimp for long-term deliverability, build a CRM-to-email sync the team could trust without auditing it, define exactly who gets subscribed and when, and hand Soleil a foundation that would still be standing years later.

Our Approach

We treated the build as system design and sequenced it accordingly.

Authentication and account-level safeguards came before a single contact was imported. Field mapping came before sync activation. Small-batch testing came before scale. Contact imports were intentionally delayed until sync behavior had been validated on real data.

Execution Highlights

Deliverability Before the First Send

We completed domain verification and authentication before any sending occurred, configured conservative sending parameters from day one, and put monitoring protocols in place ahead of activation. The domain earned its reputation gradually, on the schedule mailbox providers reward.

A CRM Sync Mapped Past the Current Sales Process

We built the Pipedrive-to-Mailchimp sync as a custom Zapier integration because the native connector could not carry the full picture. Lead source, lifecycle stage, consultation status, and customer history all needed to move between systems in real time.

Every relevant Pipedrive field was mapped into Mailchimp custom fields with consistent labeling, including fields the sales process had not activated yet. This ensured the system would not fail quietly as operations evolved. A sync that only covers today’s fields corrupts silently the first time the sales process changes, and nobody notices until the data is already wrong.

Update logic was validated through controlled small-batch imports before any scale was introduced.

Subscriber Logic Written Before the List Existed

Most accounts define who belongs on a list after the list is already a mess. We defined it first.

Eligibility criteria were set for new leads, past clients, and contacts with mixed deal histories. Subscriber cost implications were weighed before any legacy contacts were imported, and the logic was built to prevent uncontrolled list growth. Every contact that entered Mailchimp entered for a reason the system could name.

Welcome Triggers Routed Around the CRM

The welcome email is the most time-sensitive send in any lifecycle program, and CRM passthrough introduces delay. A welcome email that arrives hours after someone books a consultation meets a colder prospect than the one who just hit submit.

We identified the Pipedrive sync delay early and wired Calendly and Typeform directly into Mailchimp instead. The welcome sequence fires the moment someone books or inquires, at peak intent, while Pipedrive completes its own sync in parallel. The CRM stays the system of record without sitting in the delivery path.

A Preferences Center Instead of a Binary Unsubscribe

We implemented a Mailchimp Preferences Center giving subscribers control over how often they hear from Soleil and what kind of content they receive. Subscribers who would otherwise unsubscribe entirely get a middle path, which protects list health over years rather than months.

A missing preference center is one of the first structural gaps we flag when auditing Mailchimp accounts, including in the audit Intuit selected as its internal standard. Soleil’s was in place before the first campaign went out.

The Lifecycle Program the Foundation Was Built to Carry

With the infrastructure holding, the program itself came online. Welcome emails set expectations for the consultation experience. Founder-voice messaging built trust outside the ads. Post-consultation follow-up drove re-engagement, and project content like the 360 Nueces Condo renovation turned completed installations into emails worth opening.

Re-engagement runs with sunset logic. Inactive subscribers get a controlled window and a clear path back, and the ones who stay silent are removed before they can drag deliverability down. The list stays clean as it grows, which is the mechanism most local business email programs never build and the reason most of them decay.

Results

This phase was scoped to prevent instability rather than produce a revenue spike, and the proof it worked is what never happened. The domain never took damage. The sync never corrupted. Nothing has needed to be rebuilt.

What that groundwork enabled is the rest of the story. When paid media activated later in the engagement, every lead it produced landed in a nurture system that was already running. CRM data syncs predictably in real time, subscriber eligibility stays controlled as the list grows, and the lifecycle program has kept operating after handoff, on a platform a small flooring team runs themselves.

The infrastructure did what infrastructure is supposed to do. It held, and then it disappeared into the operation.

Constraints We Navigated

The build happened under real limitations.

• No sending history and no warmed reputation, which limited how aggressively activation could proceed
• Four disconnected data sources requiring careful field mapping to prevent sync errors and duplicate subscribers
• A small team inheriting the system, which meant every workflow had to be operable without an agency on retainer

Sender health stayed protected the entire way through because those constraints were respected instead of worked around.

Why This Worked

Sender reputation compounds the same way Soleil’s referrals did. Slowly, through consistent behavior, with no shortcut that survives contact with a mailbox provider. A business that spent 20 years earning trust in person needed an email program built the same way, and it got one.

Strategic Takeaway

Email is the only channel where the first month can mortgage everything that follows. A domain earns its reputation send by send, and an account that skips the foundation pays for the shortcut in silence, with campaigns that technically deliver and practically vanish.

For businesses sitting on years of customer data and a dormant email platform, the order of operations is the strategy. Authenticate, map, test, then send. The campaigns can always be fixed later. The foundation cannot.