Proven Hacks for Growing Your Business: Insights from the Trenches

This is where I share the advanced concepts, strategic thinking and real world methods that drive sustainable growth in SaaS, ecommerce and digital business. Everything I publish is based on lived experience and tested systems across performance marketing, data science, product design and customer journeys. I keep the language clear and free from unnecessary jargon, but I do not oversimplify. Real growth is complex, and my aim is to make that complexity accessible without losing what makes it powerful. Whether you are looking to scale faster, make smarter decisions or fix what is underperforming, these insights are built to help. If you need help applying anything or want to explore what is possible for your business, feel free to get in touch.

One payment account across many stores

Once you own your processor account, many storefronts, brands and a mobile app can share one vault and one customer list, or split by choice. The patterns, where separate accounts are right, and the real weight of a marketplace.

B2B ecommerce on Solidus: price lists, quotes, net terms and VAT

How a wholesaler sells to trade customers online on Solidus: company accounts, contract price lists, quotes as orders, pay on invoice with a credit check, late payment law, VAT by delivery address after Brexit, invoices and e invoicing, ERP sync, what to build first and what it costs.

Migrating away from Sylius to a custom Solidus store

The fairest guide in the series, because Sylius and Solidus are peers: both are open source commerce frameworks you own, one on Symfony and PHP, the other on Rails and Ruby. There is no lock in and no data to rescue. Leaving Sylius is a deliberate language and ecosystem choice. What you own, the little that is tied, the clean database and API export, passwords, payments, and who should simply stay on Sylius.

Subscriptions you actually own

Run recurring billing in a processor account you own, and your plans, schedules, mandates and tokens survive a change of storefront untouched.

Payments that move with you

If you own your payment processor account, you can change storefront, framework or platform without migrating a single saved card, because the vault already sits in an account that is yours.

How card tokenisation actually works

A saved card is a token that stands in for a card number held in your processor's vault. How hosted fields, network tokens and SCA fit together, and why owning the processor account keeps your customers' cards portable and your PCI burden light.

Own your payment stack

The card vault lives at your processor, not your shop. If the processor account is yours, your saved cards, customers and subscriptions stay portable.

Personalisation without surveillance

Tracking is dying and most visitors refuse it, yet you can still personalise for everyone. I show the five levers that work without cookies and stay fully GDPR compliant.

Migrating away from osCommerce and Zen Cart to a custom Solidus store

The honest guide to leaving the legacy open source carts osCommerce and Zen Cart for a custom Solidus store. Because they are self hosted you own the MySQL database, so the data comes out cleanly. The real reason to move is age: ageing architecture, a dated add on ecosystem, security and PHP version pressure, and a shrinking pool of developers who know these systems. What travels, what is locked, the database reality, passwords, payments and the redirect map.

Multi tenancy in Rails: the decisions that are expensive to reverse

A handful of decisions in the first month of a SaaS decide what the next ten years cost. How to keep one customer's data apart from another's in Rails, where the tenant lives in the code, Postgres row level security, users in several companies, tenant versus billing account, and why the isolation model is also your GDPR strategy.

Migrating away from Saleor to a custom Solidus store

Saleor is a capable open source, GraphQL native commerce platform, and the code and data are yours. The honest reason to leave it for a custom Solidus store is fit, not lock in: one owned Rails application, one accountable builder, and an exit from Saleor Cloud pricing. Here is what moves, what is locked and how the move really works.

Migrating away from the GoDaddy online store to a custom Solidus store

The honest guide to leaving the GoDaddy online store, the commerce side of Websites + Marketing, for a custom Solidus store you own: what the product CSV, the order download and the customer list hand over, the Commerce API that opened up in August 2026 and ties to GoDaddy Payments, the traps around the closed builder, saved cards and SEO, the fact that the domain is portable even when the store is not, and the honest shape of the move.

Competitor price monitoring in the UK and EU: what is actually legal

