Unbounce experiment planning: measure qualified enquiries and the full campaign cost

An experiment should answer a business question that the page can influence. A difference in form submissions may be useful, but it is not automatically a difference in suitable enquiries, attended consultations or profitable customers. Define the immediate page result and the later qualification before choosing a preferred version.

This fictional service business is considering two Unbounce page variants for one consultation offer. Both use the same substantive scope. The team wants to test whether a clearer explanation improves suitable enquiries without creating a different promise. It must also account for traffic, review effort and follow-up capacity.

Unbounce’s A/B testing functionality belongs to the relevant experimentation plan boundary rather than every entry configuration. Confirm the current package and the precise experiment setup. The worked figures in this article demonstrate planning and cost interpretation. They are not an observed test, a statistical significance claim or a promised result for either page design.

Design the work around the actual completion event

1. State a hypothesis with one intended explanation

Describe the visitor confusion and the specific page change expected to resolve it. Keep the offer, major traffic sources and qualification definition sufficiently comparable for the intended question.

Several unrelated changes can produce a result without revealing which assumption was correct.

2. Define the immediate event and later outcome

Specify a valid form completion and the evidence needed for a suitable consultation enquiry. Preserve the relationship between the two counts in the receiving record.

A duplicate or irrelevant submission can be counted as the same business result as a useful new request.

3. Confirm the experiment configuration and eligibility

Ask which purchased plan and controls are required for the proposed test. Inspect the actual traffic allocation and the route carrying the variant reference to reporting.

A comparison of two published pages is not necessarily the controlled experiment the team believes it is running.

4. Keep the follow-up standard comparable

Use the same acceptance and response routine for enquiries from both variants. Record staffing interruptions and material changes to the consultation calendar.

Different response coverage can influence later outcomes and be incorrectly attributed to the page.

5. Calculate cost with the right denominator

Separate traffic and page-production spend from the work to inspect and follow up enquiries. Calculate cost per valid submission and per accepted suitable enquiry as different measures.

A cheaper submission can be more expensive once irrelevant requests and follow-up repair are included.

6. Choose an interpretation appropriate to the evidence

Set a review plan that considers workload, meaningful differences and uncertainty. Seek appropriate statistical expertise where a consequential experiment requires it. Do not declare a universal winner from a handful of volatile events.

A visually satisfying small difference can lead to an overconfident design decision.

Build a complete cost model with a consistent unit

The following comparison is a fictional purchasing exercise for a service business comparing two approved consultation-page variants. Arrangement A and arrangement B are hypothetical configurations, not named Unbounce plans or current vendor prices. Their purpose is to expose a fixed-cost versus workload tradeoff. Replace every amount with the provider quote and the team’s observed work before making a purchasing decision.

Assume 300 attempted accepted suitable consultation enquiries in one review period. Arrangement A has $140 of allocated fixed cost and $1.20 of variable cost per attempt. Arrangement B has $320 of fixed cost and $0.60 per attempt. Both also require an assumed 8 hours of operating work at $45 per hour. That shared labor amount is $360. Keeping it visible prevents a subscription comparison from being mistaken for the complete cost of running the process.

Cost component	Arrangement A	Arrangement B
Allocated fixed amount	$140	$320
Attempted workload	300	300
Variable amount per attempt	$1.20	$0.60
Variable subtotal	$360.00	$180.00
Assumed operating labor	$360	$360
Scoped total	$860.00	$860.00

Under these inputs, the lower scoped total is a tie. The arithmetic does not establish functional equivalence. If one arrangement cannot produce an accepted accepted suitable consultation enquiry, its lower price does not purchase the same outcome. First establish that the relevant permissions, product functions and receiving workflow satisfy the requirement. Then compare the cost of the arrangements that remain eligible.

Calculate the crossover instead of choosing from one sample month

Ignoring the shared labor that is identical in this example, set the two totals equal: 140 + 1.20 × volume = 320 + 0.60 × volume. The difference in fixed amounts is $180; the variable difference is $0.60 per attempt. The crossover is therefore 300 attempts. Below that level A has the lower modeled platform allocation; above it B does, assuming the same definitions and the same quality of output.

For Unbounce, inspect the eligible page and experimentation arrangement and its current usage definitions. A visit, valid form submission and suitable owned enquiry are separate measures. Preserve the qualifying and receiving work when translating the campaign workload into the quoted account requirement. The 300 attempted accepted suitable consultation enquiries in this example are an internal operating measure. Translate them into the confirmed purchased units before replacing the hypothetical costs. A minimum commitment, annual term or tier boundary may require a different model; retain the current quote with its actual scope.

Divide by accepted output as well as attempted work

Suppose 240 of the 300 attempts meet the agreed completion criteria. This invented usable-output share is 80%; it is not a Unbounce success rate. Arrangement A would cost $3.58 per approved accepted suitable consultation enquiry, while B would cost $3.58. Dividing by all attempts instead would give $2.87 and $2.87. Both calculations are arithmetically valid, but only the first answers the question about accepted operating output.

