A half-finished storeisn't automaticallycheaper than a rebuild

In short

“The store is 80% done, we just need someone to finish it.” We hear that a lot. Sometimes it's true. But often the missing 20% is exactly what makes a store sell: mobile layout, product pages, purchase flow, subscriptions. Before we name a price, we check what's really there.

The case

A brand came to us with a Shopify store they'd started. Products were set up, a theme was chosen, the basic structure was in place. What was missing: clean typography, proper image crops, a layout that works on mobile, the subscription and a clear customer journey. They wanted a price for “finishing it.”

Why “80% done” tells you nothing

Completion is a feeling, not a metric. The visible parts, products and pages, are quick to set up. The time-consuming parts are often the ones you don't see at first glance:

• Mobile layout. Everything looks fine on a laptop, but the layout breaks on a phone.
• Custom code from before. A previous developer's changes have to be understood before you can build on them.
• The customer journey. Often the layout was copied from the old store, weaknesses included.
• Purchase flow and subscriptions. Features that have to work together with apps, payments and shipping.

How we check

1. Access and inventory. What's there, what's usable, what's legacy baggage?
2. Clarify the drivers. How clean is the product data? Is there custom code? Which subscription solution? Is there a brief and are there references?
3. Keep building or start fresh? Sometimes switching themes is cheaper than endless fixes to one that doesn't fit.
4. Only then a fixed price. Based on the actual state, not the perceived one.

In this case, our recommendation was to rebuild the structure and carry over the existing product data, rather than just cosmetically patching the flaws.

Your takeaways

• Plan with the actual state, not the perceived progress. Have the store checked before you set a budget.
• Good product data is almost always reusable. The theme and custom code often aren't.
• Patching isn't automatically cheaper. Lots of small fixes on a weak foundation end up costing more than a clean restart.
• Gather what you have. Brief, references, logins, notes from the previous developer. The more there is, the more accurate the price.

Got a half-built store that never gets finished? We'll take a look and tell you honestly whether building on it or starting fresh is the better route.