Workflows

CRM Sales Development

Sales teams need targeted prospects and clean Acumatica CRM records. Generic lead imports create duplicates, weak attribution, unowned follow-up, and uncontrolled outreach.

The CRM Sales Development workflow is for reviewed prospecting where Acumatica remains the CRM system of record. External territory and enrichment data can help identify candidates, but the workflow should check Acumatica before creating anything.

Business Problem

Sales teams need targeted prospects and clean Acumatica CRM records. Generic lead imports create duplicates, weak attribution, unowned follow-up, and uncontrolled outreach.

This workflow shows how external territory and enrichment data can support reviewed CRM work without turning Acumatica into an uncontrolled prospect import queue.

Example Starting Prompt

We want to grow our wholesale business around our Dallas warehouse.
Use Google Maps to identify distributors, manufacturers, importers, or inventory-heavy businesses within 45 minutes of the warehouse.
Use Apollo to enrich likely buyer contacts in operations, purchasing, supply chain, finance, or sales leadership.
Then check Acumatica for existing leads, contacts, business accounts, customers, and opportunities.
Do not create anything yet.

Complete Workflow

The workflow starts with a narrow sales motion: a warehouse radius, branch launch, delivery route, target vertical, customer cluster, or named territory. The user defines the segment before any enrichment happens.

Google Maps MCP can identify companies with useful location context: nearby warehouses, distributors, manufacturers, importers, inventory-heavy businesses, route-adjacent businesses, or other relevant operating signals. The workflow should keep this list small enough to review.

Apollo MCP can enrich reviewed companies with likely buyer contacts in operations, purchasing, supply chain, finance, sales leadership, or other approved roles. Enrichment should support review, not create an automatic import list.

The workflow ranks candidates by fit, location signal, buyer confidence, existing relationship risk, and a concrete outreach reason. A good candidate summary explains why the company is relevant and which buyer role appears useful.

Before anything is created, Acumatica MCP Tools checks for existing leads, contacts, business accounts, customers, opportunities, owners, campaign attribution, and relevant account history where exposed. The output should classify each candidate as create, skip, or review.

The user approves a small candidate set. Only approved leads or CRM records are created, and only if the specific CRM write path is allowlisted and the current Acumatica user has permission.

Campaign attribution, source fields, tasks, email activities, opportunities, and contact updates are separate decisions. The workflow may draft follow-up tasks or email activity text, but outbound communication stays draft-only unless a separate send workflow is reviewed and approved.

The final output should show reviewed candidates, duplicate-check results, approved records created or prepared, campaign/source attribution status, task or email activity drafts, and denied bulk import or automatic send attempts.

Acumatica Records and Tools

  • Google Maps MCP for territory and location context.
  • Apollo MCP for company and buyer-contact enrichment.
  • Acumatica MCP Tools for CRM dedupe and reviewed CRM record creation.
  • Contract REST API reads for existing CRM context.
  • Allowlisted CRM writes for approved leads, tasks, campaign attribution, or activity drafts.
  • AI client for ranking, recommendations, and human review.

The common Acumatica records are Lead, Contact, Business Account, Customer, Opportunity, Task, Email or Activity, campaign or source campaign fields where exposed, and account owner or territory views where exposed.

Human Approval Point

The user approves territory or segment selection, enrichment use, candidate selection, duplicate review, lead creation, contact updates, campaign attribution, task creation, email activity drafts, opportunity creation, lead conversion, and any customer or prospect communication.

Guardrails to Show

No bulk import and no automatic outbound email. Duplicate checks happen before creation, and broad import or send requests return a denied or approval-required result.

Treat lead creation, contact updates, campaign records, campaign attribution, tasks, email activities, opportunity conversion, and outbound sends as separate allowlist decisions. Avoid exposing private personal data in demos or playbook examples.

Good First Setup

Start with one narrow territory and a small candidate list. Strong first versions include a territory campaign with five reviewed candidates, branch launch candidate review, route-based prospecting with dedupe, contact refresh review for existing accounts, reviewed lead creation after duplicate checks, or task and email activity draft creation for approved leads.

Success means the workflow produces a focused territory list, enriches likely buyers without exposing private data, ranks candidates with clear reasons, checks Acumatica for duplicate CRM records, returns create, skip, or review recommendations, creates only approved leads if allowlisted, and keeps outreach draft-only.

Guided Deployment

Bring one sales territory, branch, route, or account segment for guided deployment. We will map external enrichment, Acumatica CRM duplicate checks, approvals, campaign records, and allowlists.

Request Free Guided Deployment