A factory's quoting time is a scarce resource, and it spends that resource on requests most likely to turn into orders. A vague RFQ signals risk and effort, so it goes to the bottom of the pile. Understanding why is the fastest way to stop it happening to yours.
Why this matters
Quoting costs the factory real engineering hours. A vague request asks them to absorb that cost on a job that might not be serious. They rationally deprioritize it. The fix isn't a slicker email. It's giving the factory enough that pricing your job is low-effort and low-risk — which is the same thing as being quote-ready.
Quoting costs the factory real engineering hours. A vague request asks them to absorb that cost on a job that might not be serious. They rationally deprioritize it.
The fix isn't a slicker email. It's giving the factory enough that pricing your job is low-effort and low-risk — which is the same thing as being quote-ready.
A quote is the factory spending money
Estimating cost, sourcing components, and checking feasibility take engineering time. Factories triage RFQs by how likely each is to convert and how much work it takes to price. Vague requests lose on both counts.
Estimating cost, sourcing components, and checking feasibility take engineering time. Factories triage RFQs by how likely each is to convert and how much work it takes to price. Vague requests lose on both counts.
Vagueness reads as 'not serious yet'
No target price, no volume, no motor spec — to a factory this reads as a founder still exploring, not ready to buy. They're often right, which is why the signal works against you even when you are serious.
No target price, no volume, no motor spec — to a factory this reads as a founder still exploring, not ready to buy. They're often right, which is why the signal works against you even when you are serious.
Specificity is a credibility signal
A request that states duty, volume, price, and timeline tells the factory you know your own project. That alone moves you up the queue, because it predicts a real order and a low-friction quote.
A request that states duty, volume, price, and timeline tells the factory you know your own project. That alone moves you up the queue, because it predicts a real order and a low-friction quote.
What a clear RFQ looks like
It names the product and its function, the motor requirements or explicit assumptions, a target price, a volume, a timeline, and the markets you'll sell in. It also names your open questions, so the factory answers them instead of guessing.
It names the product and its function, the motor requirements or explicit assumptions, a target price, a volume, a timeline, and the markets you'll sell in. It also names your open questions, so the factory answers them instead of guessing.
Turn a vague RFQ into one that gets answered
- Lead with the product, its function, and the order you're planning
- State the motor duty/power/torque/RPM, or your assumptions if undecided
- Give a target price or cost ceiling
- Give a volume and a timeline
- Attach a drawing, CAD, or readable spec
- Name target markets and certifications
- List your open questions explicitly
Common mistakes
Sending a one-line 'can you make this and how much' with a photo. Withholding price 'to get an honest number' — it just produces a padded one. Leaving the motor undefined, which is the costliest unknown to price. Blasting the same vague RFQ to ten factories and reading the silence as bad luck.
- Sending a one-line 'can you make this and how much' with a photo.
- Withholding price 'to get an honest number' — it just produces a padded one.
- Leaving the motor undefined, which is the costliest unknown to price.
- Blasting the same vague RFQ to ten factories and reading the silence as bad luck.
Frequently asked questions
- Why this matters?
- Quoting costs the factory real engineering hours. A vague request asks them to absorb that cost on a job that might not be serious. They rationally deprioritize it. The fix isn't a slicker email. It's giving the factory enough that pricing your job is low-effort and low-risk — which is the same thing as being quote-ready.
- What is a quote is the factory spending money?
- Estimating cost, sourcing components, and checking feasibility take engineering time. Factories triage RFQs by how likely each is to convert and how much work it takes to price. Vague requests lose on both counts.
- What is vagueness reads as 'not serious yet'?
- No target price, no volume, no motor spec — to a factory this reads as a founder still exploring, not ready to buy. They're often right, which is why the signal works against you even when you are serious.
- What is specificity is a credibility signal?
- A request that states duty, volume, price, and timeline tells the factory you know your own project. That alone moves you up the queue, because it predicts a real order and a low-friction quote.
- What a clear RFQ looks like?
- It names the product and its function, the motor requirements or explicit assumptions, a target price, a volume, a timeline, and the markets you'll sell in. It also names your open questions, so the factory answers them instead of guessing.
This guide is educational. It is not a manufacturing quote, certification review, legal advice, or a guarantee that a product can be built. If you want this applied to your specific product, request a human-reviewed Motor Readiness Scorecard.
Want this applied to your product?
Request a Motor Readiness Scorecard for a human-reviewed read, or start with a short, no-cost quote-readiness screen.