Standard Integration Build

What is a standard integration?

A standard integration moves data from one system to another, in one direction, using code we write for you. The website sends every completed enquiry to HubSpot with the right owner and pipeline stage. A paid Stripe checkout creates an invoice in Xero with the correct tax codes and tracking categories. A completed job in ServiceM8 or simPRO triggers a review request through Twilio. One source, one destination, one direction, and every edge case handled.

It is the tier you reach when a no-code connector cannot do the job: the vendor's connector does not expose the field you need, the transformation is more than a lookup, the volume makes per-operation pricing expensive, or a failure halfway through has to be recovered cleanly rather than noticed a week later. The connector-level integration remains the right answer for simple one-way triggers, and we will say so if that is what your workflow is.

Every standard integration is priced from integration discovery and scoping. Scoping produces the API capability review, the data map, the risk register and the fixed-price quote the build is delivered against. We do not quote an integration from a phone call.

What testing is included?

Most integrations are built, demonstrated once and left to run. The failures arrive later: a token that expired over a long weekend, a webhook delivered twice that created two invoices, a throttled end-of-month import that quietly dropped records. Three things catch those failures before your customers do, and all three are in the price.

Contract tests

Contract tests run against the vendor's API and confirm it still behaves the way the integration expects: the same fields, the same types, the same status codes. They run in CI on every change to your code and on a schedule, so a vendor changing its API is caught as a failing test rather than as missing data.

End-to-end tests

End-to-end tests push real records through the real workflow in the vendor's sandbox, from the triggering event to the record arriving on the other side, and check the result field by field. They are the proof that the integration does what the data map says. The same suite covers the four failure modes behind most integration incidents, token expiry mid-run, webhook retry after a timeout, partial failure of a batch and duplicate delivery of the same event, and it confirms the integration queues and backs off rather than dropping records when the vendor's published call limit is reached.

Monitoring

Health checks and alerting are wired into the same CI pipeline that runs the tests. When the integration stops moving records, someone you nominate is told, with the failed run identified so it can be replayed. Credentials live only on the backend, never in the browser, and can be rotated without a code change.

How is the build priced?

The price is from $3,500 + GST, fixed for your build in the scoping quote. The figure depends on the vendor's API, the amount of transformation between the two data models and the volume the integration has to sustain. The $1,800 + GST scoping fee is credited against that price when the build proceeds within 30 days.

Third-party platform and API fees are named in the quote, and who pays each one is settled in writing before work starts. Xero now charges for API access on usage-based tiers, so a Xero integration names that fee. We design Xero work around webhooks and delta sync rather than polling, so the integration uses as few calls as the workflow allows.

Where the workflow turns out to need data flowing both ways, or more than two systems, it is a two-way sync and multi-system integration, and scoping will place it there.

What do you own?

You own the code and the repository it lives in, the vendor accounts and API credentials, the test suites, the monitoring configuration and the runbook. Any developer can take the repository, run the tests and maintain the integration without us. If you would rather we keep it monitored and respond when a vendor changes something, the integration support retainer does that month to month with no lock-in. If you already have an integration someone else built and want it held to the same standard before deciding anything, the integration audit runs these same checks against it.

Next step

If scoping is already done, the quote names this tier and the build starts on your go-ahead.