Services

System integrations and API development

Systems that share the same records, automatically.

System integration connects the software you already rely on, so customer, job and invoice records move between them instead of being copied by hand. Where a product has no suitable connector, we build the API or the custom connection.

Who this is for

Businesses that want to keep the systems they have and stop maintaining two copies of the same record. 23Labs works remotely from Melbourne for teams across Australia and New Zealand. The product names on this page are only the ones a published project actually used.

The same record exists twice

A customer, a job, a vacancy or an invoice is in two systems, and staff are the integration.

A CSV is doing the connecting

Someone exports and imports so the systems stay roughly in step, and the file is easy to get wrong.

A new tool was added beside the old one

The team adopted another platform, and the previous one still has to be updated by hand.

Where disconnected systems cost time

The symptoms are ordinary. The same details are typed again, nobody is sure which copy is current, and the workaround breaks as volume grows.

Re-entering the customer, the job or the invoice

The information already exists. A person types it into the next system because nothing passes it across.

Two versions of the truth

The CRM, the job system and accounting each hold a slightly different record, and the team reconciles them when something looks wrong.

A connection that only works when someone remembers

An export, a manual sync or a brittle workaround keeps up until the volume or the number of tools increases.

What 23Labs connects

We connect CRM, accounting, job and website systems, and we build APIs where a product does not already offer a workable link. We name a platform only when the project is one we can point at. Everything else is described by the job the system does.

A diagram showing business tools connected through an automation hubTwo engineers reviewing system data across multiple monitorsA hand pointing to a business growth chart trending upwardA person planning workflow notes at a desk

When this is the right service

This page is the connection itself. The notifications, task creation and approvals around that data are business process automation. A new application, because none of the current systems can do the job, is custom software. Reading an unstructured document into fields is AI workflow automation, and only when a rule cannot do it.

How we work

How an integration engagement works

We check that the systems can actually exchange data before we promise a connection. There is no published price or timeline. Both depend on the systems and on how the record needs to move.

01

Name the record that is being re-entered

We identify which system should own the customer, job, vacancy or invoice, and where a copy is being typed or exported.

02

Check that a connection is possible

We look at how data can leave and enter each system. If a product cannot support a reliable link, we say so rather than inventing one.

03

Build it and test it with real records

We build the API or connector and check the fields that matter, including the cases that are not the straightforward ones.

04

Make a failure visible

We put it into use and agree how a break is noticed, and who changes it when one of the systems changes. Later changes are support, agreed separately.

Where this shows up

Transport examples below are the shape of the problem, not a named transport integration. The recruitment and professional-services examples have published projects, linked in the next section.

Transport and logistics

A booking entered in the transport system and typed again into accounting, or a file someone exports so the two stay roughly aligned. The work is to move that record, where the systems can exchange data. This does not claim a specific transport product.

Recruitment

Vacancy details kept in a recruitment system, then again on a job board and again on the website. Huntress Recruitment is the published version: Bullhorn, SEEK and the company website, with public fields so the internal record and the candidate-facing version can differ.

Professional services

A CRM and a project tool that each hold a different version of the client, so staff re-enter details before delivery can start. CorIT Tech is the published example of connecting a CRM to project management tools for that handoff.

Published work

The platform names here are the ones these projects used. We do not keep a directory of certified integrations.

Frequently asked questions

What is a system integration?

A connection that lets two or more systems share records, so staff stop typing the same customer, job or invoice into each one. That can be an existing interface, a custom API, or a replacement for a file someone exports by hand.

Which systems can you connect?

It depends on whether they can exchange data. The published recruitment project connected Bullhorn, SEEK and a WordPress website. We do not publish a list of certified platforms, and we will not claim an integration we have not built. If a product has no workable interface, we say so.

How is an integration different from custom software?

An integration keeps each system and moves information between them. Custom software is a new application for a job none of the current systems can do. If the systems are fine and the gap is the re-entry, integration is the starting point.

How is this different from business process automation?

Integration is the data moving. Process automation is the sequence around it: who is notified, what task is created, what has to be approved. This page is about the connection.

Can you connect an older system?

Often, if it can export, import or expose an interface. Where it cannot, we describe that limit rather than inventing a connector. The first step is to see how the data leaves that system today.

What does system integration cost?

Custom software and automation projects typically start from A$2,500. Final pricing depends on the systems involved, complexity and scope. For a larger or more complex project, book an initial consultation. For an integration, that includes how many systems, whether they already expose a usable interface, and how many fields and exceptions the record has.

Do you integrate systems for New Zealand businesses?

Yes. Integrations are delivered remotely. Huntress Recruitment, a New Zealand firm, is one example. 23Labs is based in Melbourne and has no New Zealand office.

Tell us which systems do not share records.

You do not need a technical specification. Tell us what gets typed twice and which systems are involved. We will say whether a connection is possible before anyone talks about a rebuild.

Custom software and automation projects typically start from A$2,500. Final pricing depends on the systems involved, complexity and scope. For a larger or more complex project, book an initial consultation.