Case studies / FrontM

Client success story GCC Engineering

FrontM builds product capability with NetSet Software's Build–Operate–Transfer model.

12 team members. A two-year engagement. A team transferred to FrontM with technical handover—after developing and maintaining frontend web and mobile experiences for its maritime platform.

FrontM

Maritime communication & workforce platform


12

team members building
lasting product capability

NetSet Software Frontend & mobile engineering

Build · Operate · Transfer — the engagement at a glance

12members

in the engineering team

2years

of development and maintenance

Team

Transferred to FrontM following the engagement

Handover

Technical handover included in the transfer

The partnership

More than application screens. A reusable product capability.

FrontM needed connected digital experiences for crew members, shore teams, medical professionals and administrators—within a platform that could serve different customers and work under shipboard connectivity constraints.

Over a two-year engagement, NetSet Software's 12-person team contributed to the development and maintenance of the frontend web application layer across medical assistance, entertainment, emergency support, crew management, social engagement and conversational workflows. The team also worked on Android and iOS implementations.

The team was subsequently transferred to FrontM, with technical handover included in the transition. The engineering transfer therefore delivered both product engineering and a team that could carry its accumulated knowledge into FrontM.

The contribution went beyond standalone modules. Shared rendering capabilities, reusable conversational interfaces and configurable micro-apps gave new use cases an existing foundation to build on.

One platform. Several engineering demands.

01 / Shipboard connectivity

Useful experiences on limited bandwidth

Designing lightweight frontend experiences for crew services and entertainment where connectivity can be constrained. Streaming still depends on available connectivity and provider services.

02 / Multiple stakeholders

Different roles. Connected workflows.

Supporting crew, doctors, support teams and administrators with interfaces appropriate to their responsibilities and access.

03 / Product reuse

New services without starting over

Creating shared frontend capabilities that could render supported backend message types and be reused across micro-applications.

04 / Customer variation

One foundation, many configurations

Accommodating customer branding, enabled modules, user roles and configurations within a common platform.

NetSet Software's GCC engagement model

Build the capability. Operate it. Transfer it.

NetSet Software's 12-person team developed and maintained the platform's frontend and mobile experiences during a two-year engagement, then transferred to FrontM with technical handover. This is the progression at the heart of the Build–Operate–Transfer model.

Build 12-person engineering team

Engineer around the client's product

For FrontM, the team developed frontend modules and shared platform capabilities, working with backend messages and teams to turn maritime requirements into connected user experiences.

Operate Two-year engagement

Carry product knowledge into ongoing delivery

The team maintained the web application layer and contributed to mobile implementation, retaining familiarity with common components, micro-app behaviour and customer configurations.

Transfer Team transfer + technical handover

Transfer the team with its technical knowledge

At the end of the engagement, the team was transferred to FrontM and technical handover was completed as part of the transition. FrontM received the team alongside the technical understanding developed through its work on the platform.

A two-year engagement delivered a platform contribution—and a team transferred to FrontM with technical handover.

NetSet Software × FrontM · Build–Operate–Transfer

Crew services. Connected through one platform.

Medical assistance

Crew, doctors & administration

Portals for medical requests, appointment booking and management, chat and calls, with administrative visibility into medical information and activities.

Entertainment

A lightweight shipboard experience

Integration with the customer's external streaming provider and a frontend experience optimized for limited bandwidth environments.

Emergency assistance

Connected requests & support workflows

Separate experiences for crew requesting help, teams handling requests and administrators overseeing activity.

Crew management

Users, roles & access

Administrative functionality to manage crew information, user access, available functionality and platform-level activities.

Guest engagement

Timelines, surveys & daily mood

Topic-based posts and interactions, questionnaires and daily mood surveys to help organizations stay connected with crew at sea.

Conversational workflows

One reusable chatbot interface

A common frontend component for order guidance, mini-surveys, information collection and chat activities across different use cases.

The engineering foundation

Implement a capability once. Reuse it across the platform.

The architecture's value was its ability to support different services and customers without repeatedly rebuilding the same frontend functionality.

Dynamic micro-apps

Shared rendering of backend messages

The frontend interpreted supported backend messages, events and data. Once a message type was supported, its rendering capability could be reused in other micro-applications.

Reusable components

A common interaction component

The same conversational interface could guide users, collect responses and support activities across multiple modules, rather than requiring a separate chatbot interface for each use case.

White-label configuration

Customer variation on a common foundation

Branding, module selection, configurations and roles could vary by customer while retaining shared platform capabilities.

Android & iOS

Native shells with web-based micro-apps

Native application components hosted much of the dynamic functionality through WebViews, allowing web micro-apps to be reused across platforms. Changes to native components could still require native releases.

Engineering value that compounds.

Reuse

A foundation for subsequent services

Shared rendering and conversational capabilities gave similar use cases an existing implementation to extend, reducing the need to develop equivalent functionality repeatedly.

Configure

Adaptability across customers

White-label branding, modules and access configurations supported customer-specific experiences on a common frontend foundation.

Connect

Web and mobile delivery

WebView-based micro-apps reused web functionality within Android and iOS applications, alongside native application components.

Transfer

An engineering team carried into FrontM

The 12-person team's transfer, including technical handover, carried knowledge gained during development and maintenance into the client's organisation.

FrontM's engagement demonstrates the full BOT progression: a team delivering product work, operating through development and maintenance, then transferring to the client with technical handover.

A clear contribution. A substantial engineering role.

NetSet Software's reported contribution covers frontend web application development and maintenance across the modules described here, alongside work on native Android and iOS components and WebView-based functionality.

The reusable conversational interface is described as frontend engineering; this case study does not claim that NetSet Software developed FrontM's underlying AI models or its backend systems.

FrontM's published metrics

4,000+ vessels · 100K+ professionals

FrontM also reports 50+ maritime operators engaged and 30+ partner apps at its Exchange. These are company-wide platform figures, provided for context but not necessarily contributed to by NetSet Software.

NetSet Software's engagement

12 people · 2 years · Completed transfer

The engagement figures describe NetSet Software's involvement. The frontend and mobile contribution is direct; NetSet Software does not claim credit for FrontM's complete platform or overall market reach.

Frontend web applications Dynamic micro-apps Native Android & iOS components WebViews White-label configuration Low-bandwidth UX

Contribution details are supplied by FrontM. FrontM report reviewed 17 September 2025; this case study describes NetSet Software's engagement and does not claim credit for FrontM's overall outcomes contributed to this engagement.

Build · Operate · Transfer · GCC

Build with NetSet Software.
Transfer into your business.

Establish an engineering team in India, operate it with NetSet Software, and plan its transfer into your organisation.

Discuss your GCC roadmap

Let's discuss your engineering plan

Share a few details. We'll get back to you shortly.

What would you like to discuss? *

Your details stay confidential · NDA available before detailed discussion