Joel LeeIf your RFQ and quoting process runs on a shared spreadsheet, a folder of email threads, and the estimator's memory, you are not behind. That combination is how most custom fabrication shops and engineer-to-order manufacturers got started, and it works until the quote volume grows, a key person is out sick, or a customer asks where their RFQ stands and nobody can answer quickly. That is when people start looking for software to manage customer RFQs and quotes in one place, and the search usually starts with the wrong question.
The goal of this post is to help you think clearly about what a consolidated RFQ and quoting system actually does, where spreadsheet-and-inbox setups break, what the decision points look like for a custom shop, and how to avoid the most common failure mode, which is buying something before you have mapped your own workflow.
What "one place" actually means for a custom manufacturer
The phrase "one place" sounds obvious, but it means different things depending on how your shop quotes work. For a job shop that runs dozens of RFQs per week with standard lead times and a defined material list, "one place" might mean a CRM (customer relationship management) tool with a quote module bolted on. For an engineer-to-order shop quoting complex assemblies with long material lead times and multi-stage internal review, "one place" has to handle a lot more state.
A consolidated RFQ and quoting system, in practical terms, does these things:
- Captures every incoming RFQ as a discrete record with a timestamp, a source, and an owner
- Tracks the status of each RFQ through the stages your shop actually uses (received, under review, costed, pending approval, sent, won, lost, expired)
- Stores the underlying estimate alongside the quote, not in a separate file
- Links the accepted quote to the job or work order that follows
- Gives any authorized person a current view of every open RFQ without asking the estimator
The fourth point is the one most shops underestimate. Quoting and job execution are not separate processes. When a customer accepts a quote and the job starts, the estimate is the cost target. If those two records live in separate systems with no link, the job costing data and the original estimate diverge immediately, and you cannot close the loop on whether your quoting assumptions were accurate. connecting job costing to the quote record
How spreadsheet and inbox setups break (and how to spot it early)
A common failure mode in custom fabrication shops is what might be called "RFQ scatter." RFQ scatter happens when incoming requests arrive through multiple channels (email, phone, customer portal, sales rep notes) and get logged inconsistently or not at all. The symptom is not that RFQs get lost, at least not at first. The early symptom is that status questions require a conversation. A customer calls and asks where their quote stands. The estimator has to check their inbox, their spreadsheet, and possibly their memory to answer. That lookup takes two to five minutes per inquiry. At 30 active RFQs, that adds up to a meaningful portion of the estimator's day spent on status, not on estimating.
The second symptom is expiration blindness. Quotes have a validity period. When quotes live in email threads, there is no automatic flag when a quote is about to expire or when a customer goes quiet past a certain point. The follow-up depends on whoever sent the quote remembering to follow up. At low volume, that works. At higher volume, it does not.
Organizations with weak order management spend far more time on manual status tracking and exception handling than those with tight processes. The delta is almost always workflow structure, not headcount.
The estimating complexity problem in engineer-to-order shops
Standard quoting software is designed for products with known bills of materials (BOM). Custom manufacturers, especially engineer-to-order shops, are quoting things that do not exist yet. The materials are not always defined. The labor routing may depend on design decisions that are still open. The markup logic may vary by customer, by job type, or by capacity situation.
This is why off-the-shelf estimating software often gets abandoned in custom shops. The tool assumes a level of product definition that the shop does not have at the quoting stage. The estimator ends up maintaining the spreadsheet model because it handles the edge cases the software cannot.
The practical decision rule here: before evaluating any quoting software, write down the five most common edge cases in your current estimating process. If every vendor demo you sit through cannot show you how the system handles those five cases without a workaround, the system is not ready for your shop. how to scope your software requirements before picking a tool
What a working quote approval workflow looks like for a fabrication shop
Quote approval workflow refers to the defined sequence of internal reviews a quote must pass before it is sent to the customer. In many small fabrication shops, the approval workflow is informal: the estimator sends the quote, the owner eyeballs it if the number looks big, and everything else goes out unchecked. That works when the owner knows every job. It breaks when job volume grows or when the owner wants to step back from daily operations.
A functional approval workflow in a consolidated system looks like this:
Stage 1: Estimate complete
The estimator flags the quote as ready for review. The system notifies the reviewer (owner, sales manager, or engineering lead, depending on job type).
Stage 2: Review and markup
The reviewer can see the line-item estimate, the proposed margin, and the customer's history. The reviewer approves, rejects, or requests a revision with a note. All of that happens inside the system, not in a reply-all email thread.
Stage 3: Quote issued
The approved quote goes to the customer. The system records the timestamp and starts a follow-up timer based on the quote's validity period.
Stage 4: Win/loss capture
When the customer responds, the outcome is recorded against the quote record. Win rate by job type, by customer, by estimator, and by margin band all become reportable without a separate analysis project.
This structure is not complicated to build. The barrier is usually that shops have not written down their current approval logic, so there is nothing to configure until that mapping happens. tracking job requirements from estimate to work order
A concrete cost and time comparison
Consider a 15-person fabrication shop running 40 active RFQs at any given time. In a spreadsheet-and-inbox setup, a conservative estimate of the time spent on status tracking, quote retrieval, and follow-up is 45 minutes per day for the estimator and 20 minutes per day for the owner or sales lead. That is roughly 8 hours per week of two people's time spent on administration rather than on quoting or running the shop.
At fully loaded labor costs of $80 per hour for the estimator and $120 per hour for the owner, that is $640 plus $160 per week, or about $41,600 per year in administrative overhead. That number does not include the cost of a quote that expired unnoticed, a follow-up that never happened, or a job that was underquoted because the estimator was working from an outdated material price in a spreadsheet.
A configured system on a modern no-code or low-code stack, tools like Airtable, Make, and Noloco are common components, typically runs $300 to $800 per month in platform costs for a shop this size. The labor cost reduction alone justifies the investment in the first quarter, before you count the margin improvement from better data. see how we scope these systems
The decision a business owner can make this week
Before buying anything, run this diagnostic on your current process:
- List every open RFQ you have right now. How long did that take? If it took more than five minutes, you have a visibility problem.
- Pick three of those RFQs at random. Can you tell, without opening an email thread, what stage each one is in and what the next action is?
- Find the last five quotes you lost. Do you know why you lost them?
If you cannot answer questions two and three without digging, you have a workflow problem, not a software problem yet. The software can only automate a workflow that is already defined. The first step is to map the stages your quotes actually move through, decide who owns each stage, and write down what "done" looks like at each handoff. That mapping is the foundation. The software is the container. learn how we run scoping engagements for custom manufacturers
Process documentation is a consistent precondition for successful technology adoption in smaller manufacturing environments. That holds in quoting systems as much as anywhere else.
How to evaluate tools without getting sold the wrong thing
When you do evaluate software, bring your mapped workflow into every demo. Ask the vendor or builder to show you how the system handles your specific stages, your specific approval logic, and your specific edge cases. If they cannot show you that without saying "we can customize that later," treat it as a red flag.
The tools that work well for custom manufacturers are often not the most expensive or the most purpose-built. They are the ones that are flexible enough to reflect the actual workflow without requiring the shop to simplify its quoting logic to fit the software's assumptions. A configured general-purpose platform that mirrors your process will outperform a purpose-built quoting tool that forces you to work around it.
Frequently asked questions
How do we track RFQ status without adding more spreadsheets?
The answer is to replace the spreadsheet with a database that has a defined status field for each RFQ record, where status updates happen inside the system rather than in a separate column someone has to remember to update. Tools like Airtable, configured with your actual stages, give every team member a live view of every open RFQ without anyone maintaining a log manually.
What is the best estimating software for a job shop with complex or variable materials?
There is no single best tool because the right fit depends on how your shop's pricing logic actually works. The most important step before evaluating any tool is to document your current estimating method, including the edge cases, so you can test whether a given system can handle your real jobs without workarounds. Many engineer-to-order shops end up with a configured database system rather than a purpose-built estimating tool because the off-the-shelf options assume more product definition than exists at the quoting stage.
How do we manage a high volume of RFQs without losing track of any?
The core requirement is that every incoming RFQ gets a record the moment it arrives, not after the estimator has a chance to look at it. Assigning an owner, a received date, and a due date at intake, before any estimating starts, is what prevents RFQs from falling through the cracks. Automation tools like Make can pull RFQs from email or a web form and create those intake records automatically.
Do we need a formal quote approval workflow, or is the owner reviewing everything good enough?
Owner review of every quote works well at low volume, but it becomes a bottleneck as quote volume grows and it creates risk if the owner is unavailable. A formal workflow does not have to be complicated. It just needs to define which job types or dollar thresholds require review, who the reviewer is, and where the approval is recorded. That last part, recording the approval inside the system rather than in an email, is what makes the workflow auditable.
How long does it take to set up a system like this, and what does it cost?
A scoped and configured RFQ and quoting system for a small to mid-size custom shop typically takes four to eight weeks to build when the workflow is already mapped and requirements are clear. Platform costs for tools like Airtable, Make, and Noloco generally run $300 to $800 per month depending on user count and automation volume. The bigger time investment is almost always the scoping work that happens before any configuration starts.
If this sounds like a handoff your manufacturing operation keeps fighting, bring us the specific workflow. Start a free scoping sprint. We'll map the people, data, tools, and decisions involved, and you'll leave with a comprehensive build plan whether or not you work with us.
