Why We Built InSyncer

We didn’t set out to build integration software. CyberWorkshop started as a Shopify agency in 2012, building online stores for businesses across New Zealand and Australia. Custom development, migrations, ongoing support — the usual agency work.

But a pattern kept emerging. Client after client came to us with the same problem: they ran MYOB as their ERP — pricing, inventory, customers, orders, all managed in Exo or Acumatica — and they needed it connected to Shopify.

The options at the time were poor. Generic middleware tools that couldn’t handle the specific data structures in MYOB. Self-serve connectors that worked for basic scenarios but fell apart when business rules got complex. Or custom-built integrations that were expensive to develop and fragile to maintain.

We built the first version of InSyncer for a single client who needed MYOB Exo connected to Shopify. Pricing from Exo, inventory from Exo, orders back to Exo. Simple in concept, surprisingly complex in practice.

That first integration worked. So the next client asked for the same thing. And the next. Each time we refined the approach, handled more edge cases, and built more robust sync logic. Eventually we formalised it as a product — a native Shopify app, available on the Shopify App Store, backed by a team that understood both systems.

Today InSyncer connects 75+ businesses across Australia and New Zealand. It’s grown from MYOB Exo to MYOB Acumatica to MYOB AccountRight. It carries a 4.8 and 5.0 star rating on the Shopify App Store. And it’s still built and supported by the same team that started it — developers who know MYOB, know Shopify, and know what happens when you try to connect two complex systems without understanding both.

We call our approach Software-with-a-Service. You get a real product — tested, maintained, updated — and a team that configures it for your business, tests it against your data, and supports it after launch. Because the software is only half the solution. The other half is knowing your business well enough to make the integration work properly.

That’s why we built InSyncer. Not because we wanted to be a software company, but because our clients needed something that didn’t exist, and we were in the best position to build it.