You just inherited an ecommerce Meta account. You have 45 days to lift ROAS on the same monthly spend, and I would spend the first two weeks cutting waste and fixing the purchase signal, not launching a single new audience.

No extra budget to buy your way out of bad structure. No fresh pixel. No pause while you “rethink strategy.” In an inherited account, I would look for the first gains in what is already running: spend spread too thin, purchases counted twice, and reports that make weak ads look strong.

I learned that the slow way running small ecommerce accounts where every wasted $50 hurt. I used to open takeovers by keeping everything live, adding three interest tests and a couple of fresh creatives, and hoping the new stuff covered for the old. I was wrong. The old stuff ate the budget and muddied the reports, so the new stuff never got a clean read. A practitioner who opens with new audiences will disagree. They can have days 1 to 14. I will take what happens on day 30.

1. Days 1–3: Find out whether the account is telling the truth

Cost against the constraint: Three days of spend with no structural changes. What it buys: A baseline you can compare with day 45 without mistaking a reporting change for a performance change.

I export campaign and ad-set counts, lifetime spend, purchase value by ad set, and the attribution window used in the old reports. That last detail is not clerical. Meta reports can look different under 7-day click plus 1-day view than under 1-day click: the same $500 of spend can read as 5.12x instead of 2.88x when delayed clicks and view-throughs are included. If you compare old screenshots with a new window, you can spend the next six weeks chasing a ROAS drop that never happened. Pick one window, write it down, and use it throughout this playbook.

Then I open Events Manager. I look for double-counted Purchases, especially when the Pixel and Conversions API both fire without a shared event ID. Meta deduplicates browser and server events when the Pixel eventID and server event_id match on the same event name, with the duplicate arriving within 48 hours. Without that match, purchase counts and reported ROAS can inflate. The account may also optimize toward purchases that did not happen twice.

I check that Purchase passes value and currency, not just a count. No reliable purchase value, no reliable ROAS. Fix the signal before judging an ad set, let alone adding another one.

2. Days 4–10: Cut ad sets until the budget has a job it can do

Cost against the constraint: Paused ad sets and delivery graphs that may look lumpy. What it buys: More of the unchanged budget reaching the ad sets you actually intend to evaluate.

Start with weekly budget and cost per purchase. Meta guidance cited in this discussion of conversion volume uses about 50 conversions a week as a useful learning threshold. The capacity check is weekly budget ÷ cost per purchase ÷ 50. It is a planning test, not permission to pretend every account can reach that threshold.

Say the account spends $3,000 a month at a $30 CPA. That is roughly $700 a week, or about 23 purchases at the current CPA. It cannot support even one ad set at 50 purchases a week. If I inherit 12 ad sets at that spend, I do not rearrange them into a prettier set of 12. I pause the weak and redundant ones, concentrate the budget in the strongest prospecting line, and accept that learning may still be limited. Cutting waste does not manufacture more purchases.

Next I look for overlap: five interest stacks and lookalikes that reach much the same people, each taking a slice of the budget. I compare their audience definitions, spend, CTR, purchase volume, and ROAS before merging or pausing. The useful part of this campaign-structure audit is simple: count what is running, identify what is duplicative, and stop funding it. Fewer viable ad sets beat a museum of micro tests.

By day 10, the surviving structure should fit the account’s actual purchase volume. At higher spend that might mean two or three prospecting ad sets and a separate retargeting line. At $3,000 a month with a $30 CPA, it means far less. The budget, not my preferred diagram, decides.

3. Days 11–14: Set a ROAS target the margin can survive

Cost against the constraint: Four days spent defining the target rather than declaring victory from a platform screenshot. What it buys: A number you can use to decide whether another order is worth buying.

Break-even ROAS is 1 divided by contribution margin, provided revenue and margin use the same basis. Shopify’s example puts a 30% margin at 3.33 break-even; a target such as 4.0 leaves room for profit. Another ecommerce ROAS calculation shows why definitions matter: 38.75% CM2 after product, shipping, and fees gives roughly 2.6 break-even on net revenue, but about 3.1 in platform terms when purchase value includes 19% VAT. Same business, different reporting basis.

I put the calculation on one sheet:

  1. Start with revenue per order on a clearly stated basis.
  2. Subtract product, shipping, fees, and expected returns to find contribution margin.
  3. Divide 1 by that margin for break-even ROAS, then set a target above break-even that leaves the profit you want to keep.
  4. Translate that target onto the same revenue basis Ads Manager reports, and record the attribution window beside it.

That last step saves an argument on day 30. I will not chase a 4.5 benchmark from somebody else’s screenshot when this store’s economics point elsewhere. I also will not set a target so high that delivery throttles and volume disappears. By day 14, I want one margin-based target, one attribution window, and clean purchase value. Every test from here gets judged against them.

4. Days 15–30: Test ads, not another stack of audiences

Cost against the constraint: A substantial share of the fixed spend goes to tests, including losers. What it buys: A way to find creative that improves purchases without restarting the audience search.

I run one testing campaign with one ad set and keep catalog sales separate. Otherwise, catalog placements can absorb most of a shared budget, leaving new concepts with too little spend to read. If catalog takes about 90% of the money, I did not test three concepts. I funded catalog and named the leftovers a test.

I start with three concepts, changing one thing at a time: one hook with three openings, or one product framed around price, proof, and use case. At $30 a day or less, the low-budget testing approach keeps three ads in one ad set; as spend approaches $100 a day, it allows up to six. That is enough to learn without turning the budget into confetti.