Every shop owner wants to know what the competition charges, and every one asks the same question first: are we allowed to? A plain language map of the rules in the UK, the EU, Germany and Austria: why prices are facts, where the database right reaches, what the Ryanair cases decided, where logins and blocks draw the line, text and data mining, GDPR, and the competition law trap nobody mentions.

Migrating away from Medusa to a custom Solidus store

Medusa is open source and self hosted, so you already own your data and your deployment. The honest reason to leave for a custom Solidus store is fit and the engineering model, not lock in. What moves cleanly, what to plan first, and who should stay.

Migrating away from Weebly to a custom Solidus store

The honest guide to leaving Weebly for a custom Solidus store you own: what Weebly is now that Square owns it and steers new shops to Square Online, what the order and item exports really hand over, the Weebly specific traps around the closed builder, saved cards held by the gateway and the URL redirect map, and the honest shape of the move.

Migrating away from Big Cartel to a custom store you own

The honest guide to leaving Big Cartel once you have outgrown its product caps and simple feature set, for a custom Solidus store you own: what exports, what is locked, how its CSV export and V1 API really work, and why your Stripe payments quietly stay in your hands.

Commission Based Pricing Month by Month: The Worked Example

One invented hamper shop in Leeds, ÂŁ1.8 million a year, walked through twelve months of my commission model: the baseline agreed before the start, the base rate or the commission each month (whichever is higher, never both), exactly what the commission is calculated on, a slow case and a bad case, what happens when you want out, and what the same year would cost on a package.

Migrating away from Swell to a custom Solidus store

What leaving Swell, a headless commerce backend, for a custom Solidus store you own really involves: how its Backend API and data model actually export, the annual sales ceiling and the API meter, the card vault and subscriptions, and the honest shape of the move.

DACH payments in Solidus: Kauf auf Rechnung, SEPA, Klarna, EPS and TWINT

The build side of selling into Germany, Austria and Switzerland: which payment methods each market expects, with sourced shares, and how each one is wired into a Solidus store. Payment methods per country, Stripe for cards, SEPA, EPS and TWINT, a specialist or your own process for pay on invoice, what invoice does to the order flow, reminders under German law, fraud, refunds, reconciliation and what the wrong mix costs.

Migrating away from Square Online to a custom Solidus store

The honest guide to leaving Square Online for a custom Solidus store you own: the ecosystem coupling that ties the website, Square Payments and the Square till together, what the item export and the Catalog, Customers and Orders APIs hand over cleanly, the Square specific traps around cards on file, subscriptions, the shared point of sale catalogue and the builder's SEO ceiling, and the honest shape of the move.

What is a smart website? Pages that adapt to the ad that brought you here

Most businesses pay for ads that promise one thing and then send everyone to a page that says another. A smart website closes that gap: one canonical page for search engines and cold visitors, shaped versions that continue the ad a visitor clicked, remembered only with consent, tested against real enquiries, and edited through the client portal instead of a CMS.

Migrating away from Lightspeed eCommerce to a custom store

The honest, specific guide to leaving Lightspeed eCommerce, the hosted online store Lightspeed calls eCom (C Series): what it exports cleanly as CSV, how the eCom API and its rate limit behave, the point of sale and payments lock, and the shape of a careful move onto a store you own.

Migrating from Shopify or Magento to Solidus: the five year total cost of ownership

A worked five year cost model for a shop paying more every year for a platform it does not own: Shopify and Magento with apps, agency, transaction fees and forced upgrades, against a Solidus build, hosting and maintenance, discounted to today. Then the migration itself: what moves and what cannot, passwords, saved cards, customer data law, the redirect map and the cutover.

Migrating away from OpenCart to a custom Solidus store

The honest guide to leaving OpenCart for a custom Solidus store. Because OpenCart is open source and self hosted you already own the MySQL database, so the data comes out cleanly. The real reasons to move are the tower of paid extensions, the painful major version upgrades, and the business rules hidden in modifications. What travels, what is locked, the export and API reality, passwords, payments and the redirect map.

Migrating away from Shift4Shop to a custom store

