A buyer sends you three emails, a forwarded thread from their operations manager, and a drawing with red pen on it. Somewhere in there is the order you are supposed to price by Friday, and you are the one who has to find it.
Why quoting straight from the thread goes wrong
Reading an RFQ thread top to bottom feels like the honest way to do it. It is also how you end up quoting the wrong job.
Threads are written in the order things occurred to people, not in the order you need them. The quantity appears in email one, gets corrected in a reply nobody copied you on, and appears a third time in a spreadsheet attachment with a different unit. The delivery date in the first message is the date the buyer would like. The date in the third message is the date their site actually opens. Those are not the same commitment, and only one of them belongs in your quote.
The bigger problem is tone. A buyer writing quickly does not mark the difference between "we need this" and "we are also thinking about this." Both arrive as plain sentences in the same paragraph. If you price everything you read, you have quoted work nobody ordered, and your number looks expensive next to a competitor who quoted only the confirmed lines. If you price none of it, you look like you were not listening. Either way you lose on something that was never a pricing problem. It was a reading problem.
The fix is to stop treating the thread as the order. Build one document from it first, then price from that document. That document is the order brief.
What belongs in an order brief
An order brief is a page, sometimes two. It is for you and your shop or warehouse, not for the customer, though a cleaned-up version of it is often what you send back to confirm. It has these fields:
- Confirmed lines. Items, quantities and specs the customer has stated plainly and not contradicted. Each one cites where it came from: the email date, the PO, the drawing revision.
- Requested lines. Things mentioned, asked about, or raised as a possibility. Priced separately or not at all until someone says yes in writing.
- Unknown lines. Things you cannot quote because a number, a spec or a decision is missing. Written down as questions, never filled in with a guess.
- Quantities with units. 48 bays is not 48 beam pairs is not 48 pallet positions. Write the unit every time.
- Dates the customer stated, and dates agreed. Keep both columns. A date you have not accepted is a request.
- Specs and documents referenced. Drawing numbers with revisions, load ratings, standards, finish, any attachment the thread points at. If a revision number is missing, that is an unknown line.
- Delivery and access terms. Who unloads, what equipment is on site, hours of access, whether it is one drop or phased.
- Who approves changes. One name, one email. Changes from anyone else go back to that person before they touch the order.
That last field saves more money than the rest combined. Most scope creep arrives from someone who is not authorized to buy.
The method, step by step
- Collect everything into one place. Copy the full text of every email in the thread, including the ones you were forwarded. Paste the relevant lines from attachments too, since ChatGPT cannot open what you did not give it.
- Ask for the brief, not a summary. A summary blends everything into an average. You want sorting: confirmed, requested, unknown, with each line traced back to its source.
- Force the units and the dates apart. Tell it to write the unit on every quantity, and to keep stated dates separate from agreed dates. If a date appears twice with different values, both go in with their sources.
- Make it list the contradictions. Where two emails disagree, you want them side by side, not resolved. You resolve them with the customer.
- Get the clarification questions. Ask for the short list of questions that must be answered before you can price, ordered by how much each one moves the number.
- Check it against the thread yourself. Read the brief with the emails open. You are looking for anything it decided rather than quoted.
- Send the questions, then price. Pricing before the answers come back is how you end up revising a quote twice and looking unsure the whole time.
The job brief builder runs steps two to five in one go, because the sorting rules are already written into it. Once the brief is agreed, the quote and pricing builder takes it and produces your internal costing and the customer quote as two separate documents.
A worked example
The following is an illustration, with a fictional company and made-up figures.
Halvorsen Storage Supply is a nine-person racking and shelving distributor. Over four days they receive three emails from Redlake Provisions, a regional food wholesaler fitting out a new warehouse.
Email one, from the buyer: "We need pricing on pallet racking for the new building, roughly 300 pallet positions, delivery early November."
Email two, forwarded from Redlake's operations manager, with a floor plan attached: "Layout attached. Working on 6 aisles. We also want to look at a mezzanine over the pick face for the slow movers."
Email three, from the buyer again: "Per the site meeting we are at 384 pallet positions now. Racking needs to be in by 11/14 so the shelving crew can start. Purchasing sign-off is me, anything over spec goes through our controller."
Read as a thread, that is a mess. Read as a brief, it looks like this.
Confirmed: six aisles per the layout attached 10/24. Buyer is the approver for purchasing; the controller approves anything above spec.
Requested by the buyer, not yet agreed: 384 pallet positions, stated 10/28 and superseding the 300 in email one, and delivery on site by 11/14. Both are what the customer asked for. Neither becomes agreed until Halvorsen confirms the count is buildable and the date is achievable, in writing.
Also requested: a mezzanine over the pick face, raised once by the operations manager, never quantified, never priced, never ordered. It sits in the requested block with a note that no square footage, load rating or access method has been given.
Unknown: beam levels per bay, pallet weight per position, floor slab thickness and condition, whether the 384 positions include the mezzanine area or not, and the revision number of the layout, which arrived as a PDF with no revision block.
Halvorsen sends five questions. The answers come back: three beam levels, 2,400 lb per position, slab drawing to follow, 384 excludes the mezzanine. Now the quote is buildable: 96 bays at a list of $1,940 per bay, $186,240 of racking, freight quoted separately, install by others, net 30. The mezzanine appears on the quote as one line under exclusions: "Mezzanine over pick face: not included. Happy to price on receipt of area, load rating and access requirement."
That exclusion line is the whole point. Six weeks later, when someone at Redlake asks where the mezzanine is, the answer is already in writing and dated.
The prompt
I'm a pallet racking distributor. Below are three emails from a customer about their new warehouse, in the order I got them. Turn them into one order brief for me. Split every line into confirmed, requested, or unknown. Confirmed means they stated it plainly and didn't contradict it later. Requested means they mentioned it but never ordered it. Unknown means I can't quote it without asking. Put the unit on every quantity, and keep the dates they asked for separate from the dates I agreed to. Where two emails disagree, show me both with the date each came from instead of picking one. Don't fill in anything I didn't give you. Then list the questions I need answered before I can price it, most important first. Emails: [paste all three]
What to check before you send
ChatGPT sorts what you paste. It does not know your business, and it will occasionally promote a polite sentence into a confirmed line.
- Read every confirmed line against the email it cites. If the citation is vague, treat the line as requested until the customer says otherwise.
- Check the units. Positions, bays, beam levels and frames get swapped constantly, and the error multiplies straight into your price.
- Check nothing moved from requested to confirmed. The mezzanine test: if it is in the confirmed block and nobody ordered it, fix it now.
- Check the unknowns are still unknown. A filled-in figure you did not supply is the one thing that makes a brief dangerous.
- Confirm the approver. One name. If the thread has three people giving instructions, ask the buyer in writing who signs.
- Send the brief back before the quote. A short "here is what I have understood, please correct anything wrong" costs you one email and settles the scope argument before it starts.
Close
The order brief is not paperwork for its own sake. It is the difference between quoting the job the customer bought and quoting the job you thought you read.
Build it once, send it back, get the corrections, then price. If the quote then goes quiet, the sales follow-up sequence gives you something useful to say about the open questions instead of checking in for the third time.