Most US software teams think the Cyber Resilience Act starts in December 2027. Its reporting duty started on September 11, 2026 and covers products already on the EU market: an actively exploited vulnerability needs an early warning within 24 hours. You can only report that fast if you know which products contain the vulnerable component, which is what an SBOM tells you.
First action
Write the five questions for the check and add a "book a CRA reporting check" button to the September 11 post and the readiness tool.
How to measure it
CRA reporting checks held
- Now
- –
- Target
- 15
- By
- 60 days
Steps
Write the check
Five questions: EU sales, products in scope, current SBOMs, who reports, how fast.
Sr. Sales Engineer 1 day
Prepare the demo
A scan of one product showing where a vulnerable component appears.
Sr. Sales Engineer 1 day
Add the button
On the CRA post, the readiness tool result and the webinar page.
Director of Marketing 2 hours
Email the list
Webinar registrants and US accounts with EU customers.
Director of Marketing 1 day
Run the checks
Thirty minutes each, with a written summary afterwards.
Sr. Sales Engineer 30 minutes each
Hand to sales
Checks that show a gap become opportunities for the AEs.
Head of Sales ongoing
Collect objections
Log what stops each company and feed it into content.
Sr. Sales Engineer weekly
Why it works
Offer a free 30-minute "CRA reporting check" run by the Sales Engineer: confirm which products are in scope, show the customer's own dependency inventory from a FOSSA scan of one product, and walk through who would file a 24-hour warning and from what data. Promote it with the November 18 webinar for US companies and the existing readiness tool, and follow up with the CRA demo form.
It turns a legal deadline into a technical conversation the Sales Engineer is hired to lead, with Legal, Engineering and Security in the room, and FOSSA already has the content to support it.
Ready to use
ChecklistCRA reporting check (30 minutes)
[ ] Do you sell software or connected products into the EU? [ ] Which products are on the EU market today? [ ] Do you have a current SBOM for each one? [ ] If a component is exploited tomorrow, how fast can you list affected products and versions? [ ] Who files the 24-hour early warning, and with what data? [ ] What would you need to send a 72-hour notification?
Risks and how to handle them
Sounds like legal advice
Frame it as a technical readiness check and point to counsel for scope.
Too few EU sellers among leads
Target accounts whose customers or offices are in the EU.
Evidence
- Your websiteCyber Resilience Act work: a September 11, 2026 post says the CRA reporting duty "applies now, and it applies to products already on the market", while most of the act applies from December 11, 2027; a CRA readiness assessment tool; a CRA demo form; a November 18 webinar for US-based companies; and German pages only for CRA content.Source
- Law firm briefingsJones Day and McCann FitzGerald confirm CRA reporting duties started September 11, 2026 (early warning within 24 hours of becoming aware of an actively exploited vulnerability, notification within 72 hours), apply to in-scope products already on the EU market, and that most other obligations apply from December 11, 2027; fines reach EUR 15 million or 2.5% of worldwide turnover.Source
- HiringSr. Sales Engineer, West Coast ($200,000-$240,000 OTE): supports Enterprise AEs with demos and business value cases, "complex sales engagements with touch points in Legal, Engineering, and Security", RFPs, RFIs and POCs; evangelises FOSSA with end users, partners and thought leaders; wants a "history of creating developer-facing content".Source