Platform is usually treated as a checkbox: pick Shopify because that is where the money is, export, send. That wastes the most informative field in the record. A merchant’s platform is a decision they made under constraints, and the constraints are still there. It tells you what they optimized for, what they gave up, who inside the business has authority, and what they are structurally unable to fix without help.
The distribution across 153,515 verified stores and sixty distinct platforms: WooCommerce 58,549, Shopify 50,002, PrestaShop 16,501, JouwWeb 15,477, Odoo 4,510, Squarespace 2,447, Magento 1,761. The two leaders are close in volume and nothing alike in buying behaviour. Treating them as one audience is how you end up with a message that lands on neither.
Shopify: the merchant buys outcomes, not implementation
The whole proposition of Shopify is that you do not have to think about infrastructure. No hosting decisions, no developer required to launch, no maintenance window. That self-selects for a specific person: someone who wanted to test a business rather than test their ability to operate a stack. They will pay a platform fee and a payment percentage as the price of not caring.
That person buys outcomes. Conversion rate, retention, creative, paid acquisition, email and SMS revenue. They do not buy “we will optimize your database queries” because that sentence describes a problem they deliberately paid someone else to own. They also buy in apps — the reflex when something is missing is to install something, which means the apps field on a Shopify store is a remarkably honest map of what they think their problems are. A store with a reviews app, a bundling app and an upsell app is telling you they are working on average order value.
The absences are equally loud. A Shopify store with real traffic and no email or SMS automation detected is leaving the cheapest revenue on the table, and they know it in the abstract without having acted. That gap is the single most reliable Shopify opener there is. Watch, too, for stores that have outgrown the setup — high product count, high traffic, still on a default theme with a thin stack. That is a merchant whose operations have overtaken their tooling, and it is a migration or a re-platform conversation.
WooCommerce: the merchant buys relief
WooCommerce is the largest population at 58,549 stores, and it is a fundamentally different animal. It is a plugin on a content management system that was not originally designed for commerce, self-hosted, infinitely extensible, and entirely the merchant’s problem when it breaks. Choosing it means choosing control, ownership of the data, and no revenue share — and accepting the operational cost that comes with all three.
So the WooCommerce merchant does not buy growth first. They buy relief. Performance, because plugin sprawl and an unoptimized data layer make these stores slow in ways the merchant can feel but not diagnose. Security and updates. Hosting that does not fall over during a promotion. Technical SEO, because the default output is messy in ways Shopify’s simply is not. Someone who will answer the phone when checkout breaks on a Saturday.
This changes the pitch and the offer shape. Retainers work better than projects. The opening observation should be technical and specific rather than commercial — a page weight number, a plugin count, a crawl issue — because that is the language of the problem they are actually living with. And the buyer is often not the founder: on a WooCommerce store of any size there is usually a technical person, internal or freelance, who is the real gatekeeper and who will kill your proposal if it reads as marketing fluff.
PrestaShop: the merchant buys continuity
PrestaShop at 16,501 stores is heavily European and heavily French, and it skews toward businesses that have been trading for years rather than launched last quarter. It is a proper commerce platform, self-hosted, with development conventions solid enough to build serious things on — and with a module ecosystem and a version history that accumulate debt over time.
The PrestaShop merchant is typically past the experimentation stage. They have a catalog, a supplier relationship, an accountant who cares about the ERP connection, and a store that has been modified over several years by people who are no longer available. What they buy is continuity: version migration without losing sales, module development or replacement, integration with the systems the business already runs on, and technical SEO on a large catalog.
Two things follow for outreach. First, deal sizes are often larger than the traffic figures suggest, because the business is real and the switching cost is high. Second, urgency comes from risk rather than opportunity — “your version is approaching end of support and here is what that means for your payment module” lands harder than any growth promise. Sell against the thing they are afraid of, not the thing they are dreaming of.
The long tail: JouwWeb, Odoo, Squarespace, Magento
JouwWeb at 15,477 stores is the surprise in the top five and a useful lesson in reading platform data honestly. It is a Dutch-market website builder, and the stores on it are overwhelmingly small, local and owner-operated. For most agency offers they are below the floor. For a low-ticket, high-volume, productized offer aimed at the Dutch market they are a coherent and almost entirely uncontested segment. Know which business you are in before you decide it is noise.
Odoo at 4,510 stores is not really an ecommerce platform, it is a business management suite with a storefront attached. The buyer is operations, not marketing. They care about inventory, invoicing, purchasing and process automation, and they will find a conversion-rate pitch irrelevant. Squarespace at 2,447 skews design-first and brand-led — often creators and boutique labels where the store is one expression of a larger brand, and where content, identity and merchandising matter more than technical depth.
Magento at 1,761 is small in count and large in value per store: big catalogs, international deployments, multiple people on the project, procurement processes. Nothing about outbound to Magento resembles outbound to Shopify. Longer cycles, more stakeholders, a first email that is closer to an introduction than a pitch, and a realistic expectation that the sequence is a six-month opening move rather than a two-week conversion.
Platform is a coarse filter — cross it with catalog and traffic
Platform alone is still too broad. Fifty thousand Shopify stores contain a person testing a product from their kitchen and a brand doing eight figures. The segment only becomes usable when you cross platform with catalog size and traffic band, which are the two dimensions that separate hobby from business.
The practical grid: platform on one axis, product count band on another, monthly traffic band on a third. A Shopify store with 40 SKUs and 3,000 visits is a different company from a Shopify store with 900 SKUs and 120,000 visits, and they have almost no overlap in what they will buy. Pick one cell. Write one offer for it. When it works, move to the adjacent cell rather than widening the one you are in.
Layer the trend on top of that grid and you get timing, which is the thing most outbound lacks entirely. A store in the right cell whose traffic has been declining for six consecutive months is a store where someone internally is already having uncomfortable conversations. You are not creating the problem, you are arriving during it. That is a completely different reception from arriving at a store that is having its best quarter.
Qualify compatibility before you qualify budget
Here is an expensive lesson worth borrowing from someone else. A perfectly qualified prospect, right size, right budget, real pain, enthusiastic on the call — and the deal collapsed at implementation because their platform could not connect to the tool the whole engagement depended on. Nobody checked. The filter existed and was not applied.
If your service depends on a specific integration, that integration is a filter, not a discovery question. Build it into the query: platform, plus the presence of the systems you need, plus the absence of the competing system you would have to rip out. The apps and paymentMethods fields exist for exactly this. Finding out on the kickoff call that the work is impossible costs you the deal, the hours and the reference.
The same logic applies to market fit signals. Currency and language tell you which markets a store is actually selling into. Payment methods tell you which ones they are set up to convert. Shipping carriers tell you where they can deliver. A store nominally in one country but configured for three is a different conversation from one that has never left its home market — and if your offer is international expansion, that distinction is the whole pitch.
Price by platform, not by service
The last implication is the one that changes your revenue rather than your reply rate. The same deliverable is worth different amounts on different platforms, because the alternative available to the merchant is different.
A Shopify merchant’s alternative to hiring you is often a twenty-euro-a-month app, and they will price you against it whether or not the comparison is fair. A PrestaShop or Magento merchant’s alternative is a development agency with a day rate, and they will price you against that instead. Identical work, wildly different anchors. If you quote both from the same rate card you are simultaneously too expensive for one and leaving money on the table with the other.
So build the offer per platform segment, not per service line. Same underlying competence, three packages, three price points, three sets of proof, three sequences. It is more work up front and it is the difference between an outbound motion that plateaus and one that keeps compounding as you move across the grid. Sixty platforms and 153,515 stores is a lot of grid.