For CRO agencies
White-label test builds
for CRO agencies.
You run the strategy and the client relationship. I build the tests. Your clients only see your agency.
Floor I · The tests
Your first test, step by step.
Your first test
Brief to Winner
Step 1
Brief
I ask my questions at the start, not in the middle of the build.
You send
- 1HypothesisThe hypothesis, in one sentence.
- 2PageThe page URL, and the template if several pages share it.
- 3DesignThe design: Figma, a mockup, or a clear written description.
- 4MetricWhat counts as success: the main metric, and any secondary ones.
- 5AccessThe testing tool, and collaborator access to the store.
- 6DeadlineThe deadline, if there is one.
Step 2
Build
I code the variant: no flicker, tracking events in place.
A simulation on a made-up page: the test script is slowed down on purpose.
Flicker-free A/B tests →Step 3
QA on desktop and mobile
I check the variant on both, in the main browsers.
You get back
HandoverSample
- ChangesProduct page template: the button text, a stock line above it.
- Off switchVariant on. One switch turns it off.
- Events
variant_view · add_to_cart_click - QA notesChecked on desktop and mobile, in the main browsers. Known limits: none.
Before the test goes live, with a preview link for each variant.
Step 4
Launch
The test goes live in your testing tool. I check that the first data comes in correctly.
If the test breaks while it is live, I fix it immediately.
First data in on both sides.
Step 5
Winner coded into the theme
When a variant wins, I rewrite it as clean, permanent theme code and remove the test code.
Theme codeSample
{%- if product.available -%} <p class="stock_line">In stock · ships today</p> {%- endif -%} <button class="add">Add to cart · Free returns</button>{%- if product.available -%} <p class="stock_line"> In stock · ships today </p> {%- endif -%} <button class="add"> Add to cart · Free returns </button>Clean and permanent.
Under your name.
Built byDylan Castor
Delivered byYour agency
White-label
I work under your name, inside your process and your tools.
Under NDA
I sign your NDA before I see any client data.
I never contact your clients
unless you ask me to.
Only the access a test needs
Collaborator access to the store, removed when you want.
You keep the strategy
The hypothesis, the design and the words come from you. I build the test.
Paris time
I work from France, on Paris time.
After the first test.
If it works for you, we move to a fixed number of days per month.
Your tests stop waiting for a free developer.
Monthly pass
Days per month
- Holder
- Your agency
- Valid
- Every month
All floors · The method
Tests first, small files, every change checked: the code your clients inherit stays clean.
Dylan Castor
Every test is built by me, Dylan Castor: no one else touches your client’s store.
I build tests for high-ticket Shopify stores in the US and Europe.
Have a test to build?
Pick one test from your backlog. I build it at my normal rate. You judge the quality, the speed and the handover.
The message did not go through. Nothing is lost: try again, or email me directly.