Explain what happened to the remaining 60 cases. Some may be inappropriate inputs; others may need a correction or an unavailable decision. Do not describe them all as software failures. Equally, do not erase their inspection cost from the comparison. A useful review separates input quality, the configuration’s behavior and the receiving team’s ability to continue the work. Each requires a different response.

Include switching effort and the cost of carrying an exception

A new arrangement may require preparation, record cleanup, template work or training. If a controlled estimate adds twelve hours at the same $45 rate, that is $540 of transition labor. State whether it is a one-time investment and over what period you intend to recover it. Do not treat it as a monthly fee indefinitely or disappear it from the decision merely because an existing employee performs the work.

Now vary the exception burden. Adding four hours of review increases either arrangement by $180. That can be more consequential than a small difference in the quoted fee. The practical question is which input or handoff creates those hours and whether the proposed configuration removes them. A larger allowance that leaves the repair process untouched may increase throughput without making the work more economical.

For a service business comparing two approved consultation-page variants, compare quiet, expected and spike periods using the same accepted suitable consultation enquiry definition. The modeled 300 attempts are only one workload. A changed package boundary or approval burden can alter the comparison, so retain a range where the work is uncertain. Link the commitment to the actual requirement and review point rather than treating the spreadsheet’s decimal places as evidence that future demand is known.

Test the six assumptions that could change this budget

The following exercises connect the financial model to the actual Unbounce workflow. Keep input definitions, the selected configuration and the person responsible for each decision beside the observed result. A provider demonstration can establish an available route; it does not replace the team’s own acceptance of the business meaning or the ongoing work required to maintain it.

Exercise 1: State a hypothesis with one intended explanation

Ask the team what they would learn if the revised page received more submissions but poorer qualification.

The hypothesis and the decision rule distinguish useful change from a larger unqualified count. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 2: Define the immediate event and later outcome

Classify a valid suitable enquiry, a duplicate and a request outside the service scope.

Each count has a stable meaning and the later qualification can be traced to the page variant. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 3: Confirm the experiment configuration and eligibility

Follow controlled visits and submissions through each proposed variant and inspect their recorded identifiers.

The actual arrangement supports the stated comparison or its limitation is recorded explicitly. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 4: Keep the follow-up standard comparable

Have a covering colleague continue controlled enquiries from both variants using the same brief.

The receiving process does not introduce an unexplained difference in qualification or next action. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 5: Calculate cost with the right denominator

Reconcile the same fictional campaign totals using both denominators and explain the result.

The decision identifies the business unit each cost figure represents. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 6: Choose an interpretation appropriate to the evidence

Review a case with a few additional submissions but no clear improvement in suitable enquiries.

The team can retain uncertainty, revise the hypothesis or gather more appropriate evidence. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Keep an operating record someone else can continue

For a service business comparing two approved consultation-page variants, keep one reference for each accepted suitable consultation enquiry. Use that reference across the input, the accepted result and any exception record. It allows a reviewer to follow the work without relying on a customer’s name, a screenshot title or the memory of the person who first handled it. Where the destination system assigns its own identifier, retain both references and explain the relationship.

Record field	What to put in it	Why it belongs in this workflow
Input reference	The original request, item or approved brief	Connects the result to the actual starting point
Configuration version	The relevant rule, template or account arrangement	Makes an observed result reproducible
Completion evidence	What establishes an accepted accepted suitable consultation enquiry	Keeps the outcome definition stable
Exception reason	The missing fact, conflict or failed requirement	Directs repair toward the cause
Current owner	The person or queue that accepted the next action	Makes continuation visible
Review point	When the case or configuration needs another decision	Prevents unfinished work from disappearing

For one accepted suitable consultation enquiry, write what the evidence establishes before proposing an explanation. In a service business comparing two approved consultation-page variants, the note needs the starting reference and the accepted next responsibility as well as a visible result. Keep the supporting source small enough to inspect. A large screenshot collection should not replace an explicit decision about this particular outcome.

Before increasing the workload for a service business comparing two approved consultation-page variants, review the held accepted suitable consultation enquiries by their actual cause. Use the six exercises to locate an input, configuration or responsibility gap, then repeat the affected route after its repair. The first ordinary accepted suitable consultation enquiry does not establish that a different unresolved case has become acceptable.

Make the next decision from the evidence

Keep the page brief, actual experiment configuration and qualification record with the result. A useful decision may be to adopt a clearer explanation, to stop a misleading variation or to learn that the current evidence is insufficient. Each is more informative than a winner label detached from the consultation process.

Purchase experimentation capability when the team has a meaningful question, an eligible configuration and enough operational discipline to interpret the result. When the first page does not deliver valid owned enquiries, repair that route before introducing more variants.

Keep a short decision note for this specific Unbounce use case: the work approved, the conditions still outstanding, the owner of each outstanding decision and the next review date. A conditional approval is useful when its boundaries are visible. It becomes misleading when an unresolved requirement is presented as an observed capability.