Investigate the drop-off
Review the journey, device experience and available behavioural evidence. Identify whether the issue is understanding, confidence, usability or the offer itself.
Use evidence to prioritise improvements to the pages and steps that influence enquiries or purchases.
Prices cover the listed scope. Additional work and external costs are quoted separately.
Conversion work starts with a specific friction point and a measurable hypothesis about what could improve it.
Review the journey, device experience and available behavioural evidence. Identify whether the issue is understanding, confidence, usability or the offer itself.
Agree the primary measure, affected audience and guardrails. Change enough to test the hypothesis while keeping the comparison interpretable.
Review the result against the test plan, including uncertainty and unwanted effects. Where traffic is limited, use usability research and staged improvements.
A lift is a finding from a completed test, not a promised result of redesigning a page.
Platform reference: Microsoft: keys to effective experimentation
Assess one conversion funnel, prioritise five hypotheses and choose a test or research approach that fits the available evidence.
Review traffic, orders or leads, tracking quality and the purchase journey.
Identify missing evidence and whether a practical experiment can support the decision.
Connect customer friction to a proposed change and a useful measure.
Each hypothesis states the observed problem and why the change could address it.
Prepare up to two variants per feasible test or use a low-traffic research approach.
Agree the measure, guardrails and decision method before evaluating the change.
Review the evidence and decide whether to retain, revise or investigate further.
Include uncertainty and inconclusive outcomes instead of forcing a winning result.
Funnel findings, prioritised hypotheses, feasible variant designs and a documented decision record.
Outside this scope: Guaranteed uplift, guaranteed test cadence without traffic, full rebuild and software
2-week diagnosis; experiment duration set by feasibility
Testing tools and development beyond scope separate
Select diagnostic or experiment track based on traffic, decision cost and measurement quality
If the full scope is beyond your budget, we’ll prioritise the most useful work and agree a smaller first phase with you.
Share what is available. We’ll identify any missing access or inputs during scoping.
Published prices apply to the listed scope. Deliverables, timing, revisions and external costs are confirmed before work starts.
An illustrative delivery approach to help you review the scope. This is a planning example, not a client case study.
| Stage | Example work | Acceptance or decision |
|---|---|---|
| Observation | Visitors ask about delivery charges after reaching the cart. | Validate the issue using approved feedback and journey evidence. |
| Hypothesis | Clearer delivery information near the buying decision may reduce uncertainty. | Agree the change and check that margin and checkout behaviour remain acceptable. |
| Decision | Use a feasible experiment or structured task review. | Record the evidence, limits and whether to keep, revise or investigate further. |
Explore the screenshots and open each project’s case study for context. Select an image to inspect it in the viewer.
Desktop page experience
A desktop test snapshot, shown with its original scores and page preview.
Each image is a separate report excerpt. Reporting windows and filters may differ; screenshots alone do not establish sales, growth or an ongoing ranking.
Illustrative platform screens show the type of work and reporting. These are not client results.
Explore sample page interactions to identify questions worth testing.
Follow the steps from product discovery through checkout and purchase.
Review storefront sections and the settings merchants can manage themselves.
Explore eight illustrative projects, from the initial brief to delivery and acceptance. Businesses and data in these walkthroughs are fictional.
A considered storefront, from catalogue to checkout.
Illustrative project
Explore the walkthroughContent and service pages your team can manage.
A campaign page and enquiry journey.
Updates, backup checks and limited edits.
Start with traffic, conversions, measurement quality and the size of decision you need to make. There is no single traffic threshold that makes every experiment useful. If a test cannot reach a useful conclusion in a practical period, choose the diagnostic and research track: inspect the journey, fix clear problems and validate customer tasks instead of promising an A/B-test win.
Review analytics readiness, customer feedback and the purchase or enquiry journey. Prioritise five hypotheses, make justified improvements within the agreed scope and document what can and cannot be inferred from the evidence.
Define the primary measure, guardrails, expected duration and decision criteria before launch. Record uncertainty and inconclusive outcomes. A short-term change in a metric is not automatically evidence of a winning variant.
$750 – $1,500 / diagnostic; $1,500 – $3,000 / month experiment programme. Testing tools and development beyond scope separate These are published USD prices. The written quote must state the complete cost, payment schedule and applicable taxes.
2-week diagnosis; experiment duration set by feasibility. To scope the work, prepare: Traffic/orders; main funnel; tracking quality. The schedule starts after the required access, inputs and approvals are ready.
Use the listed deliverables and exclusions as the starting point. The quote must state acceptance checks, review rounds, payment stages, cancellation arrangements and any ongoing support. Requested additions need an agreed cost and schedule before implementation.
Tell us where you are, what needs to change, and what success would look like for your business.