Mobile-First CRM: How intelligentfood Runs Field Sales on SAP BTP

intelligentfood distributes food products across Switzerland. Their sales reps visit restaurants, hotels, and retailers every day. They take orders, check stock, photograph shelf placements, plan routes. All from the road, all day long.

Their old system was a mess. Desktop CRM nobody opened outside the office. Paper order forms. Phone calls to the back office to confirm prices. Orders took 2-3 days to reach the ERP. Management had zero real-time visibility into what was actually happening in the field.

They didn’t need a better desktop CRM. They needed something built for how their reps actually work. Standing in a restaurant kitchen, phone in one hand, product catalogue in the other.

TL;DR: Sales reps spend only 28% of their time actually selling (Salesforce, 2024). intelligentfood fixed that for their field team by building custom SAP BTP apps on top of Sales Cloud V2 — with offline capability, photo documentation, and route planning. Results after 6 months: 60% faster order processing, 25% more customer visits per day, and 100% mobile adoption in month one.

Why Wasn’t Standard CRM Enough?

With 55% of ASUG members now using SAP BTP (ASUG, 2025), BTP extensions are becoming standard practice for closing CRM gaps. We evaluated SAP Sales Cloud V2 as the core. It was the right choice for account management, pipeline tracking, reporting. But V2’s standard mobile experience didn’t cover four things intelligentfood actually needed in the field.

Offline capability. Their reps visit locations with no connectivity. Basement kitchens, rural areas, underground storage rooms. The app had to work with zero network and sync when the signal came back. No ifs.

Photo documentation. Reps photograph product placements, competitor displays, delivery conditions. Photos need to attach to visit reports automatically, with GPS and timestamps. Not “send it in an email later.”

Route planning. With 15-20 visits per day, the difference between a good route and a bad one is 4-6 extra customer touches. That compounds over a year into serious revenue.

Custom order entry. intelligentfood’s product catalogue and pricing logic is specific to their business. Standard CRM order entry didn’t match their workflow at all.

So we built custom BTP applications that extend Sales Cloud V2.

How Does the Architecture Work?

82% of developers now prioritise API-first approaches (Postman, 2024). V2’s API-first design made this architecture possible. Three layers.

SAP Sales Cloud V2 is the core CRM. Accounts, contacts, opportunities, pipeline. Standard V2 functionality. Single source of truth for customer data. Nothing custom here.

SAP BTP applications are custom mobile apps built on Cloud Foundry. These handle field-specific workflows: visit management, offline data capture, photo documentation, route planning, and order entry. This is where the magic lives.

The integration layer ties it together. BTP apps communicate with Sales Cloud V2 through its REST APIs. Visit reports, orders, and activity data sync back to V2. The integration runs on SAP Integration Suite for reliability and monitoring.

How Does Offline Mode Work?

The mobile apps use a local data store on the device. When a rep starts their day, the app syncs their daily route, customer data, product catalogue, and pricing. Everything cached locally.

During visits, all data entry happens against the local store. No network dependency. Photos stored locally with metadata.

When connectivity returns (usually between visits or end of day), the app syncs changes back to Sales Cloud V2 via the integration layer. Conflict resolution follows a “last write wins” model with field-level granularity. This works because reps rarely edit the same records simultaneously. In 6 months of production use, fewer than 0.1% of syncs produced conflicts. Lower than most people expect.

How Does Photo Documentation Work?

Rep taps a button, takes a photo, it’s automatically attached to the current visit report. Metadata includes timestamp, GPS coordinates, customer account. Photos sync to an S3-compatible object store on BTP and link back to the Sales Cloud V2 activity record.

Management uses these photos for compliance checks, merchandising audits, dispute resolution. What used to require a separate visit now happens automatically. Neat.

How Does Route Planning Save Time?

The app calculates optimised routes based on planned visits, GPS position, traffic data. Reps see their route on a map, reorder stops as needed. Completed visits update the route automatically.

This replaced a manual process where reps planned routes the night before using Google Maps. Time savings: roughly 30 minutes per rep per day. Over a year, those extra visits compound into numbers the sales director actually notices.

What Does Sales Cloud V2 Handle?

