Hosted platforms
Themes, apps and platform-native logic on SaaS stores.
- Shopify
- Shopify Plus
- BigCommerce
- Wix
- Squarespace
- Ecwid
- Lightspeed
From Gothenburg, I build, migrate and fix online stores on any platform, and I know the systems around them: payments, ERP, shipping, feeds, search and tracking. Years of building and fixing stores showed me where they actually break: the checkout, the catalog data and the integrations, usually on a Friday. I use AI agents to move faster, and I review every change myself.
ShopifyBigCommerceWooCommerceMagentoHeadlessand the rest of the stack
A store is a platform plus a dozen systems around it. This is what I work with. Search for the one you use.
12 layers · 138 tools
Platforms
Themes, apps and platform-native logic on SaaS stores.
Custom plugins and modules, performance work, hosting and upgrades.
Large catalogs, price lists, approvals and ERP-heavy setups.
Custom front ends on commerce APIs, with the CMS, search and checkout wired in.
Front ends and hosting
Commerce APIs
Content
Around the store
Cards, wallets and pay later, with webhooks that don’t double-charge or drop orders.
Rates, labels, tracking and hand-offs to warehouses.
Orders, stock, prices and product data, synced both ways with retries and readable logs.
ERP
PIM
Inventory and orders
Middleware
One clean catalog, published to every channel that sells it.
Marketplaces
Feeds and catalogs
Finding, filtering, recommending and bundling.
Email and SMS flows, review and loyalty programs, subscriptions and helpdesks.
Email, SMS and CRM
Reviews, loyalty and subscriptions
Support
VAT and sales tax, cookie consent, and selling in more than one market.
Tax
Consent
Markets
Event models, server-side tracking and dashboards. See the marketing page
No match, but the list is long, not complete. The fundamentals carry across platforms, so email me what you run and I’ll tell you how well I know it.
A fast, on-brand storefront that your team can manage without me.
From any platform to any other, with catalog, customers, orders and SEO intact.
A custom front end on commerce APIs, with the CMS, search and checkout wired in.
The thing your store needs that no off-the-shelf app does properly.
Orders, stock, prices and product data that stay in sync, and fail loudly instead of silently.
Providers connected so payments reconcile, shipping rates are right and tax is calculated where it should be.
One clean catalog, published to Google, Meta, TikTok and the marketplaces that sell it.
Bundles, tiered pricing and checkout changes that raise conversion without breaking payments.
Find what’s slowing the store down, fix it, and put a budget in place so it stays fast.
Help shoppers find things and buy them, then prove the change worked.
Clean events, server-side tracking and consent that works, so every channel optimizes on real data.
Answers order and return questions from your real data, and hands over to a person when it should.
Four quick questions point to a column below. It’s a starting point, not a verdict, and the stack above has more options than these five.
| Shopify | BigCommerce | WooCommerce | Magento | Headless | |
|---|---|---|---|---|---|
| best for | Most stores. Fast to launch, low maintenance. Plus for scale. | Mid-market and B2B stores that want SaaS with more built in. | Content-led stores and teams that want to own the stack. | Very large catalogs and complex B2B. | Brands where the front end is the product. |
| hosting | Included and managed for you. | Included and managed for you. | You choose and manage it, or use managed WordPress hosting. | Self-hosted or Adobe’s cloud. Both need experienced developers. | A front end on an edge host, plus a commerce backend as a service. |
| customization | Themes, apps, Functions and checkout extensions. | Themes, apps, a strong API and a customizable checkout. | Anything PHP and WordPress can do. | The deepest. Everything is a module. | Unlimited on the front end. You build what a platform normally gives you. |
| maintenance | Low. The platform updates itself. | Low. The platform updates itself. | Medium. Core, plugins and hosting all need updates. | High. Needs a dedicated developer. | High. Two systems to run: the storefront and the backend. |
| team you need | None, or a part-time developer. | None, or a part-time developer. | A part-time developer. | In-house or retained developers. | A development team, in-house or retained. |
| i’d pick it when | There’s no strong reason not to. | You want built-in B2B tools or several storefronts, without running servers. | You already run WordPress, or need full control. | You already have it and it earns its keep, or you need what only it does. | Speed, brand experience or multi-channel reach justify the extra cost. |
Four steps, tracked like an order. Nothing touches your live store until it has passed the one before.
We agree scope, platform and what “done” means. You get a written plan.
Agents scaffold and write code against the plan. I review every diff. Work happens on a dev store or staging, never live.
Automated tests, real checkouts in test mode, and checks for redirects, tracking and speed.
A scheduled cutover, monitoring afterwards, and documentation for your team.
Very likely. The stack above is long but it isn’t complete. Catalog data, checkout, integrations and tracking work the same way on every platform, so the fundamentals carry over. If I haven’t used a specific tool I’ll say so, and learn it quickly. Email me what you run.
Yes. Every old URL gets a 301 to its new equivalent, and I compare indexed pages before and after. Metadata, structured data and internal links are checked as part of QA. Redirects are boring, which is exactly what you want from them.
Yes. Changes happen on a dev store or staging first, and go live through a reviewed release. I never edit a live store directly. Live stores are for customers, not for experiments.
Faster delivery and more tests for the same effort. It doesn’t change who is responsible: I read the code and I stand behind it. The agents are fast, but they don’t sign anything.
Use the comparison above. The short version is Shopify unless you have a specific reason not to, and headless only when the front end is the product. If your situation is odd, tell me and we’ll look at it properly.
Yes. See the marketing page. Tracking is usually the first thing I fix on a store, because everything else depends on it. For how I think about Meta ads for a store, read my take on Jon Loomer’s Master Brief, or the short answers.
Add the services you’re interested in to your brief and email it to me. I’ll reply with questions and a proposed plan. A rough brief is fine; the questions are part of the job.
Add what you need to your brief and email it, or just write to me and describe the store. Rough notes are fine.
Nothing here yet. This cart only holds a brief, so there is nothing to pay for. Add services from the list and they’ll appear here, then email the brief to me when it looks right.
This opens your email app. Nothing is sent from this page.