Proveny turns one supplier product into one coherent Meta test path: a selling thesis you pick, a landing page and ad package that carry the same promise, and a launch you cap. You define what counts as a win. The market gives the answer.
A Product Test is one complete round of work: a product idea with a real source, a handful of ways it could sell, one direction you commit to, a page and Meta package that carry that promise, a spend cap you authorise, and a result scoped to the path that actually ran.
Five milestones. Proveny does the research, briefing, production and wiring; every decision that costs money waits for you.
You set the bar — Proveny doesn't recommend one, doesn't score the product and doesn't rank the angles it drafted. Two numbers: a cost per purchase you'd accept, and the order count that makes it real.
Spend against cap, clicks, add-to-carts, purchases and cost per purchase, day by day — with the signal called immature until it isn't.
A test buys the answer — expect it to spend, not to profit. One cap you authorise before submission. No auto-budget, no auto-kill, no auto-scale.
Actual against your two numbers, where the funnel gave out, and what wasn't tested. This result describes the selected path — not the whole product.
You choose what gets launched. The market provides the answer.
Same complete job on both plans, same readable result. Free is one test; Studio is repeat volume and the right to edit what Proveny generated — not a better or truer answer.
No. Automatic money actions: none. It prepares the package and shows the exact cap; nothing is submitted to Meta until you release it, and it never raises budget, kills or scales by itself.
No. You set the cost per purchase and order count that count as a win, and Proveny puts the actual result next to them along with where the funnel gave out. One selected angle on one channel is not a verdict on the product.
Not in this version. You compare two or three selling theses and build one. The rest are saved as alternatives — saved is not tested, and they are not ruled out by this result.
It is the best-supported starting point for a coherent execution: what your product source and assets can actually back up, and whether the ad and the page can carry one promise. It is not a prediction of performance.
You set a fixed cap per test — around $175.00 over 7 days is a common starting point. It is a cap, not an estimate, you authorise it before submission, and you can stop early.
At package generation, right after you pick a direction and define success. Pasting a product and reading its blueprint is a reversible draft — swap products or walk away without spending the test.
One Shopify store to start, and a Meta ad account when you are ready to launch. Connecting Meta creates no spend on its own. One account, one store, Meta only in this version.
Bring the product. Proveny builds one coherent path — one thesis, one page, one Meta package — and stops at your approval. You set the bar, you release the budget, the market answers.