What Does a Systems Integrator Do?
Here is a sentence you may have already heard from a vendor. "Oh, we can connect that to your accounting system, no problem." It is said with total confidence, in the first meeting, before anyone has looked at either system. Sometimes it is true. Often it hides three weeks of discovery that nobody has priced.
A systems integrator is the person or firm who makes separate pieces of business technology work together as one operation. The craft lies in everything between "no problem" and a connection that keeps working a year later. If you are about to hire one, this guide explains what they do from first conversation to handover, what you should be holding at the end, how they differ from other vendors you might be comparing, and how to judge whether one is any good.
The short definition
Your business probably runs on several systems. A CRM holds customers. An accounting package holds money. A website takes orders. A spreadsheet holds the real pricing. Each does its own job well enough. The trouble is the gaps between them, where a person copies a number from one screen to another.
An integrator designs, builds, tests, documents, and often operates the connections across those gaps. They also make decisions that a single product vendor has no reason to make, such as which system should be the source of truth for a given record and what should happen when two systems disagree.
That last point is the real job. Plumbing is the easy part. Deciding which pipe carries what, and what to do when one clogs, is the work you are paying for.
What the work looks like, phase by phase
Every integrator has their own vocabulary, but good engagements follow a similar shape.
Discovery
This is where the integrator listens and looks. They interview the people who actually do the work, not only the owner, because the owner's description of a process is usually the idealized version. They ask to see real examples. A real purchase order. A real invoice that went wrong. The spreadsheet that everyone says is temporary.
They produce an inventory of systems, a map of how data moves today, and a list of pain points ranked by cost. A good discovery ends with a candid statement of what is not worth doing. If an integrator tells you everything on your list should be automated, be cautious.
Design
Next comes the plan. The integrator chooses the approach for each connection. Will systems talk through an API, an application programming interface, which is a published way for one program to ask another for data or to send it? Will one system push a notification to another the moment something changes, which is called a webhook? Or will a scheduled job check for changes every few minutes, which is called polling? Each choice has trade-offs in speed, cost, and failure behavior.
They also decide matching keys, which are the fields that tell two systems they are talking about the same customer or the same order. A poorly chosen key, such as a customer name that people spell three ways, produces duplicates that take months to clean up. And they define error handling, meaning what happens when a connection fails at two in the morning.
Build
The integrator builds the connections, using whatever tools fit. That might be a no-code platform for simple flows, configuration inside the products themselves, or custom code for logic that needs it. A thoughtful integrator is not loyal to one tool. They use the cheapest approach that will be dependable at your volume.
Testing
Testing in integration is different from testing a website. The risky cases are not the happy ones. They are an order with a missing field, a customer with two accounts, a payment that arrives twice, a system that is down for an hour. A good integrator runs these on purpose. They also test with copies of your real data, since invented data tends to be tidier than the real thing.
Cutover
Switching from the old way to the new way is the riskiest moment. Careful integrators often run the old and new processes side by side for a period, compare results, and keep a way back. They schedule cutover for a quiet window rather than month end.
Handover and support
At the end, you should be able to run your business without the integrator, even if you choose to keep them. That is the test of a good handover, and the next section covers what it contains.
What you should hold at the end
Deliverables are where weak engagements reveal themselves. Ask for these in writing before you sign.
| Deliverable | What it should contain |
|---|---|
| System inventory | Every system, owner, plan, and renewal date |
| Data flow map | What moves, in which direction, how often, and who owns each record type |
| Integration specification | Fields mapped, matching keys, rules, and known limits |
| Credentials register | Which accounts the integrations use, whose names they are in, and how to rotate them |
| Test results | The cases that were run and the outcomes |
| Runbook | How to check health, what common alerts mean, and what to do about them |
| Monitoring and alerting | What is watched, who is notified, and how fast |
| Source code and configuration | Delivered to a repository or account you own |
| Rollback plan | How to return to the previous state |
Two of these deserve extra attention. The first is ownership. The accounts, code, and automation workspaces should be in your name, or transferable to it on request. If your integrator holds the only login, you have rented your own operations. The second is the runbook. It is the difference between a connection that fails quietly for six weeks and one that someone notices on day one.
How an integrator differs from the vendors you are comparing
Buyers often confuse three kinds of firms. Each is useful. They simply sell different things.
A reseller sells you licenses for a product and may help you set it up. Their incentive is the sale of that product, and their expertise is usually deep in one vendor's catalog. They are a good choice when you already know what you want to buy. They are less suited to deciding which product to buy, or to connecting several products that were not designed together.
A dev shop, or software development firm, builds custom software. Their strength is creating new applications. Their natural answer to a problem is to build something. That is sometimes right, but if your need is to connect existing tools, a custom application can be heavier and more expensive to maintain than the job requires.
A systems integrator starts from the systems you already have and the process you need. Their natural answer is to configure, connect, and only then build. A good one is comfortable telling you to buy a product, change a process, or leave something alone.
There is overlap, and many firms do more than one thing. The useful question is what they are rewarded for. A reseller is rewarded when you buy more licenses. A dev shop is rewarded when you commission more code. Ask how the integrator would make money if the best answer for you were to change nothing.
A worked example (illustrative)
Consider a hypothetical twelve-person wholesale distributor. The numbers are invented for illustration.
Orders arrive by email. A staff member retypes each into the accounting package, then again into the CRM. Suppose the team handles 40 orders a day and each retyping takes about six minutes in total. That is 240 minutes a day, or four hours, across the team. At an assumed loaded cost of 30 dollars an hour, that is about 120 dollars a day, which over 250 working days is roughly 30,000 dollars a year spent on retyping. Errors are extra and harder to count.
A salesperson might propose a new order management product. An integrator would first ask more questions. Where do orders really arrive from? What decides whether a customer in the CRM is the same as a customer in the accounting package? What happens with a partial shipment? What do you do when an order references a product that does not exist?
After discovery, the plan might be modest. Orders are captured in a form or parsed from email into a structured record. A matching key based on a customer account number links the CRM and accounting. An idempotency key, meaning a unique identifier stamped on each order so the same order sent twice produces one result, prevents duplicates when a connection retries. Orders that fail validation go to a review queue for a person to resolve, instead of vanishing.
Notice what is not in that plan. There is no new platform. The integrator found the cheapest dependable path, wrote down who owns each record, and left the team with a runbook. That is the work.
How to evaluate one before you hire
You can learn a great deal in a single conversation if you ask the right things.
Questions about method
- Walk me through the last engagement that went badly and what you changed afterward.
- How do you handle a connection that fails overnight? Who finds out, and how?
- How do you choose matching keys between two systems?
- What would you test before cutover, and with whose data?
- When do you recommend against automating something?
Questions about ownership and exit
- Whose name will the accounts and workspaces be in?
- Will I receive the source code, configuration, and documentation, and in what format?
- If we part ways, what exactly do I walk away with, and what does the transition cost?
- Are there licenses or tools of yours that my integrations depend on?
Questions about scope and money
- What is in the estimate and what is explicitly out?
- How do you handle changes mid-project?
- Which charges are yours, and which are vendor or license fees billed separately?
- What does support cost after handover, and what response times are promised?
Red flags
- A firm price before any discovery.
- Reluctance to name who will actually do the work.
- No mention of testing, monitoring, or rollback.
- Credentials and code held only by them.
- Every problem answered with the same product or the same tool.
- References that cannot discuss a project that had difficulties. Every real project has some.
A last practical tip. Ask to speak to a past client whose project was small, similar to yours, and at least a year old. Their experience a year later says more than any proposal.
What you still own
Hiring an integrator does not remove your responsibilities. Someone on your side needs to answer questions quickly, because the most common cause of delay is waiting for a decision. Someone needs to own the process after it is automated, including the exceptions. And you should keep a short list of the decisions that stay with you, such as pricing rules, approval limits, and who may see which data.
Where to go from here
If you are about to engage an integrator, write your own one-page description first. List the systems, the handoffs that waste time, and what a good result would look like in numbers. That page makes every vendor conversation sharper, and it protects you from paying for discovery twice.
If you would like to compare notes, Ozcorp InfraOps does this kind of integration and ongoing operation for small teams in Puerto Rico and the United States, and InfraOps Base starts at $500 per month with vendor and license charges billed separately. A conversation costs nothing, and bringing your one-page description makes it far more useful.
Discuss your infrastructure requirements
Review the current service offer or schedule a conversation about the scope you need.
Stay in touch
Follow Ozcorp
Leave your details for occasional notes about new articles and Ozcorp updates.