IoT procurement requirements support.
Shape the requirements before you tender, so you buy what you actually need and own what you buy. Zero46 writes the security and NIS2 requirements that go into public procurement documents.
What's included
- Technical requirements: architecture, data model, integrations, exit
- Security and NIS2 requirements mapped to Article 21
- Ownership clauses: code, data, infrastructure, documentation
- Evaluation support: scoring vendor answers against the requirements
Deliverable
A requirements specification ready to go into your tender documents: technical, security, and ownership requirements your procurement team can publish, and vendors cannot write themselves around.
Timeline and price
Scoped to your tender timeline; requirements work typically runs a few weeks alongside your procurement team. Fixed fee, quoted before we start.
FAQ
Why bring in an outside architect for a tender?
Because the vendors answering it have written a hundred of these and you haven't. Requirements written loosely become lock-in written contractually. We sit on your side of the table.
Do you work with LOU?
Yes. We write requirements specifications for Swedish public procurement under LOU, and equivalent requirements for tenders elsewhere in the EU.
Can you bid on the tender afterwards?
No. If we write the requirements, we stay off the supplier side of that procurement. That separation is the point.
Planning a tender?
The earlier requirements are shaped, the more room you have. Start with the form or a call.