Find the leads worth your next conversation.
Lead scoring CRM software for explainable prioritization, engagement tracking, territory routing, qualification approvals and reliable sales handoffs.
Illustrative records derived from the system specification.
Built for the way your team works
Marketing operations, sales development and account executives coordinating lead qualification.
- Defined tables
- 25
- Operational views
- 14
- Defined roles
- 6
- Reports
- 8
Defined in the planned system specification.
What’s inside.
Lead scoring CRM software for explainable prioritization, engagement tracking, territory routing, qualification approvals and reliable sales handoffs.
Lead capture
Bring incoming prospects into a consistent qualification queue.
Scoring and AI
Explain why a lead deserves attention before the team acts.
Routing and alerts
Put the next lead with someone who can act on it.
Outreach and preferences
Coordinate useful follow-up while respecting contact preferences.
Qualification and handoff
Give account executives the context to accept a qualified lead.
Funnel analysis
Learn which sources and signals lead to accepted opportunities.
Bring incoming prospects into a consistent qualification queue
- LDS-64613: LA-97917, 17 Sep · 13:00 to 17 Sep · 15:00, Planned
- LDS-71192: LA-88084, 17 Sep · 14:30 to 17 Sep · 15:00, InProgress
- LDS-75759: LA-74126, 26 Sep · 10:00 to 26 Sep · 10:30, Planned
- LDS-15121: LA-54725, 07 Sep · 11:00 to 07 Sep · 13:00, InProgress
- LDS-66233: LA-41439, 24 Sep · 12:30 to 24 Sep · 13:30, Planned
- LDS-98920: LA-84814, 17 Sep · 15:00 to 17 Sep · 17:00, InProgress
Approval conditions
Visible to: Account Executive. Visibility does not establish approval authority.
- LDS-74186 Submitted lds-938 50 2 d
- LDS-12984 Submitted lds-943 55 7 d
- LDS-68986 Submitted lds-256 85 11 d
- LDS-59557 Submitted lds-477 20 14 d
- LDS-28060 Submitted lds-654 80 8 d
- Company
- CMP-233
- Owner
- DL
- AssignedAE
- GB
- Score
- 50
- QualificationReason
- Submitted lds-938
Approval conditions.
Approval conditions
Sales Manager: Approve independent DuplicateClusters resolution
- DC-39484 BY 16 in 3 d
- DC-52769 YX 31 12 d
- DC-33775 RZ 9 9 d
- DC-11589 JD 17 6 d
- DC-41984 WX 31 in 2 d
- ClusterCode
- CC-266
- MatchKey
- EmailExact
- LeadCount
- 16
- PreparedBy
- BY
- DetectedAt
- 20 Sep
- Status
- Submitted
Approval waits for the sales manager.
- SR-15445 Rule 441 350 8 d
- SR-56823 Rule 221 100 10 d
- SR-13488 Rule 819 840 10 d
- SR-86578 Rule 593 70 in 12 d
- SR-59634 Rule 775 310 in 10 d
- RuleCode
- RC-526
- Name
- Rule 441
- Version
- 350
- Category
- Firmographic
- Points
- 670
- PreparedBy
- AR
- SM-95909 Model 308 in 5 d
- SM-78803 Model 456 in 6 d
- SM-75220 Model 321 today
- SM-34767 Model 884 in 7 d
- SM-81195 Model 910 in 11 d
- Name
- Model 308
- Version
- Rev A
- ScoreUse
- ExplanationOnly
- PreparedBy
- SS
- EffectiveFrom
- 22 Sep
- RR-13788 TRR-6215 700 in 3 d
- RR-24040 TRR-5586 400 in 2 d
- RR-32083 TRR-1955 340 in 6 d
- RR-75279 TRR-5319 680 9 d
- RR-44824 TRR-6054 590 3 d
- RuleCode
- RC-859
- Name
- Rule 735
- Territory
- TRR-6215
- Priority
- 700
- PreparedBy
- WB
- EffectiveFrom
- 20 Sep
| Record Number | Lead | Assigned To | Assigned From | Reason |
|---|---|---|---|---|
| LA-79194 | LDS-64199 | KT | LL | InitialRouting |
| LA-34811 | LDS-23936 | HU | TA | MQLHandoff |
| LA-72733 | LDS-92462 | EV | NM | ManualReassign |
| LA-67636 | LDS-45285 | EN | GF | StaleRecycle |
| LA-83471 | LDS-17351 | UG | YW | OutOfOffice |
| LA-60711 | LDS-42408 | VK | TH | TerritoryRealignment |
| Consent Number | Lead | Channel | Decision | Purpose |
|---|---|---|---|---|
| CE-33444 | LDS-30761 | Permitted | PRP-204 | |
| CE-55602 | LDS-92360 | Phone | Restricted | PRP-797 |
| CE-83494 | LDS-70114 | Withdrawn | PRP-504 | |
| CE-31757 | LDS-26725 | Phone | Permitted | PRP-322 |
| CE-13238 | LDS-37680 | Restricted | PRP-359 | |
| CE-35264 | LDS-85745 | Phone | Withdrawn | PRP-889 |
| Alert Number | Lead | Alert Type | Due Date | Status |
|---|---|---|---|---|
| PA-87398 | LDS-84834 | ThresholdCrossed | 28 Sep | Open |
| PA-50271 | LDS-76521 | FollowUpDue | 13 Sep | Open |
| PA-10671 | LDS-61306 | ConversionFailure | 27 Sep | Open |
| PA-40311 | LDS-10397 | ThresholdCrossed | 19 Sep | Open |
| PA-99748 | LDS-54583 | FollowUpDue | 29 Sep | Open |
| PA-86387 | LDS-77482 | ConversionFailure | 19 Sep | Open |
| List Code | Name | Purpose | Member Count | Created At |
|---|---|---|---|---|
| LC-632 | List 766 | OutboundCadence | 30 | 13 Sep |
| LC-713 | List 964 | EventInvite | 25 | 16 Sep |
| LC-523 | List 902 | NurtureSync | 33 | 14 Sep |
| LC-990 | List 514 | AdAudience | 4 | 15 Sep |
| LC-488 | List 448 | Suppression | 3 | 16 Sep |
| LC-955 | List 419 | Other | 20 | 06 Sep |
Bring customer context into the workflow
Eligible owner coverage, unmatched leads and dated reassignment reasons.
opens Assignment History →| Record Number | Lead | Assigned To | Assigned From | Reason |
|---|---|---|---|---|
| LA-79194 | LDS-64199 | KT | LL | InitialRouting |
| LA-34811 | LDS-23936 | HU | TA | MQLHandoff |
| LA-72733 | LDS-92462 | EV | NM | ManualReassign |
| LA-67636 | LDS-45285 | EN | GF | StaleRecycle |
- Recorded
- Superseded
- Lead
- LDS-64199
- AssignedTo
- KT
- AssignedFrom
- LL
- Reason
- InitialRouting
- AssignedAt
- 27 Sep
- RecordNumber
- LA-79194
owner Sales Manager
Go from the big picture to the details behind it. Open any record to see its status, owner and history.
Illustrative records. Connections and approval states follow the authored specification.
Find the leads worth your next conversation
Find the leads worth your next conversation.
Illustrative previews from the system specification.
-
01
Capture
Bring prospect sources and contact preferences into the same lead queue.
Capture and prioritize leads -
02
Score
Explain the signals behind a lead’s priority with the approved scoring policy.
Capture and prioritize leads -
03
Route
Assign the next conversation to an eligible person with the right coverage.
Route and qualify prospectsAssignment HistoryRecordedRecord NumberLeadAssigned ToAssigned From -
04
Qualify
Let the assigned account executive review the prospect and accept the handoff.
Let the assigned account executive review the prospect and accept the handoff.
Route and qualify prospects -
05
Handoff
Carry qualified context into the connected CRM and track its confirmed result.
Complete the CRM handoffCRM HandoffDraftConversion NumberLeadTarget WorkspaceOpportunity Name
Keep decisions clear and work moving
Decision checkpoints where approval stays with your team.
Qualify
Let the assigned account executive review the prospect and accept the handoff.
Route and qualify prospectsKeep the next action accountable
Human approval and system automation have different jobs.
Qualify
Let the assigned account executive review the prospect and accept the handoff.
Qualification approvals
Give every person the right workspace
Marketing Operations
Prepares lead sources, scoring policy and lead-list hygiene.
Sales Manager
Owns team routing and independent duplicate resolution.
Sales Development Rep
Works assigned prospects and submits qualified leads to the selected account executive.
Account Executive
Reviews assigned qualification handoffs and requests creation of downstream CRM records.
Viewer
Reads permitted funnel summaries with personal contact fields masked.
See the result behind the activity
Start with the question. Follow it to the records behind the answer.
Lead Funnel
Lead intake through independent qualification and acknowledged CRM conversion by source.
View Lead BoardScoring Explanations
Applied score, contributing rules, model version and excluded or expired evidence for each run.
View Recent Score RunsSource Quality
Qualification outcomes by source and scoring-policy version, with unknown outcomes separate.
View My Lead QueueAssignment Coverage
Eligible owner coverage, unmatched leads and dated reassignment reasons.
View Assignment HistoryFollow-up Aging
Open alerts and due activities by permitted owner and territory.
View Priority Follow-upConversion Reconciliation
Pending, unknown and failed CRM handoffs with original request references.
View CRM HandoffDuplicate Decisions
Reviewed merges, rejected clusters and the retained survivor references.
View Duplicate ReviewContact Policy Audit
Channel and purpose decisions, withdrawals and blocked outreach outcomes.
View Consent HistoryConfigure your workflow with Proto
Let your AI agent help with everyday work. Set its permissions during setup and keep approvals with your team.
- Business connections
- Acquisition sourcesin and out
- Scoring providerin and out
- Pipeline CRMin and out
- Connection records
- ConfigurationIntegrationConnections · in and out
- ReconciliationIntegrationEvents · in and out
- Agents
- Your agentWorks within the permissions you assign
Your agent works within the permissions you assign.
List the work that needs attention. Keep the approval with the assigned reviewer.
Download agent Agent setup guide$ curl -fsSL https://www.erp.ai/skill.md
› open CRM with Lead Scoring and list records waiting on qualify
Lead to qualified handoff · records listed with owner and age
› approve the first one at qualify, as its approverYour questions, answered.
How the system works, what you can configure and how to get started.
How do I get started?+
Select Start now to create your account. Explore the system specification, or use Proto to configure it for your business.
Can we choose which signals affect a lead score?+
Yes. Define approved signals, weights, limits and expiry windows that reflect your qualification criteria. Each scoring result retains its rule version and contributing evidence so your team can explain why a lead moved up or down.
Does the system support AI lead scoring?+
Optional AI scoring can suggest priorities from explicitly allowed inputs. Record the model version and explanation, and limit its contribution under the approved policy. The result helps the team decide where to focus; it does not automatically qualify a lead.
What happens when engagement becomes outdated?+
Scores are recalculated when signals expire or are reversed. Repeated source events count once, and a calculation based on an outdated lead revision cannot replace a newer result. This keeps old or duplicated activity from inflating the score.
How are leads assigned to the sales team?+
Apply approved territory and routing rules to active, eligible owners. A deterministic routing policy and recorded assignment history make ownership clear. Leads stay visibly unassigned when no eligible owner is available.
Can we review duplicates before merging them?+
Yes. Proposed duplicate groups remain separate until an authorized independent review resolves them. A merge preserves source identifiers and contact restrictions, and must not widen access to private notes or customer information.
Does a high score automatically create an opportunity?+
No. An SDR submits qualification evidence, and the assigned account executive independently accepts the handoff. The accepted lead then follows the configured CRM conversion process, with the destination’s acknowledgment recorded before conversion is marked complete.
Can this connect to our existing sales CRM?+
Yes, through an explicitly configured connector and field mapping. Retain the destination account, contact and opportunity identifiers. Failed or uncertain handoffs remain visible and are reconciled using the original request, which helps avoid duplicate CRM records.
How are contact preferences respected?+
Lead priority and permission to contact are separate. Record the allowed purposes and channels, and recheck them before outreach. A withdrawal blocks new outreach even if the lead remains on a list or has a high score.
How can we tell whether the scoring rules are useful?+
Compare accepted qualification and confirmed conversion outcomes with the rule version that prioritized each lead. Keep missing outcomes distinct from rejected leads. Use those observations to propose and review a new rule version without rewriting historic explanations.
- 01
Agree on scope
Confirm the customer workflow and public capabilities with the responsible owners.
Team and ERP.ai - 02
Prepare the workspace
Configure role membership, source identities and reference data.
Team and ERP.ai - 03
Reconcile open work
Import actual states, ownership and prior decision evidence.
Team and ERP.ai - 04
Connect carefully
Enable each integration only after its mappings and uncertain-outcome behavior are tested.
Team and ERP.ai - 05
Practice the handoff
Run the main workflow and rejected-action cases with the people who will operate it.
Team and ERP.ai - 06
Extend gradually
Review exceptions before opening the workflow to the wider team.
Team and ERP.ai
Pricing
The base account and ordinary manual work in ERP.AI's official interface are $0. Viewing, searching, creating, editing, approving, deleting and exporting records in that interface do not consume read or write credits. There is no per-user fee.
Machine work: external API-key requests, imports, workflows, agents and scheduled jobs. Successful external API-key reads and writes use the operation rates below. Starting a managed execution from the interface still starts that metered service.
Pricing and account rules| Machine work | Included per $1 of credit |
|---|---|
| List/filter or get record calls | 20,000 |
| Search or aggregate calls | 4,000 |
| CSV or PDF exports | 100 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| File upload in MB | 2,000 |
| Workflow runs | 2,000 |
| Code-node compute beyond included in CPU-sec | 12,000 |
| Agent executions | 2,000 |
| Scheduled jobs or webhook activations | 20,000 |
Read and write rates apply to successful external API-key requests. Ordinary manual work in the ERP.AI interface is $0.
prepaid creditsSmallest pack $5, purchased credits never expire.
Explore the complete system.
Follow the operating model from the process to the people, records and decisions behind it.
Industries
Reference
Make it work your way.
Use Proto to configure this system for your business. Review fields, rules and approvals before releasing changes.
Previews contain illustrative data from the system specification.