I give a test at least 3 to 4 days before calling it. I judge purchases and margin-based ROAS, not the prettiest thumbstop rate. When volume allows, a winner has 20 to 30 purchases behind it and clears the target. If the account cannot produce that many purchases in the window, I do not call an underpowered lead a proven winner. I keep testing and say what the data does and does not show.

Losers lose their slot. A winner moves into the main prospecting ad set, and the next concept takes its place. No new audiences in this window. New ads, same people. The point is to learn what earns the existing budget before asking that budget to cover another audience too.

5. Days 31–40: Give retargeting its own capped budget

Cost against the constraint: About 15% of fixed spend moves into retargeting, reducing what prospecting gets during this window. What it buys: A controlled attempt to convert people who have already shown intent, without letting catalog swallow the creative test.

Catalog stays separate from prospecting. I cap its budget, then segment by recency: product viewers from days 0 to 7, cart abandoners from days 0 to 14, and past buyers excluded for 180 days unless the store sells consumables. I use two ad sets at most, one for viewers and one for cart abandoners.

The creative does not need a manifesto. Show the product they viewed, the price, the shipping promise, and an answer to one objection. Then watch frequency. On a small audience, frequency above 3 in 7 days is a sign I may be paying to annoy people who have already made up their minds.

If catalog ROAS clears the margin target by day 37, I keep the capped line running. If it does not, I check the feed and purchaser exclusion before blaming the bid. And I keep the accounting honest: retargeting can lift blended ROAS without proving that prospecting found more new customers. Retargeting does not fix a broken prospecting signal. It gives a cleaner one another chance to convert.

6. Days 41–45: Move money only after an ad earns it

Cost against the constraint: Zero extra dollars. Every increase for a winner comes from another part of the account. What it buys: A chance to lift revenue without changing the monthly spend ceiling.

If prospecting winners clear the margin target and the capped catalog line does too, I move budget toward them. The vertical-scaling rule I use is about 20% on a winning ad set every 3 to 4 days, followed by a read on profit rather than reported ROAS alone. Say a winner holds 3.8x against a 3.1 target at $100 a day. I move it to $120 by taking $20 from weaker spend, wait four days, and check profit after fees and shipping. The monthly budget stays flat.

Vertical scaling comes first because it builds on what the ad set has already learned. Horizontal scaling into a genuinely different, non-overlapping audience comes later, when the constraint lifts. Duplicating the same broad audience three times is not scaling. It is the overlap problem from days 4 to 10 wearing a clean shirt.

If nothing clears the margin target by day 43, I do not scale. I use the remaining days to extend testing, not spend. If winners do emerge, day 45 can end with 70 to 80% of flat spend on proven lines. That is an outcome to earn, not a quota that justifies calling a weak test a winner.

7. Day 45: Show what got cut and where the money went

Cost against the constraint: No additional spend, just a record clear enough for someone else to challenge. What it buys: Proof that the ROAS story is about changed decisions, not a nicer report.

I deliberately leave several tools shut during these 45 days:

  • No new prospecting audiences in the first two weeks. They compete for spend before tracking and structure are trustworthy.
  • No catalog-and-creative hybrid on one testing budget. Catalog can starve the concepts I am trying to read.
  • No lookalike rebuild, interest expansion, placement surgery, or landing-page redesign. Any might deserve a test later. Right now each adds a moving part to an account with a fixed budget and a short deadline.
  • No creative volume for its own sake. Fifteen variations with different background music are not fifteen useful tests. Three distinct concepts, judged against the same target, tell me more.

If I hand this plan to a Meta management company promising better ROAS, I ask for receipts, not a smooth upward line in week one. Early sales signals may appear in 7 to 14 days, while stable performance takes longer testing. A guaranteed specific ROAS ignores what an auction can do. A margin target and an action log are more useful.

My day-45 check is short:

  1. Day 3: Events Manager evidence that Purchase deduplication and value passing work, plus the attribution window in writing.
  2. Day 10: Ad-set count beside the weekly-budget and CPA math. If the account cannot reach 50 purchases a week, the report says so instead of claiming it exited learning.
  3. Day 14: Break-even and target ROAS calculated from this store’s margin, on the same revenue basis as the report.
  4. Day 30: A creative log showing concepts, spend, purchases, and which results have enough volume to trust.
  5. Day 45: Budget moved from named losers to named winners, or an explicit decision not to scale.

I also want the business to keep full admin access to its ad account, Pixel, and creatives. That is how groas positions its flat $1,499-a-month Meta Ads management: audiences, budgets, and ads worked around the clock, new ads tested, winners scaled, and a dedicated manager answerable for the result. The contrast with a provider selling activity by the hour is the work you can inspect. Show me the changes and what each one bought.

8. After day 45: Lift the constraint without dropping the discipline

Cost against the constraint: None yet; this step waits until the 45 days and flat-spend rule end. What it buys: Room to test a new source of customers without burying the account in simultaneous experiments.

This playbook is not for every store. Skip it if you sell a $20 impulse product on less than $1,000 a month: the 50-purchase-per-ad-set threshold is out of reach, and one broad campaign with patience is a better fit. Skip it if you do not know your margin; without break-even ROAS, a target is theater. Skip it if you need new customers only. The capped catalog work in days 31 to 40 aims to lift blended ROAS, not prove new-customer growth.

When the constraint lifts, I keep the proven winners funded and release budget into one genuinely new audience or one new concept at a time. Keep the margin target fixed while volume climbs. Do not reopen every tool in the box because the calendar changed.

Same spend got the account a cleaner signal, fewer competing ad sets, and ads that had to earn their budget. If a provider cannot show that sequence in plain numbers, they are not managing ROAS. They are renting you activity.