A private map of how the company actually runs.

Most firms were told to do AI and were handed a chat window. Chat does not know your vendors, your GeM tenders, or who is allowed to submit. General Inference installs a suite on the work you already run in India and Southeast Asia — so the system prepares, and your people decide.

A mandate is not a map. We start with one workflow on your cloud. The rest is the path — not the day-one install.

Keep the house you have.

What you already run

Spreadsheets, folders, ERP extracts. Open or commercial models you can swap. ERP, WhatsApp, GeM, and the portals where work already leaves. We read what we need into a private workspace on your cloud. We do not ask you to replace the systems of record.

  • Data: Files, sheets, extracts, and the records you already keep.
  • Models: Swappable. Not locked to one rented chat API.
  • Systems: ERP, email, WhatsApp, GeM. Your people still send and submit.

The real things. In one place.

The company map

Plants, warehouses, trucks, vendors, tenders, inventory — the same objects, not forty disconnected sheets. If you have heard the word ontology, this is that idea in plain language: a shared list of what the company actually is. Work is prepared on the map: quote, shortlist, compare, chase, restock, raise an order.

  • Quote: A tender or RFQ becomes a set a person can check.
  • Shortlist: The listings that fit. The team decides.
  • Compare: Supplier quotes lined up on landed cost and lead time.
  • Chase: Collections and threads that otherwise die in WhatsApp.
  • Restock: A draft when inventory needs a decision.
  • Order: A purchase order prepared. A person still raises it.

The suite prepares. People decide.

How people use it

Operators see the work in context. Automations draft and chase — they do not submit on GeM. Later, APIs and SDKs so other tools can read the same map. That fence is intentional.

  • Desks: A short view for the people who already run the day.
  • Automations: Prepare the next step. A person still sends.
  • Build: SDKs when the map is in daily use — not as the first offer.

The fence stays up.

GeM still needs a person

The suite prepares the set. Your team still submits. We do not auto-submit tenders.

ERP stays the system of record

We read what we must. We do not become a second books.

Bills stay in your name

Cloud and model charges remain on your accounts. We do not resell tokens.

Questions

What is the company map, in plain words?

A shared list of the real things in the company — a plant, a vendor, a tender — so every workflow talks about the same objects instead of another spreadsheet.

Do we get the whole map on day one?

No. You get a private workspace and the first workflow that hurts. The map grows as more work sits on the same objects.

Will this submit on GeM?

No. Your people still send and submit. The suite prepares quotations, shortlists, and follow-ups.

Where does it run?

On your cloud. Models are swappable. Compute and subscriptions stay in your name.

If you have the work and not yet the map, write to us.

Describe the workflow in plain language. We will say if the suite is the wrong place to start.

Start a conversation

See the roadmap