Russian public procurement · 44-FZ

Tender →
analysis in 5 minutes

AI analysis of Russian public procurement documents (44-FZ). Send the bot a link from zakupki.gov.ru: it downloads the documents, reads them and lays out the requirements for every item, deadlines, bid security, risks and the national regime. An hour of reading the spec becomes five minutes.

How it works
  • 44-FZ + 223-FZ
  • Requirements per item
  • National regime, Decree 1875
  • Scans and archives: OCR

Nothing to install or set up: open Telegram, send a link, and a few minutes later the analysis is in the chat. Send a batch of links and the bot works through them one after another.

Sample report
TenderLens
📥 Downloaded 4 documents + item specs from the notice page
🧠 Analyzing: Supply of office and photo paper…
📋 Tender card
• Starting price: 886,658 RUB
• Bids due: 12 Aug, 09:00
• Bid security: yes (8,866 RUB)
• Payment: within 7 business days of acceptance
⚠️ Risks
🔴 Contract security 10%
A bank guarantee is needed before signing
🟡 Acceptance against certificates
A certificate of conformity for every item
📦 Items (4)
1. Office paper A4 (1,200 packs) — 440.50 RUB/unit 📖 i.e.: white A4 paper, 80 g/m², class C 🇷🇺 national regime: ban basis: OKPD2 17.12.14.110
3 steps

From a link to an analysis

1

You send a link

Or the documents themselves: PDF, DOCX, XLSX, photos, archives. Scans go through OCR. Works with 44-FZ and 223-FZ notices.

2

The bot analyzes the tender

Starting price, deadlines, risks, the national regime under Decree 1875. It finds item specs even where the documents leave them out: straight from the notice page on the EIS.

3

It sends the analysis

The tender card, risks, items with their requirements and national regime: in the chat and in the web dashboard. Then it is your call: price it or pass.

Key features

What TenderLens does

EIS page

Reads what the documents leave out

A common case: the spec says "as per the notice", and the item specs and quantities live only on the tender page. The bot picks them up from there on its own.

Requirements

Every parameter on its own line

Buyers write requirements as ten pages of solid text. The bot breaks them down by item: parameter, value, mandatory or not. You see exactly what you will have to prove.

Risks

What stands between you and a bid

Bid and contract security, delivery deadlines, documents at acceptance, unusual payment terms. Every risk comes with a level and an explanation, not vague words.

Officialese

Puts it in plain words

"Articles of vulcanized rubber" → rubber gloves. Next to the buyer's wording the bot writes what the item really is, so a misreading shows up at once, before you bid.

Queue

A batch of tenders at once

Up to 20 links in one message. The bot handles them one by one and sends everything to the chat; you come back to finished analyses. Overnight works too.

Decree 1875

National regime by code

Ban, restriction or preference is decided from each item's OKPD2 or KTRU code against the lists of Government Decree No. 1875, not by eye.

New

Drop in links by the batch

Send the bot a batch of tenders in one message and get on with your day. It works through them one after another: downloads the documents, reads them and sends an analysis for each. A batch of eight is done in under two hours, between other tasks or overnight.

12:00you send 8 links → "📦 Added 8 tenders to the queue"
12:01the bot picks up the first tender
12:14the first one is ready: the analysis is in the chat
13:52"🏁 Queue done: ✅ 7 · ❌ 1"
13:55you pick the 2 tenders worth bidding on
Why bother

By hand vs the bot

By handWith TenderLens
Read the spec 30–60 minutes: EIS tabs, documents, scans ~5 minutes, the bot does it all
Write out the requirements By hand into a notebook, some get lost in the solid text A list for every item: parameter and value
Spot the pitfalls You notice the security and deadlines after you have bid Risks with a level and an explanation, right away
National regime Match OKPD2 codes against the Decree 1875 lists by hand Ban / restriction / preference by the item's code
10 tenders at once Not realistic A batch in the queue, done while you work
FAQ

Common questions

What are 44-FZ and the EIS?

44-FZ is the Russian federal law on public procurement. Tenders under it are published on zakupki.gov.ru, the Unified Information System (EIS), together with the specification, the draft contract and the price justification. That is what the bot reads.

Which laws does it cover?

44-FZ and 223-FZ. The bot understands both notice formats on zakupki.gov.ru, including tenders where the item specs are only on the notice page and not in the documents.

Does the bot find prices and suppliers?

Not at the moment. The bot analyzes the tender: requirements, deadlines, security, risks, national regime. Product matching and margin calculation were taken out of the product until they reach the accuracy it needs: no answer beats a wrong one.

How far can I trust the analysis?

The bot reads the documents and the notice page. Next to the buyer's wording it writes how it understood the item, so a mistake is easy to see, and a value the documents do not give stays empty instead of being guessed. The analysis saves an hour of reading; a person still submits the bid.

What do I need to start?

Just Telegram. Open the bot, send a link to a tender, and a few minutes later you get the analysis. Nothing to install, no sign-up forms, no card.

Your next tender
gets read by the bot

Telegram bot + web dashboard · 44-FZ · nothing to install