A $1,000 ChatGPT ads test can buy roughly 250 clicks and just 7 ecommerce orders at the planning rates below. That is enough to learn whether anyone responds. It is not enough to prove that the channel beats another one, no matter how convincing the agency screenshot looks.
Most ChatGPT ads “real results” I get sent are three conversions and a story. The problem is sample size, not a lack of enthusiasm. Reported CPC ranges run from $3–$6 for ecommerce to $8–$18 for SaaS and $15–$25 for finance. Your vertical can determine how many chances you get before your creative has had much chance to prove itself. At a $25 daily budget, even a $3–$5 CPC buys only about 5–8 clicks a day.
I use 3–5% click-to-lead for B2B and about 2.8% for ecommerce as planning inputs below. Against those rates, a small test can tell you whether traffic arrives and whether anyone takes the next step. It cannot give you a dependable customer CPA or ROAS. When an agency says otherwise, ask how many conversions sit behind the result.
The assumptions behind the table
I am not pricing your account. I am dividing three budgets by illustrative CPCs, then applying planning conversion rates. The point is to show where the counts get thin, not to predict your auction.
- CPCs: $4 for ecommerce and retail, $6 for travel and education, $12 for SaaS and software, and $18 for finance and legal. These sit within the reported $3–$6 ecommerce, $4–$8 travel and education, $8–$18 SaaS, and $15–$25 finance ranges. They are stand-ins, not quotes.
- Conversion rates: 4% click-to-lead for a B2B scenario, 2.8% click-to-purchase for ecommerce, and 13% click-to-lead for a high-intent local-services scenario. These are planning inputs, not measured ChatGPT ads results. The B2B and ecommerce planning figures are a starting point; your offer and landing page still have to do the work.
- Time: Four, eight or twelve weeks, with spend spread evenly. A $1,000 test over four weeks is $250 a week. A $5,000 test over twelve weeks is about $416 a week. Stretching the schedule does not increase the total number of clicks the budget buys.
The $6 travel-and-education assumption shows the middle of the CPC ladder, but the main table uses $4, $12 and $18 to keep the budget comparison readable. Divide budget by CPC for clicks; multiply clicks by the relevant planning rate for expected conversions. The columns show separate scenarios, not three outcomes you should expect from the same campaign. I would not apply a local-services lead rate to an ecommerce offer and call it a forecast.

Table 1: What the budget buys before you split it
At the $4, $12 and $18 illustrative CPCs drawn from the reported category ranges, every $1,000 buys about 250, 83 or 56 clicks respectively. Table 1 applies the stated planning rates to those clicks. Counts are rounded, so treat them as scale, not a promise that the last lead will appear on schedule. Each row represents the full budget across the full test, whether you spend it in four weeks or twelve.
| Budget | Illustrative CPC | Approx. clicks | B2B leads at 4% | Ecom orders at 2.8% | Local leads at 13% |
|---|---|---|---|---|---|
| $1,000 | $4 | 250 | 10 | 7 | 33 |
| $1,000 | $12 | 83 | 3 | 2 | 11 |
| $1,000 | $18 | 56 | 2 | 2 | 7 |
| $3,000 | $4 | 750 | 30 | 21 | 98 |
| $3,000 | $12 | 250 | 10 | 7 | 33 |
| $3,000 | $18 | 167 | 7 | 5 | 22 |
| $5,000 | $4 | 1,250 | 50 | 35 | 163 |
| $5,000 | $12 | 417 | 17 | 12 | 54 |
| $5,000 | $18 | 278 | 11 | 8 | 36 |
The expensive-click rows are the ones I would put beside any small-business case study. A $3,000 SaaS scenario at $12 a click produces about ten leads at the 4% planning rate. If someone calls a change in those ten leads a proven improvement, the headline is doing more work than the data.
Use Table 1 to choose the question, not to forecast revenue. To get from leads to customers, you need a close rate; to get from customers to ROAS, you need revenue. Neither comes from CPC alone.
Table 2: The conversion count behind a “real” lift
A baseline and a winner are different things. You might collect enough leads to estimate an early lead cost without collecting enough to show that one ad, landing page or channel is better than another.
For a rough illustration of two-variant test size, the draft planning rule is about 15.68 divided by the square of the relative lift you want to detect. That puts a 20% lift at about 392 conversions per variant, not 392 clicks and not 392 conversions across both variants. These are illustrative thresholds, not a universal guarantee of significance: the starting conversion rate and test design matter too. Their useful message is the order of magnitude.
| Relative lift you want to detect | Approx. conversions per variant | What Table 1 says about a small test |
|---|---|---|
| 30% | ~174 | Even the largest local-lead scenario shown reaches about 163 conversions in total, before a split. |
| 20% | ~392 | At a 4% B2B lead rate, one variant alone would need about 9,800 clicks. |
| 10% | ~1,568 | At that same 4% rate, one variant would need about 39,000 clicks. |
| 7.5% | ~2,788 | Far beyond the conversion counts in Table 1. |
That is why 10 leads versus 14 can feel persuasive without settling a test. Four extra leads look substantial when the starting count is ten. They can also come from ordinary variation. I used to tell clients a 40% gap must mean something. I was wrong. Even at 150 conversions a month, confirming a 20% lift can take about 24 weeks.
The practical rule is blunt: do not split $1,000 into A versus B to declare a winner. You are buying two smaller anecdotes instead of one more readable baseline. Do not peek early, find a good Tuesday and call the work done, either.
What $1,000, $3,000 and $5,000 can answer
$1,000 buys a traffic reality check. At $4 a click, the table gives you about 250 visits, ten B2B leads or seven ecommerce orders under the corresponding planning assumptions. Run one offer and one landing page for four weeks rather than dividing the spend among variants. Check whether delivery is real, whether visits look useful and whether anyone starts or completes the intended action. Click-through rate needs impressions as well as clicks; purchases and leads need their own counts.
Early agency tests reported about 1.5% CTR and visitors spending 25–35% more time on site than paid-search visitors. That is a pattern you can look for, not a benchmark your 250 visits must reproduce. A handful of form fills may give you a next question. They do not give you a stable cost per customer. In the $12-click scenario, the table expects about three B2B leads. That is a diary entry, not a performance verdict. Spend $1,000 to check whether the channel merits another test.
$3,000 buys a rough lead-rate comparison. The table gives you about 750 clicks at $4, 250 at $12 or 167 at $18. Apply the 4% B2B planning rate as a separate scenario and those become about 30, ten or seven leads. The difference between 30 and seven is why a single “ChatGPT ads results” headline tells me so little without a CPC and conversion count.
If you compare with Google, keep the offer and landing page identical. Otherwise you are testing pages as well as channels. Google’s public cross-industry baseline reports 6.64% CTR, $5.42 CPC, 8.18% conversion rate and $66.69 cost per lead. At those average CPC and conversion-rate figures, $3,000 works out to roughly 553 clicks and 45 leads. That is context, not a matched control for your particular business. If ChatGPT produces 30 leads while your Google comparison produces 45, note the gap and the different traffic; do not promote either count into a final verdict. I worked through the companion question in what a $1,500 ChatGPT ads test can prove. Use $3,000 to compare lead rates cautiously, on the same page.

