We plan the catalogue, selling templates and business setup together, so the store works for customers and the team running it from launch.
The visible design is one part of the job. Product and variant structure determine what can be sold. Navigation and filters determine whether people can find it. Shipping, payments and tax settings determine whether an order can complete. The admin setup determines whether your team can keep the store current.
We make those decisions before filling pages with content.
If an existing store also needs products, customers, orders or URLs moved, we scope that as a migration rather than hiding it inside the build.
We start with the range, markets and systems orders have to reach. That exposes expensive assumptions early. We use an existing theme when it can do the job well; custom work has to solve a specific requirement.
Your scope states the templates, catalogue limits, integrations, responsibilities and separate costs before the build starts.
Fixed, from-price or scoped after discovery
Migration and build
From £5,000From $6,500
Moving to Shopify and building the store in one project, so the data and the storefront land together rather than in two disconnected pieces of work.
Starting price
Plus, B2B, multi-market
From £8,000From $10,500
Shopify Plus, B2B, multi-market, multi-language, custom integrations or headless work. These configurations are sized after discovery, not instant-priced.
Starting price · scoped after discovery
One bounded piece
£1,500$2,000
One bounded improvement: landing pages, a template rebuild, an analytics implementation, or a build-readiness review credited against a larger project.
Fixed price
Starting figures in GBP and USD, excluding VAT. Catalogue size, the number of distinct templates, integrations and market or B2B requirements are what move a launch build off its starting price.
The build is rarely the constraint. Catalogue data, photography, copy and the decisions only the business can make are what set the date, so the schedule is agreed against those inputs rather than against a standard number of weeks.
Usually not at launch. A restrained adaptation of a well-built theme gets a new store trading sooner and leaves budget for the catalogue and configuration work that actually decides whether it sells. Where the theme itself is the constraint, we say so and explain why.
Yes, once the catalogue model is agreed. The import itself is straightforward. Deciding what a product is, what a variant is and what belongs in a metafield is the part that takes the time and the part that is expensive to redo.
Then it is a migration, and it is scoped as one. Data mapping, redirects, integrations, validation and cutover change the shape and the price of the project, so they are handled on their own terms rather than folded into a launch build.
Catalogue shape, markets and the systems orders need to reach are enough for a useful first scope.
