Personal prospecting
Targets, contacts and notes remain in individual files or notebooks.
POCKET CRM · Field sales edition
Equip the field team.
Keep the pipeline alive.
An edition designed to connect prospecting, portfolios, opportunities, visits, objectives and the sales team’s next action.
01 / 03
Relationship gaps
What weakens trust and management.
Poorly prepared visits
The salesperson arrives without a clear view of open items, commitments and latest interactions.
Declarative pipeline
Stages and dates are updated late, without criteria or next action.
Ambiguous field ordering
Pricing, stock, rights and the responsible system are not always clarified before entry.
A shared discipline
From identity to next action, without losing context.
Operational benefits
Information designed for decisions and action.
Every visit, reminder and opportunity remains linked to the account, objective and next action.
01
A genuinely prioritised portfolio
Bring potential, history, recent activity, commitments and next actions together without confusing a score with human judgement.
Explore in the lab
02
Prepared and documented visits
Share context, objective and open items before the interaction, then retain outcome, documents and expected follow-up.
Explore in the lab
03
An explainable pipeline
Every stage relies on agreed criteria, recent facts and a dated next action.
Explore in the lab
04
A clean connection with ERP
CRM prepares the relationship and opportunity; ERP confirms items, terms, order, availability and billing according to its role.
Explore in the labDecision lab
Test CRM behaviour in the situations that matter.
Criteria, selected order and adjustment are retainedSituation
Visit priority
Several accounts require a visit within a constrained period.
Signals to verifyCommitment and due datePotential and activityArea and availability
Expected decisionBuild an explainable priority list, then let the owner adjust it to the real context.
Retained evidenceCriteria, selected order and adjustment are retained
Structured capabilities
Explore the scope without turning the page into a catalogue.
Selected capability
Prospecting
Targets, contacts, activities and qualification.
- Target qualified by source, segment and potential
- Consent and contact permission verified before action
- Prospecting outcome linked to a next step
System responsibilities
CRM connects the relationship. It does not replace responsible systems.
This edition structures prospecting, opportunities, visits, objectives and forecasts. Field order entry, route optimisation and offline mode remain conditional on validated scope, devices and integrations.
Prospecting and opportunities
Owns targets, portfolios, activities, visits, opportunities, objectives and next actions.
- Portfolio and activity
- Opportunity and stage
- Visit and next action
Offer and order
Retain items, pricing, terms, availability, order, billing and accounting according to the architecture.
- Commercial master data
- Confirmed order
- Billing and settlement
Field context
Provide appointments, geography and device access according to rights; no automatic optimisation is assumed.
- Appointment and availability
- Area and route
- Device and security
Two business editions
One shared foundation, two usage priorities.
Choose according to the work to structure: relationship continuity or field-team activity. Both share accounts, contacts, activities and history.
Composable architecture
One relationship source, explicit responsibilities.
Interfaces are defined event by event: source, owner, frequency, rights, error and recovery. No universal compatibility is assumed.
POCKETCRM
POCKET CRM
ERP
Calendar
Mobility
Mapping
BI
Controlled deployment
Start with the journey that genuinely needs to change.
Scope
Roles, journeys, pain points, objectives
Govern
Master data, rights, consent, rules
Connect
Channels, ERP, events, errors
Configure
Stages, activities, views, approvals
Pilot
Real scope, adoption, corrections
Extend
Validated teams, uses and interfaces
Resources
Go further.
Frequently asked questions
Clear answers before scoping.
01Is mobility included?+
The mobile scope depends on the selected uses, devices and security rules.
02Can objectives be configured?+
They must be defined according to the sales organisation, roles and approved indicators.
03Can a visit be prepared and documented?+
Yes. Customer context, meeting, open points, report, documents and next action can follow the approved journey.
04Can an order be entered in the field?+
That depends on scope, rights, prices, available stock and integration with the order system of record.
05SaaS or on-premise?+
Both deployment modes are available. The choice depends on mobility, devices, connectivity, security and interfaces.
Your next step
Turn relationships into shared decisions and actions.
Let’s discuss your teams, data, channels and the priority journey to structure.