Strategy
Sales SLAs That Win RFQs: The 5-15-60 Rule for Manufacturers
TL;DR
Manufacturers who respond to an RFQ within 5 minutes win 8x more often than those who reply in 24 hours. The 5-15-60 SLA - acknowledge in 5 mins, qualify in 15 mins, send first quote in 60 mins - works for valves, fittings, EPC sub-supply, anything. It needs CRM, WhatsApp, and one accountable RFQ owner. Doubling win rate is realistic in 90 days.
Quick answers
- How fast should we respond to a B2B RFQ?
- Acknowledge in 5 minutes, qualify in 15 minutes, send a first quote in 60 minutes. Speed of first response correlates with win rate more than price.
- Why does speed matter so much?
- Buyers anchor on the first quote and use it to benchmark the rest. The first vendor sets the agenda. Late vendors negotiate against an anchor they didn't set.
- Does Kalk help build this?
- Yes - SLA design, CRM workflow, WhatsApp routing, and dashboards are part of our [growth system](/growth-system) and [Odoo CRM rollout](/erp).
The cheapest way to double sales is to respond faster. Most Indian manufacturers leave 40–60% of inbound RFQs to die in an unattended sales@ inbox. Here's the SLA system that fixes it.
Why does response speed matter for RFQs?
Atomic answer: B2B buyers anchor on the first vendor quote and treat it as benchmark. Vendors who arrive within the first hour win 8x more often. After 24 hours, the buyer has already evaluated 3 alternatives - your price now needs to be 15–25% lower to compete.
What is the 5-15-60 rule?
| Stage | Time | Channel |
|---|---|---|
| Acknowledge enquiry | 5 minutes | WhatsApp + email auto-reply |
| Qualify (budget, timeline, spec) | 15 minutes | Human call or WhatsApp |
| First quote / next-step plan | 60 minutes | Email + PDF |
This is achievable for any manufacturer with one named RFQ owner per shift, a CRM, and WhatsApp Business.
The 8-step build
- Centralise inbound channels. sales@, WhatsApp, IndiaMART, website form - all routed into one CRM queue.
- Auto-acknowledge in 60 seconds. Templated WhatsApp + email.
- Assign by region/product. Round-robin or fixed owner.
- Mobile CRM for the founder. They get an alert if any RFQ exceeds 30-min response time.
- Standard qualification script. 7 questions, max 4 minutes.
- Pre-built quote templates by product family. Fill 3 fields, send.
- WhatsApp follow-up cadence. Day 1, Day 3, Day 7, Day 14, Day 30.
- Weekly RFQ scoreboard - SLA % met, win rate, average ticket.
What "first response" should actually contain
- Acknowledgement of the spec.
- Two clarifying questions.
- Realistic next-step time ("Detailed quote within 4 working hours").
- Founder/RFQ-owner name and direct WhatsApp.
Reality check: "Thanks for your enquiry, our team will get back" is not a response. It's a confession that you don't have a process.
How to set up the dashboards
- SLA % met by RFQ owner, weekly.
- Win rate by source (website, IndiaMART, referral, LinkedIn).
- Ticket size by source - usually website > IndiaMART by 3–5x.
- Time-to-quote average and 90th percentile.
We build these dashboards inside Odoo CRM as part of our ERP rollout.
Common mistakes
- Letting the founder be the RFQ owner. Founders are unreliable responders.
- Routing RFQs to multiple owners ("whoever's free"). No accountability.
- Sending PDF quotes only on email. Always pair with a WhatsApp message.
- Skipping the 7/14/30 day follow-ups. 30% of revenue lives there.
What to do next
If your win rate is stuck below 25% on inbound RFQs, the fix is almost never pricing - it's response speed. Kalk's Manufacturing Growth System installs the 5-15-60 SLA stack in 30 days. Start with our free audit.
Free strategy session
Want this built for your factory?
30-minute call. No pitch. We map your highest-ROI growth lever and you walk away with the plan - whether you hire us or not.
Questions about this topic
Auto-acknowledge via WhatsApp + CRM, then have one named RFQ owner per shift. Even acknowledgement under 5 mins compresses the perception gap.