LiftCRO
← All services

A/B test development

Your test ideas, coded, QA'd and ready to launch in 5 days.

Send us the brief. We write the variation in plain JavaScript and CSS, with no flicker and no layout shift, in the testing tool you already use, and hand it back with a QA report. You keep the strategy and the client; we are the development team behind it.

Get a free QA audit
  • From $2,000 a month for 70 hours, about $29 an hour
  • Built in Optimizely, VWO, Convert, AB Tasty or Kameleoon
  • QA report with every test

Built in the testing tool you already use

What's included

What we take on

Scoped in writing after the first call. These are the parts most A/B test development work is made of.

Variation code

Scoped JavaScript and CSS written from your brief and mockups, with a preview link for sign-off before anything touches live traffic.

Targeting and goals

Page targeting, audiences, custom events and goals set up in your tool and checked before the test starts.

QA on real devices

A second person runs our 14-point checklist on the browsers and devices you name, then sends the report.

Winners built in

When a test wins, we build the change into your theme or codebase so the result does not live in the testing tool forever.

Stack

The tools we work in

OptimizelyWingify (VWO and AB Tasty)KameleoonConvertGoogle AnalyticsShopifyWordPress

How we work

From brief to launch

Step 1

Send the brief

Use our one-page template or your own. A hypothesis, a mockup and the pages to target are enough. We ask questions within one working day.

Step 2

We build

The variation is written in your testing tool and shared on a preview link. Nothing touches live traffic.

Step 3

We QA

A second person checks the agreed browsers and devices, the targeting and every goal, then sends the report.

Step 4

You launch

You press go. If anything breaks after launch, we fix it within 24 hours at no charge.

Pricing

Test development retainers

Every plan includes QA, a report with each test and 24-hour bug fixes. Three-month minimum, billed monthly.
Starter
$2,000 a month

For teams starting a testing programme.

  • 70 developer hours a month
  • About $29 an hour
  • Roughly 5 large tests, or 17 small
  • 2 to 5 business days by size
  • QA report with every test
GrowthRecommended
$3,600 a month

For teams shipping two tests a week.

  • 135 developer hours a month
  • About $27 an hour
  • Roughly 9 large tests, or 33 small
  • 2 to 4 business days by size
  • QA report with every test
Scale
$6,000 a month

For agencies and high-traffic stores.

  • 240 developer hours a month
  • About $25 an hour
  • Roughly 17 large tests, or 60 small
  • 1 to 3 business days by size
  • QA report with every test

QA and a written report with every test. Bugs fixed within 24 hours of launch. Three-month minimum, billed monthly in advance. Unused hours roll over to the next month, once. Move between tiers with a week's notice. We estimate every brief in hours before we start, against the size guide, and you approve the estimate. Hours include the build, QA and the 24-hour fix window. Agencies get white-label rates: see agency pricing.

Pilot test

Start with one test

One A/B test, built and QA'd in your tool within 5 business days. Free for agencies. $500 for brands, credited against your first month. If the code is not good enough to launch, you owe nothing.

Request a pilot test

Questions

Before you start an A/B test development project

Straight answers to what teams ask us first.

Do you do CRO strategy or research?

No. We are a development team. The research, hypotheses, analysis and client relationship stay with you; we build, QA and hand over the tests you design.

Which testing tools do you work in?

Optimizely, VWO, AB Tasty, Convert and Kameleoon, through the access you grant. If you have no tool yet, we can run your tests on our own platform at no extra cost.

How fast is turnaround?

It depends on the size of the test: small changes in 2 business days, medium in 3, large in 5 on the Starter plan, faster on Growth and Scale. You get an hour estimate and a date before we start.

How do you count tests?

In hours, against a published size guide: small 2 to 4, medium 5 to 8, large 9 to 14, QA included. We estimate every brief before we start and you approve it, so a big test never squeezes out the small ones.