$5,000 can buy a provisional cost per lead, but usually not a defensible customer CPA or ROAS. The distinction is what happens after a lead arrives. The draft planning range for paid B2B leads closing is 1–3%, compared with 5–10% for organic and referral. Apply that paid-lead range to 50 leads in the $4-click, 4%-lead scenario and you are still talking about roughly one or two customers. Apply it to 17 leads in the $12-click scenario and zero customers remains entirely plausible. I would not build a revenue claim on either outcome.
At the higher-count end, 35–50 conversion events can start to give you a cost-per-lead range worth watching, with a wide error band. At the lower-count end of Table 1, even that read stays thin. Google’s Smart Bidding guidance is about 30 conversions in the trailing 30 days for reliable operation; it is another reason not to scatter a small budget across campaigns. Keep the conversion action consistent and read the lead rate before you read the sales deck. Quote provisional CPL where the lead count supports it. Do not relabel it customer CPA.
If you sell into a different vertical, replace my stand-in CPCs with the CPC and conversion-rate ranges for your industry and redo the arithmetic: budget divided by CPC gives clicks; clicks times conversion rate gives leads or orders; leads times close rate gives customers. Each extra step inherits uncertainty from the one before it. A short row of conversions cannot become a precise revenue forecast just because it sits in a neat spreadsheet.
Put an agency’s “real results” back into raw counts
When an agency shows me a small-business ChatGPT campaign, I run Table 1 in my head before looking at the screenshot. A 100% lift from two leads to four is still six leads across the two periods. A 3.1x ROAS on seven orders deserves the underlying order count and window beside it. What the deck calls “early signal,” I call the part of the test where randomness does a lot of talking.
I stopped reading case studies only the way agencies want them read and started asking for the change log behind the last month’s work: what changed, when, and what happened next in raw counts. For a small ChatGPT ads test, I want four answers before I believe the headline:
- How many conversions sit behind it? Ask for clicks, leads or orders, and the exact window. Fewer than 30 leads total is an early read, not proof of a lift.
- Compared with what, on the same offer? If the landing page changes between ChatGPT and Google, the comparison changes with it.
- Over how many weeks, with what spending pattern? Four days at $25 a day buys roughly 20–32 clicks at the $3–$5 starting CPC range. That is not a useful conversion-rate read.
- What count would change the decision? If the agency cannot name the next threshold and the budget needed to approach it, it is selling the story rather than the test.
Those questions do not dismiss a promising result. They keep a promising result in its proper place: a reason to continue, not permission to claim you have settled the channel.
Set the question before you set the budget
The order most small tests get wrong is budget first, question second. Someone picks $1,000 because it feels safe, splits it across two messages and a landing-page variant, then wonders why nothing is readable. The tables explain why. Pick the question your budget can pay for, then spend toward that question.
At $1,000, check traffic quality and whether anyone takes the intended action. At $3,000, compare an early lead rate with a Google control on the same offer and page. At $5,000, price a provisional cost per lead if enough leads arrive. Customer CPA, close rate and ROAS need customer and revenue counts that these lead scenarios do not reliably buy.
That is also the discipline I use inside groas. Search Ads covers Google, Bing and ChatGPT ads for one flat $1,499 a month. We look for a readable lead rate on a small, steady ChatGPT slice before asking for more budget to chase CPA. Continuous work helps keep the test from turning into a new campaign structure every two weeks, but it cannot manufacture conversions the budget did not buy.
So if you have $1,000, buy a reality check. If you have $3,000, buy a cautious lead-rate comparison. If you have $5,000, buy an early CPL read and stop there. No test in this range proves the channel. It can show whether the channel deserves a larger test. That is the decision the numbers support.

