Tendaro is built for companies that answer tenders. Public publications, private RFQs, buyer-portal packages and uploaded documents run through the same reviewable workflow with company knowledge, sources and human approval.
The formal course of a Swiss tender is similar across industries: publish, ask questions, prove qualification, submit the bid, await the award. What differs is the substance. An IT provider proves certifications and reference architectures, an engineering firm key people and methodology, a construction company capacity, collective labour agreement compliance and subcontractor lists. That is why Tendaro is built industry-neutral but set up differently per profile.
The mechanics are identical: tender documents are structured, requirements are captured individually with their source, matched against existing company knowledge and returned as a supported draft. What changes is the structure of the knowledge library and which evidence the Submission Check profile enforces.
The five pages are examples, not a restriction. Tendaro does not require an industry configuration. If you regularly answer public or private tenders and your knowledge currently sits scattered across documents and people's heads, the same workflow applies.
No, not in the sense of development work. The knowledge library and the Submission Check profile are set up for your evidence types and tender types during onboarding. The underlying workflow is identical.
Yes. Public tenders from SIMAP, private RFQs, invitations from buyer portals and manually uploaded documents run through the same workflow in the same workspace. The difference lies in the deadlines and the formal requirements, not in the tool.