Question 1

What does a project cost?

Accepted Answer

It depends on scope, and we won't pretend otherwise. Builds are fixed-price after a scoping week; testing retainers are sized to your traffic and the cadence you want. Either way you get one itemised number before we start, and it doesn't drift.

Question 2

How long before we see results?

Accepted Answer

Builds: 8–14 weeks to launch. Testing: the first experiments ship within two weeks of kickoff, and you should expect a statistically solid read on programme value within one quarter.

Question 3

Do you work with small stores?

Accepted Answer

For builds, yes. Any size. For A/B testing you need roughly 30k monthly sessions or 500 monthly orders; below that, tests take too long to conclude and we'll tell you so rather than take the retainer.

Question 4

What happens in the first two weeks?

Accepted Answer

A scoping week (analytics audit, session recordings, stakeholder interviews), then a readout where we show you what we found and what we'd test or build first. If you walk away after that, you keep everything.

Question 5

What if a test loses?

Accepted Answer

Then it saved you from shipping a loser to 100% of traffic. Losing tests get documented with the same rigour as winners. One of them stopped a client spending $225k on a navigation redesign that would have hurt revenue.

Question 6

How many tests do you run a month?

Accepted Answer

Four to eight per client, depending on traffic. Cadence matters less than power. We'd rather run four conclusive tests than twelve underpowered ones.

Question 7

Which testing tools do you use?

Accepted Answer

Optimizely, VWO, or Convert, whichever fits your stack and budget. We also build server-side tests for checkout and pricing work where client-side tools fall short.

Question 8

Do you test on our live customers?

Accepted Answer

Yes, that's the point. Every test has a QA checklist, guardrail metrics, and an automatic stop rule, so a broken variant never runs long enough to do real damage.

Question 9

Shopify or WordPress: which do we need?

Accepted Answer

Selling products? Shopify, almost always. Content-heavy site with some commerce? WordPress with WooCommerce. We build on both and will tell you honestly which fits. The answer changes our fee by very little.

Question 10

Will our team be able to run the site without you?

Accepted Answer

Yes, that's a design requirement, not an afterthought. Editors get a training session, documentation, and a build that doesn't break when someone changes a homepage banner.

Question 11

Do you migrate our existing data?

Accepted Answer

Products, customers, orders, redirects, and SEO equity are all part of the fixed price. We've replatformed stores with 32k SKUs without losing a ranking.

Question 12

How do you handle site speed?

Accepted Answer

Performance budgets are in the contract: Core Web Vitals targets per template, and every app install after launch gets weighed against its conversion cost.

Question 13

Who actually works on our account?

Accepted Answer

The people you meet in the pitch. No handoff to a junior team. A strategist, a designer, and an engineer are on your account end to end, and you have their direct emails.

Question 14

How do you report?

Accepted Answer

A weekly readout: what ran, what won, what lost, what we learned, what's next. One page, plain English, numbers your board can read. No 40-slide decks.

Question 15

Can we pause or cancel the retainer?

Accepted Answer

Monthly rolling after the first quarter. Pause anytime with two weeks' notice; seasonal brands do it every January.

Question 16

Do you sign NDAs?

Accepted Answer

Yes, and we mean them. Case studies only go public with written sign-off, and revenue figures are always shared as percentages unless you approve otherwise.

Questions we get askedbefore every project.

Answered everything? Good.