What is the difference between an engine and a layer?

An engine is a Dynamic Ad flagship running the full six-layer operating system (Dynamic Lead OS or Dynamic Commerce OS). A layer is one discipline of the operating system, sold as a standalone wedge scoped to its own outcome. Engines commit to the make-good; layer wedges commit to layer-specific deliverables.

Can a layer wedge graduate to a full engine?

Yes. The layer-wedge artifact (Gap-Map, signal contract, baseline snapshot) carries forward into the engine engagement. Nothing is rebuilt. The transition is scoped on a follow-on call after the wedge closes.

Why are layers sold standalone at all?

Because many buyers have the budget and team to run five layers in-house but need one specific discipline filled (most commonly Infra or Intelligence). The wedge meets that buyer where they are. If the wedge surfaces a structural gap that a stacked operation would close faster, the Gap-Map names that on cycle close.

Engine vs Layer

A Dynamic Ad engine is the full-stack flagship (Lead OS or Commerce OS) running all six layers; a layer is one discipline of the operating system, sold standalone as a wedge.

Common questions

What is the difference between an engine and a layer?: An engine is a Dynamic Ad flagship running the full six-layer operating system (Dynamic Lead OS or Dynamic Commerce OS). A layer is one discipline of the operating system, sold as a standalone wedge scoped to its own outcome. Engines commit to the make-good; layer wedges commit to layer-specific deliverables.
Can a layer wedge graduate to a full engine?: Yes. The layer-wedge artifact (Gap-Map, signal contract, baseline snapshot) carries forward into the engine engagement. Nothing is rebuilt. The transition is scoped on a follow-on call after the wedge closes.
Why are layers sold standalone at all?: Because many buyers have the budget and team to run five layers in-house but need one specific discipline filled (most commonly Infra or Intelligence). The wedge meets that buyer where they are. If the wedge surfaces a structural gap that a stacked operation would close faster, the Gap-Map names that on cycle close.

The site exposes two ways to engage: the full operating system, or a single layer. The two are not the same product at different prices; they are different products with different scopes and different commitments.

An engine is the stacked operation. It commits to the make-good guarantee on the primary engine metric (cost-per-qualified-acquisition for Lead OS; contribution-margin ROAS for Commerce OS) and ships the full operating record at cycle close. The pricing reflects continuous-operation cadence on six layers.

A layer is the wedge. It is scoped to the layer's own outcome (Infra ships server-side tracking parity; Intelligence ships the read; Strategy ships the testing roadmap; etc.) and closes with a Gap-Map artifact specific to that layer. The make-good guarantee does not run on a single-layer engagement; the wedge is scoped to a specific deliverable, not a measured lift.

Example

An operator submits a predictive audit. The Gap-Map names Infra as the highest-leverage layer to engage first. The operator has a choice: engage Infra as a standalone wedge (4-6 weeks, scoped to server-side tracking parity + signal contract), or stack into the full Lead OS engine (90-day cycle, all six layers continuous, make-good runs on cost-per-qualified-acquisition). Both engagements start with the same Gap-Map; they differ in scope, commitment, and pricing.

Always on · Algorithm-led · Human-approved

Walk this operation against your account.

Thirty focused minutes with one of the founders. We map Engine vs Layer against your stack and tell you which entry point fits your stage.

Book a 30-minute call →Or write us