Built for Indian manufacturing
The OS for the purchase department
One agent — Nish — takes a requisition all the way to a purchase order. It drafts the RFQ, chases the vendors, and puts an evaluated comparison in front of you minutes after the quotes land — with a should-cost sheet for every RFQ, so you negotiate against a number instead of a feeling.
Deterministic
No model sits in the comparison or costing maths.
India-first
INR, GST treatment, MSME status, en-IN throughout.
Human-sent
Every outbound email is staged. A person clicks Send.
Live example · evaluated comparison
Bearing 6206-2RS · 500 nos · Plant 1 · 3 of 5 quotes in
Vendor
Quoted
Evaluated
Krishna Traders
L1Rajkot · Composition dealer · ex-works
₹4,18,000
—
Suraj Bearings Pvt Ltd
Pune · Registered · ex-works · 30-day credit
₹4,26,000
—
Meenakshi Industrial Supply
Coimbatore · Registered · delivered · 100% advance
₹4,41,000
—
As received, Krishna Traders looks cheapest by ₹8,000. Nothing has been normalised yet.
01
Requisition
02
Approval
03
RFQ
04
Quotes
05
Comparison
06
Award
07
PO
08
Delivery
The process stays yours.
It just stops living in seven tabs.
ProcureOS does not ask your team to work a new way. It takes the way the purchase department already works — indent, quotes, comparative statement, approval, PO — and gives every step a place to live, a clock, and a record.
How it runs today
On ProcureOS
01
An indent arrives on WhatsApp, or as a photo of a paper slip.
The requester asks in their own words. Nish files it as a case against a budget head.
02
The RFQ gets retyped into Gmail, vendor by vendor.
One RFQ, drafted from the item spec and your standing terms, staged to every shortlisted vendor at once.
03
Quotes come back as PDFs, photos, and "same rate as last time".
Quotes are read on arrival and echoed back to the vendor to confirm before they count.
04
Somebody rebuilds the comparative statement in Excel, by hand.
The deck computes itself — versioned, re-runnable, every figure traced to a quote line.
05
Freight, GST treatment and credit terms get compared unevenly.
Freight, input-credit position, payment terms and validity are normalised for every vendor.
06
Approvals get chased on WhatsApp. Nobody knows what is pending.
Approvals route on your own value bands. Finance approves from the email, with the numbers in it.
07
The PO is typed a third time. Delivery slips, quietly.
The PO drafts from the awarded lines. Delivery dates are watched and the chase is written before you notice.
Two engines your team
cannot run by hand.
Everything else on this page is plumbing — good plumbing, but plumbing. These two are the reason a purchase head keeps the seat: an evaluated comparison on every RFQ, and a should-cost sheet before the first quote lands. Both are deterministic. Both improve when you correct them.
Engine 01
Evaluated comparison
Vendors quote on different terms, and the lowest number is almost never the lowest cost. The deck lands every quote on the same footing, then tells you who is actually L1 — and by how much.
Runs itself on every RFQ, the moment the quotes are in — you do not ask for it.
Normalises freight, input-credit position (registered · composition · unregistered), payment terms and quote validity.
Flags L1 per line as well as on the total, so a split award is visible when it is cheaper.
Same quotes in, same deck out, every time. There is no model anywhere in the maths.
If it read a quote wrong, say so in the thread. The correction is versioned — and it sticks for the next RFQ.
Engine 02
Precedent costing
A should-cost build-up for the part you are about to buy, drawn from what you have actually paid before. You walk into the negotiation with a number, and every line of it can be defended.
Drafts before the quotes arrive, from your own PO history, rate bases and index anchors.
Every line carries its provenance: your sheet, an index, an org norm, or a stated assumption.
Direct plus overheads plus margin, with a confidence band — not a single lonely number.
Should-cost · per unit
Lot 250 nos
Steel HRC 2.5 mm · 4.2 kg
index · steel-hrc
₹260
Machining, 3-axis · 1.4 hr
org norm
₹588
Heat treatment
your PO 2024/1187
₹85
Freight, Rajkot → Plant 1
assumption
₹24
Direct
₹957
Overheads @ 18%
₹172
Margin @ 12%
₹135
Should-cost · ±6%
₹1,264
Lowest quote for the same part: ₹1,402/unit. The ₹138 gap is the conversation.
Nish works where you can see it.
Nav on the left, the conversation in the middle, the thing being worked on to the right. You ask in a sentence; the workspace changes while you read the reply; the record of what changed sits in the thread forever.
procureos.app / case / RFQ-1042
Needs review
3
Cases
18
Vendors & items
Data library
Playbook
Reports
Nish · RFQ-1042
Anil · Purchase head
tool · send_reminder · 2 vendors
tool · edit_rfq · deadline → 31 Jul, 18:00 IST
Nish
Suraj Bearings has already quoted, so the deck will recompute the moment either reply lands.
2 emails staged for your send
reminder · RFQ-1042 · 2 recipients
Workspace · staged mail
StagedTo
sales@meenakshi-industrial.in
Cc
purchase@vajra-precision.in
Reply-to
case-1042@in.procureos.app
RFQ-1042 · Bearing 6206-2RS · revised deadline Fri 18:00
Dear Meenakshi Industrial Supply,
Following our enquiry of 22 Jul for 500 nos of deep-groove ball bearing 6206-2RS (C3 clearance), we have revised the quote deadline to Friday 31 Jul, 18:00 IST.
Please confirm freight to Plant 1, Aurangabad, your GST registration status, and validity of the offer…
Nothing leaves the building until a human clicks Send.
Typed tools only
Nish cannot improvise an action. It calls a named tool — draft the RFQ, record an offer, recompute the deck — and each call is logged with its arguments.
One decision at a time
At most one action card is ever open in the thread. No queue of half-understood approvals waiting on you.
Undo means undo
Every tool call can be reversed, and the workspace goes back to the state it was in — including the previous version of the deck.
Answers respect the role
The same question gets a different answer for a requester than for you. Requesters never see prices, from any surface.
Your rules, in a table
anyone can read.
Nobody at a plant is going to drag boxes onto a canvas. So the playbook is not a workflow builder — it is a list of rows: value bands, approval steps, clocks, skip rules, routing. Tell Nish the rule in a sentence and it becomes a row, in a new version, with your name on it.
01
You: "Anything above forty lakh needs the CFO too."
02
Nish: drafts playbook v7 with one changed row and shows you the diff.
03
You: approve. The next PO over ₹40,00,000 routes to the CFO — including the one already in flight.
Playbook v7
Active2 rows changed · 12 Jul 2026 · Anil
Value band
Up to ₹40,00,000
Finance approves. No second signature.
Value band
Above ₹40,00,000
changed in v7
Finance, then the CFO.
Clock
Quote reminder
Two days before the RFQ deadline, to whoever has not quoted.
Clock
PO acknowledgement
Chase on day 3.
Skip rule
Single source
Allowed with a written reason. Recorded as a deviation on the case.
Routing
Electricals
Always invite Ravi Engineering Works to the RFQ.
Notify
Budget head at 90%
changed in v7
Tell Finance and the case owner the same day.
Receipt route
Short delivery
Reopen the case and chase the balance quantity.
Every version is kept. You can read what the rule was on the day a case was approved.
One paid seat. The plant joins for free.
The purchase department buys seats for purchasers. Finance approves from email, requesters raise indents on your work domain at no cost, and suppliers never log in at all.
Paid seat
Purchaser
The shell, both engines, awards, PO approvals, the playbook, roles and reports.
Runs cases end to end with Nish
Releases the comparison deck
Owns the playbook and who can approve
Free
Finance
Email-first. Approves from the inbox, with the numbers inside the email — no login required to say yes.
Approves POs from email
Sees budget heads, commitments and actuals
Optional shell access when they want it
Free
Requester
Anyone on your work domain joins automatically and can raise and track their own requests.
Raises an indent in plain words
Tracks only their own requests
Never sees prices — from any surface
No seat, ever
Supplier
Suppliers work over email, the way they already do. There is no portal, no password to reset, no onboarding to run.
Receives the RFQ as normal mail
Replies with a quote in any format
Confirms what we read back to them
Roles are set by a purchaser with the right permission — approve POs, edit the playbook, edit roles, view reports. Nothing is granted by default, and every grant is a row you can read. Requesters never see prices.
An agent you can audit.
Decisions are human
Nish drafts, computes and chases. A person approves the budget, awards the order, and clicks Send on every external email. There is no auto-award switch to leave on by mistake.
The maths is computed, not generated
The comparison deck and the cost sheet are deterministic. The same quotes always produce the same deck — no language model sits anywhere in that path.
Every figure names its source
Each line points back to the quote line, past PO, rate basis, index or stated assumption it came from. Where a number is an assumption, it says so.
Retrieval respects the role
Ask “where is my bearing order?” as a requester and you get status and dates. The prices are simply not in the answer.
Your records are scoped to your org
Vendors, prices, playbook versions and cases carry your organisation on every row, and are read back through that scope on every query.
Drafting is automated and drafts can be wrong. The supplier's own quote and documents govern over any summary of them — check amounts and terms against the source before you commit.