CRM On Mobile Devices — Field Notes
Sales operations / Workshop notes01 — Field workflow
A field guide for SaaS sales teams

The deal moves between meetings.

For field-facing sellers, a CRM update often happens in the gap between conversations. Evaluate mobile workflows around that moment, so qualification details and next steps are ready for the next person to use.

01 / Rank mobile priorities
Workflow sketchIllustrative example
01
Field conversationCapture the context
02
QualificationRecord what is known
03
HandoffAssign the next action

Three connected moments to test, not a product interface.

01 / Priority exercise

Rank the work a seller does on the move.

Before comparing CRM software, ask field sellers to walk through their last meeting day. Rank tasks by urgency and consequence, not by how often they appear in a feature list.

01

Find the meeting context

Can a seller locate the right account, contact, opportunity and previous notes on a small screen? Test the path from a crowded schedule to the relevant record.

02

Capture qualification evidence

Choose the few fields that matter after a conversation, such as buying process or an identified need. Check whether notes and structured fields are practical to update on mobile.

03

Leave a usable next step

Evaluate how a seller records an owner, action and due date. Then ask whether a manager or teammate can understand the handoff without reconstructing the meeting.

Workshop prompt Put the three tasks in order for your team. For the top task, define what a complete record looks like before evaluating screens or settings.

02 / Data quality check

A saved update is not always a useful update.

Mobile entry can expose gaps in a qualification process. Agree on a small set of checks that sales operations and frontline managers can review together.

Missing qualification context

Review opportunities with a stage change but no supporting detail. Decide which evidence should accompany that change and where it belongs.

Next steps without an owner

Look for open opportunities with an action but no named owner or date. Clarify who is responsible for completing the handoff.

Notes that cannot be interpreted

Sample a few recent field updates. Can someone outside the meeting distinguish a confirmed fact from an assumption or an unresolved question?

Updates delayed by connectivity

Ask sellers where connection is unreliable. When evaluating a CRM, investigate offline behavior, sync visibility and what happens if an update conflicts.

03 / Practical next steps

Bring the field into the evaluation.

  1. Map a real handoff. Follow one opportunity from a field meeting to the next internal conversation. Note where details are re-entered or clarified.
  2. Test on actual devices. Use representative tasks and realistic records. Ask sellers to find context, update qualification and leave a next step.
  3. Review the resulting data. Have a manager read the update without extra explanation. Record what is missing and refine the required fields or guidance.
  4. Ask implementation questions. Explore permissions, field requirements, offline behavior and reporting with any vendor under consideration. Confirm what can be configured for your process.
Return to the priority exercise