Procurement & project coordination autopilot

Your operations, on autopilot.

PashX captures requests from email, WhatsApp, documents and project systems — then coordinates suppliers, purchase orders, deliveries, invoices and exceptions in one operational workspace. It chases the follow-ups. You approve the judgement calls.

  • Live on one workflow in weeks
  • Every action scored, logged, reversible
  • Your ERP stays the system of record
Autopilot · exceptions
Needs review
WhatsApp · supplier

“Sir 16mm ka load ready hai but truck Monday niklega, 23rd ko site pe pahunchega. Rate 68,400 hi rahega.”

Extracted & matched

Purchase order
PO-2214 · Skyline Tower B
97%
Supplier
Sri Balaji Steels
96%
Item
TMT Fe500D · 16mm · 24 T
94%
Promised date
18 Aug → 23 Aug (5 days late)
71%

Delay detected. Draft chaser to site engineer and re-baseline the delivery date?

Approve Edit then syncs to your ERP

BUILT TO SIT ALONGSIDE

Your system of record stays where it is. PashX syncs approved actions out to it.

SAP
Zoho
Oracle
Microsoft
QuickBooks
Tally
SAP
Zoho
Oracle
Microsoft
QuickBooks
Tally

DESIGN PARTNERS & PILOTS

Bharath
Greyline
Hammer & Nail
ILMTEC
MAB
Empact
Landmark
Bharath
Greyline
Hammer & Nail
ILMTEC
MAB
Empact
Landmark

THE OPERATOR'S DAY

Your team is the integration layer

Not because the systems are bad — because the work arrives as messages, and only a human can read a message, decide what it means, and put it somewhere.

The real order book is a chat thread

Confirmations, rate revisions and delivery dates arrive on WhatsApp and email. Nothing that matters starts life as a record.

Chasing is a full-time job nobody was hired for

Unconfirmed POs, missing test certificates, silent subcontractors. Someone re-reads the same thread every morning to work out who to nudge.

Re-keying is where the errors get in

A quantity typed from a PDF into the ERP, a rate copied from a quote sent three weeks ago. The mistake surfaces at reconciliation, not at entry.

Exceptions are found after the money moves

Short delivery, price drift against the quote, a duplicate invoice. All visible in the messages at the time — all caught at month-end.

WHAT AUTOPILOT DOES

From a message to a completed action

Six steps, run on every inbound message. Steps one to four happen without you. Step five is where you come in.

  1. Step 1

    Capture

    Email, WhatsApp, PDFs and spreadsheets, web forms, and events from your project systems — all land in one queue.

  2. Step 2

    Classify & extract

    Autopilot decides what the message is — quote, PO confirmation, delivery note, invoice, query — and pulls the fields out as structured data.

  3. Step 3

    Match

    Fields are resolved against your suppliers, projects, BOQ lines, purchase orders and goods receipts. Every match carries a score.

  4. Step 4

    Follow up

    Unconfirmed orders, missing documents and silent subcontractors get chased on a schedule, in thread, until they answer.

  5. Step 5

    Detect & escalate

    Delays, price changes, quantity mismatches and missing paperwork are raised as exceptions. Only these reach a person.

    Human decides

  6. Step 6

    Sync

    Approved outcomes are written back to PashX and pushed to your ERP or finance system, with the full trail attached.

THE EXCEPTION COCKPIT

Autonomy you grant, not assume

Autopilot does not get to be confidently wrong on your behalf. Work it is sure about clears; work it is not lands in one queue with the evidence attached, and a person decides.

A score on every field

Extraction and matching each produce a confidence value. It is stored with the record, not thrown away after the decision.

Thresholds you set

You choose what Autopilot may do alone and where it must stop. Start with everything routed to a human; loosen it once you trust the numbers.

Approve, edit, or reject

Low-confidence items queue up with the original message side by side with what was extracted. Your edit is the correction the system learns from.

A trail that survives audit

Every extraction, score, edit, approval, message sent and sync event is logged and attributable. Nothing the AI did is a black box after the fact.

Today's queue

2 need a person · 2 cleared on their own

Threshold 85%
  • PO-2214Needs review

    Delivery slipped 5 days — Sri Balaji Steels

    71%
  • INV-0982Needs review

    Rate ₹68,400 vs quoted ₹66,900 — 2.2% over

    64%
  • GRN-455Auto-flagged

    Short delivery: 22 T received against 24 T ordered

    88%
  • PO-2190Auto-approved

    Confirmation matched, dates unchanged

    96%

Every row expands to the original message, the fields extracted from it, and the full history of what changed.

THE WORKFLOWS

