Module
SIAARU CRM
A pipeline that knows whether you can actually deliver what you are about to promise.
What it produces
- Deals, contacts and activities, with the pipeline by stage and expected close
- Every deal line checked against stock, open orders and measured lead times
- A per-line verdict: from stock, from stock and orders, if ordered now, or cannot fulfil
- The shortfall and the days of slack, with the arithmetic shown
- A won deal converted to a sales order without re-keying a line
A worked example
D-2291 — Acme Industrial, ₹48,00,000 — cannot fulfil
line 3 · RM-10291 · 4,000 KG promised 12 Sep
820 available plus 0 incoming leaves 3,180 short
lead time 34 days against 21 to the promise
→ 13 days late even if ordered today; move the date or split the delivery
Illustrative figures. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
A pipeline that does not know what the plant can make is a list of promises waiting to be broken. A salesperson commits to a date because the customer asked for one, and the first person to discover it was never possible is on the shop floor six weeks later. Reading the same stock, capacity and lead times the planner reads means the date can be checked before it is given. It is a smaller feature than it sounds, and it changes which conversations happen and when they happen.
Opened by the sales manager, the supply chain manager and the planner — what each of them sees first.
Said before you ask
What is not finished.
BETA rather than AVAILABLE. The fulfilment engine is the reason to build a CRM here rather than buy one: nothing else can check a promise against your own stock and measured lead times. Pipeline screens, the deals import and converting a won deal to a sales order all work. Email and calendar capture now exists through the company CRM mailbox: CC or BCC it on deal correspondence, or book it into a meeting, and the daily sweep attaches the message to every open deal whose contact it involves — deduplicated, so a re-run writes nothing twice. It reads that one shared mailbox only, never anybody's personal mail, and it needs Mail.Read and Calendars.Read granted to the app registration — until then the sweep names that refusal instead of reporting a quiet week. Still BETA because no customer has yet run the pipeline against their own deals.
Where this sits
One of 16 modules, on one engine.
SIAARU CRM reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 15 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.