CRM & sales
Spatial customer ops
The CRM skill turns Nexma into a spatial customer-relationship platform. It models accounts, contacts, deals, and territories, and gives Jax the tools to plan field-based sales motions over a map. Where logistics routes trucks, this skill routes people — and weighs every stop by pipeline value, not freight.
What this skill models
The ontology captures a sales operation with the entity types, link types, and constraints a revenue leader expects.
- Entity types.
Account,Contact,Lead,Opportunity,Deal,Activity,Campaign, andQuote. Each carries typed properties — stage, value, owner, close date. - Link types.
ContactAssociation,DealPipeline,ActivityLog, andCustomerJourney. Activities carry channel, outcome, and timestamp. - Key constraints. Stage gating (an opportunity cannot skip stages); quota tracking; forecast roll-up; and territory exclusivity.
The ontology ships sensible defaults: Salesforce-aligned stage names (configurable per organization) and standard activity types.
What Jax can do
Jax reasons about pipeline and geography together because the Skill binds its capabilities to this ontology.
- Design territories that balance account count, pipeline value, and drive time.
- Route reps through their accounts. "Plan next week for the West rep. Visit every Tier-1 account due for a touch in the last 90 days. Group geographically."
- Forecast pipeline with stage-weighted roll-up and risk flags.
- Prioritize accounts by combining last-touch recency, deal stage, and product fit.
- Validate the forecast roll-up, territory balance, and activity coverage.
Territory balancing and rep routing run through the Nexma MathEngine, writing the plan back to the world model so territory polygons and route lines update the moment Jax finishes.
Tip: Set the rep roster and each rep's capacity before asking Jax to draw territories. Territory balance is a function of who is available and how much they can carry, so pinning the roster first keeps reruns from reshuffling boundaries.
Constraints and standards
The skill enforces the rules a sales plan must satisfy to be consistent and forecastable.
| Concern | Rule enforced | Standard |
|---|---|---|
| Pipeline | Stages cannot be skipped | Stage-gating policy |
| Forecast | Stage-weighted roll-up | Org forecast model |
| Territory | Exclusivity per owner | Territory policy |
| Data model | Account / Contact / Opportunity | Salesforce alignment |
| Account ID | B2B location identification | GS1 GLN |
Sync targets include Salesforce and HubSpot through the connector — activities push back to the source CRM after a pre-billing-style review.
Out of scope today: marketing-automation campaign authoring (campaign data consumed, not authored), quote-to-cash document generation, and customer-support ticketing (a separate skill, planned).
Where to go next
- Logistics — the routing engine adapted to fleets.
- Legal practice — another professional-services ontology.
- Skills overview — the full catalog.
- Nexma MathEngine — the optimizer behind territory and route design.