Three Vendors, One Price Comparison

The indent that took a week to become a purchase order

A real estate company in Chennai running two active towers had a procurement process that looked organised on paper: a site engineer raised a material indent, the procurement head called three approved vendors for quotes, compared prices in a notebook or a quick Excel sheet, and placed the order with whoever was cheapest that week. In practice, this took anywhere from four to seven days per indent — most of it spent waiting for vendor callbacks and re-confirming quantities that had changed since the indent was raised.

The site team, meanwhile, often ran short on cement or TMT steel mid-pour because nobody had visibility into where an indent actually stood in the approval chain.

What changed when indents fed straight into RFQs

The company moved procurement into the same ERP tracking their construction schedule and BOQ. Every material indent raised on site now auto-generates a request for quote sent to approved vendors, with the price comparison — L1, L2, L3 — built automatically instead of assembled by hand.

• BOQ line items auto-generate RFQs the moment a site engineer raises an indent, instead of a separate manual step days later.
• Price comparison across vendors computed automatically as quotes come in — no more notebook tallying.
• Work orders and bills tracked against the same budget line the site schedule already uses, so overspend on one material shows up immediately, not at month-end.
• Vendor ratings — on-time delivery percentage and quality rejection rate — visible before the next order goes out, not discovered after a late delivery holds up a pour.

The average time from a site engineer raising an indent to a purchase order being placed dropped from most of a week to same-day, in most cases, once vendor quotes arrived within a fixed response window instead of an open-ended phone tag.

The budget conversation that got easier

Because procurement now runs on the same budget-vs-actual view as the rest of the project, a material price spike shows up as a variance the same day, not as a surprise the site engineer has to explain weeks later. The monthly cost review meeting shifted from reconstructing what happened to simply confirming numbers everyone had already seen coming.

Why procurement belongs inside the ERP, not a separate marketplace

It is tempting to treat procurement as a standalone marketplace problem — a place to shop for the best material price independent of any one project. In practice, the more valuable signal is internal: real demand data straight from your own BOQ and site indents, matched against vendors you already trust, inside the same system tracking cost against budget. That is exactly what the Real Estate ERP's procurement module is built to do.