ERP requirements specification · fixed-price product

Turning an idea into a tender-ready requirements specification.

A sound ERP requirements specification is the basis for any serious ERP tender. The platform bundles scope, processes, functional requirements, integrations and scoring logic into a standard document — following a firmly defined methodology, delivered by a permanent partner of the platform.

Fixed price from EUR 25,000 net 6–10 weeks delivery Tender-ready, vendor-open
Why a requirements specification

Without a requirements specification, an ERP selection turns into a series of vendor monologues.

Those who compare ERP systems without documented requirements judge vendor demos instead of company needs. The requirements specification makes the decision logic traceable — before, during and after the tender.

Structure the tender

A standardised document makes it possible to address vendors on a comparable basis.

Anchor the scope

What belongs to the ERP project and what does not: clearly delimited phases, countries, entities and integrations.

Enable evaluation

Criteria, weightings and must/should requirements define the later scoring matrix.

Align internally

Management, business units and IT work on the same document — instead of on perceived requirements.

Scope of delivery

The requirements specification covers the relevant layers for a serious tender.

Part 1

Company and project framework

Organisation, entities, countries, relevant business models, target picture of the ERP replacement, non-goals and constraints.

Part 2

Process and module view

Core processes (finance, controlling, procurement, sales, warehouse, production where relevant) including variants and responsibilities.

Part 3

Functional requirements

Detailed requirements per module with prioritisation (must/should/can), typically 150–400 individual items, structured for vendor responses.

Part 4

Technology, integration, interfaces

Operating model, identity, data model, existing system landscape, interfaces to retain or replace.

Part 5

Non-functional requirements

Performance, multi-tenancy, security, data protection, compliance, audit readiness, availability, languages.

Part 6

Scoring and selection logic

Criteria, weightings, scoring scheme and template for vendor responses — as preparation for the later matrix.

Price & framework

A fixed-price product with a clearly defined scope.

The requirements specification is deliberately priced as a product, not as an open advisory mandate. This makes effort, outcome and timeframe plannable for you.

Package 1

Selection Advisory Compact

Structured sparring framework to validate an already mature pre-decision. For companies with a clear direction who want a sound second opinion.

from EUR 1,000 net · one-off
  • Evaluation of your Fit-Check by the editorial team
  • One structured strategy call (60 minutes, remote) with participants of your choice
  • Top-3 system assessment with reasoning per system
  • Written recommendation (2 to 3 pages, suitable for internal circulation)
  • One feedback round on the recommendation (asynchronous, written)
  • Confidentiality under NDA if required
Request Compact package
Lead time: 1 to 2 weeks Your effort: < 2 h
Upgrade path

ERP Requirements Specification

Fully elaborated, tender-ready requirements specification based on our structured template process with 26 subject-matter interview guides and six ERP profiles.

from EUR 25,000 net · one-off
  • Full requirements capture across all business units
  • Structured requirements spec following our own methodology
  • ERP profile matching based on six defined target profiles
  • Tender-ready basis
  • Suitable for projects with a budget > EUR 500k
Request requirements package
Lead time: 6 to 10 weeks Your effort: 20 to 40 h

Individual pricing for group structures, more than three entities or multiple countries with their own accounting reality. All prices net, plus statutory VAT.

Approach

Five phases to an aligned document.

The approach is deliberately phased so that the client, business units and IT participate in defined steps.

1

Kick-off & scoping

Jointly define target picture, framework, organisation and scope of the project.

2

Process workshops

Capture core processes along the modules in a structured way — including variants and exceptions.

3

Requirements detailing

Derive functional requirements, prioritise them and transfer them into the standard document.

4

Technology & non-functional

Add integrations, operations, data protection, compliance and security.

5

Review & release

Two structured feedback rounds, joint acceptance and handover.

When a requirements specification is useful

Four situations in which a fixed-price requirements specification is the right choice.

Before the tender

It is clear that a system change is coming — now a clean basis is needed for addressing vendors.

Before the committee decision

Advisory board, supervisory board or shareholders require a documented requirements picture before the investment.

With a heterogeneous stakeholder picture

Several business units have different expectations — the requirements specification consolidates them on a shared document.

Under compliance / audit pressure

Financing round, ISO or GoBD context: the requirements documentation becomes part of the project history.

Partner transparency

Who delivers the requirements specification and why it is structured this way.

The requirements specification product is a contractual service delivered by a permanent partner of the platform. The erp-check.info editorial team remains independent in terms of content.

Service provider

Tech IQ Business Consulting GmbH

The fixed-price requirements specification is delivered by Tech IQ Business Consulting GmbH. The partnership is exclusive and ensures that methodology, document standard and quality remain consistent across all projects.

Why a permanent partner instead of a platform-owned consulting arm? A "neutral platform with its own consulting" would neither be credibly neutral nor economically separable. Roles are therefore clearly separated: the platform profiles, the partner delivers the contractual service.

Contracting party
Tech IQ Business Consulting GmbH
Contract basis
Fixed-price offer, Tech IQ terms
Place of delivery
Hybrid (remote + on-site by arrangement)
Data protection
Data processing agreement under Art. 28 GDPR
Frequently asked questions

What you should know about the requirements specification product.

How does the requirements specification differ from Selection Advisory Extended?

Selection Advisory Extended (from EUR 5,000 net) delivers a structured recommendation including a scoring matrix across vendors. The requirements specification product (from EUR 25,000 net) additionally produces the full requirements document, which you can use for a tender independently of the selection advisory.

In short: selection advisory answers "Which system fits?", requirements specification answers "What exactly must the new system deliver?".

Why a fixed price instead of a day rate?
Fixed pricing makes the product plannable for you: you know what the document costs, the timeframe in which it is created and the quality. Open day-rate models experience has shown lead to hard-to-calculate side costs in ERP initiatives.
Do we receive the requirements specification as a standalone document?
Yes. The document is handed over as a PDF and editable Word file and belongs to the client afterwards. It can also be used independently of a later selection advisory.
Will we be steered towards a particular ERP system?
No. The requirements specification is vendor-open. It contains requirements, not a system recommendation. A system recommendation is the subject of the separate selection advisory and is made exclusively on the basis of the documented requirements.
What do we need internally so that the project works?
A named project lead, contact persons from the core processes (finance, controlling, procurement/sales, IT) and access to existing process documentation, org chart and system landscape. The partner moderates — the knowledge lies with you.
How does the requirements specification fit into a later tender?
The document is deliberately structured so that it can be sent as an RFI/RFP with a cover letter to vendors. Must/should requirements and the scoring template are designed for this.
Do we have to do a Fit Check first?
The Fit Check is free and provides the profiling of whether a requirements specification is even the right instrument in your situation. In many cases, Selection Advisory Compact is the more sensible entry point. The recommendation arises from the Fit Check — not in advance.
What if we only have one or two entities?
Then we check whether the requirements specification product is economically sensible or whether Selection Advisory Extended is sufficient for your case. The goal is not to sell every client the largest package but the appropriate one.

Before we approach a requirements specification, there is the structured profiling of your initiative.

The Fit Check clarifies free of charge whether requirements specification, selection advisory or a solutions overview is the right entry point.

Response typically within two business days · No disclosure to third parties
Profile your ERP project? Start Fit Check