Small promises, kept.
We did not set out to change how you work. Loonar started with a complaint we kept hearing: the people best placed to decide on a bid are the ones with the least time to read it. So we built for that decision.
-
10 min
to read a 500+ page RFQ package end to end, from upload to a full requirement list.
-
5000+
pages of RFQs and tenders Loonar has read and structured to date.
-
0
important requirements missed, each one carrying the page it came from.
Reading large RFQ packages should never have been competing for an engineer's attention. That is the category of work we take, and we stop there.
AI where AI is strongest
AI changes how a commercial team works only where it is pointed at a job with a defined edge. Most of it is pointed at everything at once, which is why so little of it survives contact with a large RFQ.
Loonar is built as modules. Each has one mission, one input and one deliverable. The AI inside works only against the documents in front of it: your customer's package and your own reference library. Held that tightly, it is at its most reliable, and every line it hands back carries the page it came from.
The Loonar way
-
Precision
Say the specific thing.
A vague promise has to be believed. A precise one can be pictured. We describe every module down to what goes in and what comes back, so a head of sales can see the exact morning it lands on their desk.
-
Boundaries
State where we stop.
Loonar extracts, compares and drafts. It does not decide and it does not submit. Naming that edge out loud is what makes everything on our side of it worth trusting.
-
Ownership
The customer is the protagonist.
Their team answers more bids. Their margins hold. Their experts get their week back. The process stays theirs, run by their people. We are the tool; they do the growing.
Five modules, one job each
A large RFQ package is not one problem. It is the requirements, the terms, the deviations, the catalogue match and the final read before the offer goes out. We built a module for each, and kept them separate on purpose.
You run the one you need. Each takes a defined input, returns a defined deliverable, and hands back every line with the page it came from.
- 01 RFQ Analysis From received package to structured requirements.
- 02 T&C Analysis Every clause in their terms, measured against yours.
- 03 Deviation Analysis and Matching Every requirement answered with evidence, every line item matched.
- 04 Speed Reader One pass over the package; only what deviates surfaces.
- 05 Offer Review The finished offer, checked before it ships.
The team behind it
-
Gianlorenzo Gai
Co-founder & CEO
Works the commercial side: the RFQ desks we build for, and what has to be true before a bid is worth answering.
-
Matteo Giardini
Co-founder & CPO
Owns the product: what each module reads, what it returns, and where its work stops and an engineer's begins.