Case study 04 · Procurement

Syphon AI

Tenders run to 200 pages, and one missed line can kill a bid. Syphon reads the whole document, lists every requirement, flags the traps, and shows the exact page behind every answer.

Product
RFP and procurement copilot
Industry
Procurement, enterprise
What we did
Document AI pipeline, product design, web app
Used by
Bid teams and procurement officers
Tender_Facilities_2026.pdf212 pages read · 6 findings
9. Submission requirementsPage 147 / 212

§9.2Proposals shall be submitted in two sealed envelopes, technical and financial, clearly marked.

§9.3A bid bond of two percent (2%) of the bid value must be submitted in original form no later than 12:00 on the closing date. Bids without an original bond will be rejected without evaluation.

§9.4Late submissions will not be accepted under any circumstances.

Try it: click a finding or a page marker, or ask the document a question. The tender is fictional.

10×

faster first review of a tender than reading it by hand.

Hours

to decide whether a bid is worth chasing. It used to take days.

200+

page tenders read in full, appendices and scanned pages included.

1 click

from any finding or answer to the exact line it came from.

01The problem

One sentenceon page 147.

A bid team can spend three weeks on a proposal and lose it on day one, because the bid bond had to be the original, not a copy, and that rule sat in one sentence deep in the submission section.

Tenders hide their deal-breakers in appendices, contradict themselves between sections, and bury obligations in tables. Reading them properly takes days, and people still miss things.

Page 147, §9.3 “Bids without an original bond will be rejected without evaluation.”
02How it works

Read like an expert.Prove every word.

Tap any step to see what happens there. Nothing reaches the bid team without a page number attached, so every finding can be checked in seconds.

Step 2

Read. The document is read page by page, including tables and scanned pages, and every sentence keeps its page and section number so it can be found again.

03The question every buyer asks

“How do I knowit didn’t make that up?”

It is the first objection to AI in any legal or procurement team, and it is the right one. A confident wrong answer in a bid is worse than no answer at all.

So Syphon is built to show its work: every finding and every answer links to the page and clause it came from. And when the document simply does not say, it answers Not in the document instead of guessing. Try the third question in the reader above.

AI
Reads and drafts

Reads every page, lists the requirements, drafts answers. Never without a source.

Rules
Checks

The team's own rules, applied to every tender the same way.

Team
Decides

People decide whether to bid and sign off every answer. The AI saves them the reading.

04Both sides of the table

For the team that bids.And the team that buys.

Suppliers use Syphon to read tenders. Buyers use it to write them. The buyer side starts from what they need to do, asks a few guided questions, and drafts the document.

Seller side

Read the tender

  • Every requirement as one checklist
  • Deal-breakers and contradictions flagged
  • Questions answered with the source page
Buyer side

Write the documents

  • Update procurement policies
  • Create procurement documents and RFPs
  • Run market research on suppliers
Guided questions
How are suppliers evaluated and selected?
Which approvals are needed above what value?
Which new regulations must it reflect?
First draft
Procurement policy
1. Purpose and scope
2. Roles and approval limits
3. Supplier selection and evaluation
4. Compliance and new regulations
5. Breaches and consequences
05How we built it

The hard partis not the AI.

Any model can summarise a clean page of text. Real tenders are not clean: two-column layouts, tables that run across pages, scanned annexes, clause numbers that restart in every appendix.

Most of the work went into reading the document faithfully and keeping every sentence tied to its page and clause. Once that is right, the answers can always point back to the source.

Step 1

Real tenders first

We collected real tenders of every shape and wrote down what a senior bid manager looks for in each.

Step 2

Faithful reading

Layout-aware parsing for columns, tables and scans, with page and clause anchors on every sentence.

Step 3

Findings and answers

Requirement extraction, rule checks and question answering, each tied to its source.

Step 4

Both sides

The seller workspace, then the buyer side: guided questions that turn into policies and tender documents.

For the technical reader.

Document AI

Layout-aware parsing and OCR for scanned pages, tables and multi-column layouts.

Retrieval (RAG)

Every chunk keeps its page and clause, so answers are grounded and cited.

GPT-4o

Requirement extraction, rule checks, question answering and document drafting.

Python backend

The processing pipeline and API behind the seller and buyer workspaces.

Common questions

What is Syphon AI?

A procurement copilot that reads long tenders, lists every requirement, flags disqualifying traps and contradictions, and answers questions with the exact source page.

How can teams trust its answers?

Every finding and answer links to the page and clause it came from, and when the document does not say, Syphon answers “Not in the document”.

Can it read tables and scanned pages?

Yes. It reads page by page, including tables, appendices and scanned pages.

Is it only for suppliers?

No. Buyers use it to draft procurement policies, RFPs and supplier research from a few guided questions.

More case studies

All case studies →