Consulting.

Consulting that sees the process on the floor and builds it in the system.

We design your enterprise processes on ERP: costing, finance, production, procurement, sales, budgeting, HR and CRM. We listen to the process from your own team and build its working counterpart in the system, telling you upfront what a standard module solves and what genuinely needs development.

What we do

Most ERP projects fail because of process, not software. The system gets installed, training is delivered, and yet nobody does their daily work in it — because the process that was configured is not the process that actually runs on the floor. We start with the process, not the software.

On the costing side the most common problem is this: the report produces a number, and nobody trusts it. The cause is rarely a single error. It is accumulated small configuration mistakes — the wrong cost centre, missing allocations, scrap and waste left out, exceptions added later that nobody remembers.

We treat production, procurement and sales as linked rings of one chain. If procurement does not raise the order on time, the production plan slips; if production slips, the delivery commitment sales made slips too. Consulting that looks module by module cannot see this chain.

In finance, budgeting and HR we make the data the system produces decision-ready: budget versus actual that is genuinely comparable, cash flow visibility, and personnel cost reflected correctly into production cost.

We tell you upfront what a standard module solves and what truly needs development. Unnecessary customisation is the most expensive line item in an ERP project, and once it exists it bills you again at every version upgrade.

Our experience on IFS projects

We have provided on-site consulting across more than 20 ERP projects, including IFS 10 and IFS Cloud. We have hands-on experience in every one of the costing, finance, CRM, procurement, production, sales, budgeting and HR modules.

Verhex is not an IFS partner; this experience was earned directly in the field. We do not sell licences and we do not represent any product. That independence changes the substance of the work: we can tell you what a standard module will cover and what genuinely needs development, with no pressure to sell a product.

We work independently of sector. Process names and regulations differ by industry, but the logic of cost flow, planning discipline and the approval chain does not.

Who it's for

Organisations with an ERP in place whose critical processes still run in Excel
Manufacturers who do not trust the number in their costing report
Companies implementing a new ERP, upgrading a version, or switching systems
Operations teams whose modules work in isolation, with no end-to-end flow
Finance and operations leaders who want an independent second opinion

How we work

01
Listening to the process on the floor
We learn the process from the person doing the work, not from a document. The written process and what actually happens are almost never the same, and you cannot configure anything before seeing that gap.
02
Gap analysis
We compare the current configuration against how the work really runs. The output is a table listing every gap with its cause and its cost to the business — evidence, not opinion.
03
Process design and system counterpart
We design the target process and build its counterpart on the ERP. What a standard module can solve is separated from what needs development, and every item in the second group comes with its justification.
04
Go-live and handover
The process goes live and is handed over to the team that will use it. The goal is not dependence on us; it is a team that can run the process on its own.

What you get

Gap table between the floor process and the system configuration
Target process design and its counterpart on the ERP
Standard module versus development split, with justification per item
Costing and reporting verification checklist
Handover documentation for the user team

Frequently asked questions

Are you an IFS partner?: No. We have on-site consulting experience across IFS 10 and IFS Cloud projects, but we are not an IFS partner and we do not sell licences. That independence works in your favour: we can tell you what a standard module will cover and what needs development, with no pressure to sell a product.
Which modules do you work in?: Costing, finance, CRM, procurement, production, sales, budgeting and HR. We treat them as one connected flow rather than separate headings, because a configuration error in one module almost always surfaces as a report problem in another.
Do you only work with IFS?: The weight of our experience is on IFS. But the subject of the consulting is the process, not the product: the logic of cost flow, planning discipline and the approval chain does not change with the ERP product. If you run a different system, we scope it together in the first conversation.
Can we get process consulting and software development together?: Yes. Once the process is designed, the same team can carry out the required development, integrations and AI work. Having the people who designed the process sit at the same table as the people building the system removes the handover loss in between.
How long does an engagement take?: It depends on scope: reviewing one module's process is not the same as designing configuration across the organisation. We give a fixed timeline and price after scoping in the first conversation — we do not work open-ended man-day arrangements.

All services

AIAI systems that run in production, not just in demos.IntegrationWe fix the place where your systems stop talking to each other.

Let's start

A short intro call is enough. We'll scope it together from there.

Get in touch

What we do

Our experience on IFS projects

We work independently of sector. Process names and regulations differ by industry, but the logic of cost flow, planning discipline and the approval chain does not.

Who it's for

Organisations with an ERP in place whose critical processes still run in Excel

Manufacturers who do not trust the number in their costing report

Companies implementing a new ERP, upgrading a version, or switching systems

Operations teams whose modules work in isolation, with no end-to-end flow

Finance and operations leaders who want an independent second opinion

How we work

Listening to the process on the floor

We learn the process from the person doing the work, not from a document. The written process and what actually happens are almost never the same, and you cannot configure anything before seeing that gap.

Gap analysis

We compare the current configuration against how the work really runs. The output is a table listing every gap with its cause and its cost to the business — evidence, not opinion.

Process design and system counterpart

We design the target process and build its counterpart on the ERP. What a standard module can solve is separated from what needs development, and every item in the second group comes with its justification.

Go-live and handover

The process goes live and is handed over to the team that will use it. The goal is not dependence on us; it is a team that can run the process on its own.

Frequently asked questions

Are you an IFS partner?

No. We have on-site consulting experience across IFS 10 and IFS Cloud projects, but we are not an IFS partner and we do not sell licences. That independence works in your favour: we can tell you what a standard module will cover and what needs development, with no pressure to sell a product.

Which modules do you work in?

Costing, finance, CRM, procurement, production, sales, budgeting and HR. We treat them as one connected flow rather than separate headings, because a configuration error in one module almost always surfaces as a report problem in another.

Do you only work with IFS?

The weight of our experience is on IFS. But the subject of the consulting is the process, not the product: the logic of cost flow, planning discipline and the approval chain does not change with the ERP product. If you run a different system, we scope it together in the first conversation.

Can we get process consulting and software development together?

Yes. Once the process is designed, the same team can carry out the required development, integrations and AI work. Having the people who designed the process sit at the same table as the people building the system removes the handover loss in between.

How long does an engagement take?

It depends on scope: reviewing one module's process is not the same as designing configuration across the organisation. We give a fixed timeline and price after scoping in the first conversation — we do not work open-ended man-day arrangements.