{"id":8273,"date":"2026-10-08T15:12:15","date_gmt":"2026-10-08T15:12:15","guid":{"rendered":"https:\/\/kanhasoft.com\/blog\/?p=8273"},"modified":"2026-10-08T15:12:15","modified_gmt":"2026-10-08T15:12:15","slug":"context-engineering-enterprise-ai-crm-erp","status":"publish","type":"post","link":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/","title":{"rendered":"Context Engineering for Enterprise AI: The Missing Piece in CRM &#038; ERP"},"content":{"rendered":"<p><span>A company can connect a powerful large language model to its CRM and still get a mediocre AI assistant. The problem may not be the model at all. For businesses investing in <a href=\"https:\/\/kanhasoft.com\/crm-software-development.html\">custom CRM development<\/a>, context engineering for enterprise AI is becoming just as important as model selection, prompting, and integrations.<\/span><\/p>\n<p><span>An enterprise AI system needs more than access to customer records. It must know which records matter, which information is current, what a user is allowed to see, which business rules apply, what happened earlier in the workflow, and which actions are safe.<\/span><\/p>\n<p><span>That is the job of context engineering.<\/span><\/p>\n<h2><span>Quick Answer: What Is Context Engineering for Enterprise AI?<\/span><\/h2>\n<p><span>Context engineering for enterprise AI is the practice of selecting, organizing, updating, and governing the information an AI model receives before it answers a question or takes an action.<\/span><\/p>\n<p><span>In CRM and ERP systems, that context can include customer records, transactions, documents, user roles, business rules, conversation history, workflow status, retrieved knowledge, approved tools, and real-time operational data.<\/span><\/p>\n<p><span>Prompt engineering tells the AI what you want.<\/span><\/p>\n<p><span>Context engineering gives the AI what it needs to know before deciding what to do.<\/span><\/p>\n<p><span>Anthropic describes context engineering as a progression beyond prompt engineering: instead of optimizing only the instructions given to a model, developers manage the broader information available during inference, including tools, external data, message history, and other evolving state.<\/span><\/p>\n<p><span>This article is especially useful for:<\/span><\/p>\n<ul>\n<li><span>CTOs and CIOs planning enterprise AI initiatives<\/span><\/li>\n<li><span>CRM and ERP product owners<\/span><\/li>\n<li><span>operations and sales leaders evaluating AI agents<\/span><\/li>\n<li><span>SaaS companies adding AI capabilities<\/span><\/li>\n<li><span>technical teams designing RAG or agentic AI systems<\/span><\/li>\n<li><span>business leaders deciding how much AI autonomy is appropriate<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-engineering-for-enterprise-AI-connecting-CRM-and-ERP-data-to-AI-decision-making.jpeg\" alt=\"Context engineering for enterprise AI connecting CRM and ERP data to AI decision-making\" width=\"1500\" height=\"844\" class=\"alignnone wp-image-8275 size-full\" srcset=\"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-engineering-for-enterprise-AI-connecting-CRM-and-ERP-data-to-AI-decision-making.jpeg 1500w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-engineering-for-enterprise-AI-connecting-CRM-and-ERP-data-to-AI-decision-making-300x169.jpeg 300w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-engineering-for-enterprise-AI-connecting-CRM-and-ERP-data-to-AI-decision-making-1024x576.jpeg 1024w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-engineering-for-enterprise-AI-connecting-CRM-and-ERP-data-to-AI-decision-making-768x432.jpeg 768w\" sizes=\"auto, (max-width: 1500px) 100vw, 1500px\" \/><\/span><\/li>\n<\/ul>\n<h2><span>Why Good AI Models Still Give Bad Enterprise Answers<\/span><\/h2>\n<p><span>Consider a sales manager who asks an AI assistant:<\/span><\/p>\n<p><strong><span>\u201cWhich deals are most likely to slip this month?\u201d<\/span><\/strong><\/p>\n<p><span>The CRM may contain everything needed to answer.<\/span><\/p>\n<p><span>However, useful reasoning could require the AI to understand:<\/span><\/p>\n<ul>\n<li><span>opportunity stage<\/span><\/li>\n<li><span>expected close date<\/span><\/li>\n<li><span>last customer interaction<\/span><\/li>\n<li><span>outstanding quotation<\/span><\/li>\n<li><span>salesperson notes<\/span><\/li>\n<li><span>customer support issues<\/span><\/li>\n<li><span>decision-maker engagement<\/span><\/li>\n<li><span>pending tasks<\/span><\/li>\n<li><span>historical stage duration<\/span><\/li>\n<li><span>recent emails<\/span><\/li>\n<li><span>account ownership<\/span><\/li>\n<\/ul>\n<p><span>Giving the model only the opportunity record provides too little context.<\/span><\/p>\n<p><span>Dumping the entire CRM into the prompt provides too much.<\/span><\/p>\n<p><span>The challenge is selecting the smallest useful set of trustworthy information for the task.<\/span><\/p>\n<p><span>That is context engineering.<\/span><\/p>\n<p><span>The same problem appears in ERP systems. A procurement agent deciding whether material needs replenishment may need inventory levels, production demand, incoming purchase orders, approved suppliers, lead times, warehouse locations, reorder rules, and purchasing authority.<\/span><\/p>\n<p><span>One missing piece can change the recommendation.<\/span><\/p>\n<h2><span>Context Engineering vs.\u00a0Prompt Engineering vs.\u00a0RAG<\/span><\/h2>\n<p><span>These terms are related, but they solve different problems.<\/span><\/p>\n<table width=\"100%\">\n<thead>\n<tr>\n<td width=\"176\"><span>Approach<\/span><\/td>\n<td width=\"176\"><span>Main Question<\/span><\/td>\n<td width=\"176\"><span>Typical Purpose<\/span><\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td width=\"176\"><span>Prompt engineering<\/span><\/td>\n<td width=\"176\"><span>How should we instruct the model?<\/span><\/td>\n<td width=\"176\"><span>Improve instructions and output behavior<\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"176\"><span>RAG<\/span><\/td>\n<td width=\"176\"><span>Which external information should we retrieve?<\/span><\/td>\n<td width=\"176\"><span>Ground responses in documents or business knowledge<\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"176\"><span>Context engineering<\/span><\/td>\n<td width=\"176\"><span>What information should the model know right now?<\/span><\/td>\n<td width=\"176\"><span>Assemble the complete, task-relevant AI context<\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"176\"><span>Fine-tuning<\/span><\/td>\n<td width=\"176\"><span>What behavior or patterns should the model learn?<\/span><\/td>\n<td width=\"176\"><span>Specialize model behavior<\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"176\"><span>Tool integration<\/span><\/td>\n<td width=\"176\"><span>What systems can the AI interact with?<\/span><\/td>\n<td width=\"176\"><span>Retrieve information or perform approved actions<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span>RAG is therefore part of context engineering, not a replacement for it.<\/span><\/p>\n<p><span>A RAG system might retrieve a pricing policy from a knowledge base. Context engineering determines whether that policy should be combined with the customer\u2019s contract, user permissions, current quote, account tier, transaction history, and approval limits.<\/span><\/p>\n<p><span>That distinction matters in enterprise software.<\/span><\/p>\n<h2><span>What Actually Goes Into Enterprise AI Context?<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-combining-CRM-ERP-rules-permissions-and-workflow-data.jpeg\" alt=\"Enterprise AI context combining CRM, ERP, rules, permissions, and workflow data\" width=\"1500\" height=\"844\" class=\"alignnone wp-image-8276 size-full\" srcset=\"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-combining-CRM-ERP-rules-permissions-and-workflow-data.jpeg 1500w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-combining-CRM-ERP-rules-permissions-and-workflow-data-300x169.jpeg 300w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-combining-CRM-ERP-rules-permissions-and-workflow-data-1024x576.jpeg 1024w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-combining-CRM-ERP-rules-permissions-and-workflow-data-768x432.jpeg 768w\" sizes=\"auto, (max-width: 1500px) 100vw, 1500px\" \/><\/span><\/h2>\n<p><span>A strong context architecture usually combines several information types.<\/span><\/p>\n<h3><span>1. Transactional CRM and ERP Data<\/span><\/h3>\n<p><span>This is structured operational information such as:<\/span><\/p>\n<ul>\n<li><span>customers and contacts<\/span><\/li>\n<li><span>opportunities<\/span><\/li>\n<li><span>quotations<\/span><\/li>\n<li><span>orders<\/span><\/li>\n<li><span>inventory<\/span><\/li>\n<li><span>invoices<\/span><\/li>\n<li><span>payments<\/span><\/li>\n<li><span>production orders<\/span><\/li>\n<li><span>purchase orders<\/span><\/li>\n<li><span>support cases<\/span><\/li>\n<\/ul>\n<p><span>This data tells the AI what is happening now.<\/span><\/p>\n<p><span>For businesses modernizing operations through <\/span><a href=\"https:\/\/kanhasoft.com\/erp-software-development.html\"><span>custom ERP development services<\/span><\/a><span>, structured and well-governed operational data becomes an important AI foundation.<\/span><\/p>\n<h3><span>2. Business Knowledge<\/span><\/h3>\n<p><span>AI also needs information that rarely lives neatly inside a CRM table.<\/span><\/p>\n<p><span>Examples include:<\/span><\/p>\n<ul>\n<li><span>pricing policies<\/span><\/li>\n<li><span>SOPs<\/span><\/li>\n<li><span>product documentation<\/span><\/li>\n<li><span>sales playbooks<\/span><\/li>\n<li><span>supplier agreements<\/span><\/li>\n<li><span>implementation guides<\/span><\/li>\n<li><span>support procedures<\/span><\/li>\n<li><span>internal FAQs<\/span><\/li>\n<li><span>compliance documentation<\/span><\/li>\n<\/ul>\n<p><span>RAG and semantic search can retrieve relevant knowledge without forcing every document into every prompt.<\/span><\/p>\n<h3><span>3. Business Rules<\/span><\/h3>\n<p><span>Enterprise software contains rules that should not be left to an LLM to invent.<\/span><\/p>\n<p><span>For example:<\/span><\/p>\n<p><span>Discounts above 15% require sales director approval.<\/span><\/p>\n<p><span>Or:<\/span><\/p>\n<p><span>Purchase orders above $25,000 require finance approval.<\/span><\/p>\n<p><span>Context engineering should expose relevant rules when needed, while the CRM or ERP backend remains responsible for enforcing them.<\/span><\/p>\n<h3><span>4. Identity and Permissions<\/span><\/h3>\n<p><span>Two users asking exactly the same question may require different answers.<\/span><\/p>\n<p><span>A salesperson might see their opportunities.<\/span><\/p>\n<p><span>A regional manager might see the team\u2019s pipeline.<\/span><\/p>\n<p><span>A finance employee may see invoice values.<\/span><\/p>\n<p><span>An external supplier should see none of those records.<\/span><\/p>\n<p><span>Therefore, retrieval must respect role-based access control before information reaches the model.<\/span><\/p>\n<h3><span>5. Workflow State<\/span><\/h3>\n<p><span>Enterprise decisions rarely happen in isolation.<\/span><\/p>\n<p><span>An AI agent may need to know:<\/span><\/p>\n<ul>\n<li><span>what happened previously;<\/span><\/li>\n<li><span>what step is currently active;<\/span><\/li>\n<li><span>what another user approved;<\/span><\/li>\n<li><span>which actions already ran;<\/span><\/li>\n<li><span>whether an exception exists; and<\/span><\/li>\n<li><span>what should happen next.<\/span><\/li>\n<\/ul>\n<p><span>Without workflow state, AI can repeat work or recommend actions that are no longer relevant.<\/span><\/p>\n<h2><span>A Practical CRM Context Engineering Example<\/span><\/h2>\n<p><span>Suppose a salesperson asks:<\/span><\/p>\n<p><strong><span>\u201cPrepare me for tomorrow\u2019s Acme renewal meeting.\u201d<\/span><\/strong><\/p>\n<p><span>A basic chatbot may search notes and summarize them.<\/span><\/p>\n<p><span>A context-engineered assistant could assemble:<\/span><\/p>\n<ol>\n<li><span>customer profile;<\/span><\/li>\n<li><span>current contract;<\/span><\/li>\n<li><span>renewal date;<\/span><\/li>\n<li><span>product usage;<\/span><\/li>\n<li><span>recent support cases;<\/span><\/li>\n<li><span>outstanding invoices;<\/span><\/li>\n<li><span>latest emails;<\/span><\/li>\n<li><span>meeting history;<\/span><\/li>\n<li><span>relevant renewal policy;<\/span><\/li>\n<li><span>user\u2019s access rights.<\/span><\/li>\n<\/ol>\n<p><span>The model could then produce a concise briefing:<\/span><\/p>\n<ul>\n<li><span>relationship summary;<\/span><\/li>\n<li><span>unresolved concerns;<\/span><\/li>\n<li><span>renewal risks;<\/span><\/li>\n<li><span>possible expansion opportunities;<\/span><\/li>\n<li><span>questions worth asking;<\/span><\/li>\n<li><span>relevant internal actions.<\/span><\/li>\n<\/ul>\n<p><span>Notice what changed.<\/span><\/p>\n<p><span>The model did not necessarily become smarter.<\/span><\/p>\n<p><span>The <strong>information supplied to the model became smarter<\/strong>.<\/span><\/p>\n<h2><span>An ERP Example: Investigating a Production Delay<\/span><\/h2>\n<p><span>Imagine an operations manager asks:<\/span><\/p>\n<p><strong><span>\u201cWhy will order SO-4102 miss its promised shipping date?\u201d<\/span><\/strong><\/p>\n<p><span>Answering accurately may require data from several ERP modules.<\/span><\/p>\n<p><span>The context pipeline could retrieve:<\/span><\/p>\n<p><strong><span>Sales order \u2192 BOM \u2192 production order \u2192 component inventory \u2192 purchase orders \u2192 supplier ETA \u2192 machine schedule \u2192 logistics capacity<\/span><\/strong><\/p>\n<p><span>The AI may discover that one component is below requirement, the replacement purchase order arrives three days late, and production cannot begin until then.<\/span><\/p>\n<p><span>It can explain the dependency rather than simply saying, \u201cInventory is low.\u201d<\/span><\/p>\n<p><span>This is where enterprise AI becomes useful: it connects operational signals around a business question.<\/span><\/p>\n<p><span>Kanhasoft\u2019s case-study material includes an ERP implementation that unified production, inventory, procurement, sales, and logistics, including BOM-driven planning and real-time inventory tracking. That project is not presented as a context-engineering implementation, but it illustrates the structured operational foundation an AI context system would need to reason across manufacturing workflows.<\/span><\/p>\n<h2><span>The Architecture Behind Context Engineering for Enterprise AI<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-engineering-architecture-for-CRM-and-ERP-systems.jpeg\" alt=\"Enterprise AI context engineering architecture for CRM and ERP systems\" width=\"1500\" height=\"844\" class=\"alignnone wp-image-8281 size-full\" srcset=\"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-engineering-architecture-for-CRM-and-ERP-systems.jpeg 1500w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-engineering-architecture-for-CRM-and-ERP-systems-300x169.jpeg 300w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-engineering-architecture-for-CRM-and-ERP-systems-1024x576.jpeg 1024w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Enterprise-AI-context-engineering-architecture-for-CRM-and-ERP-systems-768x432.jpeg 768w\" sizes=\"auto, (max-width: 1500px) 100vw, 1500px\" \/><\/span><\/h2>\n<p><span>A simplified enterprise architecture may look like this:<\/span><\/p>\n<p><strong><span>User Request<\/span><\/strong><\/p>\n<p><span>\u2193<\/span><\/p>\n<p><strong><span>Identity + Permission Check<\/span><\/strong><\/p>\n<p><span>\u2193<\/span><\/p>\n<p><strong><span>Intent Detection<\/span><\/strong><\/p>\n<p><span>\u2193<\/span><\/p>\n<p><strong><span>Context Orchestrator<\/span><\/strong><\/p>\n<p><span>\u2193<\/span><\/p>\n<p><strong><span>CRM \/ ERP Records + APIs + Knowledge Base + Workflow State + Business Rules<\/span><\/strong><\/p>\n<p><span>\u2193<\/span><\/p>\n<p><strong><span>Context Filtering and Ranking<\/span><\/strong><\/p>\n<p><span>\u2193<\/span><\/p>\n<p><strong><span>LLM \/ AI Agent<\/span><\/strong><\/p>\n<p><span>\u2193<\/span><\/p>\n<p><strong><span>Policy and Authorization Check<\/span><\/strong><\/p>\n<p><span>\u2193<\/span><\/p>\n<p><strong><span>Answer, Recommendation, Draft, or Approved Action<\/span><\/strong><\/p>\n<p><span>The context orchestrator is especially important.<\/span><\/p>\n<p><span>It determines what information should enter the model\u2019s context window and what should remain outside it.<\/span><\/p>\n<p><span>Modern agent frameworks increasingly treat conversation state, tools, retrieval, guardrails, and orchestration as separate parts of the agent system rather than expecting one large prompt to manage everything. OpenAI\u2019s current agent resources similarly cover conversation state, tool use, orchestration, RAG, guardrails, and evaluation as distinct building blocks.<\/span><\/p>\n<h2><span>More Context Is Not Always Better<\/span><\/h2>\n<p><span>A common mistake is assuming that larger context windows solve context engineering.<\/span><\/p>\n<p><span>They help, but they do not remove the need for selection.<\/span><\/p>\n<p><span>Adding every email, document, CRM activity, ERP transaction, policy, and conversation into one enormous context can introduce:<\/span><\/p>\n<ul>\n<li><span>irrelevant information;<\/span><\/li>\n<li><span>conflicting records;<\/span><\/li>\n<li><span>outdated information;<\/span><\/li>\n<li><span>unnecessary token consumption;<\/span><\/li>\n<li><span>slower processing;<\/span><\/li>\n<li><span>permission risks; and<\/span><\/li>\n<li><span>weaker attention to important evidence.<\/span><\/li>\n<\/ul>\n<p><span>Anthropic describes context as a finite resource and recommends prioritizing high-signal information rather than simply maximizing token volume.<\/span><\/p>\n<p><span>A useful principle is:<\/span><\/p>\n<p><strong><span>Give the model enough context to make the decision, but not everything the company knows.<\/span><\/strong><\/p>\n<h2><span>Context Engineering and AI-Ready Data Solve Different Problems<\/span><\/h2>\n<p><span>Another common misunderstanding is treating context engineering as a data-cleaning exercise.<\/span><\/p>\n<p><span>Both matter, but they address different questions.<\/span><\/p>\n<p><strong><span>AI-ready data asks:<\/span><\/strong><span><br \/>\nCan we trust and interpret this information?<\/span><\/p>\n<p><strong><span>Context engineering asks:<\/span><\/strong><span><br \/>\nWhich trustworthy information should this AI receive for this task?<\/span><\/p>\n<p><span>Kanhasoft&#8217;s recent article on <\/span><a href=\"https:\/\/kanhasoft.com\/blog\/ai-agents-ai-ready-crm-erp-data\/\"><span>AI-ready CRM and ERP data<\/span><\/a><span> discusses the first problem: accuracy, freshness, relationships, governance, and traceability.<\/span><\/p>\n<p><span>Context engineering sits one step later in the pipeline.<\/span><\/p>\n<p><span>Clean data does not guarantee good context.<\/span><\/p>\n<p><span>You may have perfectly accurate customer data but still retrieve the wrong customer history for a sales question.<\/span><\/p>\n<h2><span>How Context Engineering Relates to MCP and AI Agents<\/span><\/h2>\n<p><span>The Model Context Protocol, APIs, and AI agents are also part of this architecture, but they serve different roles.<\/span><\/p>\n<p><span>MCP or APIs can expose capabilities such as:<\/span><\/p>\n<ul>\n<li><span>retrieve customer history;<\/span><\/li>\n<li><span>check available inventory;<\/span><\/li>\n<li><span>search company knowledge;<\/span><\/li>\n<li><span>create a task;<\/span><\/li>\n<li><span>prepare a quotation;<\/span><\/li>\n<li><span>inspect an invoice.<\/span><\/li>\n<\/ul>\n<p><span>Context engineering decides <strong>when those capabilities should be used and which outputs should be passed back to the model<\/strong>.<\/span><\/p>\n<p><span>For a deeper architectural discussion, see Kanhasoft&#8217;s guide to <\/span><a href=\"https:\/\/kanhasoft.com\/blog\/headless-crm-erp-ai-agents-mcp\/\"><span>headless CRM and ERP for AI agents and MCP<\/span><\/a><span>.<\/span><\/p>\n<p><span>The safest pattern remains straightforward:<\/span><\/p>\n<p><strong><span>AI reasons. Enterprise software governs.<\/span><\/strong><\/p>\n<p><span>An LLM can recommend a $30,000 purchase order. The ERP should still verify permissions, supplier rules, budgets, duplicate requests, and approval thresholds before anything is committed.<\/span><\/p>\n<h2><span>A Decision Framework for Enterprise Teams<\/span><\/h2>\n<p><span>Before building sophisticated context infrastructure, determine how much your use case actually requires.<\/span><\/p>\n<table width=\"100%\">\n<thead>\n<tr>\n<td width=\"158\"><span>Use Case<\/span><\/td>\n<td width=\"211\"><span>Context Complexity<\/span><\/td>\n<td width=\"158\"><span>Recommended Approach<\/span><\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td width=\"158\"><span>FAQ chatbot<\/span><\/td>\n<td width=\"211\"><span>Low<\/span><\/td>\n<td width=\"158\"><span>Prompt + knowledge-base retrieval<\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"158\"><span>CRM record summarization<\/span><\/td>\n<td width=\"211\"><span>Low\u2013Medium<\/span><\/td>\n<td width=\"158\"><span>Record context + permissions<\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"158\"><span>Sales copilot<\/span><\/td>\n<td width=\"211\"><span>Medium<\/span><\/td>\n<td width=\"158\"><span>CRM + email + activities + policies<\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"158\"><span>Executive business assistant<\/span><\/td>\n<td width=\"211\"><span>High<\/span><\/td>\n<td width=\"158\"><span>CRM + ERP + BI + knowledge retrieval<\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"158\"><span>Procurement agent<\/span><\/td>\n<td width=\"211\"><span>High<\/span><\/td>\n<td width=\"158\"><span>ERP + supplier data + rules + approvals<\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"158\"><span>Cross-system AI agent<\/span><\/td>\n<td width=\"211\"><span>Very High<\/span><\/td>\n<td width=\"158\"><span>Dynamic context orchestration + tools + governance<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span>Not every AI feature requires an elaborate platform.<\/span><\/p>\n<p><span>If users only need answers from product manuals, conventional RAG may be enough.<\/span><\/p>\n<p><span>Context engineering becomes more valuable when an AI system must combine <strong>multiple information sources, users, permissions, workflow states, or actions<\/strong>.<\/span><\/p>\n<h2><span>Five Context Engineering Mistakes to Avoid<\/span><\/h2>\n<h3><span>Sending Entire Records to the Model<\/span><\/h3>\n<p><span>Retrieve only the fields required for the task.<\/span><\/p>\n<h3><span>Treating Vector Search as the Whole Architecture<\/span><\/h3>\n<p><span>Semantic retrieval is excellent for unstructured knowledge. Transactional CRM and ERP questions often require SQL, APIs, business relationships, and deterministic filters as well.<\/span><\/p>\n<h3><span>Ignoring Data Freshness<\/span><\/h3>\n<p><span>Yesterday\u2019s inventory level may already be wrong.<\/span><\/p>\n<p><span>Context pipelines should understand which sources require near-real-time retrieval.<\/span><\/p>\n<h3><span>Letting the Model Enforce Permissions<\/span><\/h3>\n<p><span>Authorization belongs in application infrastructure.<\/span><\/p>\n<p><span>The model should receive only information the requesting user or agent is permitted to access.<\/span><\/p>\n<h3><span>Measuring Only Response Quality<\/span><\/h3>\n<p><span>Enterprise AI evaluation should also examine:<\/span><\/p>\n<ul>\n<li><span>retrieval accuracy;<\/span><\/li>\n<li><span>missing information;<\/span><\/li>\n<li><span>stale context;<\/span><\/li>\n<li><span>permission leakage;<\/span><\/li>\n<li><span>incorrect tool selection;<\/span><\/li>\n<li><span>action failures; and<\/span><\/li>\n<li><span>human override rates.<\/span><\/li>\n<\/ul>\n<p><span>Good answers are useful. Safe and repeatable workflows are better.<\/span><\/p>\n<h2><span>Practical Expert Note<\/span><\/h2>\n<p><span>One pattern we repeatedly see in enterprise software projects is that information already exists, but it lives in the wrong places.<\/span><\/p>\n<p><span>Customer activity sits in the CRM. Financial information sits in the ERP. Procedures live in documents. Conversations live in email. Exceptions live in people\u2019s heads.<\/span><\/p>\n<p><span>The hardest AI problem is often not generating another paragraph.<\/span><\/p>\n<p><span>It is assembling the right business state at the moment a decision is being made.<\/span><\/p>\n<p><span>That is why context engineering deserves architectural attention early rather than being added after an AI prototype starts producing inconsistent answers.<\/span><\/p>\n<h2><span>Building Context Engineering Into CRM and ERP<\/span><\/h2>\n<p><span>A practical implementation can start small.<\/span><\/p>\n<p><span>Choose one workflow, such as:<\/span><\/p>\n<p><strong><span>\u201cHelp sales managers identify stalled opportunities.\u201d<\/span><\/strong><\/p>\n<p><span>Then map:<\/span><\/p>\n<ol>\n<li><span>What information is required?<\/span><\/li>\n<li><span>Which systems own that information?<\/span><\/li>\n<li><span>How fresh must it be?<\/span><\/li>\n<li><span>Who may access it?<\/span><\/li>\n<li><span>Which business rules matter?<\/span><\/li>\n<li><span>What should the AI retrieve dynamically?<\/span><\/li>\n<li><span>What should remain deterministic?<\/span><\/li>\n<li><span>Which actions require human approval?<\/span><\/li>\n<li><span>How will incorrect context be detected?<\/span><\/li>\n<li><span>How will responses and actions be audited?<\/span><\/li>\n<\/ol>\n<p><span>After the first workflow works reliably, the same architecture can support additional agents and use cases.<\/span><\/p>\n<p><span>This is usually more manageable than attempting to build an enterprise-wide autonomous AI platform from day one.<\/span><\/p>\n<h2><span>Planning Context Engineering for Your CRM or ERP?<\/span><\/h2>\n<p><span>Kanhasoft works with businesses designing custom CRM, ERP, AI-enabled applications, APIs, workflow automation, RAG systems, and enterprise integrations.<\/span><\/p>\n<p><span>If you are considering AI agents, a useful first step is to map the workflow before selecting the model. That means identifying data sources, permissions, business rules, integrations, retrieval requirements, approval boundaries, and the context each AI interaction actually requires.<\/span><\/p>\n<p><a href=\"https:\/\/kanhasoft.com\/\"><span>Kanhasoft<\/span><\/a><span> can help review those areas and turn them into a practical AI architecture roadmap without assuming that every workflow needs maximum automation.<\/span><\/p>\n<h2><span>Final Words<\/span><\/h2>\n<p><span>Enterprise AI is moving beyond chatbots toward copilots and agents that can work across business systems.<\/span><\/p>\n<p><span>That shift makes context engineering for enterprise AI increasingly important.<\/span><\/p>\n<p><span>The model needs more than a clever prompt. It needs the right customer record, transaction, policy, workflow state, permission, document, and tool at the right moment.<\/span><\/p>\n<p><span>The goal is not to give AI access to everything.<\/span><\/p>\n<p><span>The goal is to give AI the minimum trustworthy context required to make the next useful decision.<\/span><\/p>\n<p><span>For CRM and ERP systems, that may prove to be the difference between an impressive AI demo and an AI capability employees can actually rely on.<a href=\"https:\/\/kanhasoft.com\/schedule-a-meeting.html\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Build-Context-Aware-Enterprise-AI-with-KanhaSoft.png\" alt=\"Build Context-Aware Enterprise AI with KanhaSoft\" width=\"1000\" height=\"250\" class=\"alignnone wp-image-8277 size-full\" srcset=\"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Build-Context-Aware-Enterprise-AI-with-KanhaSoft.png 1000w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Build-Context-Aware-Enterprise-AI-with-KanhaSoft-300x75.png 300w, https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Build-Context-Aware-Enterprise-AI-with-KanhaSoft-768x192.png 768w\" sizes=\"auto, (max-width: 1000px) 100vw, 1000px\" \/><\/a><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A company can connect a powerful large language model to its CRM and still get a mediocre AI assistant. The problem may not be the model at all. For businesses investing in custom CRM development, context engineering for enterprise AI is becoming just as important as model selection, prompting, and <a href=\"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/\" class=\"more-link\">Read More<\/a><\/p>\n","protected":false},"author":6,"featured_media":8274,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,11],"tags":[],"class_list":["post-8273","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-crm-development","category-erp-development"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Context Engineering for Enterprise AI in CRM &amp; ERP<\/title>\n<meta name=\"description\" content=\"Learn how context engineering helps enterprise AI use the right CRM and ERP data, business rules, permissions, memory, and tools at the right time.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Context Engineering for Enterprise AI in CRM &amp; ERP\" \/>\n<meta property=\"og:description\" content=\"Learn how context engineering helps enterprise AI use the right CRM and ERP data, business rules, permissions, memory, and tools at the right time.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/kanhasoft\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-08T15:12:15+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1400\" \/>\n\t<meta property=\"og:image:height\" content=\"425\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Ketan Modi\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@kanhasoft\" \/>\n<meta name=\"twitter:site\" content=\"@kanhasoft\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ketan Modi\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":[\"Article\",\"BlogPosting\"],\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/\"},\"author\":{\"name\":\"Ketan Modi\",\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/#\\\/schema\\\/person\\\/cb4b493c5dc440d54e6bfd7cbf6e4133\"},\"headline\":\"Context Engineering for Enterprise AI: The Missing Piece in CRM &#038; ERP\",\"datePublished\":\"2026-10-08T15:12:15+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/\"},\"wordCount\":2213,\"publisher\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png\",\"articleSection\":[\"CRM Development\",\"ERP Development\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/\",\"url\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/\",\"name\":\"Context Engineering for Enterprise AI in CRM & ERP\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png\",\"datePublished\":\"2026-10-08T15:12:15+00:00\",\"description\":\"Learn how context engineering helps enterprise AI use the right CRM and ERP data, business rules, permissions, memory, and tools at the right time.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/#primaryimage\",\"url\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png\",\"contentUrl\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png\",\"width\":1400,\"height\":425,\"caption\":\"Context Engineering for Enterprise AI The Missing Piece in CRM & ERP\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/context-engineering-enterprise-ai-crm-erp\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Context Engineering for Enterprise AI: The Missing Piece in CRM &#038; ERP\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/\",\"name\":\"\",\"description\":\"Web and Mobile Application Development Agency\",\"publisher\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/#organization\",\"name\":\"Kanhasoft\",\"url\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/cropped-cropped-Kahnasoft-Web-and-mobile-app-development-1.png\",\"contentUrl\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/cropped-cropped-Kahnasoft-Web-and-mobile-app-development-1.png\",\"width\":239,\"height\":56,\"caption\":\"Kanhasoft\"},\"image\":{\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/kanhasoft\",\"https:\\\/\\\/x.com\\\/kanhasoft\",\"https:\\\/\\\/www.instagram.com\\\/kanhasoft\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/kanhasoft\\\/\",\"https:\\\/\\\/in.pinterest.com\\\/kanhasoft\\\/_created\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/#\\\/schema\\\/person\\\/cb4b493c5dc440d54e6bfd7cbf6e4133\",\"name\":\"Ketan Modi\",\"pronouns\":\"He\\\/Him\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/cropped-Ketan-Modi-96x96.png\",\"url\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/cropped-Ketan-Modi-96x96.png\",\"contentUrl\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/cropped-Ketan-Modi-96x96.png\",\"caption\":\"Ketan Modi\"},\"description\":\"Ketan Modi is a highly experienced and professional Custom ERP and CRM Developer with expertise in scalable business management solutions. He helps organizations streamline operations through ERP, CRM, workflow automation, and system integration. Through his articles, he shares practical insights on custom software development, business automation, and digital transformation.\",\"sameAs\":[\"https:\\\/\\\/kanhasoft.com\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/ketan-modi-b5a54232\\\/\"],\"url\":\"https:\\\/\\\/kanhasoft.com\\\/blog\\\/author\\\/ketanmodi\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Context Engineering for Enterprise AI in CRM & ERP","description":"Learn how context engineering helps enterprise AI use the right CRM and ERP data, business rules, permissions, memory, and tools at the right time.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/","og_locale":"en_US","og_type":"article","og_title":"Context Engineering for Enterprise AI in CRM & ERP","og_description":"Learn how context engineering helps enterprise AI use the right CRM and ERP data, business rules, permissions, memory, and tools at the right time.","og_url":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/","article_publisher":"https:\/\/www.facebook.com\/kanhasoft","article_published_time":"2026-10-08T15:12:15+00:00","og_image":[{"width":1400,"height":425,"url":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png","type":"image\/png"}],"author":"Ketan Modi","twitter_card":"summary_large_image","twitter_creator":"@kanhasoft","twitter_site":"@kanhasoft","twitter_misc":{"Written by":"Ketan Modi","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Article","BlogPosting"],"@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/#article","isPartOf":{"@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/"},"author":{"name":"Ketan Modi","@id":"https:\/\/kanhasoft.com\/blog\/#\/schema\/person\/cb4b493c5dc440d54e6bfd7cbf6e4133"},"headline":"Context Engineering for Enterprise AI: The Missing Piece in CRM &#038; ERP","datePublished":"2026-10-08T15:12:15+00:00","mainEntityOfPage":{"@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/"},"wordCount":2213,"publisher":{"@id":"https:\/\/kanhasoft.com\/blog\/#organization"},"image":{"@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/#primaryimage"},"thumbnailUrl":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png","articleSection":["CRM Development","ERP Development"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/","url":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/","name":"Context Engineering for Enterprise AI in CRM & ERP","isPartOf":{"@id":"https:\/\/kanhasoft.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/#primaryimage"},"image":{"@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/#primaryimage"},"thumbnailUrl":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png","datePublished":"2026-10-08T15:12:15+00:00","description":"Learn how context engineering helps enterprise AI use the right CRM and ERP data, business rules, permissions, memory, and tools at the right time.","breadcrumb":{"@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/#primaryimage","url":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png","contentUrl":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/10\/Context-Engineering-for-Enterprise-AI-The-Missing-Piece-in-CRM-ERP.png","width":1400,"height":425,"caption":"Context Engineering for Enterprise AI The Missing Piece in CRM & ERP"},{"@type":"BreadcrumbList","@id":"https:\/\/kanhasoft.com\/blog\/context-engineering-enterprise-ai-crm-erp\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/kanhasoft.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Context Engineering for Enterprise AI: The Missing Piece in CRM &#038; ERP"}]},{"@type":"WebSite","@id":"https:\/\/kanhasoft.com\/blog\/#website","url":"https:\/\/kanhasoft.com\/blog\/","name":"","description":"Web and Mobile Application Development Agency","publisher":{"@id":"https:\/\/kanhasoft.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kanhasoft.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/kanhasoft.com\/blog\/#organization","name":"Kanhasoft","url":"https:\/\/kanhasoft.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kanhasoft.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-cropped-Kahnasoft-Web-and-mobile-app-development-1.png","contentUrl":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-cropped-Kahnasoft-Web-and-mobile-app-development-1.png","width":239,"height":56,"caption":"Kanhasoft"},"image":{"@id":"https:\/\/kanhasoft.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/kanhasoft","https:\/\/x.com\/kanhasoft","https:\/\/www.instagram.com\/kanhasoft\/","https:\/\/www.linkedin.com\/company\/kanhasoft\/","https:\/\/in.pinterest.com\/kanhasoft\/_created\/"]},{"@type":"Person","@id":"https:\/\/kanhasoft.com\/blog\/#\/schema\/person\/cb4b493c5dc440d54e6bfd7cbf6e4133","name":"Ketan Modi","pronouns":"He\/Him","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-Ketan-Modi-96x96.png","url":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-Ketan-Modi-96x96.png","contentUrl":"https:\/\/kanhasoft.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-Ketan-Modi-96x96.png","caption":"Ketan Modi"},"description":"Ketan Modi is a highly experienced and professional Custom ERP and CRM Developer with expertise in scalable business management solutions. He helps organizations streamline operations through ERP, CRM, workflow automation, and system integration. Through his articles, he shares practical insights on custom software development, business automation, and digital transformation.","sameAs":["https:\/\/kanhasoft.com\/","https:\/\/www.linkedin.com\/in\/ketan-modi-b5a54232\/"],"url":"https:\/\/kanhasoft.com\/blog\/author\/ketanmodi\/"}]}},"_links":{"self":[{"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/posts\/8273","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/comments?post=8273"}],"version-history":[{"count":3,"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/posts\/8273\/revisions"}],"predecessor-version":[{"id":8282,"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/posts\/8273\/revisions\/8282"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/media\/8274"}],"wp:attachment":[{"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/media?parent=8273"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/categories?post=8273"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kanhasoft.com\/blog\/wp-json\/wp\/v2\/tags?post=8273"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}