CRM delivers $3.10 for every dollar spent when implemented well (Nucleus Research, 2024). The BTP apps handle field operations. V2 handles everything else.

Pipeline management. Opportunities created during field visits appear in V2 immediately after sync. Management sees the full pipeline without waiting for reps to “update the CRM.” That alone is worth the investment.

Reporting and analytics. Visit frequency, order volumes, pipeline by territory. All in V2’s analytics. No separate reporting tool needed.

Account 360. Every customer interaction (visits, orders, calls, emails) appears on the V2 account timeline. When a rep visits a customer, they see the full history. No more “let me check” moments.

AI insights. V2’s Joule flags accounts that haven’t been visited recently, opportunities at risk, revenue trends. Feeds directly into territory management decisions.

What Were the Results After 6 Months?

Order processing time dropped by 60%. Orders entered in the field hit the ERP the same day. Previously, the paper-to-system lag was 2-3 days. Gone.

Visit frequency increased by 25%. Route optimisation plus faster data entry means more customer touches per day. That’s 3-4 additional visits per rep per week. De facto, a 25% sales capacity increase without hiring anyone.

Pipeline accuracy improved. Management reports went from “best guess” to real-time data. Quarterly forecasting accuracy moved from roughly 65% to 85%.

Rep satisfaction hit 100%. The mobile app replaced three separate tools. One device, one app, data entered once. Adoption was 100% within the first month. Why? Because the app actually makes their job easier. That’s the only adoption strategy that works in field sales. Everything else is a PowerPoint slide.

What Can You Take from This Project?

If you’re considering something similar, here’s what we learned.

BTP is the extension platform. Don’t force complex field workflows into standard CRM. Build what you need on BTP and integrate through APIs. V2’s REST APIs are comprehensive and well-documented. The integration was straightforward. No workarounds needed, which is refreshing if you’ve spent any time with the old C4C APIs.

Offline-first is a design choice, not something you bolt on later. We’ve seen projects try to add offline after the fact. It never works well. Design for it from day one.

And keep the core clean. All custom logic lives on BTP. Sales Cloud V2 stays standard. Upgrades don’t break anything. That was the single most important architectural decision on this project.

Need a mobile CRM that works the way your field team actually works? We build custom BTP solutions on top of SAP Sales Cloud V2. Let’s talk.

Frequently Asked Questions

Can this approach work for industries other than food distribution?

Yes. The pattern (Sales Cloud V2 as core CRM plus custom BTP apps for field-specific workflows) applies to any industry with field sales teams. We’ve discussed similar architectures for equipment maintenance, pharmaceutical sales, and construction. The offline capability and photo documentation features are relevant whenever reps work in areas with limited connectivity or need visual proof of work.

How long did the intelligentfood implementation take?

The core implementation (BTP app development, V2 configuration, integration setup, and user training) took 4 months from kickoff to go-live. The offline sync architecture required the most development time, roughly 6 weeks. Route planning integration took 2 weeks. V2 core CRM configuration was the fastest component since we used standard features without heavy customisation.

What happens when sync conflicts occur?

Sync conflicts are rare because field reps work on their own accounts and rarely edit the same record. When conflicts do occur, the system uses “last write wins” at the field level (not record level), so only the specific conflicting field gets overwritten. The sync log flags all conflict resolutions for review. In 6 months of production, fewer than 0.1% of syncs produced conflicts.

How much does a custom BTP extension like this cost compared to standard CRM?

Custom BTP development adds 30-50% to the cost of a standard Sales Cloud V2 implementation, depending on complexity. For intelligentfood, the ROI justified the investment within 4 months. The 60% reduction in order processing time alone saved enough back-office hours to cover the annual BTP hosting costs. The real question isn’t cost. It’s whether standard CRM can support your field workflows without custom extensions.

Does the mobile app work on both iOS and Android?

Yes. The BTP apps are built as progressive web apps (PWAs), which run on both iOS and Android through the device’s browser. This avoids maintaining separate native apps for each platform. PWAs support offline storage, camera access for photo documentation, and GPS for route planning. The trade-off is a slightly less native feel compared to a dedicated app, but significantly lower development and maintenance cost. Fair enough trade-off for most field teams.