Soor LLC builds KanchanFlow

Walk into a job shop with a good ERP and ask where work gets lost. Nobody says scheduling. They say the RFQ that sat in a shared inbox over a long weekend. They say the quote that went out on Tuesday and never got followed up. They say the argument with a buyer about what Rev 2 said, settled eventually by scrolling through sent mail on somebody's phone.

All of that happens before there is an order — which is exactly the region an ERP was never designed for. An ERP starts existing when a job does. Everything upstream is a shared inbox, a spreadsheet, a folder of PDFs and one person's memory.

The obvious answer is to bolt a sales module onto the ERP, and the industry has tried it for twenty years. It usually produces a module that is worse than a CRM at following up and worse than the ERP at everything else, and which needs an ERP consultant to change a quote template. The other obvious answer is a general-purpose CRM, which has no idea what a quantity break is, no concept of a quote revision, no cost buildup, and a data model built around a single deal amount rather than forty priced line items.

So we built the missing thing. A CRM that understands an RFQ has line items, that a quote has revisions and those revisions matter legally, that price depends on a cost buildup and not on a salesperson's optimism, and that the last step is not a closed-won flag but a purchase order matched against a signed revision and pushed into production.

And then we stopped. Deliberately, at the boundary where production starts. Not because scheduling is unimportant, but because you already have something running the floor, and the useful thing we can do is hand it a clean confirmed order instead of competing with it badly.