"We'll digitize when we get the ERP" --- the most expensive sentence in mid-market procurement
Someone on your leadership team has said this. Maybe it was in a planning meeting, maybe in a budget review, maybe in response to the third spreadsheet error that month. The logic feels sound: why invest in point solutions when you're going to roll out a comprehensive ERP system that handles everything? Better to wait, do it right, plan the whole thing at once.
Here's the problem. That ERP implementation is twelve to twenty-four months away. In the best case. It's probably further than that, because ERP projects have a well-documented tendency to slip timelines, blow budgets, and deliver less functionality than the original scoping document promised. Meanwhile, your procurement team is still running quote cycles through email, tracking supplier responses in spreadsheets, and manually re-keying order data between three different systems.
Every month you wait, you're paying for that delay in concrete ways: slower response times to customer RFQs, higher error rates in quoting, missed price changes from suppliers, and the steady accumulation of inefficiencies that nobody tracks because there's no system to track them in.
The premise of this article is simple. You don't need an ERP to digitize your procurement. Several of the highest-impact process improvements --- RFQ workflow, customer and supplier portals, BOM management, document tracking --- don't require an ERP at all. In many cases, they actually work better as purpose-built tools. And when you do eventually get that ERP, these tools integrate with it, giving you the best of both worlds.
The ERP waiting trap
The ERP waiting trap works like this. A company recognizes that its manual processes are unsustainable. Someone proposes digitization. The conversation immediately jumps to ERP, because ERP is what large companies use, and it sounds like the serious, comprehensive solution. An evaluation process begins. Vendors are invited to demo. Requirements documents are written. Budgets are requested.
Then reality sets in. The ERP costs more than expected. The implementation timeline is longer than expected. The customization needed to fit your specific workflow is more extensive than the vendor initially suggested. Internal resources are stretched. The project gets pushed to next quarter, then next fiscal year, then "when we have bandwidth."
Meanwhile, every other digitization initiative stalls. "We can't invest in a quoting tool --- the ERP will have a quoting module." "We can't set up supplier portals --- the ERP will handle vendor management." "We can't implement BOM tracking --- the ERP has a materials management module."
The trap is that the promise of a comprehensive future solution prevents any improvement in the present. And the present is where your team is losing hours every day to manual processes that should have been automated years ago.
This isn't a criticism of ERP systems. ERPs are genuinely powerful for what they're designed to do. The trap is the assumption that ERP is a prerequisite for all digitization, and that nothing should happen until the ERP is in place.
What ERP does well
Let's give credit where it's due. ERP systems earn their complexity in several areas.
Financial management and accounting. General ledger, accounts payable, accounts receivable, fixed asset management, financial reporting, multi-entity consolidation. This is the historical core of ERP, and it's where these systems are genuinely strong. The integration between purchasing, inventory, and accounting --- so that a received shipment automatically generates an AP entry and updates the GL --- is valuable and hard to replicate with disconnected tools.
Production planning and scheduling. If you run a manufacturing operation, MRP (Material Requirements Planning) calculations that convert a production schedule into component demand, account for lead times, and generate planned purchase orders are a core ERP capability. Scheduling work orders, tracking work-in-progress, and managing shop floor operations are tightly coupled processes that benefit from a unified system.
Inventory management at scale. Multi-warehouse inventory with lot tracking, serial number management, bin locations, and automated reorder points. When you're managing thousands of SKUs across multiple locations with compliance requirements for traceability, a robust inventory system is essential.
Compliance and audit trails. Regulated industries --- medical devices, aerospace, automotive, food and pharma --- need system-enforced controls, electronic signatures, and comprehensive audit trails. ERP systems built for these industries embed compliance into every transaction.
These are legitimate strengths. If your primary pain point is financial consolidation across multiple entities, or production scheduling for a complex manufacturing operation, an ERP may indeed be the right tool. But notice what's not on this list.
What ERP doesn't do well
Here's where the ERP-first assumption breaks down. Several critical procurement and commercial processes either aren't covered by typical ERP modules, or are covered so poorly that companies end up supplementing them with email and spreadsheets anyway.
RFQ workflow and quote management. ERPs can generate purchase orders, but the process that leads to a purchase order --- sending RFQs to multiple suppliers, collecting and comparing quotes, negotiating pricing, managing revisions --- is usually rudimentary in ERP systems. Most ERPs treat supplier quoting as a simple data entry step: someone receives a quote by email, types the numbers into the system, and creates a PO. The actual workflow of distributing RFQs, tracking responses, comparing side-by-side, and managing the negotiation cycle? That lives in email.
On the sales side, the picture is even thinner. Generating customer quotes with line items, price breaks, validity periods, terms and conditions, and managing the revision cycle until acceptance --- this is either handled by a separate CRM or, more commonly, by a Word template and an email thread.
Customer and supplier portals. Most ERPs don't have a native portal layer. Some offer add-on modules or partner solutions, but these are typically expensive, limited in functionality, and hard to customize. The result is that your customers and suppliers interact with your company through email and phone, not through a self-service portal where they can submit RFQs, view quotes, track orders, and download documents.
The portal gap is significant because it's not just about convenience. Portals change the nature of the relationship. A customer who logs into your portal to check order status doesn't tie up your sales team. A supplier who submits quotes through your portal gives you structured data instead of a PDF that someone has to manually parse. The efficiency gains compound with every transaction. We cover this in depth in our B2B portal guide.
BOM intelligence. ERPs can store a bill of materials --- a list of components with quantities. But they typically don't provide lifecycle intelligence: which components are approaching end-of-life, which have single-source risk, what the current market pricing is versus what you're paying, whether qualified alternatives exist. BOM management in most ERPs is a static data store, not an active risk management tool.
For electronics companies, this gap is particularly costly. Component lifecycles are measured in years, not decades. Parts go EOL, get placed on allocation, or experience sudden price spikes. Without proactive BOM monitoring, you find out about these problems when procurement tries to place an order and discovers that a critical component has a twenty-week lead time.
Bidirectional commercial flow. B2B companies that both buy and sell --- distributors, EMS providers, contract manufacturers --- need to manage purchasing and sales as two sides of the same coin. A customer's RFQ triggers supplier sourcing. A supplier's quote feeds into the customer quotation. An accepted quote becomes a sales order --- and the purchase orders behind it.
ERPs handle purchasing and sales as separate modules with limited connection between them. The bidirectional flow that's natural in distribution and contract manufacturing requires manual bridging between modules, or custom development that adds complexity and cost. Purpose-built platforms handle both directions natively.
Speed to value. ERP implementations are measured in months and years. Purpose-built procurement tools are measured in days and weeks. When you're losing money every day to manual processes, the time-to-value difference matters enormously. A tool you can deploy in a week and start seeing results from immediately beats a comprehensive system that won't be operational for eighteen months.
5 areas to digitize without ERP
If you're waiting for an ERP to modernize your procurement, here are five areas where you can start today --- without waiting, without a massive budget, and without the risk of a failed enterprise implementation.
1. RFQ and quote management
This is the single highest-impact area for most B2B companies. The RFQ-to-quote cycle is where revenue begins, and it's where email-based processes create the most friction.
What you're replacing: RFQs sent by email to individual suppliers. Quotes received as PDF attachments. Comparison done in spreadsheets. Customer quotes built in Word or Excel templates. Revisions tracked by email thread and memory.
What you're gaining: Structured RFQ distribution to multiple suppliers simultaneously. Responses collected in a unified format for side-by-side comparison. Customer quotes built with consistent formatting, automatic markup calculation, and one-click revision. A clear audit trail showing who quoted what, when, and what changed.
The efficiency gain here isn't marginal. Companies that move from email-based quoting to a structured platform typically see response time improvements measured in days, not percentages. A quote that used to take forty-eight hours from request to delivery takes four. The accuracy improvement is equally significant --- manual transcription errors that plague email-based workflows simply don't occur when data flows through a structured system.
You can explore how the trade flow works end-to-end to see this in practice.
2. Customer portals
Your customers shouldn't need to email or call your team for routine interactions. Checking order status, reviewing past quotes, downloading invoices, submitting new RFQs --- these are all self-service activities that a portal handles without human intervention.
What you're replacing: Phone calls and emails for status checks. Manual quote delivery by email. Order history maintained in spreadsheets or personal memory. Document retrieval requests that interrupt your team.
What you're gaining: A branded, white-labeled portal where your customers log in and get immediate access to everything relevant to their relationship with you. Quote requests submitted in structured format. Quotes delivered straight to the portal. Live order status. A document library with invoices, shipping documents, and certificates.
The downstream effect is powerful. Your sales team stops being a relay service and starts being a sales team. Customers develop habits around your portal that create natural retention. And the data you collect --- which customers are most active, what they're requesting, how quickly they respond to quotes --- gives you commercial intelligence that email never could.
3. Supplier portals
The same logic applies to your supply side. When your procurement team sends RFQs by email and tracks responses in spreadsheets, every sourcing cycle involves unnecessary friction.
What you're replacing: Individual emails to each supplier for every RFQ. Manual follow-up when suppliers don't respond. Quote comparison built by hand in Excel. Order acknowledgements tracked by email.
What you're gaining: A supplier-facing portal where your vendors receive RFQs, submit structured quotes, acknowledge orders, and update fulfillment status. All responses land in one place, in one format, ready for comparison.
The time savings are significant, but the data quality improvement is transformative. When suppliers submit quotes through a structured form instead of a free-text email, you get clean data: pricing per quantity break, lead times, MOQs, validity periods. That data feeds directly into your comparison and decision-making process without manual re-entry.
4. BOM management and health monitoring
If you work with bills of materials --- and in electronics, every company does --- moving BOM management from spreadsheets to a purpose-built tool eliminates an entire category of risk.
What you're replacing: BOM spreadsheets with uncertain version history. Manual lifecycle checks by searching manufacturer websites. Alternative part research done ad hoc when problems surface. Cost tracking that's always out of date.
What you're gaining: Centralized BOM data with automatic version control. Lifecycle monitoring that flags EOL and NRND components before they become emergencies. Alternative part tracking with qualification status. Cost data maintained in one place, so your estimates stay current.
The ROI on BOM digitization shows up the first time you catch an EOL risk early enough to qualify an alternative before your current stock runs out. That single event --- avoiding a production stop, a spot-market premium, or an emergency redesign --- typically pays for the tool several times over. You can see what a BOM health dashboard looks like in practice.
5. Document and activity tracking
Every B2B transaction generates documents: quotes, purchase orders, order acknowledgements, invoices, packing slips, certificates of conformance, inspection reports. When these live in email attachments and local file folders, finding the right document at the right time means digging through three years of inbox.
What you're replacing: Documents scattered across email, shared drives, and local folders. No reliable audit trail of who did what and when. Version confusion on everything from quotes to specifications.
What you're gaining: A centralized document repository linked to the relevant transaction. Full activity logging that records every action: who sent the RFQ, who responded, when the quote was accepted, when the order was confirmed. Searchable, organized, and always accessible.
This area often gets overlooked in digitization discussions because it's not "exciting." But when a customer disputes a quote, or an auditor asks for a transaction history, or a new team member needs to understand the history of a supplier relationship, having structured activity and document tracking saves hours of detective work. For a broader look at the digitization journey, our digital transformation guide lays out the five pillars in detail.
Can they work together?
Here's the question you're probably asking: if I digitize these areas now, what happens when the ERP eventually arrives? Do I end up with competing systems? Do I have to rip out the procurement tools and start over?
The answer is no, and here's why.
Different layers of the stack. ERP and purpose-built procurement tools operate at different layers. ERP handles the financial and operational backbone: accounting, production planning, inventory valuation, compliance. Procurement tools handle the commercial workflow layer: sourcing, quoting, portal interactions, BOM intelligence. These layers are complementary, not competitive.
Integration, not replacement. When the ERP goes live, you don't discard your procurement tools. You integrate them. An accepted quote in your procurement platform triggers a sales order in the ERP. A purchase order generated from your quoting tool flows into the ERP's AP module. Inventory data from the ERP feeds back into BOM cost calculations. The two systems exchange data, each doing what it does best.
Data foundation. Here's an underappreciated benefit of digitizing before the ERP: you build a clean data foundation. Companies that implement ERP on top of email-and-spreadsheet processes spend enormous time and money on data cleansing and migration. Companies that have already been operating in a structured digital system have clean contact records, clean product data, and clean transaction history ready to import. The procurement tool actually makes the ERP implementation smoother and faster.
Portal layer persists. ERPs don't have good portals. They're not designed for external-facing, branded, self-service interactions. Even after ERP implementation, your customer and supplier portals continue to serve as the external interface while the ERP handles the internal back-office processing. This is a common and effective architecture.
You can see how Gloyd compares to ERP-based approaches on our comparison page --- and yes, ERP connectors are first up on Gloyd's integration roadmap.
Decision framework: when to digitize now vs. wait for ERP
Not every company should jump to a procurement platform immediately. Here's a framework for deciding what makes sense for your situation.
Digitize now if:
Your RFQ response time is measured in days, not hours. If it takes your team more than a business day to turn around a customer quote, you're losing deals to faster competitors. An RFQ platform delivers immediate improvement here, and waiting eighteen months for an ERP to address it means eighteen months of lost opportunities.
Your team spends more time on data entry than decision-making. If procurement professionals are spending their days copying information between emails, spreadsheets, and systems instead of analyzing supplier performance and negotiating better deals, you have a process problem that a purpose-built tool solves immediately.
Your customers are asking for self-service. When customers start asking "can I check my order status online?" or "do you have a portal?", they're telling you that your competitors do. Customer expectations for B2B self-service have been rising steadily, driven by B2C experiences. A portal addresses this within weeks, not years.
You manage BOMs with lifecycle risk. If your products contain components that go EOL, get placed on allocation, or experience price volatility, waiting to digitize BOM management means accepting unmonitored risk. Every month without lifecycle monitoring is a month where an EOL surprise could stop your production line.
Your ERP implementation is more than six months away. If the ERP is genuinely coming in three months and procurement workflow is in scope, maybe you wait. But if the timeline is six months or more --- and ERP timelines almost always extend --- the cost of waiting exceeds the cost of implementing a purpose-built tool that you'll keep using alongside the ERP anyway.
Wait for ERP if:
Your primary pain is financial consolidation. If the main problem is multi-entity accounting, revenue recognition, or financial reporting across business units, that's an ERP problem. Procurement tools won't solve it.
Production planning is the bottleneck. If MRP calculations, shop floor scheduling, and work-in-progress tracking are your critical needs, the ERP's manufacturing module is the right solution. Procurement tools complement this but don't replace it.
You're already in active ERP implementation. If the ERP project is underway and procurement modules are being configured, adding a separate procurement tool mid-implementation may create unnecessary complexity. Focus on getting the ERP live, then evaluate gaps.
The pragmatic middle ground
For most companies, the right answer isn't "ERP or procurement platform." It's "procurement platform now, ERP later, integrated together." You get immediate improvement in the areas where manual processes are costing you the most, and you build a data foundation that makes the eventual ERP implementation smoother.
This isn't an unusual pattern. It's how most successful mid-market companies approach digitization. They start with the highest-pain areas, prove value quickly, and build toward comprehensive systems over time. The companies that struggle are the ones that wait for the comprehensive system to start, and keep paying the cost of manual processes while they wait.
The cost of the wait
Let's put some shape around what the waiting costs.
Quote cycle time. Every day your RFQ response time is longer than it needs to be, you're losing a percentage of potential deals to faster competitors. You can't measure the exact number because you never see the quotes that didn't come to you, or the ones that went to a competitor who responded first. But your sales team knows. Ask them how often customers say "we already went with someone else."
Team capacity. A procurement professional who spends two hours a day on manual data entry, email follow-ups, and spreadsheet compilation is operating at roughly 75% capacity for their actual job --- analyzing suppliers, negotiating better terms, managing risk. Multiply that by the size of your team and the duration of the ERP wait, and the lost capacity is staggering.
Error cost. Every manual transcription --- from email to spreadsheet, from spreadsheet to system, from one system to another --- introduces error risk. A wrong part number, a transposed price, a missed quantity change. Each error costs time to detect and correct, and some aren't detected until they've cost real money.
Customer experience. Your customers are comparing your buying experience to every other supplier they work with. If your competitor responds to RFQs in hours while you take days, if their customers can track orders online while yours have to call, the comparison isn't abstract. It influences purchasing decisions.
Data value. Every transaction you process through email and spreadsheets is a transaction whose data is effectively lost. You can't analyze patterns in supplier pricing if the quotes live in scattered email threads. You can't track RFQ conversion rates if the RFQs aren't in a system. You can't identify your most profitable customer segments if the data isn't structured. The longer you wait to digitize, the more historical data you lose.
None of these costs appear on a financial statement. They're embedded in slower growth, thinner margins, higher headcount than necessary, and competitive disadvantage that accumulates quietly. They're real, but invisible --- which is exactly why the "wait for ERP" decision feels costless when it isn't.
Start where it hurts most
You don't need anyone's permission to stop running procurement on email and spreadsheets. You don't need an ERP to structure your RFQ workflow. You don't need an eighteen-month implementation project to give your customers a self-service portal. You don't need a seven-figure budget to monitor your BOM health.
What you need is to identify the one process that costs your team the most time and produces the most errors, and fix that first. For most companies, it's the RFQ-to-quote cycle. For some, it's the customer communication layer. For electronics companies, it might be BOM lifecycle risk.
Wherever the pain is sharpest, that's where you start. Not when the ERP arrives. Not next quarter. Now.
The digital foundation you're building doesn't compete with the ERP --- it becomes the workflow layer that makes the ERP more valuable when it eventually goes live. And in the meantime, your team gets hours back every week, your error rate drops, and your customers get the experience they've been expecting.
Ready to digitize without waiting? Start your 14-day free trial with Gloyd and see results from the first week. No ERP required, no implementation project, no consultants. See what's included on the pricing page.
