Mobile CRM for field sales teams

A field sales rep does not use a CRM the way a colleague at a desk does. They have two minutes in a parking lot, a patchy signal and a phone in hand. A CRM built for a desktop screen and squeezed onto mobile as an afterthought rarely gets filled in. Here is what a mobile CRM should do, how I build one, what it costs and when you are better off keeping an off-the-shelf tool.

What reps actually need in the field

Before each meeting, the rep wants the customer’s history in a few seconds: latest orders, last visit report, open issues, contacts. After the meeting, they want to log the essentials before driving off. Everything else is secondary.

The features that make the difference:

• a customer record that reads well on a small screen, with the useful information at the top and the rest collapsed;
• the calendar and today’s visits, with directions in one tap;
• a short, structured visit report: a few required fields, a free-text note, the next action and its date;
• a map of nearby customers and prospects, to fill a gap in the day;
• offline mode, with automatic sync when the signal comes back;
• visible follow-ups: what is overdue, what is due this week.

The visit report deserves an article of its own: I cover its structure and the metrics it enables in visit reports and activity tracking for sales reps.

PWA or native app

For a mobile CRM, I usually recommend a progressive web app (PWA). It installs on the home screen like an app, keeps the data it needs locally, works without a connection and updates without app store review. A single codebase serves the phone, the tablet and the manager’s computer.

Native makes sense in specific cases: deep hardware access, integration with a specialized device, demanding background processing. The full comparison is in PWA vs native app, and data entry without a signal is covered in detail in offline order taking.

Location data: useful, but regulated

Showing customers near the rep’s position is useful. Tracking the rep continuously is a different matter. In France, the data protection authority (CNIL) states in its guidance on geolocating employees’ vehicles (in French, checked in October 2026) that an employer may not monitor an employee permanently, nor track employees who are free to organize their own travel, such as traveling sales reps. Data collected outside working hours is also off-limits. Other countries have their own rules, generally in the same spirit under the GDPR in Europe.

In practice, I design the mobile CRM to use location only when the rep asks for it (customers near me, directions), with no trip history. If you want to record where a visit took place, that decision belongs with your data protection officer or legal counsel, with proper notice to employees and their representatives. This page is not a substitute for their advice.

The budget

The starting point is the floor for a business app: $6,800 (€6,000)excl. VAT. Building blocks are added depending on your needs. Here is a sample breakdown for a team of 10 to 50 reps:

A simpler version, without the map or integration, stays close to $11,200 (€10,000)excl. VAT. On the other hand, adding order taking with customer-specific pricing pushes the project toward the top of the $6,800 to $22,400 (€6,000–€20,000)excl. VAT range. For your own combination, the estimator gives you a range in one minute. The cost drivers of a CRM are also explained in how much a custom CRM costs.

On top of this come hosting (a few tens to a few hundred euros a year) and maintenance. None of these costs depend on the number of reps.

When a custom mobile CRM is not the right choice

I will be blunt: many off-the-shelf CRMs come with a decent mobile app. If your team has a handful of reps, follows a standard sales process and mostly works with a signal, a well-configured standard tool will be faster to roll out and cheaper in year one.

Custom software makes more sense when:

• your reps often work without a signal (rural areas, basements, industrial sites);
• your current CRM’s app is too slow or too cluttered, and reps have stopped filling it in;
• you need to show ERP data (stock, prices, outstanding balances) that the CRM does not have;
• license costs go up with every hire.

There is often a middle path: keep the office CRM and build only the field app, connected to its API. It costs less than a full replacement.

Where to start

1. A free 30-minute discovery call: you walk me through a typical day for your reps and what gets in the way.
2. Scoping (1 to 2 weeks): priority screens, offline rules, integrations, fixed quote and schedule.
3. Clickable mockups (1 to 3 weeks): two or three reps test them on their own phones, in real conditions.
4. Development in batches: customer record and visit report first, then map, dashboard and integrations.
5. Go-live, data migration and onboarding, with 3 months of support included.

For an example of a platform designed for mobile professionals (directory, Google Maps routes, calendar, invoicing), see the OptiRoad project, currently in development. The full offer is on the custom CRM page.