HorizonVale Holdings HorizonVale Holdings BV
A rack wall of unlit network ports and patch bays in a Belgian integration workshop under overhead strip light

Service lines

We draw the cable between your systems.

Five service lines, one integration problem. Belgian organisations usually need two or three of them at once, and we say which before we quote a build.

See the five service lines Which one do I need?
Web apps, internal portals and case workflows Eight to sixteen weeks
Macro photograph of four empty metal network ports on a patch bay under overhead strip light

Custom business application development

The application no package covers: the internal tool for a process your business runs differently from everyone else's. Web applications, internal portals, planning boards, claims and case workflows.

Stack follows the constraint, not the fashion, and we build on your existing identity provider so people don't get another password to forget. What you get is a maintainable codebase with tests and documentation, not a prototype that becomes production by accident.

Typical duration for a first usable release: eight to sixteen weeks, depending on how many systems it has to touch.

ERP, CRM, WMS, HR and finance platforms Most common entry point

System integration and application integration

The work of making systems exchange data reliably. Point-to-point scripts work until they don't, so we design API-led connectivity: a managed layer of APIs and events between systems, with monitoring and versioning attached.

It covers ERP, CRM, WMS, HR and finance platforms, whether they sit on-premises, in a private cloud or in SaaS. The deliverable is a set of connectors and flows, documented, with the data contracts written down where your team can find them.

If your problem is between two systems you already own, this is almost always the line to start on.

Two patch cables hanging from an overhead cable tray above the coated floor of an integration workshop
Adapters and internal APIs Legacy AS/400, vendor databases, warehouse systems

API-led connectivity and connectors

Where the systems are old and closed, we build adapters. A legacy AS/400 or a vendor database with no API gets wrapped in a controlled interface so the rest of your estate can talk to it in a modern way without anyone writing directly against its schema.

We also publish internal APIs for your own teams, with a developer portal if that's useful, so the integration layer becomes something your organisation builds on rather than a black box.

What gets wrapped

  • Legacy ERP and finance ledgers
  • Vendor databases with no published API
  • Warehouse and logistics systems
  • HR and payroll platforms
Workato, Tray.ai or Microsoft Power Automate Maintainable by business teams

Workflow automation

Not everything needs custom code. Approval chains, document routing, notifications between systems, the "when a quote is signed, create the project and notify three people" kind of work: that's where Workato, Tray.ai or Microsoft Power Automate earn their licence cost.

We build these where business teams can maintain them, and we're clear about the ceiling. When a flow grows past a few hundred lines of logic and starts making decisions, it's time to move it into code.

Where it earns its keep

  • Multi-step approval chains
  • Document routing and sign-off
  • Notifications that cross between systems
  • Data entry that teams routinely re-key
Strangling the old system slowly Old and new coexist

Legacy system modernisation

You rarely get to switch the old system off. So the practical version of modernisation is usually strangling it slowly: put an interface in front of the legacy system, move one function out at a time, keep the rest running. Six months in, nobody is querying the old database directly anymore.

We scope these projects so the old and new coexist for as long as needed. Cutover dates that assume everything moves on one weekend are how projects get cancelled.

  1. First, an assessment of what the legacy system exposes today.
  2. Then an adapter or a facade in front of it.
  3. Functions move out one at a time, with rollback available.

Which platform fits

We do not resell, so the platform advice stays plain

HorizonVale does not sell platform licences. When a flow belongs on Workato, Tray.ai, SnapLogic or SAP Integration Suite, we say so, and when it belongs in code we say that too.

Whole-page view: the platforms we implement.

Tray.ai

Runs on

Cloud-native, SaaS estate

Where it fits

Complex multi-step flows between SaaS tools

Where we draw the line

Deep decision logic moves into code

SnapLogic

Runs on

Cloud, hybrid pipelines

Where it fits

Bulk data movement and batch synchronisation

Where we draw the line

Not a substitute for a real-time event layer

SAP Integration Suite

Runs on

On-premises and private cloud

Where it fits

Hybrid estates anchored on SAP

Where we draw the line

We are not your SAP rollout partner

Workato

Runs on

Cloud, with on-prem agents

Where it fits

Business-owned approvals and routing

Where we draw the line

Flows grow out of the tool past a few hundred lines

How services combine

Four lines, one process fixed

Real engagements rarely use one queue at a time. The usual shape: start narrow, prove the connection works, then expand outward.

See our delivery approach

Step one

An integration assessment finds that order data is being re-keyed three times, across three departments that never see each other's edits.

Step two

We build a connector from the ERP to the CRM. Order status now travels once, and the two teams stop trading spreadsheets.

Step three

A small custom application handles the exception cases that fit neither system. Internal portal, one screen, built on your identity provider.

Step four

The approval chain that used to run over email becomes a workflow the business team maintains. Four service lines, one process fixed.

Which one do you need?

Integration before application

If you're not sure, the honest answer is usually integration before application. Most "we need a new tool" conversations turn out to be a data-flow problem between tools you already own. We'll say so in the first meeting rather than selling you a build.

A short integration assessment, one to three weeks, is the cheapest way to find out which of the five applies to you.

Start with an assessment Describe your project

Reading the situation

  • Two systems disagree on the same fact Integration, not a new tool.
  • A process runs in email and private spreadsheets Workflow automation, unless the logic has grown.
  • A closed vendor system blocks the rest API-led connectivity, an adapter in front.
  • A workflow no package covers exactly Custom application development.
  • The old system can't be switched off Legacy modernisation, one function at a time.

Boundaries

What we don't do, said plainly

A services page is only useful if it also tells you where it ends. Here is where HorizonVale says no.

We don't do ERP implementation.

We're not going to run your SAP rollout or migrate you to Business Central. We work alongside the partner who does.

We don't sell platform licences.

When we recommend Workato or SnapLogic or SAP Integration Suite, it's because it fits, not because we're reselling it.

We don't take on "make everything better".

That scope never has a definition of done. Narrow, provable work is the only kind we can quote honestly.

Next step

Tell us what your systems are doing today

Describe the process that hurts and we'll say which of the five lines applies, or that none of them does. A short assessment is one to three weeks and lands with a written finding, not a proposal to sign.

Start with an assessment Compare platforms we implement

Direct line

Email
[email protected]
Phone
+32476715081
Hours
Mon to Fri, 9:00 – 18:00
Also useful
Engagement models

HORIZONVALE HOLDINGS BV

Enterprise software development and system integration across hybrid cloud and on-premises environments, delivered from Zaventem for Belgian organisations.

About HorizonVale Contact Privacy Policy Terms of Service Cookie Policy