Home dashboard
SugarAI · Mobile CRM · Manufacturing field sales
From CRM access to visit readiness.
I redesigned Sugar mobile around the field rep's day: prepare for the next visit, answer customer questions in the moment, capture what changed, and sync clean updates back to CRM.
The problem
Mobile CRM gave reps access, but not momentum.
Sugar mobile gave reps access to accounts, emails, notes, contracts, leads, opportunities, dashboards, and reports. That access mattered, but the app still made reps assemble what mattered while moving through a customer day.
Most modules reused the same pattern: list view, record view, tabs, related records, and long create forms. The consistency was useful, but it reflected the database more than the conditions reps worked in.
The existing experience starts with the system. The redesign starts with the rep’s next customer.
Problem anatomy
The data was there. The mobile workflow got in the way.
Dashboards showed activity without surfacing the next move. Lists exposed records without ranking urgency. Record views scattered context across tabs and field rows. Create screens asked for more input than a rep should handle on a plant floor.
The opportunity was to move priority, context, and capture into the moment of customer work.
Current app examples
The current flow made reps rebuild context on the go.
The workflow was possible, but required reps to navigate records and complete forms while moving through customer visits. The redesign aimed to reduce that effort rather than reproduce the desktop workflow on a phone.
List view
Record view
Create form
Field research
Design for the rep standing inside the plant.
I met with five sales reps to understand how field work actually happens: on the road, inside customer facilities, on noisy factory floors, in warehouses, and in low-connectivity areas. They needed account context, product data, ERP inventory, service history, pricing, and fast capture without stopping the conversation.
The pattern was consistent: reps were willing to capture information, but not if the app interrupted the conversation or forced them to rebuild context later.
Before the visit
What should I know before I walk in?
- Route and siteWhere am I going and what site context matters?
- Account healthWhat changed since the last visit?
- Open issuesWhich orders, tickets, or equipment risks need attention?
During the visit
What can I answer or promise right now?
- Product lookupSpecs, blueprints, and compatible parts.
- ERP contextInventory, lead times, and production schedule.
- CaptureNotes, cards, photos, tasks, and stage updates.
Design challenge
The redesign had to solve four things at once.
The interviews made the challenge concrete. The redesign needed to show the next customer action, keep account and site context close, support product and service questions during the visit, and turn messy field capture into reviewable CRM updates.
SugarAI could not simply replace modules with chat. It had to reduce the work around the visit while keeping CRM, ERP, catalog, and service context visible enough for reps to trust.
Key decisions
Four choices shaped the redesign.
Start with Today
A field rep does not wake up needing Accounts. They need to know where to go, what changed, and what to do when they arrive.
- Considered
- A faster module launcher for accounts, tasks, and opportunities.
- Chose
- A Today view organized around the next customer visit.
Make sites first-class
Manufacturing accounts often span plants, warehouses, HQ offices, and service locations. Each site carries different contacts, risks, and work.
- Considered
- Treating every location as detail inside the account record.
- Chose
- Site-level visit context so reps could prepare for the actual place they were entering.
Brand the workspace
Customer identity anchors the workspace. SugarAI appears where it helps: briefings, prompts, capture, and review.
- Considered
- Making SugarAI the primary surface for every task.
- Chose
- Use AI as a layer inside customer context, not a separate destination.
Review before saving
Messy field input becomes suggested CRM updates the rep can inspect, edit, remove, and save with confidence.
- Considered
- Auto-saving dictated notes directly to the CRM record.
- Chose
- A review step so reps could trust what changed before committing it.
These choices became a reusable mobile system: priority visit cards, route cards, offline pills, source badges, quick actions, live capture, outcome controls, suggested update rows, and Ask SugarAI prompts.
The palette separates readiness, availability, AI assistance, and success states so the interface does not make every action feel equally urgent.
Before and after
Move CRM work into the rhythm of the visit.
The redesign does not remove CRM structure. It brings the right records, context, and capture steps forward when they help the rep act.
Before · object path
Assemble the visit
Start with CRM objects and stitch together context across separate screens.
- 01Scan dashboardLook for a useful signal
- 02Find accountSearch or browse the right customer record
- 03Open recordMove through tabs and related data
- 04Piece together contextCheck notes, activity, product, and service history
- 05Enter updates laterReturn to forms after the conversation
After · visit loop
Prepare, capture, and sync
Start with the rep's day and keep the customer visit moving.
- 01TodaySee the next stop and what needs attention.
- 02Visit BriefReview account, site, route, and risk context before walking in.
- 03Active VisitCapture notes, products, photos, and follow-ups during the conversation.
- 04ReviewInspect SugarAI's proposed CRM updates before saving.
- 05SyncSave the visit and return to Today with the next stop ready.
The new concept
Four prototype flows show the field-sales loop.
The prototype focused on the moments where mobile CRM usually breaks down: preparing before the visit, answering questions during the conversation, capturing updates without a long form, and sending clean CRM updates afterward.
Prototype flows
Supporting actions
Keep small tasks attached to the visit.
The visit flow also needed to handle the actions reps take around a meeting: directions, calls, inventory checks, and follow-up messages.
- Before
- Reps left the CRM flow to navigate, call, check stock, or draft follow-up, then had to find their place again.
- After
- Those supporting actions stay attached to the visit context, so reps can act quickly without turning the main visit flow into a pile of extra steps.
Testing and learnings
What the concept test showed.
Due to time constraints, I tested the prototype with two of the five sales reps interviewed during research. Their feedback supported the visit-centered approach and informed a roadmap item for the next release.
-
01
Less to carry, less to search
Both reps welcomed the prospect of visiting customers without carrying a laptop, relying on on-site Wi-Fi, or digging through CRM records. They valued having the relevant customer context available within the visit workflow.
-
02
Their day extended beyond the CRM
They requested synchronization with their personal calendars so their schedule would be visible in both SugarAI and their native calendar app. Some reps combine work and personal commitments and did not want another schedule to manage separately.
-
03
Calendar sync became a next-release roadmap item
This feedback put personal-calendar synchronization on the roadmap for the next release. It was a planned follow-up, not a capability delivered in the tested prototype.
What I learned
Organizing the app around customer visits was only part of the solution. It also needed to fit into the tools reps already used to manage their day. The calendar request showed that reducing effort meant connecting to those existing habits, not asking reps to maintain another schedule.