RFQ as a first-class object
Today an enquiry becomes a quote and the enquiry itself disappears. We are making the RFQ a record in its own right, with its own due date, its own owner and its own outcome.
Development progress
5%
Target Wave 1 · M2. Progress figures move when the work does, and the changelog records the release.
In short
RFQ management makes the request for quote a first-class object in the KanchanFlow RFQ-to-Order CRM, separate from the quote that answers it. It is in active development at roughly 5 percent, targeted at Wave 1 Milestone 2, and it is the record every other Wave 1 RFQ feature is being built on top of.
What it is
Right now an enquiry turns into a quote and the enquiry stops existing. That is fine until you want to know your quote-to-RFQ ratio, how many RFQs you declined and why, or how long it takes your desk to turn an enquiry around. None of those questions can be answered from a list of quotes.
The work in progress makes the RFQ its own record: received date, source, buyer, the parts requested, the drawings supplied, the customer's required response date, an owner and an outcome. A quote is then something raised against an RFQ, and an RFQ can be declined without a quote ever existing, which is a legitimate and common answer.
Capabilities
What it does
The RFQ as its own record
Received date, source, buyer contact, required response date, owner and status live on the RFQ itself, not on a quote raised later.
No-quote as a real outcome
Declining an RFQ is a recorded decision with a reason — capacity, material, lead time, price expectation. Today that decision leaves no trace at all.
Response-time measurement
Time from RFQ received to quote sent, measured per estimator and per customer. This is the number most shops guess at and most buyers judge you on.
Multiple quotes against one RFQ
A complex enquiry may be answered with alternate approaches. Each is a quote against the same RFQ rather than three unconnected documents.
Drawings attached to the RFQ
The prints the customer supplied belong to the enquiry, not to the quote. They stay with the RFQ and are inherited by every quote raised against it.
Step by step
How it works
The order these steps happen in matters more than the feature list above it.
- 1
The RFQ is created
From an email through AI extraction, from an IndiaMART enquiry, from a WhatsApp message or by hand. Source is recorded because response expectations differ by channel.
- 2
Parts and drawings are attached
Each requested part becomes a line on the RFQ with quantity and required date, and the supplied prints attach to the enquiry itself.
- 3
It is qualified and owned
An owner is assigned and the RFQ is qualified — do we make this, do we have capacity, is the required date possible. The answer may be no.
- 4
A quote is raised against it
One or more quotes reference the RFQ. Lines, drawings and dates carry across, and the RFQ shows what has been quoted and what has not.
- 5
The outcome is recorded
Won, lost or no-quote, with a reason. That is what turns a pile of enquiries into a win-rate you can act on.
What this is not
This is not a supplier-side RFQ or e-sourcing tool — it manages the enquiries your customers send you, not the enquiries you send your suppliers.
This is not an ERP, MRP, CAD, BOM, or advanced CPQ system — it manages customer RFQs, quotes, follow-ups, and order handoff.
Tier availability
What you get on each plan
These rows come from the same feature matrix the pricing page publishes. If the two ever disagree, the matrix is wrong and we fix it.
| Plan | Availability |
|---|---|
| Starter | Unlimited RFQ line items, unlimited revision history — never capped on any tier. |
| Professional | Unlimited line items and revisions, plus full approval routing on the RFQ. |
| Enterprise | Unlimited line items and revisions, plus custom workflow routing. |
Starter is $39 per user per month, Professional $49, Enterprise $99 plus a $2,000 monthly platform fee. Annual billing is 17% lower. See the full matrix.
Interface
What it looks like
RFQ record in development showing received date, source, six requested parts, attached prints and required response date.
Development build capture, not yet in production. Layout will change before release.
RFQ outcome panel with won, lost and no-quote reasons.
Development build capture. Reason list is not final.
Screenshots are described rather than mocked up. Captures are taken from the build current at the date shown in the changelog, on a sample workspace.
Connectors
Integrations this feature uses
Starter includes one accounting connector and one lead source; Professional and Enterprise include all of them. Browse every integration.
Questions about rfq management
In development, at approximately 5 percent, targeted at Wave 1 Milestone 2. Today you can quote from an enquiry, but the enquiry is not yet a record of its own.
Related features
Multi-item RFQ header
Multi-item RFQ header
Read moreTechnical pre-sales routing
Technical pre-sales routing to engineering, costing and production
Read moreQuote editor
Quote editor with attachments, share links, FX and revisions
Read moreWhat's shipping today
All 47 features grouped by status on one page, with the newest releases alongside.
Read moreSee a live quote draft built from a real RFQ
Fourteen days, no credit card, sample data pre-loaded. If it does not fit your shop, we will tell you in the first call.
- Delaware LLC
- SOC 2 Type II
- USA Data Centers (AWS)