I2 · Prozorro tender co-pilot — deep dive

Prepared 2026-10-20 from the Prozorro public API (53 full tender records across 10 procedure types, 2,308 decided tenders from one overnight slice, all 141 translation tenders of the last 12 months), the text of Law 4888-IX, Prozorro's standards repository and competitor pages. Rates from the overnight slice are indicative, not annual statistics. Notes and data: research_notes/Owned ideas deep dives/i2-prozorro_notes.md, i2-prozorro_stats.json, i2-prozorro_sample53.csv.

Bottom line

• Almost everything is public, but mostly not structured. Open tenders have a median of 13 criteria and 21 requirements in structured fields, but 89% are bare "I confirm" boxes. Of 439 recent 24-hour defect notices, 97% cite a clause in the Word documentation (6.7k–19.5k words). Rejection grounds, protocols, notices and bidders' contacts are all public (Prozorro API). A system can triple-check formal completeness, but can't honestly guarantee technical compliance or a win.
• The pain is measurable. In 834 decided open tenders, 20.4% of awards were rejected and 34% of tenders got a 24-hour correction notice. One rejection in five was "didn't fix within 24 hours". Scaled up, that's roughly 40–50k rejections and 60k notices a year (estimate).
• "AI reads the tender documents" already sells at about 100 UAH a tender. SmartTender's SmartCheck AI charges 89–129 UAH per analysis on promo (SmartCheck AI); Newtend has Newtend AI (Newtend). The draft report missed this. Your edge: each buyer's defect history, deterministic checks of the customer's own files, a 24-hour rescue and a written guarantee.
• The MVP needs no runtime model. Requirements are the same for every bidder, so documentation is read once per tender: about 20–60 a day in 2–3 CPV niches, as operator work on your Claude Code subscription if you approve. File checks run on rules plus local OCR.
• The most personalised channel is public rejection data: "Your bid in tender X got a notice for Y — here's a free check of your next one." It's legally grey (e-commerce consent versus opt-out, personal-data notice), so email companies once with an opt-out after a lawyer's review. Reach FOPs through a "Why did I lose?" lookup, buyer pages and opt-in alerts.
• Sell a subscription, not arbitrage. Plans at 490 and 1,490 UAH plus 249 UAH checks. About 330 subscribers on 1,490, or about 485 on a blend, gives $10k/month profit: 0.8–1.2% of the "more than 42,000" competitive bidders in 2025 (Forbes UA). Bidding yourself fails the zero-owner-time test: in translation, 94% of tenders demand prior analogous contracts and prices land 38% below estimate.
• Timing: Law 4888-IX takes effect on 24 March 2027, with machine-readable documents, one correction round per bidder and coded rejection grounds; Prozorro has already drafted 57 codes (Rada; ProzorroUKR). Launch on today's rules; have the 2027 rule set ready by March.

Is everything public?

Coverage by item (from the 53-record sample; "open" means open tenders with особливості under Resolution 1178):

What can be triple-checked. Three independent layers back each other up:

1. Structured criteria: the skeleton, straight from the API (criteria standard).
2. Documentation-derived requirements: read once per tender from the Word files. Today about 98% of the non-signature tender files are Word. The 2027 law bans scans and photos.
3. This buyer's history: what it flagged in past 24-hour notices and rejection protocols. If layer 2 misses something a repeat buyer always checks, layer 3 catches it.

