Why Quotes, BOMs, and Submittals Should Not Live in the Same Inbox

Independent manufacturer reps and distributor salespeople still run a large part of the job from one mailbox. An RFQ arrives. A BOM arrives as a spreadsheet. A submittal package arrives as a zip of PDFs. An expedite lands as a one-line email from a buyer who needed the part yesterday. All of it sits in the same inbox, next to vendor newsletters and internal chatter.

Email is a good delivery pipe. It is a poor job system. When quotes, BOMs, and submittals live only as threads, they do not have an owner, a next action, or a due date. The quote goes out. The thread goes quiet. Engineering questions stay buried. Follow-up becomes whatever someone remembers on Friday afternoon.

This is not an outbound-sequence problem. It is not a CRM-adoption lecture. It is the document pile inside one inbox, and it is how quoted work disappears without anyone deciding to lose it.

Why do quotes, BOMs, and submittals die in the same inbox?

They die because the inbox treats four different jobs as one stream of mail.

An RFQ is a request to price work. It needs an owner, a complete set of assumptions, a send-by time, and a named next step after the quote leaves. A BOM is a structured list. It needs version control, a check against current pricing, and a record of what changed. A submittal is a package the customer or contractor must approve. It needs a checklist, a return date, and a place to store the approved set. An expedite is a live operations request. It needs a promised date and a single person who will answer the buyer.

When those four sit in one thread, nobody can tell which job is open. Two people can both assume the other is handling it. Or both can leave it, because shared mailboxes dilute responsibility. There is no expiry. There is no next meeting. There is no record of whether engineering already answered the tolerance question or whether that answer still lives eight messages down.

Industry writeups of manufacturing quoting keep finding the same failure pattern: slow response, missed follow-up, and unclear ownership, often before price is even the issue. Procition's 2026 look at quoting problems describes RFQs sitting in email, getting forwarded, and going cold because nobody can see what is still active. That matches what reps describe in their own shops: the work did not lose on price. It lost because the next step was never written down.

The other leak is the quote itself. A PDF goes out with no expiration, no list of open assumptions, and no scheduled call to walk the buyer through lead time. Then the follow-up is a just-checking-in note that adds nothing. The buying group is larger than one inbox. If the quote lands with purchasing and never reaches engineering or quality, silence is not a no. It is a document that never made it out of the first mailbox.

What belongs in a quote record instead of a thread?

You do not need a giant CRM to stop this. You need one record per request that lives outside the inbox. A spreadsheet is enough to start. A lightweight tracker is better. A custom workflow is worth it later, when volume or headcount makes the sheet fail.

Each record needs four fields, and they are not optional:

• Owner. One name. Shared ownership is how work sits.
• Type. RFQ, BOM, submittal, or expedite. Mixing types is how a pricing job hides under a PDF dump.
• Next action. A verb, not a status. Call buyer about lead time Thursday is an action. In progress is not.
• Due date. When that next action is late. If there is no date, there is no sweep.

Add three more fields once the basic four are habit: customer or program name, the date the quote or package went out, and a one-line list of open questions. That last field is where engineering questions go. They do not stay in the thread. If a tolerance, finish, or lead-time question is still open, it is the next action, assigned to the person who can answer it, with a date.

The method is simple on purpose.

1. When mail arrives, create the record the same day. If you wait until you have time to price it, the request has already entered the same fog as everything else in that inbox.
2. Send the quote or package with a next step already booked. A time to walk through assumptions is better than a PDF with no expiry. Write that time on the record before you hit send.
3. When a reply comes back, log it on the record the same day. Approved, parked, needs a resubmittal, or dead. If you only archive the email, the record still looks open and you will chase a ghost next week.
4. Friday, spend fifteen minutes on anything with no next action or a due date that has passed. Call it, close it, or give it a new date. Do not leave it in limbo.

Email can still carry the file. The record is the job. If a request is not on the list, it does not exist, even if it is sitting in the inbox with a flag.

This is the same discipline operations teams already use for jobs in the field. A work order that lives only as a voicemail is not a work order. A quote that lives only as a thread is not a quote in process. It is a hope. Related reading on the same failure, from the sales-touch side rather than the document side, is why most outbound follow-up breaks after the first few touches.

How should a manufacturer rep run the week without drowning?

Start the day in the record list, not in the inbox. Inbox-first is how expedites jump the queue and RFQs from Friday afternoon get priced on Wednesday. Scan new mail, create records, then work the list by due date. The inbox is intake. The list is the work.

Give expedites a shorter clock than quotes. A buyer asking where a release is cannot wait for the same Friday sweep as a new RFQ. If everything is treated as equally urgent, nothing is. Put expedites on a same-day or next-morning due date. Put new RFQs on a clock you can actually keep, then keep it. Slow quoting is not a mystery in this market. Buyers compare response time before they compare price. If your honest cycle is two days, say two days on the record and to the buyer. Missing a promised day is worse than quoting a day later with a date you will hit.

Keep submittals off the quoting pile. A submittal package that comes back redlined is not a new RFQ. It is the same job, new next action: revise the drawing, return by a date. If you open a new thread every time a package bounces, you will lose the approved set. The record should point at the current file, the previous file, and who has the live version.

BOMs need a version stamp. The sheet that arrived on Monday is not the sheet that arrived on Thursday with two line items swapped. If you price the wrong revision, you eat the miss later on the invoice. Put the file name, date, and revision on the record. Do not trust the email subject.

When the customer goes quiet, do not send another empty check-in. Send the one thing that was still open: lead time, an assumption you priced around, or a note that you will close the record if you do not hear back by a date. Then close it if they do not answer. A closed record you can reopen is healthier than a hundred maybe rows that make the list useless.

When is a custom workflow worth building?

A spreadsheet fails in predictable ways. More than one person touches the same quote. Volume is high enough that Friday sweeps take an hour. Submittals, expedites, and new RFQs compete in the same list and the urgent work always wins. Inside sales, outside sales, and engineering all need to see the same next action without forwarding mail. At that point the sheet is not a system. It is a shared document that nobody trusts.

A custom workflow is worth it when the process is already clear and the tool's job is to enforce it. Automatically log inbound mail into a record. Route by product, territory, or customer. Surface anything with no owner, no next action, or a passed due date. Keep a history so that when the buyer calls back in three months, you can see what was quoted, what was assumed, and what was approved.

The software does not invent the process. If you cannot describe the four fields and the Friday sweep on a whiteboard, a custom build will only automate confusion. If you can describe it, the build is a way to stop the inbox from being the system of record.

Warning signs that the sheet is done are the same warning signs that show up in other operations-heavy shops: missed follow-ups, status that lives in someone's head, and work that only moves when a customer yells. That pattern is laid out in what are the warning signs that my business needs automation.

Should you replace email?

No. Buyers will keep sending RFQs to the address on your card. Inside staff will keep forwarding PDFs. The fix is not a new front door that nobody uses. The fix is a record that is created when the mail arrives, and a habit of working that record instead of living in the thread.

Email delivers the file. The record owns the job. Quotes, BOMs, and submittals should not share an inbox as their only home. They can arrive there. They should not live there.

What should you read next if this issue sounds familiar?

If this topic matches what your team is dealing with, these pages are the best next step inside Prologica's site.

• Customer Intake Conversion Workflow for a closely related next read.
• Custom Web Application Development for delivery context.
• How to Compare Software Vendors Without Getting Lost in Features for a closely related next read.