Compound Decisions, Not Campaigns
Part 3 of 3: Why decision loops, not better campaigns, are the only compounding advantage left in a world of noise and infinite attention surfaces.
Part 1 showed every tech wave monetizes through advertising - AGI became Advertising Generated Income. Part 2 mapped what happens when all that infrastructure comes online at once: attention inflation, trust collapse, agents multiplying noise with your budget. It ended with Five Truths- a progression from structural noise → trust as scarcity → privacy as moat → attention that compounds into learning → audience portability across every surface.
That last truth- audience portability, the ability to move your audience across consolidating martech and adtech attention surfaces without losing context is where most companies stop. But portability without a learning loop is just a fancier way of resetting to zero on every surface. You move the audience. You don’t move the knowledge.
Part 3 is about what closes that loop.
The Decision Gap
Every customer-facing org already has a decision system. It’s invisible. It’s the Slack thread, the spreadsheet, the weekly meeting where someone says “I think we should try this” from a dashboard nobody trusts. It’s tribal knowledge in one person’s head that vanishes when they leave.
This is where the AGI-vs-AGI conflict from Parts 1 and 2 gets structural. Advertising Generated Income pushes more automated spend into auctions. Agents accelerate execution. But without decision memory, agents just accelerate the loss function- more spend, more noise, more guesswork, faster.
These decisions are implicit - reasoning isn’t captured. Non-compounding — the next decision doesn’t learn from the last. And non-portable insight stays locked where it was made. Forrester’s 2025 State of AI survey found over 70% of enterprises have AI in production, but few measure financial impact. The bottleneck isn’t intelligence or data or tools now, every company has both in abundance now. It’s infrastructure for decisions that learn from themselves. Without it, you’re automating guesses faster, at scale, with your massive marketing budget.
Why Your Marketing Cloud Can’t Fix This (But Your Data Cloud Can)
Every major marketing cloud - Salesforce, Adobe, HubSpot, Braze - claims to be your orchestration layer. So does every major ad platform - Google, Meta, Linkedin, The Trade Desk. What they both mean is campaign orchestration: multi-step sequences within their tool, fancy content, rich graphics. Channel-first thinking with a fancier workflow builder. When your decision logic lives inside Braze, it doesn’t know what Salesforce learned. When your ad platform optimizes spend, it doesn’t know what your CRM knows about that customer. The martech and adtech stacks are converging but the decision-making is still siloed. Five tools, ten platforms, all making independent guesses about the same customer no shared memory, no compounding.
A real decision system sits above all tools. It asks “what’s the right decision for this audience, right now?” then routes to whatever channel or agent executes it. Decision-first, not channel-first.
Here’s the uncomfortable part most vendors won’t say: you already have most of what you need. If you’re on Snowflake, BigQuery, or Databricks - your customer data, behavioral signals, and transaction history are already there. With enterprise AI access, you have intelligence on tap. What’s missing is the decision loop connecting them. And every month without it, you’re leaving compounding advantage on the table.
So why do vendors keep selling you more? Most “AI-powered” marketing tools supplement your decisions with borrowed intelligence: their models, their training data, their generic abstractions applied across thousands of customers. That’s useful as a signal but they don’t remember your outcomes across tools. Your competitive advantage is your unique first-party data, your specific customer relationships, your institutional memory. Second or Third-party dynamic signal or intelligence can inform a decision. But only your own decision loops can compound it.
This doesn’t mean rip and replace. Keep your Braze, Salesforce, Meta, LinkedIn Ads or any campaign/ content tools. But stop treating them as your activation/ operating system. Your OS should be your own data, your own intelligence, and your own decision loops running on your data cloud, composable, in your control & bespoke where every martech and adtech tool is a spoke, not the hub. When your decision layer and data cloud are the hub, every martech and adtech tool becomes a spoke you can plug in, experiment with, and retire without structurally changing your data layer or losing institutional memory. Try a new personalization engine for 90 days. If it doesn’t perform, swap it out. Your decision traces, your audience context, your learning loops none of that moves. The spoke changes. The hub compounds.
Scott Brinker has been tracking this shift. His State of Martech 2025 identifies cloud warehouses becoming the gravitational center of marketing infrastructure - 56.2% of organizations already integrate cloud data cloud or warehouses with their martech & adtech stacks with composable architectures replacing monolithic stacks & apps. 15,384 martech tools and counting. That’s not bloat that’s an ecosystem (well it can be bloat if the hub & spoke architecture is missing). And ecosystem-led growth demands an architecture that welcomes experimentation instead of punishing it.
Brinker has since taken this further. He reframed the martech stack around “systems of context and systems of truth” and, more recently, built an entire thesis around context-as-a-service (CaaS) - where domain-specific platforms become enterprise aggregators, providing the contextual substrate that makes every app, agent, and automation in the stack coherent and trustworthy. It’s consistent with his long-standing thesis: ecosystem-led growth with open architecture beats monolithic consolidation. Harness the energy of thousands of tools rather than trying to replace them.
I agree with the framing. But context without a decision loop is still passive, it tells you what’s happening, not what to do next. The decision layer is what makes context operational. It’s what turns “we know this customer is price-sensitive and high-intent” into “the system chose the 10% offer over the 15% because 847 prior traces proved the margin tradeoff.” Context is the substrate. Decisions are the compounding layer on top.
The Decision Trace
The core unit of this architecture is what I call a decision trace - a structured record of every decision, with enough context to reconstruct the reasoning and learn from the outcome. Ten elements:
Credit: @ iCustomer
Without all ten, you have a log. With all ten, you have a learning system. The elements almost nobody captures, buyer intent as distinct from seller intent, the arbitration logic between them, alternatives considered, and feedback are what separate a decision trace from a campaign report. A campaign report says “23% open rate.” A decision trace says “customer signaled expansion interest, business prioritized upsell over renewal play, arbitrated to the ROI case study offer at mid-tier discount — and for this segment, that combination converts 2.3x better. System auto-executes next time.”
This enables three things: compound learning across campaigns (every decision feeds the next), audience portability with memory (every surface inherits what the last one learned), and agents that get smarter (access to traces turns a stateless executor into a system that knows what worked last time, for this person, in this context).
The Shared Learning Loop
Five layers make this operational:
Observation - continuous signal detection from data cloud, website, product, CRM.
Contextual reasoning - this is where Brinker’s context becomes operational. Interpreting signals not through a generic enterprise AI lens, but through the specific context of this customer, this relationship, this journey moment. Domain-specific to your customer experience, not a horizontal platform optimizing supply chain and marketing with the same abstraction. The customer is the unit. The experience is the outcome. The AI is just infrastructure underneath.
Execution within autonomy - routine decisions auto-execute within guardrails; high-stakes decisions escalate.
Human steering - your homepage isn’t a dashboard, it’s a decision queue.
The trace layer - every decision writes a trace: buyer intent, seller intent, evidence, guardrails, alternatives, arbitration, execution, authority, measurement, feedback. Lives on your data cloud - your Snowflake, BigQuery, Databricks. Not another SaaS database. Your data, your traces, your compounding institutional memory.
What the Category Proved (and What’s Missing)
In January 2026, Gartner published its inaugural Magic Quadrant for Decision Intelligence Platforms - formally recognizing the category. Leaders: FICO, SAS, Aera Technology. Pega, a Challenger. All enterprise platforms - rules engines and scoring models designed for banking compliance, insurance underwriting, and supply chain planning. Gartner predicts that by 2030, explicitly modeled business decisions will be five times more trusted and 80% faster than ungoverned ones.
The challenge: these tools weren’t built for the fragmented, multi-surface, composable reality of modern marketing & CX. What’s missing is domain-specific decision intelligence, data-cloud-native, composable, built for your existing stack and autonomous agents. Not 18 months of implementation. Not a Watson-style catch-all. A context layer for audiences whose signals, preferences, taste and intent are constantly evolving - one that plugs into your data infrastructure you already own and brings dynamic, signals outside-in context into your decision loops.
In Practice
B2B: System detects intent surge - product page visits up 3x, pricing page email engagement. Reasoning layer pulls decision traces: last quarter, outreach within 24 hours of this pattern converted at 2.1x baseline, email-first beat LinkedIn by 40% for this profile. Rejected: LinkedIn-first outreach 40% worse for this segment. Executes within guardrails. Trace written. System smarter.
D2C: Second cart abandonment, both winback emails opened. Buyer intent: high purchase interest, price-sensitive. Seller intent: convert without eroding margin. Trace layer holds 847 prior decisions for this behavioral pattern and the arbitration is clear: a 10% discount via SMS within 4 hours converts at 3.2x, while 15% only lifts conversion another 0.3x at significantly worse margin. Agent fires the 10% SMS. No A/B test needed. Conversion. Trace written. System updated.
Multiply by a thousand decisions a week. Your competitor without decision loops resets to zero every campaign.
The Only Durable Advantage
Part 1: intelligence is commoditizing. Part 2: attention is inflating. Part 3: the compounding advantage isn’t AI or data - it’s decisions that learn.
That’s what we’re building at iCustomer - a Decision OS on your data cloud that turns every interaction into a compounding decision trace. Data-cloud-native. Composable. Domain-specific for marketing & CX. Not another CDP. The decision intelligence layer hyper focussed on customer/audience decisioning that was always missing.
But the architecture matters more than the vendor. Your data. Your intelligence. Your decision loops. Your infrastructure. The execution tools are spokes. The decision layer is the hub.
The noise won’t stop. The attention auction won’t get cheaper. The trust bar won’t drop. The only question is whether your system learns or resets.
Start here: pick one decision your team makes every week a send, a suppress, an upsell. Ask whether the reasoning is captured anywhere. If it isn’t, that’s your decision gap.
What’s the decision you’re trying to automate, and where does it break: context, constraints, or measurement? I’d love to hear - reply or reach out.
If this series landed, share it with someone still running campaigns from static segments in this AGI first noisy world.
Author’s note: An LLM helped with research, citations, and light proofreading without changing content. All ideas, arguments, voice, and em dashes are mine. :)




Great read, thanks ! I thought to ask how you see the Decisioning layer being operationalised in practice. You touched on AI as the intelligence layer - do you see this as a set of agents orchestrating different intelligence activities, or more of a specialised Decisioning/Recommendation engine? And if the latter, do you think that typically ends up being a SaaS component or something built in-house?
Great article. You probably want to add regulations and compliance somewhere in the table. Maybe in the Guardrails section?