Fintech · Government solutions

Manipal's Claude agent cut tender review from a day to 9 minutes

Tender CoPilot is a tender analyst for The Manipal Group, built by KnackLabs on Claude. It watches 280+ tender portals, writes a cited analysis report for each tender in about 9 minutes, and answers the team's questions inside Microsoft Teams, across 17 business units.

The agent
Tender CoPilot
Where it lives
Microsoft Teams
Built on
Claude API
Sonnet 5 + Haiku 4.5 on Gantry
Status
In production
17 business units live
tender-copilot / tender inbox
Tender CoPilot tender inbox - discovery across portals, search, filters, Watching status and Teams notification actions

FIG.01 · the tender inbox: new tenders from 280+ portals, each one a click from a Teams notice

The challenge

Finding tenders was slow, and reading them took days.

Manipal's business-development team competes for government and enterprise contracts worth crores. The opportunities are real, but finding and reading them took most of the team's time.

Tenders and RFPs are published across 280+ separate portals, central and state government, PSUs, private buyers, each with its own format, login, and posting rhythm. The only way to keep up was manual: scan, download, read dense RFPs, and decide whether to bid.

Reading was the slow part. An average tender runs to about 30 pages and took a reviewer a full day. A large one, 200 pages or more, took about six days. Eligibility, EMD, deadlines, penalty clauses, and compliance terms were pulled out by hand, different reviewers picked up different things, and questions from legal and finance went back and forth over email.

1 day
to review an average 30-page tender by hand
~6 days
to review a 200-page tender by hand
The solution · how it works

Claude reads every tender and answers the team in Teams.

We embedded a Forward Deployed Engineer with the BD team to map the workflow, then built Tender CoPilot on Gantry with Claude doing the reading and the answering. It reports back where the team already works.

01
It monitors every portal.
Continuously scans 280+ tender portals for new postings. Claude Haiku 4.5 also finds new portals worth watching, and an admin approves each one before it goes live.
02
It judges relevance, not keywords.
Each posting is semantically ranked against the profile of each of Manipal's 17 business units, so every team sees the tenders that fit it, not every keyword match.
03
It reads the whole tender so the team doesn't.
Once an admin approves a deep analysis, Claude Sonnet 5 reads the full document set and writes a structured report: eligibility, EMD, deadlines, penalty clauses, and compliance terms, each finding cited to its page. An average tender takes about 9 minutes.
04
It answers in Teams.
Every relevant find lands as a Teams alert. Anyone can then ask about the tender in plain language, and Claude answers from the document with a page citation. Each business unit sees only its own tenders.
tender detail · summary
Tender CoPilot tender detail - AI-written tender summary and core details

FIG.02 · a tender's AI summary and core details, ready before anyone opens the PDF

Why it works

A wider net and a sharper filter.

More coverage usually means more noise. Semantic ranking gives both: every portal watched, only the right tenders surfaced.
Every Claude report and answer cites its page, so legal and finance can check each finding before a go or no-go call.
Built on Gantry: deep analysis runs only after admin approval, each business unit sees only its own tenders, and every action is audit logged.
tender-copilot · discovery
live
280+
portals monitored
17
business units live
119
tenders analyzed by Claude since go-live
~9 min
for a cited report on an average tender, down from a day
3,000+
questions answered in Teams, 95% in under 50 seconds
~$0.95
average cost per analysis report
The results

Tender review went from days to minutes, and the gain is biggest on the largest tenders.

Measured on the live deployment: 119 tenders analyzed across 17 business units since go-live.

Before
With Tender CoPilot
Average tender (~30 pages)
About a day of manual review
A cited Claude report in about 9 minutes
Large tender (200+ pages)
About six days of manual review
About 15 minutes for a 234-page tender
Questions on a tender
Back and forth over email
3,000+ answered in Teams, 95% in under 50 seconds, each cited to its page
Portal coverage
Checked by hand, portal by portal
280+ portals monitored automatically
Under the hood

How Tender CoPilot is wired

Continuous portal monitoring, semantic relevance ranking, retrieval over the full tender documents, and Claude for the reports and the answers, delivered in Microsoft Teams, all on Gantry.

Sources
Govt portals
central · state · PSU
Enterprise RFPs
private buyers
280+ portals
each its own format
→
Tender CoPilot on Gantry
monitor
scan + Claude Haiku 4.5 discovery
rank
vector search
read
Claude Sonnet 5 reports
audit
every action logged
→
Delivery
Microsoft Teams
structured alert · score · summary
Ask anything
plain-language questions · Claude, cited to the page
In their words

"Tender Copilot from Knacklabs has helped us streamline and simplify our tender evaluation process, making it easier for the team to analyse large volumes of tender documents and extract relevant information quickly."

The Manipal Group
Rahul Sharma
Manager, Corporate Development & Strategy, The Manipal Group
This is for you if…

…your business chases tenders, RFPs, or grants across many sources.

Your team's time disappears into finding and reading them. We don't just advise on AI. We embed our engineers and build production-ready systems alongside your team.