For operators with multi-brand, multi-market, or multi-entity complexity — where the $1 Deal funnel and the three Activation Moves stop being the right answer and a custom-built engagement starts. Scoped, staffed, and led personally by Ethan Mercer. Every engagement built from your actual infrastructure — not a template.
Our team has built data and marketing systems for some of the largest brands in America.
DVC's main practice is built around Activation — identification, retargeting, behavioral triggers, lookalike acquisition — productized as the $1 Deal trial and the three Activation Moves. That product serves operators investing up to roughly $40K/month with DVC.
Above that line, the work changes. The questions stop being "which Moves fit?" and start being "how do we build a revenue architecture that serves a multi-brand portfolio, a regulated compliance environment, or attribution that has to answer to a CFO and a board?" Enterprise Engagements are how DVC answers those questions.
Every engagement is custom-scoped — the architecture is defined during scoping, not before. The scope library further down on this page is illustrative, not exhaustive. What ends up in your engagement is whatever your operation actually requires.
A $40M operator with four brands across three states and a regulated compliance environment is an Enterprise engagement. A $200M single-brand operator may be a Total-tier Activation client. The scoping conversation is where the right answer gets found.
Enterprise Engagements typically run 3–9 months from first conversation to signed engagement. That's not friction — that's the work. Scoping the infrastructure an operator actually needs cannot be done in a discovery call.
One to three conversations with Ethan directly. Business architecture, data environment, organizational structure, compliance requirements, strategic objectives. No pitch deck — a working conversation about what your operation is and what it needs to become.
Custom-scoped engagement proposal reflecting what the build actually requires. Staffing plan, phased delivery timeline, investment structure, success metrics defined against your business — not a template output. Proposals are reviewed and refined with your team before signing.
Phased engagement structure. Senior operators staffed specifically to the engagement — not distributed across a book of accounts. Kickoff establishes governance cadence, access protocols, and the first 90-day build milestones. Compliance-sensitive engagements include engagement-specific data handling, access control, and audit requirements built in from kickoff.
Custom data infrastructure, attribution systems, and media architecture stood up. Timeline varies by scope — most engagements have a measurable operational deliverable inside 90 days, with the full architecture built out across the first six months. Every milestone is reviewed against the success metrics set in the proposal.
Executive cadence with Ethan and the senior team. Monthly or quarterly strategic reviews depending on engagement structure. Quarterly scope reviews to confirm the architecture is delivering against the success metrics — and to evolve the scope as the business evolves. Typical engagement runs 12–24 months minimum, with multi-year extensions standard when the architecture becomes core infrastructure.
Agencies that promise enterprise revenue architecture on a two-week sales cycle are selling a template with a custom invoice. Architecture decisions affect data infrastructure, attribution, compliance posture, and organizational accountability — for years. The 3–9 month scoping cycle is the difference between a build that serves your operation and a build that serves the vendor's pipeline.
Every engagement is scoped individually. The four scope areas below are illustrative, not exhaustive — what's in your engagement is determined by what your operation actually needs.
Enterprise customer data platform, identity resolution across brands and markets, revenue intelligence infrastructure. Built to integrate with your existing systems — ERP, CRM, POS, loyalty, e-commerce — not replace them with a vendor lock-in.
When it matters: your current reporting can't answer "what's the total value of this customer across our brands," or compliance requires provable data lineage, or attribution breaks at the entity boundary.
Media, measurement, and strategy coordinated across regions, brands, or business units. Cross-entity reporting and consolidated attribution that rolls up to the enterprise level while preserving per-entity performance visibility.
When it matters: you operate multiple brands or markets that share customers, share infrastructure, or share budget — and today each one runs like its own small company with its own tools.
Integrated media across all major platforms, with custom attribution tying spend to revenue at the entity, brand, and market level. Built on behavioral intelligence refined across $1B+ in cumulative managed spend.
When it matters: your ad spend is large enough that "platform attribution" stops being credible, and you need attribution built to answer to a CFO — not a dashboard.
Architecture built from the ground up for operators with regulatory, legal, and audit requirements. HIPAA, SOC2, GDPR, and engagement-specific compliance frameworks handled natively — not retrofitted.
When it matters: healthcare, financial services, PE-owned assets with portfolio compliance requirements, publicly traded companies, or any operator where marketing data touches regulated information.
Enterprise Engagements are never handed to an account manager. They're scoped, staffed, and led personally by Ethan Mercer — VP of Sales & Growth at DVC and the same operator who'd walk into a Fortune 50 CMO's office with a scoping brief.
The first conversation is not a pitch. It's a working session — your business architecture, your data environment, your real constraints, the outcomes you're trying to engineer. If Enterprise is the right engagement, Ethan will scope it. If it isn't, he'll tell you what is — inside DVC or outside.
No marketing-speak. The answers an operator weighing a multi-year architecture decision actually wants.
Activation Total is a productized tier — Grow Base plus all three Activation Moves at full intensity plus DVC as agency-of-record for paid media. Enterprise is a custom-scoped engagement — the architecture is defined during scoping, not before. The answer is usually about data complexity, not revenue size. A $200M single-brand operator is usually Total. A $40M operator with four brands across regulated environments is usually Enterprise.
No. Every engagement is scoped individually, and pricing is built from the architecture being delivered — not from a tier table. Engagement investment is established in the architecture proposal after the scoping phase, so the number reflects what you're actually getting, not an anchored starting point that gets negotiated down. What we will tell you in the first conversation: whether the engagement is likely to land in Enterprise territory at all.
Ethan Mercer, personally. Scoping is led by Ethan. The architecture proposal is written by Ethan. Kickoff is run by Ethan. Ongoing engagement reviews happen with Ethan in the room. There is no handoff to an account manager at any point in the engagement. That's the structural difference between Enterprise and a productized program.
Scoping: typically 4–8 weeks from first conversation to signed engagement, longer for compliance-heavy or multi-entity builds. Build phase: first measurable operational deliverable by Day 90, full architecture built out across the first six months. Ongoing engagement: 12–24 months minimum, with multi-year extensions standard when the architecture becomes core infrastructure.
Yes — mutual NDA is standard and available before the first scoping conversation for any engagement where sensitive business information, acquisition activity, or competitive positioning is in play. We can work from your paper or ours.
No. Most Enterprise Engagements begin with an existing vendor stack — some pieces of which are performing, some of which are not. Scoping identifies what stays, what gets replaced, and what gets built from scratch. In practice, Enterprise often consolidates 4–8 existing vendors into a single integrated architecture. Sometimes it augments an in-house team instead. The scoping conversation decides.
Yes. HIPAA, SOC2, GDPR, and engagement-specific compliance frameworks are handled natively within the architecture — not retrofitted after. We've built for healthcare, financial services, publicly traded operators, and PE-owned assets with portfolio-level compliance requirements. Compliance framework is a scoping input, not an add-on.
Yes — explicitly. Private equity is one of the primary Enterprise client profiles. Portfolio-wide engagements (one architecture deployed across multiple holdings) and individual portfolio company engagements (architecture scoped to a single asset inside a portfolio) are both supported. We also work directly with PE operating partners on pre-acquisition marketing and data diligence.
Ethan walks through your business architecture, your data environment, and the outcomes you're trying to engineer. If Enterprise is the right engagement, he'll scope it. If it isn't, he'll tell you what is — inside DVC or outside.