Industry

Requirements Specification Analysis Agent

Three engineers read the same requirements specification. Only one of them finds the evidence requirement on page 88.

Reads hundreds of requirements and automatically flags the ones that need evidence.

Reads hundreds of requirements and automatically flags the ones that need evidence.

Open agent

Enlarge demo

Public administration

Four processes that take up the most time today

Developed in Germany · Hosted in the EU

Developed in Germany · Hosted in the EU or on-premises

Delivered together with

Sovereign hosting in Germany, single-tenant from the first user.

Sovereign hosting in Germany, single-tenant from the first user.

Legal, tax and compliance expertise for legally sound deployment.

Legal, tax and compliance expertise for legally sound deployment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

340 requirements, three readers, one missed evidence requirement.

The specification arrives as a PDF with appendices, and the requirements are spread across running text, tables and references to applicable standards. Each reader marks by instinct what will take effort and what the portfolio covers. What ends up costing money is the one requirement with an evidence obligation that was never priced into the quotation.

340

requirements

They are scattered across the specification in running text, tables and references.

3

readers

Three engineers split the document between them by chapter.

26

evidence requirements

They call for a test certificate, a declaration or a sample approval.

4

days of reading

That is how long the first pass takes before costing begins.

The 60% cut in reading time is won in the first pass, because every requirement that needs evidence is already flagged there with its page number.

The 60% reduction in reading time is this agent's headline figure. 26 evidence requirements among 340 is a typical ratio for a specification of this size; the ratio was not counted.

Three steps through the process.

The agent extracts the requirements from the specification and flags the ones that need evidence; engineering checks whether the estimated effort holds up before submission.

1.

1.

Extract the requirements from the specification

The agent reads running text, tables and appendices and records each requirement separately with chapter and page. It merges requirements that are stated twice.

The agent reads running text, tables and appendices and records each requirement separately with chapter and page. It merges requirements that are stated twice.

340 requirements from 118 pages, each with chapter and page number

2.

2.

Flag evidence requirements in the text

The agent flags every requirement that calls for a test certificate, a declaration or a sample approval. It names the required evidence using the wording of the requirement.

The agent flags every requirement that calls for a test certificate, a declaration or a sample approval. It names the required evidence using the wording of the requirement.

26 evidence requirements, 4 of them material certificates under Appendix C

3.

3.

Estimate the effort per requirement

For each requirement, the agent places the requirement text next to the portfolio data and suggests an effort category, each with a reference. Engineering goes through the suggestions and sets the basis for costing.

For each requirement, the agent places the requirement text next to the portfolio data and suggests an effort category, each with a reference. Engineering goes through the suggestions and sets the basis for costing.

Requirements list LH-2026-072, 61 effort suggestions with references

What the agent does not do.

It does not set the basis for costing.

It does not set the basis for costing.

It categorises and backs each call with a reference. Which effort goes into the quotation is the responsibility of engineering together with quotation management.

It does not judge whether a requirement is technically feasible.

It does not judge whether a requirement is technically feasible.

It places requirement text and portfolio data side by side and flags where they diverge. Whether the product meets it is for the relevant department to say.

It cannot analyse applicable documents that are not enclosed with the specification.

It cannot analyse applicable documents that are not enclosed with the specification.

If chapter 9 refers to one of the customer's in-house standards that was not sent, it lists the requirement as open with a note on the missing appendix.

Connected systems

Requirements management

PLM system

quotation costing

Operations

Deployment model

EU cloud or private cloud

EU cloud or private cloud

Data processing

GDPR-compliant, no model training on your data

GDPR-compliant, no model training on your data

Responsible teams

Engineering, quotation management

Engineering, quotation management

The questions that come up before the first meeting.

How quickly is the Requirements Specification Analysis Agent ready to use?

Where is the data processed?

Where does the figure “60% less reading time” come from?

Related agents.

All agents

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English
neuland.ai

The AI management and orchestration platform from Cologne.

Developed in Cologne. Operated in the EU or in your data center.

Certifications and compliance: ISO 27001, ISO 9001, GDPR, EU AI Act, DORA, StBerG, and BRAO
WirtschaftsWoche Best of Technology 2026 seal, 2nd place in the Process Management category for neuland.ai

© 2026 neuland AI AG