Use cases · Sales & B2B

How it works

You load the entire tender pack — invitation, specification, contract terms, pricing schedules, every annex — and overnight the machine reads all of it in one pass and produces a bid / no-bid memo: what is actually being asked, what would disqualify you, what the real obligations are, and what looks dangerously absent. This is not the lookup tool that answers single questions from a page; here the model reasons across the whole document to reach a recommendation that a person then owns. It runs on ml2, the machine with the bigger card, because a job this size keeps the attention layers and the whole working memory of the read on the GPU while the bulk of the model sits in ordinary system memory — for any one word only a small part of the model does the work, which is what lets it finish a long read overnight. That same design is why it cannot answer while you wait: it is an overnight job by nature, not a chat.

Data you need

The complete pack as files with selectable text — the invitation, the terms, the pricing schedules and all the annexes, not a subset. Public-sector packs routinely arrive as scanned or image-only PDFs with no text layer, and those return nothing useful until they have been OCR'd first, as no vision model is served. Nothing of your own is required, but a memo written from half the annexes is worse than none, so a complete, readable pack is the real prerequisite.

What to expect

Where the pack is complete and readable, the memo is a strong first read that surfaces the clauses that decide the matter and saves a person from cold-reading hundreds of pages. It will still miss things: a disqualifying requirement buried in an annex the model treated as minor can be left out of the memo entirely, so "nothing dangerously absent" is never proof that nothing is. Contradictions between two documents can come back as one confident recommendation rather than a flagged conflict, and the model cannot price the bid or judge whether you have the capacity to deliver. It reads and drafts; it does not decide, and its reading is not legal advice.

Where people stay involved

The bid owner reads the memo against the pack and makes the call — the memo is a briefing, not the decision. Every mandatory requirement and deadline it names is checked against the source document, because in tendering a wrong "yes, we qualify" is a disqualification, not a typo. The go / no-go decision, and any commitment that goes into the submission, is always a person's and never automatic.

• Draft a quote from a customer's enquiry email and your price list

  Turns an inbound enquiry and your price list into a filled-in quote draft for a salesperson to check and send — a document to correct, not a blank page.

• Pull the line items out of RFQ emails and PDFs into a spreadsheet

  Extracts part numbers, quantities, units and dates from RFQ emails and PDFs into one consistent table, instead of someone retyping them.

• Sort incoming sales emails: real enquiry, existing customer, supplier, junk

  Tags every email hitting the sales inbox — new enquiry, existing customer, supplier, junk — within seconds, so real enquiries reach the right person.

• Grade new leads against your own definition of a good customer

  Scores each new enquiry against your written definition of a good customer, with a short 'why' note the salesperson can read and disagree with.