Data & catalogue
Volume, source quality, transformations, bundles, subscriptions, markets, and reconciliation requirements.
Technical starting points
Clear enough to qualify the fit. Honest enough not to pretend every project is identical.
Find the risk first
Migration readiness audit
From $750
A bounded discovery engagement covering source data, URLs, integrations, target model, launch risk, and the next responsible scope.
See scope detailsFocused improvement
Theme or conversion sprint
From $2,000
A defined group of storefront, mobile, performance, cart, or checkout-adjacent improvements with implementation and validation.
See scope detailsMove platforms
Shopify migration
Typically $8,000-$25,000
Replatforming scope shaped by catalogue, customer and order history, content, redirects, integrations, markets, and launch constraints.
See scope detailsBuild the storefront
Custom Shopify build
From $12,000
A new or substantially rebuilt storefront with technical discovery, reusable templates, integrations, QA, launch support, and handover.
See scope detailsBuild the workflow
Custom Shopify app
From $8,000
Purpose-built admin, portal, integration, or operational software when an existing supported app does not fit the requirement.
See scope detailsBeyond the theme model
Headless commerce
From $15,000
Hydrogen, React Router, or Next.js architecture and delivery when the customer experience or product genuinely requires it.
See scope detailsOngoing roadmap
Embedded engineering
From $1,500/mo
Reserved senior capacity for a prioritised technical roadmap, with explicit monthly outcomes instead of an undefined support bucket.
See scope detailsUnsure whether custom work is justified?
The first useful answer may be a smaller theme change, a supported app, or a discovery phase, not a larger proposal.
Run the free risk reviewWhat shapes the quote
Price follows complexity, responsibility, and launch risk.
Systems
ERP, PIM, WMS, fulfilment, marketplace, finance, customer account, and third-party API responsibilities.
Customer journeys
B2B rules, account flows, configurators, subscriptions, promotions, search, localisation, and checkout constraints.
Launch risk
Organic traffic, revenue concentration, cutover window, freeze periods, stakeholders, rollback options, and peak-season timing.
Content & design readiness
Whether approved design, content models, assets, copy, and decision owners exist before implementation begins.
Operating responsibility
Hosting, monitoring, support, documentation, training, data ownership, and the team maintaining the system after launch.
What the proposal contains
The fixed price is only useful when the boundary is visible.
- Commercial and technical objective
- Named deliverables and acceptance criteria
- Explicit exclusions and assumptions
- Client inputs and decision owners
- Dependencies and third-party responsibilities
- Milestones and review checkpoints
- Launch and stabilisation responsibilities
- Change process for genuinely new scope
Payment structure
Milestones instead of one large leap of faith.
The exact checkpoints follow the project, but larger fixed-scope engagements normally use the existing three-part structure.
30%
Start
Deposit after scope and agreement
40%
Delivery
At agreed implementation checkpoints
30%
Launch
At final delivery or production launch
Get a scope, not a mystery hourly estimate.
Bring the current system, desired outcome, timeline pressure, and known constraints. The first call establishes whether enough is known to quote or whether discovery should come first.