TL;DR

At Veyl Ventures, the growth problem was not budget. The budget was flat. The growth problem was decision lag at six-figure daily spend, where every hour of latency cost real money. We compressed decision cycles from days to hours, built incrementality testing into the daily operating cadence, and let the honest numbers drive reallocation. The result was approximately 17% month-over-month revenue growth at nine-figure scale on a flat media budget.

  • Decision velocity is the lever at scale, not spend.
  • Incrementality testing is infrastructure, not a one-off study.
  • The daily dashboard either drives the meeting or the meeting wastes the day.
  • Platform-reported metrics are a starting point, not a verdict.
  • Named owners on every channel beat committee budget calls.

In this article

The decision velocity problem at nine-figure scale

At a nine-figure DTC supplement subscription portfolio spending six figures per day across Meta, Google, YouTube, and native, the binding constraint on growth is not creative quality and it is not budget. Both of those exist. The binding constraint is the time between a signal landing in a dashboard and a decision being made on that signal.

Most growth teams I have worked with at this scale run on a cadence where the signal arrives Monday, gets discussed Tuesday, gets debated Wednesday, gets approved Thursday, and gets executed Friday. By the time the decision lands, the signal has moved. At six-figure daily spend, that lag is the most expensive line item nobody puts on a P&L.

The Veyl problem was not abnormal. It was the standard nine-figure DTC problem: too many channels, too many platforms, too many internal reports, and too many opinions in the room. The mandate I took on was straightforward: grow revenue without growing the media budget. The only way to do that is to make better decisions faster.

At six-figure daily spend, decision lag is the most expensive line item nobody puts on a P&L.

The operating cadence that compressed decision lag

The first lever was operating cadence. The team had inherited a weekly business review structure where most channel decisions waited for the Wednesday meeting. That is a sensible cadence at $5M annual spend. It is malpractice at six-figure daily spend.

We rebuilt the cadence in three layers.

Daily channel review (30 minutes, same time, same dashboard)

Each morning, the team met against a single dashboard for thirty minutes. The dashboard was the source of truth. The agenda was fixed: what did yesterday tell us, what are we reallocating today, what is the test plan for the next forty-eight hours. No slideware. No retroactive screenshots. No "let me pull that up."

The thirty minutes ended on time. Decisions made in the meeting were executed inside the same day. Decisions that required additional analysis got a named owner and a same-week deadline, not a "let's revisit next week."

Weekly portfolio review (60 minutes, owner-led)

One hour a week, the channel owners walked through their P&L line items against the portfolio target. Each owner had a number. Each owner owned the trajectory of that number. The conversation was about decisions not yet made, not about decisions already explained.

This is the meeting most companies turn into a status update. Status updates are activity, not decisions. We banned them. If a slide did not propose a decision, the slide did not get presented.

Monthly incrementality review (90 minutes, methodology-driven)

Once a month, the room got bigger. Finance, analytics, and growth sat together against the incrementality reads from the prior month. The conversation was: which channels are actually causing revenue, which are coasting on attribution credit, and what does the next thirty days of budget look like in light of that.

This is the meeting that prevented the program from running on flattering numbers. Without it, the daily dashboard would have made the right tactical calls against the wrong strategic frame. With it, the tactical and the strategic stayed aligned.

What incrementality testing infrastructure actually means

Incrementality testing is one of those phrases that gets used loosely. At Veyl, it was infrastructure. Three components made it real.

1. A continuous test calendar, not one-off studies

Incrementality is not a project you finish. It is a calendar you run forever. We had a rolling schedule of geo holdouts, audience holdouts, and platform-on/platform-off windows so that at any given week, three or four causal reads were in flight or arriving. The team treated the calendar like an inventory system: never empty, never overbooked.

The discipline here is the part most teams skip. A one-off incrementality study tells you what was true for two weeks last quarter. A continuous program tells you what is true this week. Budgets at this scale need the second answer, not the first.

2. A pipeline that turned raw signal into decision-grade reads

Raw incrementality data is messy. The pipeline took the test design, the platform output, and the internal revenue data and produced a single page per test: hypothesis, baseline, treatment, lift, confidence, and decision recommendation. The page was the artifact. Without the page, the test did not exist.

This is the same brief discipline I used at NASM. Different domain, same principle: the artifact is the system. Without standardized artifacts, every test becomes a custom argument and the team spends its hours debating methodology instead of acting on results.

3. A written agreement on which numbers drive budget

The single most useful artifact was a one-page document, signed off by growth and finance, that named which number drove which decision. Platform-reported ROAS drove no budget decisions. Incrementality-adjusted contribution drove most channel-level decisions. Aggregate marketing efficiency ratio drove portfolio-level decisions. Each owner knew which number was theirs.

The agreement ended the standing argument about whose numbers were right. The argument that replaced it was "what should we do," which is the right argument to have on a Tuesday morning at six-figure daily spend.

Incrementality is not a study. It is a calendar, a pipeline, and a written agreement on which numbers drive budget.

How a flat budget plus better decisions produced 17% MoM

The growth math at flat budget is not complicated, but it is unforgiving. If spend is flat, revenue can only move through one of three levers: better creative, better targeting, or better reallocation. The team was already strong on creative. Targeting at platform level was tightly tuned. The unlocked lever was reallocation.

Reallocation at six-figure daily spend is a velocity game. The opportunity is the gap between what the data says today and what the spend pattern looks like today. The faster you close that gap, the more revenue you compound, because every percentage point of misallocation compounds over months.

