I'm Ben. I make your systems agree with each other.
I'm a senior integration engineer with a decade on enterprise ERP integrations — most of it inside NetSuite, one of the least forgiving integration environments there is. That's where I learned the discipline this work actually requires: idempotent writes, partial-failure recovery, reconciliation, and documentation someone can actually follow at 2am.
Today I bring that discipline to the integrations most businesses actually live on: storefront to books. Shopify to QuickBooks. Orders to inventory. The syncs that no-code tools promise in five minutes and quietly corrupt at volume.
I started FlowSync because I believe the best systems are the ones your team actually trusts. Most integration work optimizes for the demo. I optimize for month-end.
How I work
Tested before it ships
I stand up a running copy of your stack, seed it with your real data shapes and volumes, and run every path — including the failures. You approve it passing before anything touches production.
You own everything
Real code, in your repos, with a written runbook and a build-ready spec. No black boxes, no per-task metering, no dependency on me to change a field mapping.
Built for failure
Networks flake. APIs rate-limit. Webhooks arrive twice. Production integrations are defined by how they fail — mine fail loudly, retry safely, and reconcile automatically.
One person, accountable
The person you scope with is the person who builds, tests, and stands behind it. No handoffs, no juniors, no account managers.
What I won't do
- × Sell you another black-box zap and call it an integration
- × Ship anything to production you haven't watched pass first
- × Build dependency — everything is documented so your team can extend it without me
Start with the Teardown
$1,500 fixed. One week. A full diagnosis of where your sync is bleeding money — yours to keep, whoever builds the fix.
See What's Included