Not sure where to start?

A five-day Health Check

Fixed price. One honest report on your org, ranked by cost and risk. Yours to keep whether or not you hire us.

Request a Health Check

Selected work

Quotes from six days to four hours

How a components manufacturer moved tacit pricing rules out of one person’s head and into CPQ.

Read the case study

MARKETING CLOUD

Journeys built on the same data your sales team trusts

One customer record, one consent state, one suppression list. Campaigns stop contradicting the account team.

The most common marketing platform problem is not creative or cadence. It’s that the marketing database and the CRM disagree, so a customer gets a win-back offer the week after they renewed, or an unsubscribe is honoured in one system and not the other.

We implement Marketing Cloud with the CRM as the source of truth for identity and consent. Journeys are triggered by CRM events, suppression is centralised, and preferences are captured once. Then deliverability gets the attention it needs — authentication, warm-up, list hygiene — because none of the strategy matters from a spam folder.

What you get

  • One consent and preference state across CRM and marketing.
  • Journeys triggered by real CRM events, not by list uploads.
  • Suppression handled centrally, including regulatory and reputational exclusions.
  • Deliverability set up properly: SPF, DKIM, DMARC, IP warm-up, engagement-based sending.
  • Attribution that connects a send to an opportunity, not just to a click.
  • Templates that render correctly across the clients your audience actually uses.

Features

Marketing Cloud Engagement setup and business units · Data Extensions and contact model · Journey Builder, Automation Studio, Email Studio · Mobile and SMS where relevant · Consent and preference centre · CRM connector or API-based sync · Deliverability configuration and monitoring · AMPscript / SSJS personalisation · Reporting into CRM campaigns

How we run it

01 Contact and consent model design · 02 Data flow and CRM sync build · 03 Journey design for the top three lifecycles · 04 Template system and preference centre · 05 Deliverability setup and warm-up · 06 Attribution reporting and optimisation

What you receive

Contact and consent model · Data extension schema · Journey specifications · Template system · Preference centre · Deliverability configuration record · Attribution dashboard · Marketing operations runbook

Common questions

Do we need Marketing Cloud, or will Account Engagement (Pardot) do?

Account Engagement suits B2B nurture at moderate volume. Marketing Cloud earns its cost at high volume, multi-channel, or with complex consent. We’ll model both against your actual sends.

How is consent handled across systems?

One authoritative field set in CRM, synced outward, with the preference centre writing back. Never two independent opt-out lists.

Can journeys use service data?

Yes — case events, CSAT and entitlement status all make good triggers, and they’re usually more valuable than another product email.

Who owns deliverability afterwards?

You do, with a monitoring dashboard and a monthly review if you’re on managed services.

Start here

Tell us what your CRM is getting wrong

Thirty minutes with a consultant, not a salesperson. You’ll leave the call with at least one thing you can fix yourself — whether or not you hire us.

Prefer email? hello@zeptglobal.com · Typical reply time: one business day