Skip to content
Al Khobar, Saudi Arabia

Procurement & Supply Chain

RFQs that chase suppliers, not the other way around

Your team writes one request. ProCul finds matching suppliers, sends it, follows up until they answer, and turns replies into a comparison table you can act on the same day.

2 to 4

weeks to a working first version

2,582

manufacturers already mapped for matching

24/7

automated follow-up on open requests

Supplier matchingAutomated dispatchReply chasingQuote parsingComparison tablesArabic and EnglishPDPL-aware handlingAudit trail

The direct answer

RFQ Automation runs your request-for-quote process on ProCul instead of email threads and spreadsheets. You describe what you need, the system matches it against a supplier base, sends the request, chases non-responders, and parses replies into a structured comparison. It's built for procurement or ops teams in Saudi Arabia who send more than a handful of RFQs a month and lose time to manual follow-up.

Concept demo · in-house render
Before and after

What this removes.

RFQs stall on follow-up

Today

You send a request, then wait, then email again, then call. Half your week goes to chasing suppliers who never opened the first message.

With the system

The system sends scheduled follow-ups on a cadence you set. You see who's responded and who hasn't without opening your inbox.

Quotes arrive in different formats

Today

One supplier replies in an email body, another attaches a PDF, a third sends an Excel sheet with its own layout. Comparing them means retyping numbers.

With the system

Replies get parsed into the same fields regardless of format, so unit price, lead time, and terms line up in one table.

Supplier lists go stale

Today

The supplier list your team uses is whoever someone remembered last time. New RFQs go to the same five names by default.

With the system

Each RFQ is matched against a mapped supplier base by category, so you see options beyond your usual contacts.

No record of what was asked or promised

Today

When a supplier disputes a price or a spec later, there's no clean record of the original request and reply.

With the system

Every dispatch, follow-up, and reply is logged against the RFQ, so you can pull the history in seconds.

What we build

What lands in your hands.

RFQ intake form

A structured request form for your team, in Arabic and English.

Supplier matching rules

Category and product matching against the mapped supplier base.

Automated dispatch and chasing

Scheduled sends and follow-ups with a cadence you approve.

Reply parsing

Emails, PDFs, and spreadsheets normalized into one comparison format.

Comparison dashboard

Side-by-side quotes with price, lead time, and terms.

Activity log

Full history of what was sent, to whom, and when.

Systems and platforms we work with

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Python
  • Flutter
  • PostgreSQL
  • Supabase
  • Tailwind CSS
  • Docker
  • GitHub
  • Google Cloud
  • Figma
The delivery plan

Five stages. You sign off every one.

Read each stage as a small contract: what we need from you, what lands in your hands, and the sentence that has to be true before we move on.

01 / 05

Scope and access

3 to 5 days

We map your current RFQ process, the product categories you buy, and where supplier data currently lives.

What you do
  • Share current RFQ templates
  • List product categories in scope
  • Name who approves sends
What we deliver
  • Process map of current RFQ flow
  • Confirmed scope and category list
Exit criteria

We move on when the process map matches how your team actually works, not how it's documented.

02 / 05

Supplier matching setup

1 week

We configure category matching against the supplier base and add any suppliers specific to your business that aren't already mapped.

What you do
  • Review matched supplier lists
  • Provide any private supplier contacts
What we deliver
  • Configured matching rules per category
  • Test match run on sample RFQs
Exit criteria

We move on when a sample RFQ returns a supplier shortlist your buyer would actually send.

03 / 05

Dispatch and chasing configuration

1 week

We set the send templates, follow-up cadence, and escalation points, then test the full loop on a real or simulated RFQ.

What you do
  • Approve email templates
  • Set follow-up cadence and limits
What we deliver
  • Configured dispatch and chase automation
  • One full test cycle with results
Exit criteria

We move on when a test RFQ dispatches, follows up, and logs replies without manual steps.

04 / 05

Quote parsing and comparison

3 to 5 days

We tune the parser against real supplier reply formats from your process and build the comparison view your team will use.

What you do
  • Share sample past supplier quotes
  • Confirm the fields that matter for comparison
What we deliver
  • Parsing tuned to your supplier formats
  • Working comparison dashboard
Exit criteria

We move on when quotes from past RFQs parse correctly into the comparison table without manual correction.

05 / 05

Live operation and support

ongoing

Your team runs RFQs on the live system. We monitor dispatch and parsing accuracy and handle new categories or supplier additions as they come up.

What you do
  • Run real RFQs
  • Flag any parsing or matching misses
What we deliver
  • Monitoring of send and parse accuracy
  • Support for new categories and suppliers
Exit criteria

We move on when we move on when your team is running RFQs independently and issues are handled through support, not a rebuild.

Buyer questions

Asked before signing.

How is this priced?

Setup is a fixed project fee based on the number of categories and integrations in scope, agreed before we start. Ongoing use runs on a monthly fee tied to RFQ volume. We'll give you a specific number after the scoping call, not a range you have to guess from.

Does this work in Arabic?

Yes. The intake form, supplier-facing emails, and parsing both handle Arabic and English, since most KSA supplier replies mix the two. You choose which language goes out by default per category.

What happens to our data?

RFQ and supplier data stays in your ProCul instance, handled under PDPL. We don't sell or share it, and we can walk you through the specific data flows before you commit to anything.

Can this connect to our existing ERP or Excel process?

Yes for common cases, we've connected to Excel-based procurement logs and can integrate with Odoo, SAP, or similar systems depending on what you run. We scope the integration in week one so there are no surprises later.

Stop chasing suppliers by hand

Tell us how you run RFQs today. We'll show you what automation looks like for your categories before you commit to anything.