Service · App development

Custom B2B app development for business users.

A custom app for your professionals: engineers on site, sales reps at client meetings, buyers at a trade show. With SSO, role-based access, offline mode and integrations with your ERP and CRM, so the work carries on wherever the user happens to be.

SSO & SAMLMulti-tenantOffline modeERP integration

A B2B app isn't a consumer app with a different logo.

The user is a professional who opens your app daily or weekly to get work done: placing an order, completing an installation, approving a quote. Speed, reliability and context matter more than visual wow factor. A glitch costs money straight away or holds up a process somewhere down the chain. That changes how you design an app, how you build it and how you maintain it.

That's why, with a B2B app, we start by thinking about flows: what does the user need to do, in what order, and under what conditions (no signal, in a hurry, wearing gloves)? And about integrations: which systems need to supply or receive data so the app doesn't become an island? Compared with a consumer app, the emphasis shifts to authentication, role management, ERP integrations and audit trails.

We build B2B apps for service organisations, B2B brands, trade associations and enterprises. Sometimes a new app replaces a set of Excel files and emails; more often it sits alongside existing systems and opens up the specific part where mobile access makes the biggest difference: the engineer on the building site, the buyer at the trade show, the manager approving a quote on the move.

The ROI of a B2B app rarely lies in "nicer mobile working". It lies in less time per administrative task, fewer errors in orders, quicker invoicing because a job is closed off immediately, or more revenue per sales rep because they carry a complete catalogue with them. We measure those effects from day one, not to turn them into marketing material, but to base the next sprint's priorities on them.

Three types of B2B app we build.

Different audiences call for different architectures. We'll advise which one fits in our first conversation.

Single tenant · fixed sprint budget

Field service and sales force app

For engineers, installers and inspectors on site. Retrieve work orders, take photos, capture the customer's signature, keep working offline in a basement or roof gutter, and sync automatically as soon as there's a signal. Integrates with your planning and invoicing system and makes sure the back office sees in real time what's happening out in the field, without the engineer having to type up a report.

Offline modePhoto + signatureRoute planningPlanning integration
Multi-tenant · fixed sprint budget

Sales or order app for on the road

For sales reps, key account managers and wholesale buyers. A catalogue with customer-specific prices, an order book that also works on a trade show floor, integration with CRM and ERP, and in-app chat with the back office. Suited to distributors, dealer networks and B2B brands with an established customer base who want to simplify their ordering process without losing their grip on the customer relationship.

Customer-specific pricesCRM syncPunchOut/cXMLMulti-language
Multi-tenant · larger project

Enterprise or industry app

A mission-critical app with multiple organisational contexts in one codebase: a white-label app for a trade association, an approval app for a mid-sized corporate, or an onboarding app for a large employer. Deep integration with multiple systems, audit log, compliance requirements per industry. Often paired with its own admin portal in which your IT or operations team manages tenants, users and branding settings themselves, without having to call us.

White-labelApproval workflowAudit logNEN 7510 / ISO 27001

What sets a B2B app apart technically.

Four building blocks that show up in almost every B2B app, and that a consumer app usually doesn't need.

  • Single sign-on (SSO)Sign in via Microsoft Entra, Okta, Google Workspace or your own Keycloak, using SAML 2.0 or OIDC. Users use the account they already have, and IT administrators stay in control of permissions and offboarding.
  • Multi-tenant with role-based accessOne app, multiple organisations or branches. A user can belong to several tenants and switch between them. Roles (manager, field, viewer, approver) determine what is visible and editable, with tiered approval for large amounts or high-risk actions.
  • Offline mode that actually worksA local database (SQLite, Realm or WatermelonDB) with conflict resolution on sync. An engineer in a basement, a buyer on a trade-show floor with slow wifi or an installer in a village without 4G: the app stays usable and pushes changes as soon as there is coverage.
  • ERP and CRM integration at the core, not as an afterthoughtSAP, AFAS, Exact and Microsoft Dynamics on the ERP side; HubSpot, Salesforce and Dynamics on the CRM side. Customer data, price lists, stock and order status come from there. The app is a client that shows their reality, not a second source of truth.
  • Audit log + e-signing + document uploadWho approved, downloaded or changed what. A compliance requirement in healthcare, finance and construction. Plus document upload with server-side virus scanning and optional e-signatures for order confirmations.
  • Custom branding per tenantFor white-label or partner apps: each organisation gets its own logo, colours and, if needed, its own App Store listing. One codebase, multiple brands, manageable without a new release for every change.

B2B audiences we often build for.

A selection of the audiences for which a dedicated B2B app pays off. If you recognise yourself in one of these patterns, we'd be happy to talk further.

Field service

Engineers & installers

Field service management apps for service organisations, installation technology and maintenance. Work orders, time tracking, material usage, customer signatures and an automatic invoicing trigger as soon as a job is completed. See also our field service app page.

