Custom Builds

Built onto what you already run.

Custom software and AI automation for businesses whose work already lives in an ERP, a CRM, an accounts package and fifteen years of files. We build onto those systems rather than asking you to replace them, and we do the data work that makes anything built on top of them actually reliable.

Scoped after an audit, delivered in phases, supported after it ships.

The part everyone skips

The data comes before the AI.

Most businesses arrive with the same problem, and it is not a model problem. The data is spread across systems that do not agree with each other. The same customer exists four times under four spellings. The figure in the ERP and the figure in the spreadsheet are different, and nobody is certain which is right. Point a language model at that and it will answer confidently and wrongly, which is worse than not answering.

So the first real phase of most builds is unglamorous data work: pulling the relevant records out of the systems holding them, resolving the duplicates, reconciling what disagrees, and getting it into a shape something can retrieve from reliably. That is what our Iris data core does — centralise, clean, categorise — and it is the difference between a demo and a system somebody trusts with money.

It is also the honest reason a build cannot be quoted from a conversation. Until somebody has looked at the state of your data, any number is invented.

Engagement sizes

One workflow, or the whole operation.

Discovery

Credited against the build

2–3 weeks

Starts with an Operational Audit and ends with a scoped, priced build. The fee is credited against the build if you proceed, so the diagnostic is not a toll on getting started.

  • Operational Audit included
  • Fixed scope out

Build

From €10,000

4–12 weeks

One workflow, properly. Fixed scope and fixed price, with weekly demos so you see it working rather than hearing that it is going well.

  • Fixed price
  • Weekly demos
  • 30 days post-launch support

Platform

From €30,000

3–6 months

For a structural need across multiple workflows and teams rather than a single process. Phased rollout, with managed support for the first 90 days after launch.

  • Multi-team
  • Phased rollout
  • 90 days managed support
How it runs

Four phases, each one shipping something.

01

Map it

An Operational Audit first. Stakeholder interviews, process mapping, and a ranked register of what is worth building — including what is not. The build is scoped from that, not from a wish list.

02

Fix the data

Pull the relevant data out of the systems holding it, resolve the duplicates, and get it into a shape a model can retrieve from. Skipping this is why so many AI projects demo well and fail in production.

03

Build in phases

Each phase ships something usable and is judged on whether people actually use it. If phase one does not earn its keep, that is the moment to find out, not month nine.

04

Support it

An ongoing cadence after launch: adoption, governance, and the next phase. Software nobody maintains stops being used, and an unused build is a write-off however well it was made.

Where we stop

What we won’t tell you we are.

We are not a managed IT provider. There is no 24/7 service desk here, and if what you need is somebody to run your infrastructure and answer the phone at three in the morning, that is a different kind of company.

We are not a systems integrator either. If the honest answer to your problem is a full ERP re-platforming programme, we will say so, and we will work alongside the firm doing it rather than bidding for work we are not shaped for.

What we are is the team that works out where AI genuinely helps, gets your data into a state where it can, builds the thing, and makes sure people actually use it. Everything on this page sits inside that. Anyone promising you all of it and the managed service and the infrastructure overhaul is describing three companies.

Common questions

The things people actually ask.

Do you integrate with our existing ERP and CRM?
Yes, and that is the normal case rather than the exception. Builds read from and write to what is already in place — the ERP, the accounts package, the CRM, the project tool, the shared drive. We do not ask a business to migrate before it can have anything useful.
What if our data is a mess?
Then that is the first phase, not a blocker. Most businesses arrive with data spread across systems that do not agree, duplicate records under four spellings, and history nobody has reconciled. Centralising, cleaning and categorising that is the work our Iris data core exists to do, and it is what makes everything built on top of it trustworthy.
Will you replace our systems?
Almost never, and we will say so early if we think you should. Replacing a working ERP to get automation is usually the most expensive way to reach the outcome. Where a genuine re-platforming programme is needed, that is a systems integrator's job and we will work alongside one rather than pretend otherwise.
What happens after it ships?
A Build carries 30 days of post-launch support; a Platform engagement carries 90 days of managed support through the phased rollout. Beyond that, work usually continues on an ongoing cadence — with Metec that means monthly, covering onboarding, governance and the next phase, so adoption keeps building instead of fading after week six. We are not a 24/7 managed IT provider and do not claim to be.
How long does a build take, and what does it cost?
A Build is 4 to 12 weeks from €10,000, fixed scope and fixed price with weekly demos. A Platform engagement, for a structural need across multiple workflows and teams, is 3 to 6 months from €30,000. Both are scoped by a 2 to 3 week Discovery that begins with an Operational Audit, and the Discovery fee is credited against the build if you proceed.
What do we get besides the software?
Builds ship with production-grade authentication, audit logging and monitoring, and a model-agnostic AI layer, from day one rather than as a later hardening phase. You are not buying a prototype that somebody else has to make safe for production.
Who actually does the work?
The people you meet. Nomad is deliberately senior-only: there is no account manager passing your build to a junior team you never speak to. Where a programme needs more hands than that, we say so at scoping rather than stretching and missing dates.

Start with the map.

A 30-minute call about what you are trying to build, what your data is actually like, and whether a build is the right answer at all.

Talk to us →