System integration – get your programs talking to each other
Do you type the same order, customer or hour into more than one program? We build an integration that connects the programs so the information moves by itself – correctly, every time. For example, the hours and materials on a job go straight onto an invoice.
- The problem
- Is the same order, customer or hour typed into two programs?
- What we do
- We connect the programs so the information moves by itself. For example, the hours and materials on a job go straight onto an invoice. So nobody has to type the same thing twice, and there are fewer mistakes.
- What it costs
- First solution from 15,000 DKK at a fixed price. Operations from 2,500 DKK/mo. All prices excl. VAT. See all prices, and work it out for your own task
How we integrate your systems
Integration connects two or more systems so they share data automatically, instead of a person copying it from one to the other by hand. It suits any company where the same information is typed into more than one system. Once systems are connected, that information moves between them on its own, correctly and every time.
Most systems that share data do it through an API, short for application programming interface: a defined way for one program to ask another for data, or to send data to it. The two systems do not need to know anything about each other beyond that shared, agreed way of asking and answering.
Not every system offers an API. Where one does not, we connect it another way: through a file it exports on a schedule, or through a direct connection to its database, reading the data from where the system already stores it rather than waiting for a purpose-built door into it.
Some information arrives as plain text, in an email for example, rather than in a field a system can use directly. Then AI reads the text and turns it into the shape the next system needs, before the integration passes it along.
Integration also covers moving away from a legacy system: an older system the company still depends on, but one that is hard to maintain, no longer updated by its supplier or unable to connect to anything newer. We move its data into the new system and run the two side by side, connected, until the new one has shown that it holds everything the old one did. Only then is the old system switched off, so the daily work never depends on a single switch-over day.
Where it fits
Manufacturing
Enters orders that arrive by email into the ERP system, such as Business Central, so nobody has to type them in again.
Online shops
Moves orders from the online shop into stock and invoicing, so each order is entered once.
Trades and construction
Connects job planning to accounting, so hours and materials logged on a job become an invoice.
Transport and logistics
Connects the order system, route planning and invoicing, so each delivery is recorded once.
How you get started
We always work in the same three steps. Here is what they mean for integration:
Review
Read moreShow less
We list your systems and every place where someone copies data from one to another.
Solution
Read moreShow less
We connect two systems first and test the connection on real data before anyone relies on it. The integration runs in your real systems, and a named person gets an alert if a transfer fails.
Operations
Read moreShow less
We connect further systems step by step, reusing what the first connection showed about your data. We watch the connections, update them when a system changes and add new ones as you add software.
What it gives your company
Once systems are connected, nobody has to remember to copy a figure from one place to another, and nobody has to notice, later, that the copy was never made or was made with a typing mistake. The same piece of information exists once and reaches everywhere it is needed on its own.
That removes an entire category of error: the total that no longer matches because one system was updated and the other was not, the record that exists in one place but not the other, the report built from whichever system happened to be updated last. Two systems that share data cannot quietly disagree about it.
It also changes how a business can grow. Adding a new system used to mean deciding, again, who would keep it in step with everything else by hand. Once your systems already share data through defined connections, a new one joins that pattern instead of adding another manual step for someone to remember.
Why Lynggaard Jardim
At Lynggaard Jardim, Alexander answers for operations and finance and Victor for development and IT. An integration we build gets checked against both: how the data is actually used in the business, and how the connection itself holds up as your systems change.
We are based in Copenhagen, work across Denmark and connect the systems your team already uses as they stand, rather than asking you to replace one of them so it fits a standard integration package. A connection built around your actual systems is one that keeps working when one of them is updated, not one that breaks the next time it is.
Your data
As far as possible, your data stays with you, so we have no access to it. When it is necessary, we sign a data processing agreement.
The solutions themselves run in the EU, and we never publish your data. Which AI works in the solution depends on the setup. Wherever possible it runs on your own account, for example your own ChatGPT, and then your own terms apply. If you would rather use ours, it runs on our agreement, and then your data is not used to train AI. We follow the rules and your own requirements for data.