Sales on the road

Sales reps & dealer apps

Catalogue, customer-specific prices and an order book for sales reps and distributors. Syncs with CRM and ERP, works on a trade-show floor with slow wifi, and accounts for volume discounts per customer, contract prices and seasonal agreements that don't belong in a general price list.

Wholesale & purchasing

Buyers & procurement

Wholesale order books for trade shows (ISPO, PV shows, MIPIM), purchasing apps for mid-sized corporates with approval workflows, and PunchOut/cXML integration with enterprise procurement platforms such as Coupa, SAP Ariba and Ivalua, so your customers can order through their own e-procurement system.

Construction & contracting

Construction site & project apps

Apps for contractors, subcontractors and project managers. Work packages, time registration, snagging items, photos per construction site and integration with construction administration software. Also read about our approach to the contractor app.

Healthcare & labs

Medical and research

Healthcare apps compliant with NEN 7510 (for healthcare professionals, not directly for patients), and lab apps for sample tracking with an audit trail. Strict logging, encryption and role-based access per department, plus clear agreements on processing, hosting and data residency.

HR & L&D

Onboarding & training

HR onboarding apps for new employees (employee engagement) and corporate L&D apps for mandatory training, certification and compliance tracking, often linked to an LMS or HR system such as AFAS, Workday or SuccessFactors for automatic source data and expiring certifications.

How a B2B app project works with us.

1

Discovery and flow analysis

Together we map out which flows the app needs to support, which users will work in it, and which systems already hold data we can reuse. We often find at this stage that a considerable share of the requirements is already covered by existing system functionality, so there's no need to build it again. We also talk to a handful of future end users; their feedback on how they currently do their work often produces better requirements than an internal workshop alone.

2

Architecture, auth and integration spike

A short technical sprint in which we settle the key decisions: cross-platform or native, which auth provider to use, and how to connect to your ERP and CRM. We often build a working auth flow and one integration stub here, so we know the difficult parts work before we schedule feature work.

3

Iterative build in sprints

A working build every two weeks, tested by your key users and, where possible, by real users in the field. We work from a prioritised backlog rather than a fixed scope: whatever proves valuable in practice takes precedence over what was in the original document.

4

Field beta

A phased rollout to a pilot group: one region, one customer segment or one tenant. Sentry or Bugsnag for crash monitoring, Datadog or Mixpanel for usage. We measure what users actually do, and adjust wherever the assumptions turn out to be wrong.

5

App store release and ongoing support

App Store and Google Play release, with automated builds via Fastlane or App Center. For enterprise distribution, MDM/MAM (Intune, Jamf, VMware Workspace ONE) or your own internal store is also possible. After that comes ongoing support: security patches, OS updates, and further development based on usage data and new features. A dedicated support team knows the app and can quickly reach your IT organisation in the event of incidents.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

When to go custom and when to use a standard platform.

Not every B2B app has to be built from scratch. We're honest about when a standard platform is enough, and when custom development is worth the effort.

Often sufficient

Salesforce Mobile Publisher

If your flow sits almost entirely within Salesforce CRM and you only need a mobile shell, Mobile Publisher is usually the faster route. You keep the Salesforce data models and the Lightning UX, with your own branded container. We wouldn't replace it for commodity CRM mobile.

Often sufficient

SAP Mobile Services / Fiori

SAP-only workflows often run perfectly well through Fiori apps on SAP Mobile Services. We only come into the picture when your app also needs to do something outside SAP, needs a UX that Fiori doesn't offer, or when you want to bring several systems together in one user experience.

Sometimes sufficient

Power Apps, OutSystems, Mendix

Low-code platforms are strong for form-heavy mid-office apps. Limitations appear with offline work, complex UX, niche hardware (barcode scanners, NFC, BLE printers), or when per-user licence costs at scale exceed the budget for a custom build. Native push notifications and deep linking are also sometimes limited.

Custom pays off

When we do build

Deep integration with several systems at once (ERP + CRM + DMS + IoT), sector-specific compliance (NEN 7510, FSM, construction collective labour agreement), genuine offline mode, white-labelling for an industry association, or AI-augmented features that a standard platform can't deliver. A combination is often the right choice: low-code for the office modules, a custom app for the part that faces the outside world.

Tech stack and compliance.

Cross-platform or native

React Native or Flutter for cross-platform: one codebase, two platforms, fast iteration. Native iOS (Swift) or Android (Kotlin) when performance, security or platform-specific hardware is critical (think payment apps, biometrics, complex BLE integrations).

Backend and infrastructure

Cloud-native on AWS, Azure or GCP. Node.js, Spring Boot or .NET, depending on what your IT organisation has experience with. We would rather deliver a backend your team can maintain than an exotic stack that only we can work with.

Auth, CI/CD and monitoring

