What switching to Pact looks like.

A 230-person SaaS company. An enterprise CRM, a marketing automation platform for nurture, a standalone consent vendor, and a data-enrichment platform. Four annual contracts. Three integration consultants on retainer. A nineteen-page “consent flow diagram” pinned in the privacy team’s office that no one actually understood end-to-end.

They moved to Pact in six weeks. The consent flow diagram came down. The integration consultants moved on. Their VP of Marketing ops described it like this: `For the first time, when our DPO asks me a question about a specific contact, I open one screen and answer in five seconds. Not five days.`

What changed: the consent state, the suppression list, the campaign membership, the field-level provenance, the audit log — all live in the same database, behind the same API, gated by the same permission model.

A regulated B2B fintech. CCPA, GDPR, CASL, plus three state-specific privacy laws. Their previous annual audit took eight engineering-days of evidence gathering — pulling consent records from three systems, reconciling timestamps, generating proof bundles by hand.

This year, they exported the consent ledger straight from Pact for the date range the auditor asked for. The export included lawful_basis, proof_text, proof_version, source, actor_id, correlation_id, and the full event chain back to the original opt-in. The auditor’s reaction was a quiet `oh` and a forty-minute review instead of a four-day one.

The VP of Sales at a Series-C company opens her dashboard on a Tuesday. Pipeline is down. She wants to know when. She drags the timeline scrubber from `today` backward through the quarter, and the dashboard animates — bar charts shrinking, funnels reshaping, the geo heatmap pulling color from regions as deals fade in and out. She finds the exact week pipeline cratered. She zooms in. The dashboard recomposes around that week. She sees a specific account turn red. She clicks. She has her answer in ninety seconds.

Most CRMs let you change the date range and re-render. Pact replays state — because the analytics layer is event-sourced from the same ledger that powers consent, the system already knows what every dashboard looked like at every moment in history.

A mid-market apparel brand running a marketing automation platform, a separate email platform, and a homegrown consent banner. Their decision to leave was made on a Wednesday. Pact’s import wizard pulled their contacts, suppression lists, sequence definitions, consent records, and custom fields by Friday afternoon. The “delta sync” mode kept both platforms in sync with Pact through the weekend so the marketing team could verify side-by-side. By Monday morning, Pact was the source of truth.

They didn’t lose a single suppression preference. The customer who opted out in 2021 stayed opted out. Every opt-in’s proof_text survived the migration with its original timestamp.

A 1,400-person logistics company. They’d been on one CRM-plus-marketing suite and a constellation of add-ons for nine years. Implementing a new field used to require a meeting with the platform admin team and a JIRA ticket that lived for two weeks.

In Pact, their RevOps lead added a custom field, set up a multi-step validation, attached it to a playbook, and pushed it to all sellers — in twelve minutes, on a video call, while explaining what she was doing. The Object Manager and Field Manager are first-class surfaces, not configuration ghettos buried six clicks deep.

The CFO’s annual savings on the prior CRM stack alone exceeded what they pay Pact for the entire company. The RevOps lead’s words: “It’s not that Pact is cheaper. It’s that Pact is faster, and that compounds.”

An enterprise on an integrated marketing stack — campaign management, CDP, personalization, and analytics across four platforms. Their consent decisions lived in a separate compliance tool; their marketing actions lived in the campaign platform; their analytics lived in a dedicated analytics suite. When their privacy team asked “can you guarantee that no one who revoked consent yesterday received an email today?”, the answer required pulling logs from three systems, reconciling identifiers across two identity graphs, and a six-hour SQL query.

Pact answers that question with a single endpoint: GET /v1/consent/events, filtered to the contact. The full event chain is one query. They’re keeping some downstream infrastructure for external reasons — but Pact is now the consent source of truth, and the integration keeps the existing systems in sync.

A mid-market e-commerce company runs a holiday campaign. The marketing team queues a send to 2.3M contacts at 5 a.m. Eastern. Somewhere in the queue is a 200,000-row segment that was last refreshed six weeks ago. In any other system, those 200K sends would go out, including to people who’d revoked consent in the intervening weeks.

Pact’s frequency-cap and consent-gate run at delivery time, not queue time. Forty-three thousand sends were silently dropped that morning — they’d have triggered CASL violations or frequency-cap complaints in any other system. The marketing team didn’t notice; the campaign reports just showed consent_blocked and frequency_capped outcomes alongside the delivered counts. The compliance team noticed, and quietly bought another year.

A consumer media company was paying mid-six figures for a consent-management vendor to run a CMP banner, a privacy request workflow, and a vendor-tracking matrix. The marketing team paid mid-six figures more for an email platform. The two systems exchanged exactly two CSV files per week.

In Pact, the CMP isn’t a separate product. It’s a thin frontend over the same core/consent ledger that gates marketing sends. The privacy request workflow is built on core/erasure — submit a request, the system enumerates and purges every reference, returns a verifiable receipt.

The previous tool was purpose-built for point solutions. Consolidating it removed the complexity.