An LLM-powered assistant embedded in ERPNext that drafts email and quotation replies, summarizes records and threads, scores leads, and answers plain-English questions over your ERP data. Built, installed, and supported by ECOSIRE as a build-to-order Frappe app. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $499.00 USD; request a quote for a scoped proposal.

An LLM-powered assistant embedded in ERPNext that drafts email and quotation replies, summarizes records and threads, scores leads, and answers plain-English questions over your ERP data. Built, installed, and supported by ECOSIRE as a build-to-order Frappe app.
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
Sales and support teams live inside ERPNext, but ERPNext native has no generative layer. Reps retype the same quotation follow-ups, read through a long Lead or Issue timeline before every reply, and answer questions like "which open opportunities in the GCC closed above 40% margin last quarter" by hand-building a report. ERPNext ships list views, report builder, and email templates, but none of that drafts prose, summarizes a 30-comment thread, or turns a business question into a filtered query. That gap is where hours quietly disappear.
Frappe app `erpnext_ai_assistant` with its own module, DocTypes, and `hooks.py` — no core patches, installable/removable via `bench install-app`
"Draft with AI" client-script button on Quotation, Lead, Opportunity, and Issue that returns an editable draft into the Email dialog (never auto-sends)
Natural-language query panel that translates questions into permission-safe `frappe.get_list` / query-report calls — the model reads through the user's own role and User Permissions
Record and thread summarization over the Communication and Comment timeline, condensing long histories into a briefing
Lead scoring and next-best-action computed on a Scheduler event and written to sortable/filterable custom fields
Knowledge Base retrieval layer that indexes chosen DocTypes and File attachments so answers are grounded in your own data
ECOSIRE builds erpnext_ai_assistant, a proper Frappe app (its own module, DocTypes, and hooks.py) that wires an LLM directly into your ERPNext workflow. A "Draft with AI" button on Quotation, Lead, Opportunity, and Issue (via client scripts) calls a @frappe.whitelist() server method that assembles context from the linked records and returns an editable draft into the Email/Communication dialog — nothing is sent automatically, the human always approves. A conversational side panel answers natural-language questions by translating them into permission-safe frappe.get_list/query-report calls, so the model reads data through the same role permissions and User Permissions the logged-in user already has — it can never surface rows a user isn't allowed to see. Record and thread summarization runs over the Communication and Comment timeline; lead scoring and next-best-action are computed on a Scheduler event and written to custom fields you can sort and filter on. A configurable AI Prompt DocType lets you tune tone, guardrails, and per-DocType behavior without a redeploy, and an AI Interaction Log DocType captures every prompt, response, token count, and cost for auditability.
Technically it is a clean, upgrade-safe app: LLM calls run through Frappe hooks.py doc events and background jobs so the UI never blocks; API keys live in Site Config (never in code or the database in plaintext); a Knowledge Base retrieval layer indexes your chosen DocTypes and files so answers are grounded in your own content rather than the model's guesses. It targets Frappe/ERPNext v15 and v16, respects the framework's permission model end to end, and adds zero core patches — it is installable and removable with bench install-app / bench uninstall-app.
Because this is build-to-order, we start from your actual workflow. After a short scoping call we confirm which DocTypes, actions, and questions matter to your team, pick and configure the LLM provider you prefer, then build, test on a staging bench, and hand over. Typical delivery is 2-4 weeks from confirmed scope. You receive the installable source for your version, install and configuration on your environment, documentation, a training session, and a post-go-live support window — plus the git repository so your team fully owns what we build.
Runs a pipeline in ERPNext and wants reps to spend time selling, not retyping follow-ups. Needs AI-drafted quotation and opportunity replies, lead scoring, and next-best-action surfaced right on the record — with the human still approving every send.
Owns the Issue/Helpdesk queue and needs agents to resolve faster. Wants instant thread summaries of long tickets, suggested replies grounded in the knowledge base, and consistent tone across the team without leaving ERPNext.
Constantly asked for ad-hoc numbers. Wants to ask ERPNext data questions in plain English and get permission-safe answers instead of hand-building query reports, while keeping a full audit log of what the AI accessed.
Responsible for a clean, upgrade-safe ERPNext. Needs an app with no core patches, keys stored securely in Site Config, role-and-permission-aware AI access, and a git repo the team can maintain across v15/v16 upgrades.
Buy the license on ecosire.com and download the AI Sales & Support Assistant app ZIP from your account dashboard.
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install AI Sales & Support Assistant and apply its schema.
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Fit to your ERPNext workflow | Built to your exact DocTypes, actions, and questions | Fully bespoke but you specify and manage everything | Generic assumptions, limited to what the vendor shipped | |
| Natural-language data queries | Permission-safe queries via `frappe.get_list`/reports | Possible, but you design the safety layer yourself | Often absent or a bolt-on chatbot | |
| Permission & audit safety | Runs under user roles; every call logged | Depends on your team's discipline | Varies; often broad service-account access | |
| Upgrade safety (v15/v16) | Separate app, no core patches, clean uninstall | Risk of core patches if built in a hurry | Depends on vendor's version support | |
| LLM provider & key handling | Pluggable provider, keys in Site Config | You build and secure the integration | Usually locked to one provider/cloud | |
| Time to value | 2-4 weeks from confirmed scope | Months of in-house build and QA | Fast install but generic behavior | |
| Ownership & source code | Full source + git repo handover | You own it — and all the maintenance | Closed source, subscription lock-in | |
| Support & maintenance | Post-go-live window + optional ongoing | Self-supported by your team | Vendor SLA, often tiered add-on |
No. This is a build-to-order app that ECOSIRE builds, installs, and supports for your specific ERPNext workflow. There is no instant download — we scope your DocTypes, actions, and questions first, then build the `erpnext_ai_assistant` app for your v15 or v16 environment.
Typical delivery is 2-4 weeks from confirmed scope. After a short scoping call we agree on the exact DocTypes, AI actions, and provider, then build, test on a staging bench, and hand over. Timeline depends on how many workflows and integrations you want included.
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments, and you receive the git repository so your team can maintain and extend the app. We also offer ongoing support or version-upgrade work (for example when you move from v15 to v16) as a separate arrangement.
No. All data access goes through Frappe's permission engine — the assistant reads via `frappe.get_list` and query reports under the logged-in user's own role permissions and User Permissions. It cannot surface rows the user couldn't already open, and every AI interaction is written to an audit log.
The provider is pluggable — OpenAI, Anthropic, Azure OpenAI, or a self-hosted model — chosen during scoping to fit your data-residency and budget needs. API keys are stored in Site Config, never hardcoded or kept in plaintext database fields, and all token usage and cost are logged.
No. It ships as a separate Frappe app with its own module, DocTypes, custom fields, `hooks.py` doc events, and client/server scripts. There are no core monkey-patches, so it installs and removes cleanly with `bench install-app` / `bench uninstall-app` and stays upgrade-safe across ERPNext versions.
By default, no. AI-drafted replies land in the standard Email/Communication dialog for a human to review, edit, and send. Any automated actions (such as scheduled lead scoring writing to custom fields) are explicit, configurable, and logged — you decide what runs autonomously versus what stays human-approved.
An LLM-powered assistant embedded in ERPNext that drafts email and quotation replies, summarizes records and threads, scores leads, and answers plain-English questions over your ERP data. Built, installed, and supported by ECOSIRE as a build-to-order Frappe app.