gmi.software
01 · Your app

Mobile apps

When the app is slow to change, crashes or nobody owns it.

  • Develop or take over an app
  • Loyalty apps
  • Mobile app code audit
  • App maintenance and releases

SFD: 100,000+ downloads, 4.9 App Store rating

02 · Your shop

Online shops

When the platform takes a cut of every sale or blocks what you need.

  • Online shop development
  • Shop app analytics
  • Plan and prototype before you build

120+ projects delivered

03 · Systems behind them

Integrations

When orders, stock and points are copied by hand.

  • ERP, warehouse and payments
  • AI for one manual process
  • Workshops and estimate

100+ integrations

Before a call
  • App cost estimateScope and a budget range
  • Shop platform adviserDecisions, risks and options
  • Shop cost over 5 yearsOff-the-shelf or custom, compared

After workshops: an agreed scope and a fixed price for delivering it

All services →
SFDLoyalty and shopping app100,000+ downloads · 4.9 App Store ratingMój Świat KsiążkiLoyalty programme for a bookstore chain100,000+ downloadsEMKAMedical waste tracking app5000+ downloads in first month
All 120+ projects →App ideas library
TeamAbout usWho we are and how we workCareersHow we work and open roles
Contact and stackContact[email protected]TechnologiesReact Native, MedusaJS, Node.js and the rest
Reviews5.0 on Google4.9 on ClutchClutch ↗ (opens in a new tab)
Blog
ENBook a free consultation
What we do+−

01 · Your app

Mobile apps

  • Develop or take over an app
  • Loyalty apps
  • Mobile app code audit
  • App maintenance and releases

02 · Your shop

Online shops

  • Online shop development
  • Shop app analytics
  • Plan and prototype before you build

03 · Systems behind them

Integrations

  • ERP, warehouse and payments
  • AI for one manual process
  • Workshops and estimate

Before a call

  • App cost estimateScope and a budget range
  • Shop platform adviserDecisions, risks and options
  • Shop cost over 5 yearsOff-the-shelf or custom, compared
All services →
Projects+−
  • SFD100,000+ downloads · 4.9 App Store rating
  • Mój Świat Książki100,000+ downloads
  • EMKA5000+ downloads in first month
  • All 120+ projects →
  • App ideas library
Company+−
  • About usWho we are and how we work
  • CareersHow we work and open roles
  • Contact[email protected]
  • TechnologiesReact Native, MedusaJS, Node.js and the rest
Blog→
Book a free consultation

5.0 on Google · 4.9 on Clutch

Back to blog
Mobile apps
Published: November 20, 2026
9 min read

Custom CRM or Salesforce and HubSpot: what should a field sales team choose?

Off-the-shelf CRM or a custom app for field sales: data model, offline work, API limits and ERP integration, licensing model, data processing terms and the hybrid option. Based on Salesforce and HubSpot documentation.

Mikołaj Lehman, CEO & Founder, GMI Software
Mikołaj Lehman
CEO & Founder, GMI Software

In brief

An off-the-shelf CRM such as Salesforce Sales Cloud or HubSpot Sales Hub gives you customer and deal records and a mobile app from day one, paid as a per-user subscription. A custom CRM or a custom field sales app makes sense when the field process needs ERP data, full work without coverage or a data model your plan cannot handle. There is also a hybrid: the off-the-shelf CRM as the system of record and a custom mobile app connected to it and to the ERP through APIs.

An off-the-shelf CRM such as Salesforce Sales Cloud or HubSpot Sales Hub gives you customer and deal records and a mobile app from day one, paid as a per-user subscription. A custom CRM or a custom field sales app makes sense when the field process needs ERP data, full work without coverage or a data model your plan cannot handle. There is also a hybrid: the off-the-shelf CRM as the system of record and a custom mobile app connected to it and to the ERP through APIs.

The short answer

Sources checked on 20 November 2026.

This guide is for the person deciding whether a sales team that visits customers should get an off-the-shelf CRM or a system built to order. We compare Salesforce and HubSpot with a custom solution on the basis of vendor documentation, pricing pages and agreements, without rankings and without prices.

The short version: start with an off-the-shelf CRM if your process fits its objects, its mobile app and the limits of your plan. Consider a custom solution when a field rep needs price lists, stock and orders from the ERP, offline work beyond what the standard app's offline mode covers, or screens the standard app does not offer. Between these extremes there is the hybrid option described in section 6.

1. The comparison in one table

The table collects the differences that matter for a field team. Details and sources are in the following sections.

1. The comparison in one table
CriterionSalesforceHubSpotCustom CRM
Billing modelPer-user, per-month subscription, features depend on the editionPaid Sales Hub plans priced per seatBuild and maintenance on your side or your contractor's
Custom data objectsCustom objects on the platformCreating custom objects with an Enterprise subscriptionAny data model
Work without coverageCached viewing and Offline Edit in the mobile appRead-only offline mode on paid plansYou design the offline scope
API limitsDaily allocation depending on edition and number of licencesPer-10-second and daily limits depending on the subscriptionYour own limits and infrastructure cost
Personal data processingSalesforce as processor under its DPAHubSpot as processor under its DPAProcessing agreement depending on the contractor's and host's role and access to the data

