The largest firms are priced for transformation. The smallest partners are priced for tickets. Neither fits the years in between.
Most manufacturers running IFS today do not need another implementation. They need a senior operator who can look at a working environment, tell them honestly where the value is leaking, and close the gap without turning a routine engagement into a program.
That is the space this firm occupies. Not a competitor to global SIs and not a substitute for a full-time internal team — a specialist retained by executives when the internal bench is thin, the SI has moved on, and the environment is quietly costing more than it should.
Where the depth is honest
Fifteen years narrows a career. This list is what the practice actually does well — not everything IFS has to offer.
Manufacturing, first
- Engineer-to-order (ETO)
- Make-to-order (MTO)
- Configure-to-order (CTO)
- Inventory- and supply-chain-heavy operations
- Maintenance-driven and service-connected environments
Where the work concentrates
- Manufacturing, supply chain, inventory
- Maintenance, service management
- Reporting & analytics
- Workflow & BPA
- Customizations, custom events, APIs
What the hands know
- PL/SQL, T-SQL — production-grade
- Quick Reports, Crystal Reports, SSRS, IFS Report Designer
- Custom events, workflow logic, BPA
- IFS Developer Studio, LU structure
- Operational troubleshooting with manufacturing context
Three ways executives typically retain the practice
Senior judgment on decisions the internal team cannot make alone
Upgrade posture, customization write-offs, support-model design, architectural tradeoffs — decisions where the cost of getting it wrong outruns the cost of external counsel.
Recovering value from an IFS environment that has stopped compounding
Reporting the operation can act on. Workflow that removes silent tax. A shop floor where the ERP quietly helps rather than quietly hinders.
A senior pair of hands the internal team can escalate to
Not to replace the team — to unblock it. Complex support items, reporting builds, workflow rewrites, upgrade analyses that need experience the team has not yet accumulated.
How the practice is run
Principal-led
Every engagement is delivered by a senior IFS practitioner. There is no bench, no rotation of junior consultants, no delivery-management overhead. The person scoping the work is the person doing it.
Fixed scope
Engagements are defined, priced, and time-boxed before they begin. No time-and-materials drift. Executives approve a specific brief with a specific deliverable and a specific end date.
Deliverable in writing
Every engagement closes with a written artifact — a findings brief, a documented workflow, a working reporting stack, a signed handover. Not slides. Not verbal reassurances.
No lock-in
Handover is part of the scope, not an upsell. The internal team is expected to own what the firm builds. If the engagement produces a dependency, it has failed.
Manufacturing-first
The practice is not an ERP generalist. Fifteen years of production, planning, service, and inventory context shapes every recommendation. If the operation is not manufacturing, this is not the right firm.
Two weeks. One executive brief. A defensible view of what your IFS environment is actually costing you.
The Executive Assessment is where most engagements begin. Fixed scope, fixed fee, written deliverable.