The honest guide to leaving Shift4Shop for a custom Solidus store I build and you own: the free plan tied to Shift4 Payments, the CSV and REST API reality, what exports cleanly, what is locked, and a worked move plan.

Migrating away from Volusion to a custom Solidus store

The honest guide to leaving Volusion for a custom Solidus store you own: what the CSV export and the ageing XML API really hand over, the hundred record export cap and the password in the URL, the Volusion specific traps around checkout, saved cards, themes and URLs, and the calm shape of a move onto a shop you control.

Migrating away from Ecwid to a store you own

An honest guide to leaving Ecwid by Lightspeed, the store you embed into a site you already have, for a custom Solidus shop. What the REST API hands over, what the widget keeps, and how a clean move actually runs.

Migrating away from Salesforce Commerce Cloud to a custom store

An honest guide to leaving Salesforce Commerce Cloud, formerly Demandware, for a custom Solidus store: the revenue share that taxes growth, what exports and what is locked, the Business Manager archives, OCAPI and SCAPI, and who is right to stay.

Migrating away from Wix to a custom store

Wix is the most closed of the common builders, so the honest story of leaving it is about the limits of what you can get out. What exports cleanly, what is only partial, what you have to rebuild, and how a careful move onto a custom Solidus store you own actually works.

Migrating away from Shopware to a custom Solidus store

The honest guide to leaving Shopware 6 for a custom store I build on Solidus: the edition tiers and the Fair Usage Policy, what the Import/Export feature and the Admin API hand over, what stays locked in gateways and plugins, and the honest shape of the move.

Migrating away from PrestaShop to a custom Solidus store

The honest guide to leaving PrestaShop for a custom Solidus store. Because you host PrestaShop, your data access is already good: the MySQL database, the CSV import tool and the Webservice API all hand records over. This covers what moves cleanly, what stays locked, the PrestaShop specific traps around modules, upgrades, payments and URLs, and how I run the move.

Migrating away from BigCommerce to a custom Solidus store

The honest guide to leaving BigCommerce for a custom Solidus store you own: the plan tiers that climb as you grow, the Open Payment Provider Fee that arrived in June 2026, what the API and CSV export hand over cleanly and what they hold back, the BigCommerce specific traps around checkout, saved cards, subscriptions, Stencil themes and URLs, and the honest shape of the move.

Migrating away from WooCommerce to a custom store

The honest guide to leaving WooCommerce for a custom Solidus store. Because WooCommerce is self hosted you already own the database, the REST API and the CSV exporter, so the data export is easy; the real reason to move is the plugin tower underneath, its security load, its performance limits and its maintenance risk. What moves cleanly, what is locked, and who should stay.

Migrating away from Shopify to a custom store you own

The honest, specific guide to leaving Shopify for a custom store: what it exports cleanly, what it keeps, how the CSV and the Admin API really behave, the checkout and payments lock in, and the shape of a careful move onto a shop you own.

Migrating subscriptions and recurring payments

Active subscriptions are the hardest thing to move in an ecommerce migration, because each one bundles a plan, a schedule, a mandate and a payment token that must all stay in sync. Here is what can move, what cannot, and the go or no go you must settle before you commit.

Migrating payment tokens and saved cards

Your shop holds a token, not the card. Saved cards move only provider to provider, encrypted, and only if the source agrees. Here is how a gateway to gateway vault transfer really works, the fallbacks when it is not available, and the decision to make before you commit.

Migrating order and purchase history

When you move a shop to a store you own, the order history is the one dataset you cannot rebuild. Here is what comes across, why imported orders are a read only record, the edges that catch people out, how to reconcile to the penny, and what the history is worth once it is yours.

Turning Solidus into a full stack car dealership and rental platform

How a Ruby on Rails and Solidus shop becomes a dealership platform: one unit stock for used cars, branches as stock locations, a rental calendar the database enforces, daily rental pricing, deposits as card holds and the UK rules that shape it, with an invented Leeds dealership.