The entries refer to plans and editions described in the documentation on the day of checking. Before you decide, compare them with the offer for your number of users.

2. What an off-the-shelf CRM gives you on day one

An off-the-shelf CRM means records for companies, contacts, deals and tasks, reports and a mobile app maintained by the vendor. You do not build sign-in or permissions from scratch.

According to the HubSpot article on working with records in the mobile app, a rep can view and manage contacts, companies, deals, leads, tickets and custom objects, for example log a call right after an in-person meeting. Creating and editing records requires a network connection.

According to the Salesforce Sales Cloud pricing page, the product follows a per-user, per-month subscription model, and the editions differ in their features. The subscription fee therefore grows with the number of reps and the chosen edition, while the total cost can also include implementation, configuration and integrations.

According to the HubSpot Sales Hub pricing page, paid plans are priced per seat.

The limit is the data model. The HubSpot documentation on custom objects states that creating and editing them is available with Enterprise subscriptions, and that the number of objects and properties depends on the subscription. If your process needs its own data types, check which plan covers them.

3. Field work without coverage

A rep in a warehouse, a shop basement or outside the city may have no network. For a field team it is worth establishing when choosing a CRM: what can be done without a connection and what happens to the data when it returns.

According to the HubSpot article on offline access, offline mode in the mobile app is read-only, available on paid plans and has to be switched on while online. The app keeps up to 50 recently viewed records for each of contacts, companies, deals and tickets, with their latest activities, without custom objects and attachments, and without a network you cannot create or edit data. Accounts storing sensitive data are excluded from this mode.

According to the Salesforce documentation on working offline, the Salesforce mobile app caches recently used records for viewing, and Offline Edit, once enabled by an admin, lets users create, edit and delete records without a connection. Changes sync when the network returns, and the app warns about conflicts. The documentation also notes that not all Salesforce data is available offline.

A separate mechanism is Briefcase Builder, used to select the records loaded for offline work. According to the list of mobile apps compatible with briefcases, it works with the Field Service mobile app, Salesforce Mobile App Plus and a custom-built app configured to sync with a briefcase.

According to the Briefcase Builder limits documentation, it is available in Enterprise, Performance, Unlimited and Developer Editions, and up to 50,000 offline records per user can be loaded across all active standard briefcases.

According to the article on briefcases in Salesforce Mobile App Plus, offline capabilities are no longer available with new Mobile App Plus contracts as of 31 July 2026, while companies that currently use offline capabilities can keep using and renewing them under their contract. The restriction in this article applies to Salesforce Mobile App Plus contracts.

The Field Service app is intended for service technicians. According to the Field Service mobile app overview, it is built for offline work and requires a suitable edition and a Field Service Mobile licence.

For the Field Service app in Performance and Unlimited Editions there is also a High-Volume Briefcase. According to the High-Volume Briefcase limits documentation, a user can retrieve up to 400,000 records offline across active briefcases of this type.

In a custom system you design the offline scope yourself: which data goes to the phone, how conflicts are resolved and what happens to an order placed without a network. This gives freedom, but also means responsibility for synchronisation and its tests.

4. ERP integration and API limits

A field rep needs data that is not created in the CRM: customer-specific price lists, product availability, credit limits and order status. This data lives in the ERP, so the CRM or the app has to fetch and refresh it.

Every such sync consumes API calls. According to the HubSpot API usage guidelines, limits depend on the subscription and on how the app is distributed: privately distributed apps have a per-10-second limit per app and a daily limit for the whole account, both higher on Professional and Enterprise, and the search API has its own, lower limits.

In Salesforce the daily API allocation depends on the edition and the number of licences. According to the Salesforce limits reference, for Enterprise Edition (the edition name used in that reference) the 24-hour allocation is 100,000 calls plus the number of licences multiplied by the calls assigned to the licence type, plus purchased add-ons.

With a large catalogue and many reps these limits shape the architecture: refresh frequency, fetching changes instead of full lists and queuing writes. We describe how to split data between the ERP, the CRM and the app in our guide to ERP integration for a field sales app.

In a custom system you set the limits yourself, but you pay for servers, monitoring and handling integration errors. The difference is who is responsible for throughput, not whether integration is needed.

5. Personal data and the processing agreement

A CRM stores personal data of customer contacts, and your company is their controller. Whether the CRM vendor, the contractor or the hosting provider is a processor and needs a processing agreement depends on its actual role, its access to the data and the way it processes it.

Under Article 28(3) GDPR, processing by a processor is governed by a contract or other legal act that sets out, among other things, the subject matter, duration, nature and purpose of the processing and the type of personal data.