Three reallocation patterns produced most of the lift.

1. Daily reallocation against incrementality-adjusted contribution

Each morning, the team looked at incrementality-adjusted contribution by channel and shifted budget toward the channels actually carrying weight. The shifts were small day-to-day, large in aggregate over a month. Compounding daily decisions beats heroic monthly ones.

2. Aggressive test budget allocation to underexplored audiences

A fixed percentage of the daily budget was reserved for tests, no exceptions. The percentage was small enough not to threaten the floor and large enough to surface new winning audiences faster than the platform algorithms would surface them on their own. The portfolio of tests acted like an exploration fund.

3. Killing what was not working faster

Most growth teams hold on to losing tactics longer than they hold on to winning ones. The honest read on what was working told us where to cut. We cut faster and reinvested the freed budget into the channels passing the incrementality read. The result was higher portfolio efficiency without higher portfolio spend.

Add those three patterns together, run them daily, hold the operating cadence sacred, and the math gets to ~17% month-over-month at flat budget. Nothing about that number is mysterious in hindsight. The discipline to produce it day after day is the work.

What scales and what does not from this approach

Two years on, I have a clearer view of what about the Veyl playbook compounds at other businesses and what is specific to that situation.

What compounds across businesses

What is specific to nine-figure scale

The principles are portable. The cost structure is not. Smaller brands should run a smaller version of this. Bigger brands should run a more disciplined version of it. The mistake is assuming the principles do not apply because the scale is different.

Applying the playbook at smaller spend levels

If you are running paid media at $1M to $20M annual spend, you do not need the full Veyl infrastructure. You need a stripped-down version that captures the principles without the overhead.

  1. Replace daily review with three-times-a-week review. Same agenda. Same dashboard. Thirty minutes. The cadence is the operating system.
  2. Run incrementality on a quarterly cycle, not a continuous one. One geo holdout per quarter on your largest channel. One platform-on/off study per quarter on a secondary channel. Use the reads to recalibrate the attribution methodology you use day to day.
  3. Write the methodology document. One page. Which number drives which decision. CFO sign-off. Same artifact as the nine-figure version.
  4. Name owners. Even if there is one person owning three channels, each channel has a name next to it. The accountability is the artifact, not the headcount.
  5. Reserve a fixed percentage of spend for tests. Small enough not to hurt. Large enough to produce signal. Non-negotiable.

This is the same logic the AI transformation playbook for consumer brands applies to AI programs: operating cadence and named owners come before tooling. The lever is discipline, not technology.

The bottom line

Veyl produced approximately 17% month-over-month revenue growth on a flat media budget at nine-figure scale by treating decision velocity as the binding constraint. The operating cadence compressed decision lag from days to hours. The incrementality testing infrastructure produced honest numbers that drove reallocation. The written agreement on which numbers drove budget ended the standing methodology debate.

If you are running paid media at any scale and your team is debating attribution every week instead of debating reallocation, the answer is not more tools. The answer is a tighter cadence, named owners, standardized artifacts, and a written agreement on which numbers count. Everything else follows.

FAQ

What did Nicholas Harris do at Veyl Ventures?

At Veyl Ventures I ran growth and paid media across a nine-figure DTC supplement subscription portfolio, with six-figure daily spend across Meta, Google, YouTube, and native channels. The program produced approximately 17% month-over-month revenue growth on a flat media budget by compressing decision lag and building incrementality testing into the operating cadence.

How did Veyl grow 17% MoM on a flat budget?

Growth on a flat budget is a decision velocity problem, not a spend problem. We compressed the gap between signal and action from days to hours, ran incrementality tests continuously to reallocate budget toward channels actually causing revenue, and let the daily dashboard drive the meeting rather than the other way around.

What is decision velocity in paid media?

Decision velocity is the time between a signal arriving and a media decision being made on that signal. At six-figure daily spend, every hour of decision lag costs real money. The program either compresses that lag or it leaks margin on every cycle.

How do you run incrementality testing at scale?

Incrementality testing at scale means a continuous program of geo holdouts, audience holdouts, and platform-on/platform-off windows that produce causal reads on what each channel is actually contributing. The infrastructure is part data pipeline, part operating cadence, and part a CFO-signed agreement on which numbers drive budget decisions.

What does six-figure daily spend feel like?

Six-figure daily spend is the level where small percentage moves are large dollar moves. A 2% efficiency shift is meaningful money per week. The operating discipline that matters at this scale is daily review on a tight schedule, named owners on every channel, and incrementality reads that overrule platform-reported metrics when the two disagree.

How does this apply to smaller brands?

The same principles work at $1M, $10M, and $100M media spend. The operating cadence, the attribution honesty, and the decision velocity discipline scale down cleanly. The tooling gets simpler and the meeting gets shorter, but the principles are the same. Brands that build this discipline early avoid rebuilding the operating model later.

About the author

Nicholas Harris ran growth and paid media at Veyl Ventures across a nine-figure DTC supplement subscription portfolio with six-figure daily spend, producing approximately 17% month-over-month revenue growth on a flat media budget. He is now President at CreativeOS, an AI-powered SaaS platform serving 25,000+ brands, and Founder at Automatic, an AI consultancy for consumer brands. He has delivered three exits and built consumer-brand operations from SMB through nine-figure scale.

He is currently open to VP AI, AI Transformation, Head of Growth, and Fractional CTO roles at consumer-facing companies. Based in Mesa, AZ. Remote or Phoenix metro preferred.

Get in touch

Related reading