We start as a customer
Before looking at any code or analytics, we go through your store the way a shopper would: on a phone, on mobile data, looking for a product and buying it.
That half hour tells us more than a week of reports, because it surfaces the friction that the people who built the store have stopped noticing.
Then the numbers and the bill
- The funnel — where sessions actually drop out
- Conversion by traffic source, not just overall
- The app list, what each costs and what each loads
- Product data consistency across the catalogue
- Page weight on the three main page types
The app audit alone frequently pays for the engagement. Overlapping apps and forgotten subscriptions are close to universal.
What we usually recommend against
- Rebuilding when three specific fixes would do it
- Changing platform without a requirement the current one cannot meet
- Adding an app to solve a problem apps caused
- Custom development where a theme setting exists
- Personalisation and recommendation engines below the data volume that makes them work
How we communicate
A weekly note saying what moved, what did not, what we need from you and whether the date has changed. Short, honest, and on the same day each week.
If something is going wrong you hear it that week, not at the deadline.
What you are left with
| Yours | Always |
|---|---|
| The Shopify account | In your name |
| Any custom code | In a repository you own |
| Documentation of every change | Written down |
| The ability to change supplier | Without losing anything |
We would rather be kept because the work is good than because leaving would be difficult.