The RFQ that never got answered
Nine days to tender close. A procurement engineer has three supplier tabs open. One site loads slowly and hides its capabilities under a rotating banner. Another lists "engineering solutions" with no scope, no sector, no proof. The third names the process, states the tolerance range, links two project narratives, and asks for drawings in the form. Guess which one gets the enquiry, and which two get closed within forty seconds.
That forty-second window is the entire game. Engineering firms spend enormous energy on brand positioning and comparatively little on the page a buyer actually lands on mid-research. Fix the second thing first, it is cheaper, faster, and it is where most of the lost leads are actually hiding.
None of this is about volume. A firm chasing fifty enquiries a month usually ends up with an estimating team that resents the marketing department, because most of those fifty were never going to close. Twelve well-matched RFQs a month, arriving with a drawing attached and a realistic timeline, will out-earn fifty vague ones every single time.
What a specifying engineer checks, in order
| Order | What they check | What kills the enquiry |
|---|---|---|
| 1 | Does the capability list match my process, in my terminology | Generic "solutions" language with no process names |
| 2 | Have they actually delivered this scale before | A gallery of photos with no scope or tolerance detail |
| 3 | Are they certified for what I need | Certifications claimed in text but not shown or dated |
| 4 | Can I submit drawings without a phone call first | A "message us" box with no upload field |
| 5 | Will they reply before my deadline passes | No stated response time, and a track record of slow replies |
Capability pages should read like a spec sheet, not a mission statement
Write each capability page as if a mechanical or process engineer with a real problem is going to read it while deciding whether to bother calling. That means naming the actual processes (CNC machining to what tolerance, structural steel fabrication up to what tonnage, pressure vessel work to which code) instead of a paragraph about "engineering excellence."
State scope boundaries honestly, including what you do not do. A page that says "we do not currently fabricate above 40 tonnes" reads as more credible than one that implies unlimited capacity, because a buyer who has been burned by an over-promising supplier before notices the difference immediately.
Every capability page needs its own enquiry path. Sending every visitor back to a single central contact page adds friction at exactly the point where intent is highest.
Build the RFQ form your estimator actually wants
- Application or part description, routes the enquiry and skips the first clarifying email
- Drawing or specification upload, not "email us separately"
- Required timeline, so urgent enquiries do not sit in a general inbox for two days
- Site or delivery location, affects lead time and logistics quoting
- A budget band or order-size range, if your quoting process actually uses it
A scenario: the RFQ that arrived at 11pm on a Sunday
A structural steel fabricator gets an RFQ notification at 11:47pm on a Sunday, a specifying engineer working late on a tender submission due Tuesday morning, browsing supplier sites while everyone else is offline. The form captures the drawing, the tonnage estimate and the delivery deadline. Nobody replies until Monday at 9am, which is still faster than most competitors, and the estimator opens the email with everything already needed to quote.
Compare that to the same engineer landing on a competitor’s site at the same hour: a "contact us" button that opens a mail client with no context, or worse, a phone number with no indication of when anyone might actually answer it. That engineer has no way to leave useful information behind, so they leave nothing, and move to the next tab.
The fabricator did not win this RFQ by being cheaper or faster to reply in real time. They won it by making it possible for a stressed, time-pressured buyer to leave a complete request at an hour when no human was available to take a call. That is the actual job of the RFQ form: capturing intent when your team is asleep.
Where the trade-off actually sits: broad reach or named capability
A recurring argument inside engineering firms is whether marketing should build broad awareness ("everyone should know our name") or lead with a specific, named capability ("we cut PGM ore-handling components to tolerance X"). Broad awareness feels safer because it offends no one and covers every possible buyer. It also converts almost nobody, because nobody searches for a company name they have never heard of.
Named capability campaigns feel riskier because they exclude buyers outside that specific scope. In practice they win more RFQs per rand, because the buyers who do see them are already close to a decision and the message answers their exact question instead of a general one.
The right call depends on sales cycle length and existing pipeline. A firm with an empty pipeline and six months of runway should run the named-capability version now and build the brand story later, once there is actual revenue funding the slower play.
Sequencing the build
- Map real capabilities into buyer languageAsk your estimators what search terms an engineer would actually type, not what your org chart calls the department.
- Approve two or three proof narratives per capabilityScope, constraint, outcome, described without breaching confidentiality.
- Rebuild the RFQ form around a complete first responseEvery field should exist because your estimator asked for it, not because a template included it.
- Pick one channel and prove it before adding a secondSEO on capability terms, or targeted LinkedIn to named job titles, not both at half effort.
- Set and publish a response SLA internallyWhoever owns the first reply should know the target time and what a complete answer contains.
A tender notice does not wait for your marketing calendar. Neither does the buyer reading your site at 11pm before a submission deadline.
Nexus industrial demand principle
SEO vs LinkedIn outreach for engineering B2B, how to split effort
| Channel | Strongest for | Realistic timeline |
|---|---|---|
| SEO on capability terms | Capturing buyers already searching for a specific process or spec | Months to build authority; compounds after that |
| Targeted LinkedIn outreach | Reaching named job titles at specific target accounts, especially for larger contracts | Faster initial contact, but conversion depends heavily on message specificity |
| Both, sequenced | Firms with a defined target account list and enough content to support both | Start SEO early since it takes longer to mature; layer outreach on top once capability pages exist to send people to |
WhatsApp is probably already your real enquiry channel
Many South African engineering buyers will WhatsApp a photo of a broken part or a drawing snippet before they ever open a contact form, especially for urgent or smaller-scale work. If your site does not surface a WhatsApp number, that conversation is either happening anyway through a salesperson’s personal number, or it is not happening at all and a competitor is getting it.
Put the WhatsApp number where the RFQ form is, not just in a footer icon. Treat replies through it with the same discipline as the form (logged, dispositioned, followed up) rather than as an informal side channel nobody tracks.
What proof actually needs to say
A photo gallery labelled "some of our completed projects" tells a specifying engineer almost nothing they can act on. The same gallery with two sentences per project (the material, the tolerance or load requirement, and the delivery timeline achieved) turns decoration into evidence. Engineers reading a capability page are pattern-matching against their own spec; give them enough detail to make that match themselves rather than asking them to trust an unqualified claim.
Where confidentiality genuinely prevents naming a client, describe the scope and constraint in enough technical detail that a reader with real domain knowledge recognises the difficulty involved, even without a company name attached. "A confidential automotive client" with no other detail reads as filler; "a components supplier requiring ±0.05mm tolerance across a 40,000-unit run" reads as a firm that actually did the work.
Two mistakes that quietly waste the most budget
Running a paid campaign to a homepage instead of the specific capability page the ad copy describes. The buyer clicks expecting an answer to the ad’s claim and lands on a generic services list, most leave before finding it.
Letting RFQ submissions sit in a shared inbox nobody owns. A form that qualifies well is wasted if the first reply takes three days. Assign ownership before you improve anything else.
What to measure, and what to ignore
Track RFQ submissions and their eventual disposition (quoted, won, lost, disqualified) by source page and channel. That is the only scoreboard that tells you anything about return on marketing spend.
Traffic, impressions and time-on-page are diagnostics at best. A capability page can carry heavy traffic and still produce zero real RFQs if the buyer cannot find a way to act once they arrive.
Review monthly which pages actually convert into quoted work, not just submitted forms. Redirect content effort toward what is proven, and stop defending a page just because it took effort to write.
What to do next
This week: open your top three capability pages on a phone and time how long it takes to find the enquiry path. If it is more than one scroll, fix that first.
This month: rebuild your RFQ form around what your estimator needs for a complete first response, and agree a response-time target with whoever owns the first reply.
Read our companion piece on digital marketing for mechanical engineering companies, and see the engineering and industrial industry page for the fuller service picture.
