Typical project scenarios and indicative costs
There is no single rate for “CRA implementation”. A quotation should distinguish requirements analysis, documentation and processes, technical changes, tests and potential formal conformity assessment costs. The product and the deliverables expected from the provider must be established first.
A limited scope, such as vulnerability reporting and handling, SBOM, a security update policy, risk assessment or part of the technical documentation. The quotation should clearly state what is excluded.
A project may combine product requirements, documentation, development and support processes, vulnerability management and evidence for the applicable conformity-assessment route.
A wider programme covering several product families, versions or development teams. This typically requires product inventories, common standards, phased work, priorities and separate assessment of the differences between products.
Agree whether the provider will prepare documents and processes, carry out engineering changes, or coordinate several workstreams. Define the products, deliverables, testing and formal assessment responsibilities before comparing project fees.
