Procurement & Supply Chain
Procurement that runs on your data, not spreadsheets
You send the same RFQ to a dozen suppliers, then chase replies by phone and re-type quotes into Excel by hand. We put that loop on ProCul, our procurement platform, so the dispatch, the chasing and the comparison happen without you.
2 to 4
weeks to a working first version
2,582
manufacturers mapped in our supplier base
30+
RFQs automated end to end in pilots
The direct answer
Procurement AI on ProCul is a system that finds relevant suppliers, sends and chases RFQs by email, and turns whatever comes back (PDFs, Excel sheets, plain-text replies) into a side-by-side comparison table. It's built for procurement and operations teams in Saudi Arabia who currently run sourcing through email threads and manual spreadsheets, and who want the paper trail without the typing.
What this removes.
RFQs sit in someone's inbox
Today
A request goes out to five or six suppliers, then somebody has to remember to follow up two or three times before anyone replies.
With the system
The system dispatches the RFQ, follows up on a set schedule and flags the request once enough quotes are in.
Quotes arrive in different formats
Today
One supplier replies with a PDF, another sends an Excel sheet, a third just writes a price in the email body. Someone re-types all of it into one sheet.
With the system
Quote parsing reads PDFs, spreadsheets and plain text and puts every line item into the same table automatically.
No record of who quoted what
Today
Six months later nobody can find what a supplier quoted last time, so the same negotiation starts from zero.
With the system
Every RFQ, quote and supplier response is stored, searchable and tied to the item and the supplier that gave it.
Supplier lists go stale
Today
The supplier list is whoever the team has emailed before, so new or cheaper options rarely surface.
With the system
Supplier discovery pulls from a mapped base of manufacturers and distributors so new options show up on the next RFQ.
What lands in your hands.
Supplier discovery module
Matches your item or category against our mapped supplier base by product and region.
RFQ dispatch and chasing
Sends the request by email and follows up on a schedule you set, with no manual nudging.
Quote parsing engine
Extracts line items, prices and terms from PDFs, spreadsheets and email text into one structure.
Comparison view
Side-by-side table of quotes per item, with the source document attached to each line.
Spend and supplier history
Searchable record of past RFQs, quotes and supplier responses tied to each item.
ERP or spreadsheet handoff
Exports the final comparison into Excel or pushes it into your existing system.
Systems and platforms we work with
- React
- Next.js
- TypeScript
- Node.js
- Python
- Flutter
- PostgreSQL
- Supabase
- Tailwind CSS
- Docker
- GitHub
- Google Cloud
- Figma
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.
- Scope3 to 5 days
- Supplier mapping1 week
- Build and configure1 to 2 weeks
- Pilot run2 to 3 weeks
- Live operation and supportongoing
Scope
3 to 5 days
We map your current sourcing process (categories, suppliers, approval steps) and confirm which parts move to ProCul first.
- Share current RFQ templates and supplier lists
- Name the categories to start with
- A written scope covering categories, suppliers and data sources
- A short list of open questions
We move on when you sign off on the scope document and the first category to automate.
Supplier mapping
1 week
We match your categories against the ProCul supplier base and add any suppliers you already work with that aren't in it yet.
- Confirm which suppliers must be included
- Flag suppliers to exclude
- A supplier list per category with contact details
- Confirmation of which suppliers are new vs already mapped
We move on when you confirm the supplier list is complete for the pilot category.
Build and configure
1 to 2 weeks
We configure RFQ templates, chasing cadence and the comparison view for your categories, and connect quote parsing to your typical document formats.
- Review draft RFQ templates
- Provide sample supplier quotes for parsing tests
- Configured RFQ dispatch for the pilot category
- Quote parsing tested against your sample documents
We move on when a test RFQ runs end to end and the parsed quotes match the source documents.
Pilot run
2 to 3 weeks
We run real RFQs through the system for the pilot category while you review each dispatch and comparison before it counts as final.
- Approve each RFQ before it sends
- Review the comparison output against what you'd have produced manually
- A live pilot covering the agreed category
- A short report on accuracy and time saved
We move on when you're comfortable the comparisons match what you'd expect from a manual process.
Live operation and support
ongoing
The system runs on your full category set. We monitor dispatch and parsing accuracy and are available for changes as your supplier base or categories shift.
- Flag any new categories or suppliers to add
- Tell us if a document format starts failing to parse
- Ongoing monitoring of dispatch and parsing
- Support for adding categories or adjusting chasing cadence
We move on when this stage doesn't end. We stay on as your supplier base and categories change.
Asked before signing.
How is this priced?
Pricing is scoped per project based on the number of categories and suppliers you want covered, and whether you need custom ERP integration. We give you a fixed quote after the scoping stage, not an hourly estimate, so you know the number before we start building.
Does it handle RFQs and quotes in Arabic?
Yes. Quote parsing reads Arabic-language documents and mixed Arabic-English quotes, which is common with Saudi manufacturers and distributors. RFQ templates can be sent in Arabic, English or both depending on the supplier.
What happens to our supplier and pricing data?
Your data stays tied to your account and isn't shared across other clients' comparisons. We follow PDPL requirements on storage and access, and can walk through our data handling in more detail before you commit to anything.
Can it connect to our existing ERP or is it a separate system?
It can run standalone with exports to Excel, or push comparison data into an existing ERP or procurement system if you have one. We scope the integration during the build stage based on what you're running and what access we're given.
Get your sourcing off spreadsheets and email threads
Tell us your current RFQ process and supplier categories. We'll scope what moves to ProCul first and what it costs.
Nearby services