A build-to-order ERPNext app for running B2B account-based campaigns: define target-account lists, sequence outreach calls, auto-distribute them to agents, and score account engagement across every contact. ECOSIRE designs, builds, installs and supports it after you confirm scope. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $349.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext app for running B2B account-based campaigns: define target-account lists, sequence outreach calls, auto-distribute them to agents, and score account engagement across every contact. ECOSIRE designs, builds, installs and supports it after you confirm scope.
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
B2B teams selling into named accounts quickly outgrow what ERPNext gives them natively. Core ERPNext models the world as Lead, Contact, Customer and Opportunity, but ABM is account-first: a single buying committee spread across five or six contacts, worked by a coordinated sequence of touches over weeks. ERPNext has no concept of a target-account list, no cadence engine to schedule the next call at the right interval, no fair-share distribution of accounts across agents, and no rolled-up engagement score that tells a rep which accounts are actually warming up. Reps end up tracking all of this in spreadsheets alongside the CRM, and management loses the single source of truth ERPNext was supposed to be.
`Target Account List` DocType for building and segmenting named-account campaigns, with filters over `Customer`, industry, territory and custom fields
`ABM Account` record that maps a full buying committee — multiple `Contact` and `Customer` links, roles and decision-maker flags — into one engagement surface
`Call Sequence` and `Sequence Step` DocTypes defining ordered touches with configurable wait intervals between steps
Automated `Call Task` generation driven by `scheduler_events` cron and `hooks.py` doc events, so the next touch is scheduled without manual queue-building
Configurable auto-distribution of call tasks to agents — round-robin or capacity/territory-weighted — instead of hand-assigning accounts
Account engagement scoring recomputed by server scripts on every logged call outcome, disposition and reply
The ABM Suite closes that gap as a proper Frappe application installed into your existing ERPNext site. We ship new DocTypes — Target Account List, ABM Account (linking one or more Contact and Customer records into a single buying committee), Call Sequence, Sequence Step, and Call Task — so campaigns, cadences and touches are first-class records with their own list views, reports and permissions. A Call Sequence defines ordered steps with wait intervals; when an account is enrolled, hooks.py doc events and a scheduler_events cron generate the next Call Task on schedule and assign it to an agent using a configurable round-robin or capacity-weighted distributor, so nobody hand-picks who calls whom. Every logged call outcome flows through server scripts that recompute an account engagement score, and the account's stage advances or exits the sequence based on rules you define.
Everything is built on native ERPNext primitives so it stays upgradeable and secure. Agent-facing behaviour (click-to-log a call, advance a step, snooze a task) is delivered through client scripts on the standard Desk forms; integrations and dashboards use the Frappe REST API and @frappe.whitelist() methods rather than direct database access; and access is governed by role profiles and DocType permissions so managers see the whole pipeline while agents see only their assigned accounts. Dialer, email or telephony hooks (e.g. a webhook that stamps call duration and disposition back onto a Call Task) are wired in as whitelisted endpoints when your stack requires them.
This is a build-to-order product, not an off-the-shelf marketplace download — there is no instant install button. After a short scoping call we confirm your account model, sequence rules, distribution logic and reporting needs, then build your version against ERPNext v15 or v16. We install it on a staging site for UAT, run through your real campaigns, and only cut over to production once you sign off, with a rollback plan in hand. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full source code and git repository so the app is yours to run and extend.
Runs account-based outreach against named-account lists and needs cadences that schedule the next call automatically, fair distribution across the team, and a clear view of which accounts are warming up — all inside ERPNext rather than a separate spreadsheet.
Wants the buying committee, touch history and engagement score to live in ERPNext as the single source of truth, with per-agent throughput and account-coverage reporting instead of siloed dialer tools.
Responsible for keeping the site upgradeable and secure; values a native Frappe app built on standard DocTypes, permissions and whitelisted methods, with source code and fixtures they can migrate across v15/v16.
Designs the sequences and account lists, defines exit and progression rules, and needs dashboards showing sequence throughput and coverage to tune campaigns over time.
Compre a licença em ecosire.com e baixe o ZIP do aplicativo Account-Based Marketing (ABM) Suite no painel da sua conta.
Extraia o ZIP na pasta de aplicativos do seu banco ou execute `bench get-app` com o caminho para o aplicativo extraído.
Execute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench Migra` para instalar Account-Based Marketing (ABM) Suite e aplicar seu esquema.
Abra as configurações de licença ECOSIRE em seu site e ative sua chave de licença. Requer os aplicativos gratuitos ecosire_connect e ecosire_license_client.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Account-based data model | `ABM Account` maps a full buying committee across many contacts | Whatever you design and maintain in-house | Usually contact/lead-centric, not committee-aware | |
| Call cadence / sequencing | `Call Sequence` with timed steps and auto-generated tasks | Build a scheduler engine from scratch | Basic follow-up reminders, limited multi-step cadence | |
| Agent distribution | Round-robin or capacity/territory-weighted auto-assignment | Hand-rolled assignment logic | Simple round-robin if any | |
| Engagement scoring | Server-script scoring recomputed on every call outcome | You define and maintain the scoring model | Generic lead score, not account-rolled | |
| ERPNext-native & upgradeable | Proper Frappe app: DocTypes, hooks, fixtures, permissions | Depends on build quality and discipline | Varies; may patch core or lag versions | |
| Fit to your workflow | Built to your rules after a scoping call | Fully bespoke but you own all the effort | Fixed feature set, configure around it | |
| Delivery model | Build-to-order, 2–4 weeks, UAT + rollback + repo handover | Open-ended internal project timeline | Instant install, no tailoring | |
| Support & ownership | Post-go-live support window + full source & git repo | Self-supported by your team | Vendor support, closed roadmap |
No. The ABM Suite is build-to-order. After we confirm your account model, sequence rules and distribution logic, ECOSIRE builds your version, installs it, and supports it. There is no instant-install button — you get a version tailored to how your team actually runs account-based outreach.
Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on how much sequence logic, distribution weighting and telephony integration you need. We agree the scope and schedule in writing before any build work starts.
We build and test against ERPNext / Frappe v15 and v16 using standard app structure, fixtures and migrations. Tell us your current version on the scoping call and we target that; the app is delivered as a proper Frappe app so it migrates cleanly on future upgrades.
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full git repository and source code, your own team can also extend the app. Longer-term maintenance or new features can be arranged as a follow-on engagement.
Yes — it's built on native primitives (custom DocTypes, `hooks.py` doc events, `scheduler_events`, whitelisted methods, client scripts and role permissions) rather than core patches or direct database hacks, so a `bench update` doesn't break it. We validate against your target version and hand over migrations and fixtures.
Yes. We expose whitelisted (`@frappe.whitelist()`) REST endpoints that your dialer or telephony webhook can call to stamp call duration and disposition back onto the `Call Task`, and click-to-dial can be wired into the Desk form via client scripts. We confirm the specific provider and integration surface during scoping.
The distributor is configurable — round-robin by default, or capacity/territory-weighted so busier or specialized agents get a proportionate share. Assignment runs on `scheduler_events` and doc events as tasks are generated, and agents see only their assigned accounts via role-profile permissions.
A build-to-order ERPNext app for running B2B account-based campaigns: define target-account lists, sequence outreach calls, auto-distribute them to agents, and score account engagement across every contact. ECOSIRE designs, builds, installs and supports it after you confirm scope.