Ask AI How to Split Your Ad Budget | A Draft Built on ROAS and Saturation

In the meeting that sets next month's ad budget, the proposal that passes most often is "same as this month." Not because it's right — because assembling the numbers to justify a change is heavy. Reallocation isn't hard to judge; it's hard to prepare.

So hand the preparation to the AI.

Ask: "How should I split ¥500K?"#

Have an AI connected to your numbers read per-channel ROAS and saturation, and the draft comes out like this (the figures are the sample store's real data):

RevenueScope MCP🔗 RevenueScopedata connected

You

I have ¥500K/month for ads. How should I split it next month?

Here's a draft from what the numbers can actually support. Google Ads: ROAS 3.22, saturation 54% — efficient, with room left to grow. Meta: ROAS 1.85, saturation 75% — less efficient and close to its ceiling. Read plainly: weight Google heavier, hold or trim Meta. Three caveats come attached: ① doubling budget won't double revenue (diminishing returns), ② precision drops where cost-per-session is unknown, ③ expect ±20–30% error on this split. This is a draft, not an autopilot — the final call is yours.📊 ROAS & saturation by channel · last 30 days📊 sample store · demo data

Two measurements do the work. ROAS (revenue per ad spend) captures efficiency; saturation captures whether a channel is approaching the point where more budget stops helping. In the sample store, Google Ads runs ROAS 3.22 at 54% saturation while Meta runs 1.85 at 75% — the asymmetry is visible in numbers, so a concrete alternative to "same as last month" writes itself.

"Draft" means exactly that#

Notice that the AI's answer arrives with its assumptions and limits pre-attached: doubling budget won't double revenue (diminishing returns); precision falls where acquisition costs are invisible; expect ±20–30% error. These caveats are attached by RevenueScope itself — not the AI being humble.

This is not a tool that reallocates automatically. It's a draft with receipts, for a human to decide on — which is why you can carry it straight into the meeting. The answer to "why weight Google?" comes bundled with the measurements.

If you haven't run ads yet, start one step earlier with where your first ad money should go. The exit-side decision lives in what happens if you stop your ads.

RevenueScope keeps your allocation evidence current, every month

Connect your ad spend (or enter it manually) and ROAS and saturation line up on the same screen as per-channel revenue. The monthly allocation meeting's prep work becomes one question.

Two boundaries: ROAS conversion values come from the ad platforms' own reporting — a separate source from RevenueScope-measured revenue (reconcile separately). And the proposed split guarantees nothing — treat the ±20–30% error band as part of the answer.

Ask for a budget draft on the sample store

FAQ#

Q. Does this require connecting ad spend?

The ROAS/saturation-based split does (connected or manually entered). Without it, you get an even three-way starter split plus the assumptions and limits — by design, nothing that could mislead.

Q. What is saturation?

An indicator of whether a channel's growth is starting to flatten as you add budget. High ROAS with high saturation reads as "efficient, but hard to grow further."