What does a requirements analysis cost?
Updated: 2026-11
The effort of a requirements analysis depends on the number of business units and stakeholders involved, the number and complexity of processes and interfaces, the required documentation depth and the form of sign-off. Existing material reduces it; politically sensitive projects with many interests increase it.
A requirements analysis is the cheapest part of a software project and at the same time the one that determines most later costs. Errors made here surface at acceptance or in operation, when fixes cost many times more.
The effort can be estimated well once system boundaries, stakeholders and processes are roughly known. That is why every estimate starts with a short clarification call.
What drives the cost
Stakeholders and business units
Each additional unit brings its own perspectives, schedules and alignment rounds.
Processes
The number and variants of processes to be modelled form the core of the effort.
Interfaces
Every connection to surrounding systems needs its own requirements on data, error cases and responsibility.
Documentation depth
A backlog of user stories is leaner than a contractually sign-off-ready catalogue for a tender.
Sign-off
Formal approvals by several bodies, as is usual in public administration, need time for reviews and clean-up.
Existing material
Current process descriptions and system documentation shorten elicitation considerably.
How we price
- 01
Fixed-scope study
Requirements catalogue with process models and sign-off as a clearly defined result.
- 02
Business analyst in the project
An ongoing project role on a time basis, for projects whose requirements evolve.
- 03
Combination
Initial catalogue at a fixed price, then support through implementation and acceptance.
We deliberately publish no online prices: every case differs. After a short first conversation you receive a binding fixed price or clear frame.
Parent service: Custom Software Engineering
Matching offers
Requirements analysis (IREB)
We elicit, document and validate requirements following the IREB Certified Professional for Requirements Engineering method: identify stakeholders, elicit requirements in workshops, model processes in BPMN 2.0, write acceptance criteria and deliver a requirements catalogue the client can formally sign off. A basis for tenders, development or standard software.
External IT project management (HERMES)
External IT project management takes over steering a project from initialisation to closure — following HERMES where the public sector or regulated environments require it. You get leadership, clean documentation and reliable communication without having to fill a position internally.
IT strategy & roadmap
An IT strategy answers which technical investments advance your business goals most — and in what order. The result is a prioritised roadmap that turns a diffuse wish list into an executable plan with clear action areas and milestones.
FAQ
Is an analysis worthwhile for small projects?
At an adapted depth, yes. Even a small project needs an agreed list of requirements with acceptance criteria.
Can we do the analysis internally?
Yes, if someone with method and time is available. An external person often helps because they ask questions nobody internally asks any more.
Is the catalogue tied to you?
No. It is written so any supplier can build on it.