Start with one. Expand when it earns it.

Autopilot goes live on a single workflow, against your real message traffic. Nothing else changes until that one is working.

Triggered when

A PO has been issued and the supplier has not confirmed quantity, rate or date.

What Autopilot does

  • Reads confirmations arriving by email or WhatsApp, in whatever format they come
  • Matches them to the open PO and its BOQ lines, field by field
  • Chases the supplier on a schedule and escalates if the thread goes quiet
  • Raises an exception the moment a date or rate moves

What you get

Your open-order book is accurate every morning without anyone re-reading a thread.

CONNECTS TO WHAT YOU RUN

Messages in. Approved records out.

Autopilot does not ask your suppliers to change how they contact you, and it does not ask you to change your system of record.

Where work comes in

Email

A shared mailbox, or forwarding rules from the one you already use.

WhatsApp

A WhatsApp Business number your suppliers already message.

Documents

PDFs, scans and spreadsheets — quotes, challans, invoices, certificates.

Forms & webhooks

Site apps and project systems posting events straight in.

Where approved actions go

Webhooks / REST API

Any system that can receive JSON

Live

Excel / CSV

Export and scheduled drops

Live

Tally

Finance

In pilot

Zoho

CRM and Books

In pilot

Microsoft 365

Mail and files

In pilot

SAP

ERP

On request

Oracle

ERP

On request

Odoo

ERP

On request

QuickBooks

Accounting

On request

“On request” means there is no packaged connector yet — the sync runs over our API or your integration layer, scoped during onboarding. We would rather say that than imply a button exists.

WHAT IT IS WORTH

Two things change. Only two.

Coordination time your team stops spending, and billing errors caught before the money leaves. Every assumption below is yours to change.

Your operation

1,200

Order confirmations, delivery updates, rate revisions, document chases — across email and WhatsApp.

6 min

Reading it, working out which order it belongs to, replying, and putting it somewhere.

₹600
₹2,50,00,000
1.5%

Rate drift against the quote, short deliveries, duplicate or mis-taxed invoices.

Indicative annual value

₹20,93,400

Coordination time

Your team spends about 120 hours a month on these messages. At a 60% automation rate that returns 72 hours ₹43,200 a month.

Exceptions caught in time

₹3,75,000 of monthly spend arrives wrong on your own estimate. Catching it before payment rather than after recovers ₹1,31,250 a month at a 35% recovery assumption.

Pressure-test this on your numbers

This is arithmetic on your inputs, not a result PashX has measured at your company. The automation and recovery rates above are deliberately conservative; a pilot measures your real baseline before and after.

SECURITY & GOVERNANCE

Built to survive the questions finance asks

An agent that talks to your suppliers and writes to your ledger has to be accountable for every action it takes.

Nothing irreversible without a human

Autopilot drafts and proposes. Sending to a supplier or writing to your ERP happens after an approval, until you raise the threshold yourself.

Complete audit trail

Every extraction, score, edit, approval and sync is recorded with who did it and when, and is exportable for an auditor.

Role-based access

Procurement, finance, site and admin see and approve different things. Permissions are enforced server-side, not hidden in the UI.

Credentials never sit in the database

Integration secrets are injected from a managed secret store at deploy time. There is no screen that saves an API key into a record.

Your data is yours

Your messages and records are not used to train shared models. Export or deletion on request, in a machine-readable format.

Only what the workflow needs

Autopilot reads the channels you connect it to and nothing else. Scope is set per workflow at onboarding, not granted wholesale.

Formal certification is in progress rather than complete, and we will publish each attestation here with its report date rather than before. Security documentation is available under NDA on request.

HOW WE PROVE IT

We measure your baseline before we claim anything

PashX Autopilot is in early access with a small group of operating teams. Rather than quote numbers we cannot show you the working for, here is exactly what a pilot measures on your own operation.

Follow-ups sent without a human

Every supplier chase Autopilot sends on its own, counted against the ones your team still had to write.

Hours returned to the procurement desk

Time your team spends reading, re-keying and chasing before Autopilot, measured again after four weeks live.

Exceptions caught before the invoice

Rate changes, short deliveries and missing documents flagged at the point they happen — not at month-end reconciliation.

What every pilot commits to

  • One workflow live first. Purchase-order follow-up, then we expand.
  • Every action scored, logged and reversible. Nothing autonomous on day one.
  • Your ERP stays the system of record. PashX writes to it, never replaces it.

BEFORE YOU ASK

The questions that decide this

Put one workflow on autopilot

Bring us a week of your supplier messages. We will show you what Autopilot would have extracted, matched and chased — before you commit to anything.