We diagnose before we quote
Before proposing anything, we buy something from your store on a phone, look at the funnel, list the apps and check the product data. That is half a day and it changes what we would recommend in most cases.
A surprising number of store proposals are written without anyone having gone through the checkout. The friction that costs you sales is usually visible in ten minutes.
A new build
| Weeks | What happens |
|---|---|
| 1 | Structure, collections, product data model agreed |
| 2–3 | Theme setup and key template design |
| 4–6 | Products loaded, delivery and payment configured |
| 7–8 | Content, policies, email templates |
| 9 | Testing, real order, real refund |
| 10 | Soft launch to limited traffic |
Catalogue size and content readiness move that timeline more than anything technical.
An improvement project
Rather than one large engagement, a series of shorter pieces with measurement between them. Fix the highest-effect thing, measure four weeks, then decide the next.
- You see results before committing further
- Each change is attributable
- You can stop at any point
- We are accountable for effect rather than for output
What we need from you
- Access, requested on day one even for things needed in week five
- Product data and images, or agreement on who is producing them
- Your delivery costs and constraints, honestly
- Someone to answer questions within a day or so
- Feedback consolidated into one response, not four separate ones
How we communicate
A weekly note on the same day: what moved, what did not, what we need and whether the date has changed. If something is going wrong you hear it that week.
Nobody enjoys the conversation where a deadline is missed by surprise, least of all us.