Firebase Auth, AWS Cognito, Auth0 or a self-hosted Keycloak for identity. Fastlane, App Center or GitHub Actions for CI/CD. Sentry, Bugsnag or Datadog for crash and performance monitoring in production.

Compliance by industry

GDPR is always the baseline. On top of that: NEN 7510 for B2B healthcare apps, ISO 27001 as the general security standard, the AI Act wherever there is AI functionality, CSRD for sustainability reporting, and EAA/WCAG for accessibility — B2B apps increasingly need to be accessible to employees with a disability too. We map out the compliance requirements early in the project, so that logging, encryption and data flows are set up correctly from the start.

Security practices in the app

Certificate pinning against MITM attacks, jailbreak/root detection where relevant, short-lived session tokens with a refresh flow, secure storage on the device for sensitive tokens and data, and code obfuscation for the release build. For healthcare and finance apps, we run an external pen test as standard in the final sprint before go-live, plus a SAST/DAST scan in the CI pipeline.

Push notifications for business events

No marketing pushes, just relevant business triggers: a quote has been approved, a delivery is scheduled, an approval is waiting for you, an SLA is about to be breached. Configurable per user and per channel type (push, email, in-app, SMS), with a log of what has been sent — so customer service can see what a user has actually seen.

Frequently asked questions.

What clients usually ask us before we start on a B2B app.

What is the difference between a B2B app and a B2C app?
A B2B app is used repeatedly by professionals for work: placing orders, completing an installation, giving an approval. What weighs more heavily: stable authentication (SSO), roles, offline working, ERP/CRM integration and an audit log. The UX is functional and fast — no onboarding funnel with confetti, but an interface that is still pleasant to use on day ten. A B2C app has to attract users; a B2B app must not get in their way.
How do we combine SSO and multi-tenancy in one app?
At login, we determine which identity provider belongs to the user's email domain (Microsoft Entra, Okta, your own SAML). After authentication, we retrieve which tenants the user has access to — often several for account managers or consultants. A tenant switcher in the app changes context, and the backend ensures that data stays strictly separated per tenant. For partners without their own IdP, an email magic link or a separate user management flow is an option.
Is offline mode really necessary?
For a sales rep in an office district: usually not. For an engineer in an underground car park, an installer on a building site without 4G, or a buyer on a busy trade show floor: yes. We build offline-first when interrupted work is a real risk. The technical complexity lies in conflict resolution during sync — two people changing the same record while offline — and we make clear decisions on that up front.
How do you integrate with SAP, AFAS, Exact and Microsoft Dynamics?
Via the official APIs or integration platforms where they exist: SAP via OData/RFC or Mobile Services, AFAS via GetConnector/UpdateConnector, Exact via REST, Dynamics via Dataverse. Where the API has limitations, we use an intermediate layer (Azure API Management, Mulesoft or a lightweight in-house integration service) to handle throttling, retries and caching properly. Also read about our approach to enterprise software integrations.
Cross-platform or native — what do you recommend?
Cross-platform by default (React Native or Flutter) unless there is a good reason to go native. Good reasons: heavy native hardware integration (BLE printers, NFC readers, biometric flows), payment apps where PCI-DSS strictly requires native, or performance-critical graphics. For 80% of B2B apps, cross-platform is faster to build, maintain and release.
What determines the cost of a B2B app?
The number of roles and flows, the depth of the integrations (one REST integration versus four bidirectional syncs), whether offline mode is needed, and which compliance requirements apply. A single-tenant app for one target group without offline work is fundamentally different from a multi-tenant white-label app with ERP, CRM and an audit log. In an initial conversation we scope together which variant fits — and which parts can wait.
How do you handle maintenance after launch?
OS updates from Apple and Google keep coming, integrations change, and security patches need to go in. We offer an ongoing maintenance contract with a dedicated team that knows your app: monitoring, crash fixes, library updates, security patches and further development based on what we see in the data. A fixed monthly price, transparent hours reporting and no lock-in — you can also hand maintenance over to your own team.
How do you handle the audit log and compliance reporting?
An audit log records, for every sensitive action, who did it, when, from which device and in which user role — immutable and exportable. For NEN 7510, ISO 27001 and internal audits, we deliver a dashboard plus automated reports. For enterprise software projects, we often agree the log fields in advance with your security officer.
Can you also take over an existing B2B app?
Yes, provided we can first carry out a short code audit. We map out the state of the codebase, dependencies, security and test coverage, plus the state of the App Store accounts and CI/CD pipelines. Based on that, we advise on what we can take over, what needs rebuilding, and which quick wins will get the app under control again.

Talk to us about your B2B app.

A no-obligation introductory call of half an hour. Tell us about your target group, your existing systems and the flows you want in an app — we ask questions, give direction and are honest about when custom development pays off and when a standard platform already does the job.

Edit content