Built with the experience of running one.
Most development shops have never had to hit a monthly number on a store. We build yours with the expertise we've earned running multi-million Shopify stores. Whether it's a new store, a custom app, or the middle layer between Shopify and your ERP, every decision is made by an ecommerce operator first and a developer second.
What we build.
Stores.
Migrations to Shopify from WooCommerce, Magento or custom platforms, rebuilds of stores that were built for a smaller business, and first stores for brands going direct. Catalogue, customers and orders carried across.
Custom Shopify apps.
When an off-the-shelf app doesn't exist or doesn't fit your needs exactly, we build our own: the tools and apps your ecommerce operation needs, working the way your team works.
Integrations and middle layers.
Shopify talking to your ERP, warehouse, supplier feeds and accounting. Orders pushed, stock synced, availability rules enforced, with the error handling that stops a bad feed becoming a bad week.
Automations and event triggers.
Order, booking and customer events wired into the tools your team already runs: email flows, WhatsApp notifications, digital delivery, internal alerts.
Ongoing development.
A store keeps changing after launch. Keep working with us on your ongoing development requirements: fixes, new features, app updates and integrations, with a written log of what was done and why.
Theme and storefront work.
Conversion-led changes to templates, sections and checkout, specified from data rather than taste, and tested before they go live.
A store isn't finished when it launches.
It's finished when it can be run.
The Agenda Bookshop replatform carried 1.2 million titles, new middleware between the ERP and the Nielsen book feed, and search that could handle the catalogue. It also shipped with daily reporting, a weekly rhythm and owners for every area, because a store nobody can read is a store nobody can grow. That's what our fractional practice brings to every project.
What we've built.
Four stores, four different problems, one standard of build.
Agenda Bookshop — Shopify Plus replatform → — a rebuilt store carrying 1.2 million titles: new middleware harmonising the ERP and the Nielsen book feed, order push and stock sync with availability rules, search and filtering built for a million-title catalogue, and a redesign built for conversion. Ongoing monthly development since launch.
Jimmy Joy — two Shopify Plus stores into one → — a Dutch store and a worldwide store consolidated into a single Plus store: one catalogue, one checkout, half the operational surface, on a subscription-heavy model with a catalogue that changes constantly. Every change since is made once.
JYSK Malta — development run to a standard → — work that used to ship wrong and late, re-specified with a briefing standard and scheduled ahead of time, alongside full-funnel reporting built so management could see conversion, order value and checkout drop-offs, not just daily sales.
High Street Culture — a store from zero → — full architecture directed end to end: the store, logistics, supplier and pricing setup, and a retention system built for a category where paid acquisition is mostly off the table.
How a project runs.
Initial call
You meet the project lead and our technical lead. We ask the questions that decide whether this is a build, a fix, or something else.
Scope
We map what you have and what you need, in writing, before anyone quotes anything.
Fixed quote
A written quote against that scope. If the scope changes, the quote is revised. It never changes silently.
Statement of work
Deliverables, milestones and timeline, signed by both sides.
Build and QA
Our developers build; our ecommerce team tests against the way it will actually be used, not a tick-list.
Launch and handover
Cut-over, first-week monitoring, and a handover that leaves your team able to run it.
Why it's different.
Same team, same standards as the fractional practice. The build is where the operating system starts.
Operators lead, developers build — the person running your project has run stores, and the developers work to our process under our project lead.
Scoped before it's quoted — you see the scope in writing before you see a price, and the price holds to that scope.
Built to be run — reporting, an operating rhythm and playbooks from our fractional practice can be scoped into the project, so the store is manageable from the day it launches, not the day someone gets round to it.
One accountable lead — the person you meet on the first call is the person accountable at launch.
Let's talk about your project.
A short call with the project lead and our technical lead. You leave knowing whether it's a build, a fix, or neither.