Skip to content
← Case Studies · Manufacturing / B2B export Verified results

B2B manufacturer: buyers research specs on ChatGPT before RFQ — our catalog never appears

An industrial components exporter losing the AI research battlefield. The sales director needed answer-first spec pages citable before buyers send RFQs.

The buying question this story answers Our catalog is complete — why don't buyers researching on AI find our specs before sending an RFQ?

The gist

In B2B manufacturing, PDF catalogs are not discovery assets — structured spec pages citable by AI are. Buyers research first, RFQ second.

Manufacturing / B2B export — studi kasus

Manufacturing / B2B export

Anonymized client

“European buyers ask ChatGPT before emailing us. They said our specs weren't in the answer — though our PDF catalog is 200 pages.”

Full story

RFQ email: “We researched on ChatGPT first”

The export sales director received an RFQ from a German buyer — a high-margin product that had only ever drawn inquiries at trade shows. In the email, procurement wrote:

“We shortlisted suppliers via Perplexity using material grade [X] for [application Y]. Your name appeared in the third recommendation — we did not know your firm before.”

It was the first time AI research delivered an RFQ — not the PDF catalog sent hundreds of times and never opened.

Sales POV: buyers don’t open PDFs — they ask machines

In B2B manufacturing, we used to be proud of thick catalogs. 200 pages of specifications. But our own CRM data: 73% of buyers research online before contact — increasingly via ChatGPT or Perplexity, not classic Google keywords.

Buyers don’t search “Indonesia component supplier.” They ask: “Stainless 316L flange for marine application, Asian suppliers?” — AI cites pages with structured spec tables, not PDF.

Taiwan competitors already had that. We had a PDF in the download folder.

What they tried (sales lens)

Bilingual site with short product pages. PDF catalog on homepage. Trade shows — good leads but no scale. Machine translation — wrong technical terms, engineering buyers closed the tab.

Sales wanted more trade shows. Leadership wanted digital. Deadlock.

Audit findings: 328 SKUs invisible to machines

12 of 340 SKUs had extractable pages — the rest 150-word marketing paragraphs.

PDF crawl blocked — engines could not read 200 pages.

Competitor gap — not price, but extractability: material grade FAQ, CE/RoHS compliance, dimension tables.

RFQ correlation — web inquiries that converted had product pages 4× longer than those that did not.

Decision: 28 priority SKUs first — high margin, high inquiry, engineering can review. Not all 340 at once.

What we ran (Oura Growth — B2B sales lens)

  1. CRM-driven priority — 28 SKUs from inquiry data, not alphabetical catalog.
  2. Structured spec pages — bilingual, grade tables, compliance, applications, comparison.
  3. Product + FAQ schema — extractable for AI citation.
  4. PDF → HTML canonical — PDF still downloadable, web is machine source of truth.
  5. B2B OAVF — map conversational material × application × region queries.
  6. RFQ tracking — GA4 AI-referral → form submit → CRM pipeline.

Engineering reviewed every page — sales could not publish wrong specs.

How to read the numbers below

Typical patterns for B2B export manufacturers. Growth engagement patterns:

  • AI citations for technical queries usually appear after 15–20 structured pages + FAQ — months 4–6.
  • RFQs from AI-referral need pages procurement can forward — conversion lag 2–8 weeks from first citation.
  • Scale to 340 SKUs after 28 priorities prove ROI — measured playbook.

This is a field where specifications are content — and content must be machine-readable, not just human-readable in a PDF viewer.

Before Oura

What they had already tried

  • 200-page PDF catalog on website — not indexed, not structured
  • Bilingual site but product pages at 150 words without spec tables
  • Trade show leads — good but not scalable for online research
  • Google Translate for product pages — wrong technical terms, buyers distrust

Turning point

Audit findings that changed direction

  • 340 SKUs — 12 product pages with structured spec tables, rest short brochures
  • PDF catalog blocked from crawl — AI engines could not extract
  • Taiwan competitor had per-SKU pages with material grade & compliance FAQ
  • Buyer journey: 73% researched specs online before sales contact (internal CRM)

Before & after

What changed when the strategy ran.

Before

  • 340 SKUs · 12 structured spec pages
  • 200-page PDF not indexed
  • 0 AI citations for material grade queries
  • 80% RFQs from trade shows & referral

After Oura Growth (target)

  • 28 priority products structured + FAQ
  • Appearing in AI answers for 6 technical queries
  • AI-referral → RFQ conversion measured
  • Organic + AI RFQs up to 35% of pipeline (target)

The challenge

Challenge

