AI for ERP/CRM-using businesses

KobiGPT does not replace an ERP or CRM. Changing data such as contacts, invoices, opportunities, people, tasks, production and maintenance records remains owned by the relevant business application. Procedures, product notes, sales playbooks and HR policies stay in the document layer. The assistant combines only the information within the connections and documents explicitly made available to it.

That separation matters for SMEs already operating an ERP or CRM. Answering stock, balance or opportunity-stage questions from an old PDF can produce a stale result; looking only at the live record can miss the company procedure or exception rule. A pilot should state which questions use documents, which use a connection and how the source type is shown to the user.

Teams may evaluate Paraşüt for accounting, Tek Sistem ERP for production and HR records, and HubSpot, Salesforce, NextMind CRM or Apollo for sales and customer workflows. These names reflect the current central integration-evidence catalog. Systems such as SAP, Logo, Mikro or Netsis are not presented as ready integrations when they are absent from that catalog.

Catalog entries do not all share the same delivery model. A ready entry means a vendor-managed connection surface is available in the catalog. A self_hosted entry requires an organisation or delivery team to operate its own mcp-host, credentials and grant configuration. In both cases, tenant enablement and proposal scope must be confirmed before a public page or sales process describes the connection as usable for that customer.

Finding a record is not the same authority as creating, updating or deleting one in an external system. Even read-only tools should be visible only within the relevant company and department grants. When a tool writes or has destructive effect, it must not complete without single-use user confirmation. The page does not assume every connector is enabled for every tenant or that every tool can write.

Setup review should include negative tests with a sample user, the wrong department and an out-of-scope customer record. Record that the assistant cannot retrieve data it should not see, does not invent a missing result and does not complete a confirmation-gated step by itself. This turns a security adjective into inspectable access, record and approval evidence.

Start with one department, a bounded document set and one connection whose enablement is verified. Test five to ten frequent questions against source correctness, permission scope, the underlying record and the required human review. No generic promise is made about launch days: timing depends on document volume, connection model, permissions and the agreed delivery scope.

A useful success record goes beyond the number of answered questions. Track wrong or missing sources, unnecessary tool calls, actions sent for approval and the path from an ERP/CRM content page to a demo or registration start. KobiGPT is the product scope; consulting and training, where required, are separately scoped and delivered by X Mind Solutions.