Storefront signals
Pull claims, proof points, product context, objections, and customer language into one starting point.
For Shopify brands running Meta ads
autoprune watches the signals that changed this week, recommends the next test, and keeps every launch tied to a reason.
The workflow spine
Pull claims, proof points, product context, objections, and customer language into one starting point.
Turn the strongest signals into a short list of testable Meta angles with a clear reason.
Review video-forward cards, approve what deserves a launch, and reject weak or off-brand ideas.
Log what happened after manual launch so the next batch starts from evidence instead of recall.
Carry the learning forward into the next weekly decision: scale, refresh, prune, or test a new angle.
Why this exists
Creative ideas live in notes, Slack, Figma, and someone's memory.
Results live in Meta without the reason a test existed.
Product context changes faster than the testing plan.
The next batch starts from vibes instead of last week's learning.
Reactive weekly plan
autoprune is the upstream decision layer before creative analytics: it watches what shifted, explains the recommendation, and keeps weak angles out of the batch.
The product, claim, objection, or customer language that makes the test worth considering.
A decision-ready test brief with format, placement, hook, rationale, proof source, and review state.
Manual launch marker, performance fields when available, and the qualitative note that should inform next week.
Week 22
Reviews and homepage copy both moved toward fewer steps.
Brief one creator video around a simpler routine.Ingredient proof is stronger, but the wording is too clinical.
Soften the claim before it enters the batch.Last run and brand notes both point away from price-first creative.
Keep it out until the offer needs a dedicated test.Approve, edit, or skip before anything launches.
Proof format
autoprune does not have mature customer outcome proof yet. The page still needs the container for it: brand, signal, test decision, and learning, without inventing lift numbers before pilots earn them.
The product or offer being tested
The storefront, customer, or ad-learning input
Approve, edit, reject, launch, prune, or scale
What the next recommendation should remember
Best fit / not fit
Early product
autoprune is early. It should not promise guaranteed ROAS, replace your media buyer, or launch spend without you.
The product is shaped around a practical founder workflow: turn product and brand context into a cleaner weekly testing system, then keep the learning visible.
Resource cluster
A weekly review loop for deciding what to scale, watch, refresh, or prune.
When more creative volume helps, and when the weekly testing workflow needs fixing first.
How to tell whether performance decay is fatigue, weak creative, or something else.
A copyable template for turning storefront signals into creative tests.
Clear definitions for prune, pause, watch, refresh, scale, fatigue, angles, hooks, and storefront signals.
Start the loop
No Meta login required for the first run. Start with brand and product context, then review the cards before anything launches.
Prefer a founder conversation first? Leave an email and Catalina will follow up with a quick fit check.