Verifiable without judgement: a file for every requirement; formats and sizes; a valid КЕП signature; the signer being the authorised person in the EDR register; issue dates before the bid deadline (Law 4888-IX bans later documents except the bidder's own letters); "not older than N days" rules; VAT, single-tax and sanctions registries; bid validity and language. These are frequent in notices: authority documents 50%, signatures or seals 44%, dates 12%.

Still judgement: technical-spec compliance (31% of notices), whether a past contract is "analogous" (30%), free-form letters. A third of bid PDFs are scans, so checks need OCR.

What the guarantee can honestly be: "If your bid gets a 24-hour notice or a rejection for a formal item our check marked green, we refund that check and give you a month free." Liability is capped at fees paid, formal items only, never technical compliance or winning. Backtest against historical notices first and publish the miss rate. Under a 5% miss rate (target), refunds cost under 5% of check revenue (estimate). Have a lawyer check the terms.

What the product does

Open the mockup (Ukrainian, fictional data). Direct screens: checklist, bid-pack check, 24-hour rescue.

Feature map:

• Alerts by CPV, region and value, with deadlines and bid-security amount (email first, Telegram optional).
• Tender card with the three-layer checklist; each item shows its source (field, clause, or "flagged by this buyer N times").
• Document vault with expiry tracking, reused across bids.
• Bid-pack check: green/amber/red report with the fix for each problem.
• 24-hour rescue: alert within minutes, notice turned into a to-do, templates, countdown.
• "Why did I lose?": your public rejections and notices, explained.
• Letter templates (consent, sanctions declaration, authority), filled from your data.

flowchart TD
  A["Free alert or why I lost lookup"] --> B["Pick CPV niches and region"]
  B --> C["New tender alert"]
  C --> D["Tender card and 3-layer checklist"]
  D --> E{"Bid on it?"}
  E -->|"no"| C
  E -->|"yes"| F["Attach files from vault"]
  F --> G["Bid-pack check"]
  G --> H{"All green?"}
  H -->|"no"| I["Fix list and templates"]
  I --> G
  H -->|"yes"| J["You sign with КЕП and submit on your майданчик"]
  J --> K{"24h notice posted?"}
  K -->|"yes"| L["24h rescue to-do and countdown"]
  K -->|"no"| M["Result and lessons saved"]
  L --> M

Submission stays on the customer's platform under their КЕП; you never hold their keys.

Getting to FOP owners

Big platforms (SmartTender, Newtend) are competitors first, not partners.

Recommended sequence:

flowchart LR
  A["Pick 2-3 CPV niches"] --> B["Why I lost lookup and buyer pages"]
  B --> C["Opt-in niche alerts"]
  C --> D["Lawyer-approved email pilot, 300 companies"]
  D --> E{"3 pct clicks and 1 pct pay?"}
  E -->|"yes"| F["Scale to 1000 a month in niches"]
  E -->|"no"| G["Fix offer or stop outreach"]
  F --> H["Accountant affiliates and small platforms"]
  H --> I["YouTube and Diia.Business"]

Subscription or arbitrage?

Arbitrage reality check: written translation (CPV 79530000-8, 141 competitive tenders, last 12 months). 114 awards worth 40.2M UAH, median 88,556 UAH; only 23 suppliers won, the top 5 took 57%. Prices land 37.7% below the buyer's estimate. 94% require an analogous past contract, 57% qualified staff, 18 notarised or sworn translation. Payment is almost always after delivery (140 of 143 terms, median 10 days). FOPs took 45.6% of awards. So the cleanest AI-friendly category is about $1M a year, closed to newcomers and fought on price, and you'd sign every bid and carry delivery penalties. Other "AI-deliverable" codes turn out to be mostly printing, valuation, teaching equipment or software maintenance.

Recommendation: a self-serve subscription with per-check top-ups. Add a capped done-for-you pack with a success fee after 50 paying customers. Arbitrage only as a later one-off probe in direct contracts under 50k UAH, where no tender is needed (Law 922-VIII), outside your customers' categories.

Where the AI compute runs

Next steps

gantt
  title I2 four-week test
  dateFormat YYYY-MM-DD
  section Build
  Pick niches and backtest set :a1, 2026-10-21, 3d
  API watcher alerts and 24h rescue :a2, after a1, 6d
  Checklist extraction and backtest :a3, after a1, 8d
  Bid-pack checks and OCR :a4, after a2, 7d
  Web app and monobank checkout :a5, after a4, 5d
  section Go to market
  Lawyer review of outreach and terms :b1, 2026-10-21, 10d
  Why I lost lookup and buyer pages :b2, after a3, 6d
  Email pilot then niche scale :b3, after b1, 21d
  section Decide
  Day 30 go or kill :milestone, m1, 2026-11-20, 0d
  Day 60 review :milestone, m2, 2026-12-20, 0d

I do:

• Pick 2–3 CPV niches with many FOP bidders and frequent notices.
• Build the watcher, checklist, bid-pack check, 24-hour rescue, lookup, buyer pages and web app.
• Backtest against historical notices; publish the miss rate.
• Run outreach, support and weekly metrics; prepare the 2027 rule set by March.

You do once:

• monobank acquiring for your FOP.
• A lawyer's review of outreach text, privacy notice, offer and guarantee.
• Approve documentation reading on your Claude Code subscription, and the outreach plan.
• Be the named sender (the law requires your FOP details in the email).

You do recurring:

• Approve guarantee refunds and the rare escalation, about 1 hour a week (estimate).
• From day 30, optional calls with partners.

Go/kill thresholds:

• Week 2: the checklist backtest finds at least 90% of the items buyers flagged in your niches. Below that, narrow the niches or stop.
• Day 30: at least 150 free sign-ups and at least 15 paying (or 40 paid checks), with outreach complaints under 1%. Kill at fewer than 5 paying.
• Day 60: at least 50 paying, churn under 15% a month, refunds under 5% of revenue.
• Kill at any point if SmartTender or Prozorro ships free buyer-defect history plus file checks.

Risks and open questions

• Incumbents: SmartTender could add file checks; Prozorro already auto-checks the EDR and anti-corruption registers for winners.
• Outreach legality: if the lawyer says no, GTM falls back to lookup, pages and opt-in alerts, which grow slower.
• Guarantee exposure: formal items only, capped at fees; a wrong "green" on a big tender still costs reputation.
• Law change on 24 March 2027: tenders started earlier finish under old rules, so you run two rule sets for a while.
• Data limits: the overnight sample and keyword taxonomy are indicative; construction is under-sampled; YouControl, Opendatabot and Zakupivli.pro blocked automated access.
• Ops: OCR for scans, a certified КЕП library, support drifting into consulting. Keep billing off Telegram (AIN).
• Reuse: the same engine transfers to I4 grant applications.
• Questions for you:
  • Which suppliers or niches do you know?
  • Do you approve reading documentation on your subscription?
  • Will you be the named email sender?
  • What guarantee size are you comfortable with?

Sources

1. Prozorro public API (openprocurement 2.5), tenders
2. Prozorro API documentation
3. Prozorro portal and search
4. ProzorroUKR standards: criteria
5. ProzorroUKR standards: draft rejection reasons and criteria for Law 4888
6. Law 4888-IX "Про публічні закупівлі" (27.05.2026)
7. Law 922-VIII "Про публічні закупівлі" (current edition)
8. Resolution 1178 (особливості)
9. Forbes UA: 10 business problems in Prozorro the new law solves (Anna Kuts, TI Ukraine, 28.09.2026)
10. SmartTender SmartCheck AI and tariffs
11. PravdaTUT advertorial: SmartTender AI tools (06.01.2026)
12. Newtend AI
13. Newtend tariffs (regulated participation fees)
14. Newtend legal support for bidders
15. Clarity Project tariffs (Wayback snapshot, 07.10.2026)
16. Clarity per-company Prozorro pages (Wayback index)
17. Law 675-VIII "Про електронну комерцію"
18. Law 2297-VI "Про захист персональних даних"
19. Tax Code of Ukraine (Art. 291.4)
20. AIN citing Opendatabot: FOPs winning tenders (20.07.2026)
21. monobank internet acquiring
22. Ukrainian Startup Fund: Microsoft for Startups credits up to $200k
23. AIN: Diia.Business marketplace of digital solutions (29.07.2025)
24. Prozorro infobox online courses
25. AIN: t.me domain put on hold (14.07.2026)