- 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.