According to the HubSpot Data Processing Agreement, HubSpot acts as a processor of customer personal data in the subscription services, except for its data enrichment products and the HubSpot tracking code with Intent data sharing enabled, where each party acts as a controller.

According to the Salesforce Data Processing Addendum, Salesforce as processor processes personal data on behalf of the customer and on its documented instructions.

With a custom system a processing agreement with the contractor or the infrastructure provider is needed when they process data on your behalf, and you choose the infrastructure provider yourself. This gives control over where the data is stored, but also requires your own access rules and backups.

6. The hybrid: off-the-shelf CRM plus a custom field sales app

The choice does not have to be binary. An off-the-shelf CRM can stay the system of record for the sales department and management, while field reps get a custom mobile app built for their process.

Such an app fetches customers and deals from the CRM and price lists, stock and orders from the ERP, keeps the required slice of data on the phone and sends changes when the network returns. Management still reports in the CRM, and the rep works on screens designed for a customer visit.

The cost of this option is CRM licences for the users who use it, plus building and maintaining the app with its integrations. The risk lies in integration: API limits, changes on the CRM vendor's side and data conflict handling require tests and monitoring.

7. When to choose which option

The conditions below are not a rule, only a starting point for a conversation with the sales and IT teams. Check each of them against your own process.

  • Off-the-shelf CRM when the process fits the standard objects, reps have coverage or offline viewing is enough, and ERP integration is limited to a few fields.
  • Hybrid when management wants reports in a familiar CRM, while the field rep needs ERP data, order entry and work without a network.
  • Custom CRM when the data model and process are specific enough that the licences and configuration of an off-the-shelf system do not cover the needs, and the company is ready to maintain its own system.

8. How to decide in five steps

Before you sign a licence agreement or order a project, test the assumptions on a real process. Carry out each of the steps below with the reps involved.

  1. Describe one customer visit step by step: what data the rep views, what they enter and what they send to the ERP.
  2. Check coverage in the places where reps work and decide whether offline viewing is enough or editing is needed.
  3. Count the API calls for syncing customers, price lists and orders at the target number of reps and compare them with the plan limits.
  4. Compare the cost of licences for the target number of users with building and maintaining the app and its integrations.
  5. Establish who processes the data on your behalf and check with whom a processing agreement is needed.

Frequently asked questions

Does HubSpot work offline in the mobile app?
Yes, but read-only and on paid plans. Offline mode has to be switched on while online, and it covers a limited number of recently viewed records. Creating and editing data requires a network.
Can data be edited without internet in the Salesforce app?
Yes, Offline Edit in the Salesforce mobile app lets users create, edit and delete records without a connection, and changes sync when the network returns. Not all Salesforce data is available offline, so check the scope against your process.
How does a custom CRM compare with licence costs?
An off-the-shelf CRM is a per-user or per-seat subscription fee that depends on the edition. A custom system means the cost of building, hosting and maintenance. The comparison only makes sense for your number of users, integration scope and a horizon of several years.
Can an off-the-shelf CRM be combined with a custom mobile app?
Yes. Salesforce and HubSpot provide APIs through which a custom app can read and write records. You need to account for the plan's API limits, user permissions and conflict handling for offline work.

Let's talk about an app for your field sales team

Use the form to tell us which CRM and ERP you use and what a rep's visit looks like, and we will help you assess whether an off-the-shelf CRM is enough or a custom app is needed.

Content updated: November 20, 2026

Mikołaj Lehman, CEO & Founder, GMI Software
Mikołaj Lehman
CEO & Founder, GMI Software

Mikołaj Lehman is the CEO and founder of GMI Software. On the blog, he covers decisions around mobile apps, ecommerce and digital product delivery.

  • Mobile apps and React Native
  • Headless and B2B ecommerce
  • MedusaJS
  • Digital product delivery

Google Preferred Sources

See GMI more often in Google

Add gmi.software as a preferred source. Google may highlight our new articles more often in Top Stories and supported AI experiences.

Share article:

Related articles

Mobile apps

How to build a mobile app for your company: stages from idea to store release

The mobile app development process for a company, step by step: needs analysis, technology choice, design, development and testing, App Store and Google Play developer accounts, release and maintenance. With store requirements checked against Apple and Google documentation.

→
Mobile apps

Upgrading React Native and moving to the New Architecture: a step-by-step plan

A plan for upgrading a React Native app: why version 0.82 and Expo SDK 55 run only on the New Architecture, how to inventory libraries, which version path to take, how to test and what the effort depends on.

→

Let’s discuss your project.

Tell us what you need. We’ll suggest the next step.

[email protected]
gmi.software Sp. z o.o.ul. Jana Heweliusza 11 / 819
80-890 Gdansk, Poland
Rated 5.0 out of 5 on Google5.017 client reviews on Google
TechnologiesReact NativeExpoNext.jsReactTypeScriptMedusaJS3D configuratorsNode.jsNestJSPostgreSQLDockerAWSPlaywrightMaestro
© 2026 gmi.software Sp. z o.o.
Privacy PolicyTerms