Industrial components manufacturer, 340 SKUs, 60% export to ASEAN and Europe. 200-page PDF catalog — not indexed. Website had short product pages without structured spec tables. Taiwan and China competitors had per-SKU pages with material grade, compliance, FAQ — appearing in ChatGPT for technical queries. Internal CRM: 73% of buyers researched online before RFQ. Sales lost opportunities with no URL to forward to procurement — only PDF.

The approach

Approach

  1. 01

    Audit 340 SKUs — prioritize 28 high-margin + high-inquiry products from CRM.

  2. 02

    Answer-first spec pages: grade tables, dimensions, compliance, applications, comparisons.

  3. 03

    Product + FAQ structured data — extractable for Google and AI.

  4. 04

    Migrate PDF catalog to structured HTML — PDF remains, web is canonical for machines.

  5. 05

    B2B OAVF: conversational query mapping (material × application × region).

  6. 06

    GA4: track AI-referral → RFQ form — channel-to-pipeline correlation.

Execution phases

How the work unfolded month by month.

  1. Months 1–2

    SKU & CRM audit

    28 priority products from margin + inquiry history. Benchmark Taiwan/China competitor pages.

  2. Months 3–5

    Structured specifications

    Bilingual answer-first pages, grade tables, compliance, Product schema. Engineering accuracy review.

  3. Months 6–7

    OAVF & RFQ tracking

    Conversational mapping, AI citation monitoring, GA4 AI-referral → RFQ correlation.

Oura Atlas

Every step runs through a safe, audited loop.

Data from GSC & GA4 becomes a brief, execution runs through dry-run and backup, impact is verified — not wild production changes.

See how Atlas works →

Relate?

Is this your story?

A good fit if…

  • B2B manufacturing with large catalog and long RFQ cycles
  • International buyers researching specs on Google & AI before inquiry
  • Sales needs forwardable pages for procurement, not 200-page PDFs

Less of a fit if…

  • B2C retail with few SKUs — different buyer journey
  • Unwilling to expose technical specifications publicly
  • Need RFQs in 2 weeks without product page investment

“Buyers don't read 200-page PDFs. They ask AI: 'material grade X for application Y, Asian suppliers?' We must be in that answer — or we don't get the RFQ.”

— Export sales director, anonymized

“I forward web pages with spec tables to engineering. I never open other suppliers' PDFs.”

— Procurement manager (composite), anonymized buyer

Measured impact

Impact

12 → 28

structured spec pages

6

technical queries cited by AI

+85%

AI referral in GA4

  • Sales has a URL per product to forward to procurement — not PDF.
  • Engineering reviews accuracy — content becomes technical asset, not marketing fluff.
  • RFQ pipeline from online research measured — not just trade shows.

Squad

The team behind execution

Managed service means real people operating Atlas — not software sold as a self-serve product.

01

Strategy & Atlas Lead

Translates data into strategy and operates the Oura Atlas loop.

02

Technical SEO Lead

Core Web Vitals, architecture, schema, and overall site health.

03

Content & Editorial

Answer-first content that Google reads and AI engines cite.

04

AI Visibility Specialist

OAVF execution, query mapping, and citation monitoring across generative engines.

Explore more

Related case studies

First step · free

Want results like this for your brand?

Start with a Free Mini Audit — we map your fastest path.

  • Free
  • No commitment
  • Results in 48h

Win on Google. Get cited by AI.

Mini Audit

Step 1 / 3

1. About you

Continue →

SEO

3 priorities

GEO

citation gap

AEO

schema check

FAQ — Case Studies

What was the main challenge in this Manufacturing / B2B export case study?

Industrial components manufacturer, 340 SKUs, 60% export to ASEAN and Europe. 200-page PDF catalog — not indexed. Website had short product pages without structured spec tables. Taiwan and China competitors had per-SKU pages with material grade, compliance, FAQ — appearing in ChatGPT for technical queries. Internal CRM: 73% of buyers researched online before RFQ. Sales lost opportunities with no URL to forward to procurement — only PDF. This story shows how the Oura squad + Atlas handle similar profiles through the Oura Growth package.

Which Oura package ran the "B2B manufacturer: buyers research specs on ChatGPT before RFQ — our catalog never appears" project?

This project ran on Oura Growth. Service scope was tailored to Manufacturing / B2B export — see the timeline and approach sections on this page for execution detail.

What is the main takeaway from this case study?

In B2B manufacturing, PDF catalogs are not discovery assets — structured spec pages citable by AI are. Buyers research first, RFQ second. Figures on this page come from real client data with publication permission.

How long until impact usually shows?

It depends on technical foundation and competition. Technical fixes and quick wins often show in 4–8 weeks; organic momentum and AI referral usually need several months of continuous iteration.

Which package fits a profile like this?

See the sidebar summary — each case study links to the Oura package that ran it. A Mini Audit helps map the realistic tier for your context.

WhatsApp