Designing the operating cycle behind field commercial execution
A fictional case that joins capabilities usually built separately—visit planning, bulk visit creation, pre-visit context, capture and follow-up—into one operating cycle.
Independently created. Contains no employer or client implementation detail, internal names or figures.
The case in brief
Current reality
Field teams had tools to plan, prepare and log visits but no cycle joining them: visits followed habit, preparation depended on the person, and follow-up lived in notebooks.
What must become true
Every visit has a reason, is prepared from current account context, ends with captured discoveries and commitments, and produces follow-up that someone owns and management can see.
Design question
What must be true before, during and after a visit for field time to become commercial progress?
01Reality
What the organization actually did.
A fictional manufacturer’s field teams visit distributors and workshops across territories. Several capabilities already existed: planning visits, creating many visits at once, pre-visit account summaries. Used separately, they saved clicks but did not change which accounts were visited or what happened afterwards.
- Visit frequency followed habit and geography, not priority
- Preparation meant scrolling through the account on the way in
- Visit notes were free text—or not written at all
- Commitments made to customers had no owner and no date
- Managers saw visit counts, not what visits changed
02One process?
What made one process insufficient?
A visit is not an isolated activity; its value depends on what happens before and after it. The variables:
- 01Why this account, nowPerformance, potential, open actions—or a scheduled cycle?
- 02PriorityWhich accounts deserve limited field time this week?
- 03Territory and routeCan the priorities be visited efficiently together?
- 04ContextWhat changed since the last visit: orders, service cases, opportunities?
- 05ObjectiveWhat should this conversation achieve?
- 06CaptureWhat must be recorded, in structure, before memory fades?
- 07Follow-upWho owns each commitment, and by when?
Field productivity is not the number of clicks saved. It is whether preparation, conversation and follow-up form one reliable commercial loop.
03Segmentation
How the reality was segmented
Visits differ by purpose; the purpose decides the preparation and the capture it requires.
Field time
- Development visitGrowth against potential: brings opportunities and plan actions.
- Recovery visitAn At Risk or No Sale account: follows its recovery plan.
- Introduction visitA new customer or a new range: gathers qualification evidence.
- Relationship visitA scheduled cycle or an issue follow-up: captures service signals.
Design decision
Design the visit as one loop with explicit inputs and outputs at each step, and build planning, preparation and capture as parts of that loop—not as separate products.
04Target model
Target operating model
Six steps, each with a clear input and output.
- 01Prioritize
- Owner
- Sales manager with the representative
- Exit criterion
- Visit list for the period, each visit with a reason
- 02Prepare
- Owner
- Representative
- Exit criterion
- Objective set; context reviewed—performance, open actions, opportunities
- 03Visit
- Owner
- Representative
- Exit criterion
- Conversation held against the objective
- 04Capture
- Owner
- Representative
- Exit criterion
- Discoveries, decisions and commitments recorded in structure
- 05Follow up
- Owner
- Action owners
- Exit criterion
- Tasks done; opportunity and account updated
- 06Measure
- Owner
- Sales manager
- Exit criterion
- Coverage of priorities and follow-up completion reviewed
05What changes by path · Prioritize → prepare → visit → capture → follow up → measure
What each moment needs—and produces
Before, during and after: the decisions and information the loop depends on.
| Dimension | Before | During | After |
|---|---|---|---|
| Decide | Who to visit, why, with what objective | What to explore, what to propose | What happens next, and who owns it |
| Information | Performance, potential, open opportunities and actions, recent activity | Objective, prepared questions, offers | Discoveries, commitments, evidence |
| Output | Visit plan with reasons | Outcome against the objective | Tasks, updates, next visit |
| Visible to management | Coverage of priority accounts | — | Follow-up completion |
Before
- Decide
- Who to visit, why, with what objective
- Information
- Performance, potential, open opportunities and actions, recent activity
- Output
- Visit plan with reasons
- Visible to management
- Coverage of priority accounts
During
- Decide
- What to explore, what to propose
- Information
- Objective, prepared questions, offers
- Output
- Outcome against the objective
- Visible to management
- —
After
- Decide
- What happens next, and who owns it
- Information
- Discoveries, commitments, evidence
- Output
- Tasks, updates, next visit
- Visible to management
- Follow-up completion
The pre-visit summary and bulk visit creation are supporting capabilities of this loop—not cases of their own.
06Exceptions and return paths
The happy path is never the whole process.
| When | Then | Owner | Returns to |
|---|---|---|---|
| A priority account is not visited in the period | Carried forward with a reason; flagged at the second miss | Sales manager | Prioritize |
| The visit is cancelled | Rescheduled, or replaced by a call that keeps the objective | Representative | Prepare |
| Capture is incomplete after a set time | Reminder, then visible in the manager’s review | Representative | Capture |
| A commitment needs another team | Task assigned to that team with the customer context | Representative | Follow up |
07Supporting capabilities and system encoding
Only now, the technology.
CRM (mobile)Route planningData platformAI assistance
Supporting capabilities
- Visit planning and bulk creationTurns the prioritized list into scheduled visits
- Pre-visit contextSummarizes performance, open items and recent activity—see the pre-visit account context case
- Mobile captureStructured notes, commitments and tasks at the end of the visit
- Route planningGroups priority visits efficiently by territory
How the system encodes the model
Operating decision: Every visit has a reason
System response: Visit purpose required when planning
Operating decision: Preparation from current context
System response: Pre-visit summary generated from account data
Operating decision: Structured capture
System response: Visit outcome, discoveries and commitments as fields and tasks
Operating decision: Owned follow-up
System response: Tasks with owners and dates created from commitments
08Measurement
What is measured—and what it triggers.
| Metric | Why | Owner | Cadence | Triggers |
|---|---|---|---|---|
| Priority coverage | Field time should follow priority | Sales managers | Monthly | Re-plan territories |
| Visits with complete capture | No capture, no follow-up | Sales managers | Weekly | Coach, and simplify capture |
| Follow-up on time | The loop closes after the visit | Sales managers | Weekly | Escalate overdue commitments |
| Opportunities and plan actions from visits | Shows whether visits change commercial progress | Sales leadership | Quarterly | Adjust visit purposes |
09The second layer
Questions that change the design.
Priority
- Who decides which accounts are visited—the representative, the manager or a rule?
- How is a habitual visit challenged?
Capture
- What is the minimum structured capture that still gets done?
- Who reads it?
Follow-up
- Who owns a commitment made by the representative but delivered by another team?
- When is a visit done?
10Decisions & outputs
What the work produces.
- 01Field operating cycle
- 02Visit purposes and required capture
- 03Prioritization rules
- 04Follow-up model
- 05Field KPIs