How to Hire SAP Consultants: Signals, Tests and Scope

SAP engagements rarely fail on configuration. They fail because the organisation customised the system rather than changing a process, or because data migration was scheduled as a technical step. Hiring well means testing for that judgement. This guide covers it, drawing on FISTA Solutions' staff augmentation work.

Do you need functional or technical consultants?

Type	Responsible for	Hire when
Functional	Process mapping, module configuration	Deciding how the business will run
Technical	Extensions, interfaces, reports	Standard configuration is insufficient
Basis / platform	System operation, upgrades, performance	Running the landscape
Data	Migration, cleansing, reconciliation	Always, and earlier than planned

Usually you need several of these, but not simultaneously. Starting with technical people produces customisations before anyone agreed the process, which is the most expensive sequencing error available.

Why does standard versus custom matter so much?

Because every customisation is paid for again at each upgrade — in regression testing, remediation, and risk.

Standard functionality that fits imperfectly is frequently cheaper across a decade than a custom fit requiring revalidation whenever the platform moves. The judgement about which imperfect fits are tolerable is the single most valuable thing a consultant brings.

What should you test in an interview?

Ask when they advised a client not to customise, and what happened. Strong consultants have pushed back on requirements and can describe the process change they proposed instead.

Consultants who have never advised against a customisation have been order-takers, and order-takers produce systems that cannot be upgraded.

What is most often underestimated?

Data migration. Extracting, cleansing, mapping, and reconciling master and transactional data from legacy systems is detailed work that scales with how bad the legacy data is.

It is routinely scheduled as a technical step near the end. It is a programme that should start early, because the cleansing decisions are business decisions. See data engineering cost.

How do you evaluate process judgement?

Ask how they handled a requirement that reflected an inefficient existing process. Good consultants distinguish between processes that are genuinely differentiating and processes that are merely habitual.

Encoding habit into an ERP is how organisations end up with expensive systems that perpetuate their worst practices.

What about integration scope?

Almost every ERP programme underestimates the number of surrounding systems that need to connect. Warehouse systems, planning tools, e-commerce, payroll, banking, and reporting all touch the ERP.

List them before estimating. Integrations discovered during the build are the standard cause of schedule slip.

How does testing work on these programmes?

It is a substantial workstream in its own right, covering process testing, integration testing, data reconciliation, and user acceptance across functions.

Programmes that treat testing as a phase at the end compress it when earlier work slips, which is how defects reach go-live.

When does staff augmentation make sense?

For defined workstreams: interfaces, reports, data migration, testing, and extension development. Those have clear acceptance criteria and benefit from capacity.

Core process decisions benefit from people who will live with the consequences, which argues for internal ownership supported by external capacity rather than the reverse.

How long does hiring take?

Long for experienced functional consultants in specific modules. The market is competitive and the good ones are usually on engagements.

What are the common hiring mistakes?

Treating certification as judgement. Hiring technical before functional. Underestimating data migration. And assuming a consultant who knows the module also knows your industry's process norms.

How do you onboard them well?

Give them the current process documentation, the list of workarounds people actually use, and access to the people doing the work. The workarounds are where the real requirements are.

How does AI fit into ERP work?

Mostly at the edges: document processing into the ERP, exception handling, reporting assistance, and master data quality. The system of record stays authoritative, and AI that writes to it without controls creates reconciliation problems rather than efficiency. See AI agents.

What does good look like after 90 days?

Agreed process decisions documented with the standard-versus-custom rationale, a data migration plan with cleansing owners named, and an integration inventory.

What should be measured?

Process outcomes — order cycle time, close duration, inventory accuracy — rather than configuration completed. Configuration measures activity; process outcomes measure whether the programme is working.

What should you do first?

List the customisations you believe you need, and for each one write down the process change that would avoid it. That document is the cheapest risk reduction available on an ERP programme.

How do you evaluate industry experience?

Ask what they would configure differently for your industry than for the one on their CV. ERP process norms vary substantially between discrete manufacturing, process manufacturing, distribution, and services, and a consultant who has only implemented in one will propose patterns that do not fit.

Industry experience is not a hard requirement, but a consultant who cannot articulate the differences has not thought about them.

What about organisational change?

The system is the smaller half. People have to work differently, and programmes that budget for configuration and not for training, communication, and support after go-live produce systems that are technically live and operationally rejected.

Ask candidates what the client did about adoption. Those who have seen a programme succeed will have views; those who have only delivered configuration will not.

How FISTA Solutions helps

FISTA Solutions supports ERP programmes through staff augmentation and forward deployed engineers: integration and extension development, data migration and reconciliation, testing capacity, and reporting, with the standard-versus-custom rationale documented for every extension we build. Where document processing or exception handling can be automated safely, that is delivered through AI agents and AI enablement. The record is 150+ projects for 50+ companies across 12+ countries.

To add ERP programme capacity, message FISTA on WhatsApp, or read hire Dynamics 365 developers.