Case · Engineering and tenders · Electromechanical engineering and installation company
They bid on three tenders a month. They could bid on nine, with the same people.
Three steps, one chain: the system crawls the portals every day, pulls deadlines, requirements and amounts from the tender document into a spreadsheet with a link to the paragraph, and drafts the proposal. The two people in the tenders team review and sign.
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.
3 → 9
tenders submitted a month, with the same two people
How it was measured April–June quarter against July–September 2026. Portals covered: from 2 to 14.
The context
Buenos Aires · 40 people · two people in the tenders team · public procurement portals, email, Google Drive and a spreadsheet.
Integrated with Public procurement portals (COMPR.AR, BAC, provincial and municipal) · email · Google Drive · spreadsheet.
The capability Tender document reading
- 01
What nobody knew
How many matching tenders a month were sitting on portals nobody was watching.
What was looked at, and what wasn't
Two familiar portals, once a week. The full tender document (six hours) got read only when the tender looked big; the small one didn't justify two days of drafting a proposal, so it got skipped.
- 02
What showed up when we looked
In the first month of monitoring, the system crawled 14 portals (national, provincial, municipal, public utilities) and found 27 tenders matching the company's profile. Sixteen were on portals nobody watched: two neighboring provinces and four municipalities. Three were already past deadline when found, and would have been the best ones.
- 03
What decision changed
They started bidding on the small ones. With the tender document read in 40 minutes and the proposal draft built in 4 hours, the ARS 30 million tender stopped being a bad deal. Two tenders won in the quarter were on portals nobody used to watch. Hours per tender document: from 6 to under 1, as a cause, not a result.
- 04
What we built
Three steps, one chain. The system crawls the portals every day and flags the ones that match. From the tender document it pulls deadlines, requirements, guarantees and amounts into a spreadsheet, with a link to the source paragraph to verify. And with the tender document read and past proposals on hand, it drafts the technical proposal with the sections that always repeat. The two people in the tenders team review, correct and sign. Nothing goes out without one of them having read it.
How it works
- 05
How it's measured from here on
Tenders detected, submitted and won per month. The tenders manager looks on Mondays.
written permission from the client: name, number, period, quote
Other cases
- Wholesale distribution · Wholesale distributor of cleaning products Four out of ten orders arrived after 6pm. Now they load on their own. See the full case
- Distribution · Distributor of food-service supplies Nobody knew which customer was slipping away until they were already gone. See the full case
- Energy · Solar energy company for small businesses and farms The lead that came in Friday at 7pm got read by someone Monday at 10am. See the full case
- Distribution · Distributor of hardware and plumbing supplies 100 prices got checked a week. The other 3,700, never. See the full case
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.