Launching the store is easy; keeping it running is the real work

Your Shopify, Webflow, or WooCommerce store can look flawless on launch day. Six months later, the question is no longer “which CMS did we pick?” — it’s who keeps inventory, checkout, reporting, and the plugins that break with every update.

In agency and ecommerce communities, the same fatigue shows up: platform limits, investment and control stay with the platform, a “manageable CMS” that falls apart as the business grows. The lesson from the agency desk —not from forum venting— is different: SaaS (software as a service: you pay to use a cloud platform) is often fine at the start. The real cost shows up after launch.

Building on a third-party platform speeds the go-live: payments, hosting, themes, apps. For a LatAm B2B that needs to sell now, that matters. At Somos Gente Digital there is no anti-SaaS ideology: if the stack lets you operate, use it.

The mistake is treating launch as the end of the project. Day one validates the channel; day one hundred validates whether you can control the operation —access, data, integrations— or whether investment and control stay with the platform.

What we see with clients (and what shows up in webdev and ecommerce communities) is not “Shopify is bad.” It’s accumulated operational debt:

• Plugins and apps that patch a gap, then break checkout or the theme on the next update.
• Checkout and payments tied to platform rules: what looked flexible in the pitch becomes an endless ticket.
• Inventory / supplier / ERP sync: the storefront looks fine; stock and prices live elsewhere. Without a clear owner of sync, ops lives in spreadsheets.
• Reporting: marketing wants one number, finance another, the platform exports a third. Nobody has a source of truth in the business’s name.

That is not fixed by swapping CMS logos. It is fixed with operational control (ownership): who holds the keys —admin, data, repos— and with ongoing support (retainer): month-to-month maintenance —sync, security, reporting, evolution— not a “closed project” and goodbye.

Operational control, in practice: access in the client’s name, documentation, code or configs that don’t die if the agency changes, and clarity on what lives in SaaS vs what is custom.

Ongoing support: the agreement to sustain what the business needs each month — not only “fix tickets.” Inventory/supplier, reporting, deploys, monitoring. If the product you sold was only the launch, the client discovered the real cost once they were already in production.

At SGD the blog is a channel; the work is B2B web/tech. When someone asks “Shopify or custom?”, we almost always reframe: can you operate next month without depending on a fragile plugin? Who maintains the sync?

Headless means separating the front (what users see) from the back (catalog, checkout, CMS): content travels over an API. Custom means building what SaaS won’t let you do without a fight.

This is not ideology. It is when SaaS already blocks the business: B2B pricing rules, multi-warehouse sync, checkout that doesn’t fit the app store, reporting that needs an extra link. If you haven’t hit the ceiling yet, headless is premature cost. If you have, stacking more plugins is more expensive than designing what’s missing.

For owners and ops already living on Shopify, Woo, Webflow, BigCommerce, or another SaaS:

1. Name who holds the keys: who has admin on the platform, the domain, analytics, repos, and the ERP?
2. Inventory the sync: stock, prices, orders, invoicing — who writes what, and how often?
3. List critical plugins: which ones touch checkout, payments, or stock? What happens if one breaks on a Friday?
4. Define maintenance vs project: is there monthly budget to sustain, or only “we launched and done”?
5. Separate marketing from the stack: a pretty theme does not fix a feed or a disconnected ERP.
6. Ask about the ceiling: what can’t you do today without a plugin or a hack? Write it down before renewing the plan.
7. Pick the next step: stay on SaaS with clear ongoing support, or map headless/custom only where SaaS blocks you.

What is SaaS in this context?

Software as a service: you use a cloud platform (Shopify, Webflow, etc.) for a subscription. You don’t “own” the engine; you rent capacity and the vendor’s rules.

Is operational control the same as “having the code”?

Not only. It’s who controls access, data, integrations, and the ability to change vendor or agency without starting from zero. It can include code; it always includes keys and clarity.

What is ongoing support?

A month-to-month agreement for maintenance and evolution — not a launch project. It covers sync, security, reporting, deploys, and the work that appears after go-live.

Is headless mandatory to grow?

No. Headless (front separated from back via API) makes sense when SaaS already limits checkout, sync, or experience. If SaaS lets you operate, use it and pay for serious maintenance.

Is this anti-Shopify / anti-Woo?

No. It’s anti the illusion that the CMS is the product. For LatAm B2B, the product is being able to operate: inventory, orders, reporting, and the keys in your name.

Is this the same as choosing between BigCommerce and Shopify?

No. That post compares platforms; this one is about who holds the keys and maintenance after launch.

If you're choosing between BigCommerce and Shopify for LatAm, that's a different arc. If the pain is already who holds the keys, sync, and maintenance —not the CMS logo— see ecommerce that fits your business or write us via Contact.