Pricing
Log inGet Started

Services · integration

Join the systems you already run

Most companies do not need a new ERP. They need the eight systems they already pay for to agree with each other, and to produce the reporting none of them can produce alone. That is a fixed-scope engagement, not a platform migration.

Get a free assessmentHow the graph works

Map your stack

Tell us what you run today. We come back with an integration map and a fixed price.

1 / 3
From $6,500, fixed scopeRead-only to startTypically live in 2–3 weeks
QuickBooksQuickBooks190NetSuiteNetSuite190StripeStripe190RampRamp190GustoGusto190ShopifyShopify190SalesforceSalesforce190PlaidPlaid190Business graphone model, all systemsDepartment P&LEntity roll-upProject marginShadow ledgerAgent contextUniversal search
What you getConnectorsHow it worksQuestions

What you get

Four outcomes, none of which require a migration.

Reporting your ledger cannot produce

Department, location, entity, and project P&L built on data your accounting system holds but cannot dimension. This is the most common reason companies start shopping for a new ERP, and it does not require one.

One customer, one vendor, one truth

Deduplicated and matched across every system, so the pipeline report and the AR ageing stop disagreeing about what an account is worth.

Context the agents can use

An AP agent that can see the contract, the PO, the budget, and the payment history behaves sensibly. One that can see only the invoice does not.

A shadow ledger from day one

Every integration engagement starts a parallel ledger that reconciles daily against your books — which is what makes any future system decision low-risk.

Connectors

What we connect, by category.

Anything not listed is a custom connector, quoted at the published rate. In practice about one engagement in four needs one.

QuickBooks OnlineQuickBooks DesktopXeroNetSuiteSage IntacctSage 100 / 300AcumaticaDynamics 365 BCOdooSAP Business One

Integration is a data-modelling problem, not a plumbing one

Moving records between systems is the easy part and most tools do it adequately. The part that decides whether an integration is useful is what happens when two systems disagree about what something is — and they always do.

Your CRM has Northwind Trading Co. Your ledger has Northwind Trading Company and, separately, Northwind (do not use) created in 2023. Your payroll system knows a department called Delivery; your ledger calls it Operations; your project tool has both. A sync that matches on name creates a third record and makes the problem permanent.

So the first two weeks of any engagement are spent on entity resolution and dimension mapping rather than on connectors. That is the work that determines whether the reporting is trustworthy, and it is the work most integration projects skip because it requires decisions from your team rather than configuration from ours.

Connectors are a commodity. Deciding what a customer is, once, across six systems, is the engagement.

Read-only until you say otherwise

Every connection starts read-only, and most stay that way. Write-back — creating a bill in QuickBooks, pushing an invoice into NetSuite — is enabled per integration, per object, as a separate and revocable permission. Nothing we install can alter your books of record unless you switch that on deliberately.

What the engagement includes

  • Discovery of what you actually run, which is reliably more systems than anyone expects.
  • Entity resolution across customers, vendors, employees, and products.
  • Dimension mapping — department, location, entity, project — into one consistent model.
  • The connectors themselves, configured and monitored.
  • Dimensional reporting built on the result.
  • A shadow ledger reconciling daily against your existing books.

What it costs and how long

From $6,500 for a standard stack — accounting system plus five to seven surrounding tools — typically live in two to three weeks. Custom connectors and unusual data shapes are quoted after a diagnostic. It is a fixed scope, and our estimating error is our problem rather than a change order.

When integration is the wrong answer

If your accounting system genuinely cannot hold the transaction volume, or you need multi-entity consolidation with real intercompany elimination, integration postpones a decision rather than resolving it. We will say so in the diagnostic — that is a migration conversation and we would rather have it early.

Questions

What people ask first.

Will this change anything in our accounting system?
Not unless you enable write-back deliberately, per integration and per object. Every connection starts read-only and most engagements never turn write-back on at all.
What if we use something not on your list?
We build a custom connector at the published rate. Roughly one engagement in four needs one, most often for an industry-specific tool or an older on-premise system.
How is this different from Zapier or a middleware tool?
Those move records between systems and leave you with the same disagreements about what a customer is. We resolve entities and dimensions into one model first, which is the part that makes the reporting trustworthy — and it is a decision exercise, not a configuration one.
Do we need your platform subscription too?
The integration layer runs on Connect at $499 a month, which is what hosts the graph and the shadow ledger. The engagement fee is separate and one-off.
What happens if we later move to a different ERP?
The integration layer survives it — you repoint the accounting connector and everything built on the graph keeps working. That is one of the better arguments for doing this before choosing a new system rather than after.

Most companies need this, not a migration.

Tell us what you run today and we will show you what it produces once it agrees with itself.

Get a free assessmentSee engagement pricing