Path A: Shopify for a hosted online store
Shopify provides a hosted ecommerce platform for products, orders, and checkout. A theme is the store's starting design. Start with its theme editor and built-in tools, then consider apps — add-ons for extra features — only when you need them. AI can draft product descriptions, suggest page layouts, and help with compatible theme code. Shopify themes use Liquid, a template language that places store information into pages, along with HTML for page structure, CSS for styling, and JavaScript for behavior. A supported Custom Liquid area or theme code editor is not permission to paste any whole website into Shopify. Arbitrary HTML cannot replace its full product, payment, inventory, and order system. Checkout has its own rules and supported customization methods. Available changes depend on your plan, theme, apps, and developer permissions; confirm current documentation before paying for a promised feature. Save a theme copy before code changes and test it before making it live. You do not need custom code for every store.
Path B: an AI site or app builder, such as Lovable
An AI builder can turn a description into a functioning website or app project, not just a picture. That does not mean every generated feature is ready for customers. A booking screen could still need a booking service; a payment screen needs a properly connected payment provider; saved customer information needs protected storage and access rules. These connections are service configuration — setting up the services the project depends on. For a simple public service page, you may not need any of them. In Lovable, review and test the project, use its publishing process, and connect a custom domain if you want one and your plan supports it. A preview is for checking work, not proof that the public version works. Confirm what is public, what requires sign-in, and whether private information could be exposed. Plan for fixes, future updates, and ongoing service costs. The Lovable course lives inside ChatGPT & AI.
Path C: WordPress, Wix, or Squarespace
Traditional builders and managed platforms let you start with a design and edit pages without writing everything from scratch. Wix and Squarespace offer hosted site-building services; selling and booking features depend on their plans and supported tools. WordPress needs one extra distinction: WordPress.com is a hosted service with plan-dependent features, while self-hosted WordPress software needs a suitable hosting provider and someone responsible for updates and backups. A managed WordPress host may take on some of that work — ask what is included. Plugins are add-ons for WordPress; some provide ecommerce or bookings. AI can help with page wording and explain supported changes, but a platform may limit scripts, code editing, plugins, or outside services. Check the exact platform and plan rather than treating all WordPress or website-builder offerings as the same.
Path D: a custom-coded website
A custom-coded site is built from code rather than mainly from a builder's ready-made editing tools. AI may write a starting version, but someone must understand how to run, test, and maintain it. Suitable hosting depends on what the code does: an information-only site is different from a tool that stores bookings or processes requests on a server, a computer service doing work behind the scenes. A folder of code or a saved file on your laptop is not a public website. You need a deployment process, hosting, and ongoing checks. For sales, use a suitable established checkout or commerce service rather than asking AI to invent card handling. Custom code can be useful for a genuinely unusual feature, but it is not automatically cheaper, safer, or necessary for a small business.
A practical comparison, not a winner for every business
Shopify brings products, stock, orders and checkout together; learning its store tools is usually simpler than assembling a custom store, but themes, checkout changes, apps and exports follow platform rules. Wix and Squarespace offer hosted editing and templates for straightforward service sites; they reduce hosting work but limit portability and advanced customization. WordPress software offers a wide range of themes and plugins and more hosting choices; you or a managed provider must still handle compatible updates, backups and security. Lovable can generate custom pages and app behavior and offers code access options; you still need to understand, test and maintain what it builds, especially connected services. Custom coding offers more control over the design and rules, but usually brings the greatest technical learning and support responsibility. None is automatically cheapest or safest.
Three realistic paths
For a vintage-doll resale store, compare Shopify first: product condition photos, one-of-a-kind stock, shipping or pickup, and supported checkout belong together. For a cleaning service, compare Wix or Squarespace: services, service area, contact details, and a supported request or booking tool may cover the job without custom code. For a customizable community app, compare Lovable or another AI builder: event filters or a simple calculator may fit, but saved member data, accounts or payments need careful service setup and review. An existing tool may still be easier than building your own.
Keep control of your work and understand what can move
Keep the domain and main site account under your or your business's control, with recovery access you can use. Use your own photos or properly licensed materials — material you have permission to use — and check provider terms about your content and AI output. Owning your writing is not the same as owning a platform's software or every theme and app. Export means downloading a supported copy; it does not guarantee the same site will run somewhere else. Shopify can export supported store data and theme files, but that is not a portable copy of its entire hosted commerce system. Lovable supports a GitHub connection for project code; GitHub stores code history and copies. Moving that code may still require new hosting, service setup, and data transfer. WordPress.com offers content exports, not necessarily a complete site with its design and plugins. Wix's complete sites depend on Wix hosting and cannot simply be exported to another host. Squarespace exports selected content, not its entire site design and every feature. Before committing, ask what can move, in what format, what stays behind, and who will do the work. If hiring someone, agree in writing on account access, content and code rights, copies, licenses, and handoff.
Budget for staying open, not just building once
Compare setup charges and ongoing costs: platform or hosting subscriptions, domain renewals, themes, apps or plugins, email, payment fees, AI usage, and outside services. An introductory price may differ from the renewal price. A payment provider may charge transaction fees — charges for processing each payment — in addition to other platform charges. Check current terms for your country, business, and plan; there is no one price that fits everyone. Ask what happens if you cancel a plan or stop paying for an app. Set renewal reminders and keep a private list of providers and costs. Budget some time or money for updates, repairs, and content changes, even when AI helped create the first version.
Compare total cost and the effort to leave
Cost types include initial setup, monthly or annual plans, domain and email renewals, paid themes, plugins or apps, payment and platform fees, storage or traffic usage, and outside help. Ask what happens when a paid add-on stops, what you can export, and how much work a move would take. An integration is a connection between services; compatibility means the exact connection works with your plan and tools. Verify the supported method before committing. Exporting writing or products does not necessarily move design, checkout, customer accounts or app behavior.
A real-world example
A cleaner compares two builders by creating a services page and trying its request form. A doll seller tries one sample product and a supported test order in Shopify. A community group asks Lovable for a public event filter using fictional events first. Each tests its own customer task instead of choosing the longest feature list.
Steps to take
- Choose products, services, or a custom tool as your main path.
- Compare two suitable platforms using your must-have features.
- Try one realistic customer task in a draft.
- Check integrations, account ownership, export limits, total costs and cancellation effects.
- Choose the setup you can maintain and record the reasons.
My choosing your website path check
This checklist is optional and not saved. Copy it to keep a personal note. Do not enter sensitive information.
Go deeper in related modules
Not sure what a word means? Check Business Words Made Simple.
Official provider guides
Independent resources, not P.E.A.C.E. partners or recommendations. Check current terms before buying.
- Shopify: exporting products (opens in a new tab)
A product data export is different from moving an entire store.
- Lovable: publishing your project (opens in a new tab)
Review the steps for making a tested project public.
- Lovable: GitHub connection (opens in a new tab)
Code sync and copies; moving a project still requires suitable hosting and services.
- WordPress.com and self-hosted WordPress (opens in a new tab)
Understand the difference before comparing hosting and maintenance.
- WordPress.com: content exports (opens in a new tab)
What a content export includes and what it leaves behind.
- Wix: hosting and export limits (opens in a new tab)
Why a complete Wix site cannot simply move to another hosting provider.
- Squarespace: exporting your site (opens in a new tab)
Selected content can be exported; not every feature or design transfers.
