Where we are. Where this goes.
Today: first workflows in a private workspace. Next: more workflows sharing the same objects. Then: a full company map for manufacturing and trading in India and Southeast Asia.
This is a path, not a promise of dates on a particular plant. What you feel at each step is listed. What does not change is listed too.
Now: A private workspace. The first workflows.
In use
Your people open a workspace on your cloud. Quotations are prepared from RFQs and tenders. Follow-ups are drafted. A person still checks and submits.
What does not change
- Your team still submits on GeM.
- ERP stays the system of record.
- Cloud and model bills stay in your name.
Next: More work on the same install.
0–6 months
Further workflows sit on the workspace you already have. Vendor and tender objects are shared between them. Directors get a short desk brief — not another place to log in.
What does not change
- The GeM fence does not move.
- The books do not move.
- New work is added. The house is not rebuilt.
Then: The living map.
6–18 months
The full company map: assets, counterparties, and inventory as reusable objects. Automations run across desks. Analytics sit on top of the same map.
What does not change
- A person still decides what leaves the building.
- ERP remains the record.
- Objects stay in your workspace, on your cloud.
Horizon: The map, across plants and countries.
After
Private or regional compute options. SDKs so other tools plug into the map. Multi-plant and multi-country trading desks on the same company map.
What does not change
- Humans still submit where the law and the customer require it.
- One rented chat API is still not the product.
- Your cloud. Your records. Your call.
Start with the workflow that already has a file and a deadline.
The map is the path. The first conversation is the work you run this month.
Start a conversation