Purchasing runs in six stages, and each has an owner
Before you automate anything, break the process into stages. Most companies have six, even if nobody calls them that. The table shows who runs each stage once it is automated and where the data ends up.
| Stage | What happens | Who does it after automation | Where the data lives |
|---|---|---|---|
| 1. Request | Someone states what they need, how many and by when | The employee fills in a CRM form | Request record |
| 2. Approval | A manager confirms the need and the budget | A CRM automation rule routes it by amount | Request record |
| 3. RFQs | The specification goes to several suppliers | The AI agent sends RFQs and chases replies | Emails and chats in the CRM |
| 4. Quote collection | Replies arrive as PDFs, Excel files, emails and WhatsApp messages | The AI agent reads them and maps them to line items | Documents in the record |
| 5. Comparison and choice | Prices, lead times and terms are put side by side | The agent builds the table, the buyer decides | Comparison table in the CRM |
| 6. Order and delivery | Purchase order, payment, delivery tracking | CRM rules create tasks, the buyer manages it | Deal and accounting system |
MakeBiz Technologies outline for routine purchases of goods and services, excluding formal tenders.
Stages three to five carry most of the manual work, so that is where the agent goes. The rest is ordinary CRM automation.
Requests belong in the CRM, not in a group chat
Automation starts with a request form, not with AI. A voice note in a group chat tells no system what to buy. In Bitrix24 a purchase request works well as a separate smart process with its own stages: new, awaiting approval, RFQ sent, comparison, ordered, closed. See how these are built on our Bitrix24 development page.
Required fields:
- item or catalogue reference, quantity and unit of measure
- required date and delivery address: warehouse, office or site
- budget estimate and the cost centre it is charged to
- attachments: photo, drawing or specification, if there is one
Without these fields a request does not move on. A CRM rule sends it to the line manager, and above a threshold you set, to the finance director too. No AI needed here.
The agent takes over RFQs and supplier follow-ups
After approval comes the part buyers like least: sending the specification, chasing silent suppliers and tracking who got what. The procurement agent does this itself: it takes suppliers for the category from your database, sends the RFQ by email or messenger and follows up with anyone who has not replied.
Every message is saved in the request record, so history stays when people leave. If your suppliers work on WhatsApp, the channel is connected to the CRM through the official platform, see our messengers in Bitrix24 page. The agent does not promise volumes and does not negotiate: if a supplier asks something outside the specification, the question goes to the buyer.
