Ship It Live — $1,999 flat
Design + build + deploy · kickoff in 24h · limited slots
Ship It Live · e-commerce sprint
A store that sells, live in 14 days.
Not a theme everyone else is running. A store designed around your products, fast on a phone, and live in a fortnight.
Quick answer
A custom e-commerce website can be designed, built and taking orders in 14 days for a fixed $1,999, covering the product catalogue, cart, checkout, payments, shipping rules and order management. Very large catalogues and complex fulfilment integrations are quoted separately.
The plan
Day one to day 14, written down.
You get this schedule before you commit, not after. If a phase slips, that is mine to absorb — the price and the date were agreed before anything started.
- 1
Days 1–2
Catalogue and structure
How your range is organised, what a product page must prove, and your shipping and tax rules. Product structure decided before any design work.
- 2
Days 3–7
Design
The product page and checkout first — the two screens that decide revenue — then collections, home and the supporting pages.
- 3
Days 8–12
Build
Catalogue, cart, checkout, payments and shipping. Image handling gets real attention, because store speed on mobile is a revenue number.
- 4
Days 13–14
Launch
Test orders end to end, payments switched live, analytics connected, and live on your domain.
What $1,999 gets you
Everything needed to launch — nothing padding the invoice.
Who books this
Built for
Brands whose store looks like the same template as their competitors
Businesses selling well on Instagram with nowhere to send people
Retailers losing sales to a slow, cluttered checkout
Real situations
Five ways this shows up, and what actually fixes it.
Not hypothetical — the shape of the problem before someone books this sprint, and the specific part of the build that resolves it.
Situation 1
The store looks like the same template as every competitor
A brand's online store runs on a common theme that visually matches dozens of competitors, doing nothing to differentiate the product on the page.
A custom-designed store built around this specific product range, not a theme with the logo swapped in, ships in 14 days.
Situation 2
Selling well on Instagram, nowhere real to send the traffic
A brand has genuine social selling traction but sends that interested traffic to a generic store page that doesn't match the momentum of the post that drove it.
A fast, custom product and checkout experience gives that social traffic somewhere that actually matches the interest driving it there.
Situation 3
A cluttered checkout is quietly losing sales
A previous store's checkout asks for more information than the order actually needs, and cart abandonment is higher than it should be as a result.
A short checkout — guest allowed, as few fields as the order needs — is built specifically to remove that friction.
Situation 4
Local payment methods the market actually expects are missing
A store selling into a specific region only offers card payment through a generic processor, missing the local payment methods customers there expect and prefer.
Local payment methods are configured for the actual market being sold into, decided on the call rather than defaulting to one processor everywhere.
Situation 5
Slow product pages on the mobile data most customers actually use
A previous store handled product images naively, and pages load slowly enough on real mobile connections to cost sales before anyone sees the product.
Image handling gets deliberate attention because store speed on mobile data is, directly, a revenue number.
The honest part
When 14 days is the wrong answer.
A fixed deadline only works when the scope genuinely fits inside it. These are the cases where I will tell you so rather than take the booking.
Catalogues in the tens of thousands of SKUs with complex merchandising rules — a bigger project with a bigger number.
ERP, 3PL or warehouse-system integrations, which are quoted once I have seen the API you are integrating with.
Marketplaces where many independent sellers list and get paid out. That is the marketplace sprint.
Inside the 14 days
- Custom design — no theme with your logo dropped into it
- Product catalogue with variants, options, galleries and stock
- Collections, search and filters that suit how people browse your range
- A short checkout — guest allowed, as few fields as the order needs
- Payments through Stripe, plus local methods where your market needs them
- Shipping zones, rates and tax rules configured for where you sell
- Order management, confirmations and status emails
- Source code, design files and 30 days of support at handover
Quoted as one number before day one. A week running long is mine to absorb.
Outside the line
- Catalogues in the tens of thousands of SKUs with complex merchandising rules — a bigger project with a bigger number.
- ERP, 3PL or warehouse-system integrations, which are quoted once I have seen the API you are integrating with.
- Marketplaces where many independent sellers list and get paid out. That is the marketplace sprint.
Real work, sized and priced separately. You hear it before you book, not at handover.
Questions
Before you book
Shopify is genuinely the right answer for many stores, and I will say so rather than sell a build. Custom wins when the buying experience is part of your brand, when app subscriptions have stacked up, or when your product needs a configurator no theme supports.
Other sprints
14 days from now, this could be live.
A 30-minute call decides whether the scope fits. If it doesn't, I'll tell you what would.