WordPress, Shopify or a custom build: how to decide
Choose a website platform from what the site must actually do, including the running costs and the exit costs each option locks you into.
The question is usually asked in the wrong order
Most businesses pick a platform first and discover its limits afterwards. A services firm ends up on a commerce platform and fights it for three years. A manufacturer with a dealer login requirement ends up on a theme held together by eleven plugins. A twenty-product brand commissions a custom build and then cannot change a price without raising a ticket.
The platform is a consequence of two things only. What the site must do that is not negotiable, and who will operate it after launch. Everything else is preference. Answer those two and the choice usually makes itself.
What each option costs you to keep running
None of the three includes your content, your photography or your product data. All three leave you with running costs after the build fee is paid. The shapes of those costs differ and that is the real comparison.
A hosted commerce platform charges a recurring plan fee and sits alongside payment gateway charges on every order. Apps that add reviews or subscriptions or shipping rules each carry their own monthly fee. WordPress has no licence fee but you pay for hosting, for premium plugin and theme renewals and for somebody to apply updates. That last cost is real whether or not you choose to pay it. A custom build has no platform fee and replaces it with dependency on developers who understand the codebase. If that relationship ends the cost of the next one is high. GST at 18% applies to Indian service fees and a subscription billed in a foreign currency also attracts card conversion charges.
Who should rule each one out
Rule out a custom build if your requirements are ordinary. A brochure site, a blog, a catalogue of a few hundred products and a standard checkout are solved problems. Paying to rebuild them buys you maintenance liability and nothing else. Custom work earns its fee when the site must do something the platforms will not do. Dealer logins with tiered pricing, a quotation workflow, live integration with an ERP, or data you are not permitted to put on a third-party platform. That is where custom corporate website development is the right instrument rather than an indulgence.
Rule out WordPress if nobody will own it. It rewards attention and punishes neglect. A business with no internal owner and no maintenance arrangement will have an outdated install within a year and plugin sprawl is how most small sites eventually break. Rule out a hosted commerce platform if you are not selling products, because you pay monthly for a cart you never use. Rule it out too if your revenue depends on deep content or on checkout logic you must control yourself, since the checkout is the part those platforms deliberately keep closed.
A sharper version of that last point. If you sell to other businesses with negotiated prices, credit terms and GST-specific invoicing then a standard commerce checkout will fight you at every step. Test that requirement before you commit to anything else.
How to make the decision in an afternoon
Write down the five things the site must do. Not the things it would be nice for it to do. Then mark the ones that are genuinely non-negotiable. Payments. Catalogue size and how often it changes. Logins. Integration with software you already run. Multiple languages. Who publishes a page on a Tuesday afternoon without help.
Take the single hardest non-negotiable and test each option against only that. The platform that handles it natively wins unless something else disqualifies it. A requirement handled natively on one platform and by three plugins on another is not a tie. Then check the exit before you sign. Can you export products, customers, orders and content in a usable format and can you keep your URL structure if you move.
How to tell whether you chose well
The metric that matters is the cost of a routine change. Time and money to add a page, change a price or publish an offer without involving a supplier. Count the workarounds too. Every workaround is a small recurring tax and they are easy to stop noticing.
The metric that flatters is a feature comparison table. Every platform wins its own table. Scalability flatters in the same way because almost nothing a small business runs comes near a platform's technical limit. The constraint is nearly always your own operating capacity.
The mistake that costs the most
The common mistake is letting the supplier choose. Most agencies build well on one platform and will fit your requirement to it. That is not dishonesty. It is specialisation. The cost appears when a requirement you stated as essential is quietly reduced to a workaround to suit the stack that was already decided.
The expensive variant is choosing custom for prestige. A bespoke site with no documentation, one developer who knows it and no handover is a single point of failure that will eventually be paid for twice. Ask who else could maintain it before you approve it.
The choice is reversible but your data is not
Platforms get replaced and that is normal. What survives a migration badly is accumulated content, review history, customer accounts and URLs that already rank. Keep those portable and the decision stays cheap to revisit. Lock them into a proprietary format and the next move becomes a rebuild.
This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.