External-source research synthesis, not a Sander Gansen client result. Evidence reflects the supplied October 2026 research and source-specific dates.
The problem sits between commercial and engineering teams
A long machinery tender combines drawings, referenced standards, commercial clauses and requirements owned by different specialists. The expensive work is not just reading hundreds of pages. It is making sure the right department sees the relevant clause, resolves the ambiguity and records the decision before the final offer is prepared.
What Atira reports for ROBEL
The provider-hosted ROBEL case describes tenders involving more than 18 specialist departments. It reports 95 sales-and-engineering hours saved per RFQ and productive implementation within a week, attributed to team lead Irfan Coskuner. Work includes clause annotation, red flags, stakeholder allocation, parallel review, norm mapping, first drafts of sub-supplier RFQs and technical summaries or test plans. More than 20 internally developed agents are described as embedded in the tender process.
A reported saving is not an audited baseline
The public case does not disclose sample size, measurement period, baseline, error or rework results. Independent reporting of the same customer claim does not independently measure it. Public product screens and a contact form do not establish a self-service trial on live tenders. Norm mapping is assistance in finding relevant material; it is not legal, safety or certification sign-off.
Build a requirement register, not a confident summary
For an illustrative packaging-machine manufacturer receiving multilingual URS documents, record each clause or page, extracted requirement, source, internal specification and revision, proposed compliance or deviation, unanswered question and responsible department. Make citations inspectable. A green summary without the clause and owner can conceal a missed requirement. Parallel review is useful when the final decision remains traceable.
Keep technical and commercial decisions separate
Engineering approves configuration and feasibility. Quality checks standards and certification assertions. Commercial owners approve prices, terms and the final signature. A Teams message or ERP writeback is not itself approval. Deterministic product and price rules stay authoritative where they already govern the business; a language model should not invent a substitute because a tender is ambiguous.
Evaluate margin and rework alongside speed
Replay representative historic RFQs with missing norms, expired prices, mixed units, alternate materials and impossible delivery windows. Measure extraction recall on critical clauses, incorrect green decisions, clarification loops, engineer hours, review/rework and quoted-to-realised margin. A faster draft that misses an exclusion can increase risk. The useful first pilot leaves final release with the named approver and compares actual work against a defined baseline.
Sources and next reading
Explore OfferSignal · Focused Business & AI Workshop · All research

