Case · Engineering and public tenders · INTED
From three days to a few hours.
Reads tender documents and pulls deadlines, requirements, amounts and guarantees into a spreadsheet, with a link to the source paragraph.
Sample data This case is built with sample data until the client's written permission exists. Real numbers get published with name, period and method.
−85%
reading time per tender, first three months
How it was measured Hours per tender before and after, over the first forty tenders.
The context
Engineering and public tenders · 60 people · Google Drive and spreadsheets
Integrated with Google Drive, Google Sheets, email.
- 01
What we found
Two people read every tender in full, 80 to 300 pages, to pull out twenty data points. Three days per tender. And they bid on fewer tenders than they could.
- 02
What we built
A reader that takes the tender PDF, pulls deadlines, requirements, amounts and guarantees into a spreadsheet, and leaves next to each value a link to the paragraph it came from, to verify in one click.
How it works
- 03
What happened
Reading time went from three days to a few hours, measured over the first forty tenders. With the same people they bid on more tenders.
written permission from the client: name, number, period, quote
Let's talk
Are we the right fit for your company?
Tell us what's going on and we'll tell you frankly whether we can help, and how.
- We reply within 24 business hours
- The first conversation is free
- We come prepared: you leave with three concrete things for this quarter, whether you continue with us or not.