Since 2011, building software that has to work in the real world.

INESSOFT is founded.

The name came from the most basic building blocks of programming: if, not and else. Those simple statements can be combined into systems of enormous complexity, which made them a fitting foundation for a software company.

The company began as a game studio on MXit, when the mobile social platform still offered an unusually open market for small developers. The King series — including Rugby Manager King and Football Manager King — grew into a family of 12 games and applications.

Game development and serious client systems run in parallel.

Shortly after launch, INESSOFT began delivering commercial software through partner relationships for major South African brands. One early system equipped field agents with a BlackBerry application for recording product placement, pricing and competitor information at store level. The captured data flowed to a central server and a Silverlight management dashboard, giving FMCG clients a detailed view of how products were performing in the field.

Projects during this period involved organisations and brands such as Dairybelle, Blue Ribbon, Tiger Brands, SABMiller, GSK, Vodacom, Rennies Distribution and The Creative Council. The systems were delivered through a partner channel, often with direct interaction between INESSOFT and the client teams using the software.

MXit products reach more than two million active user accounts at peak.

The MXit portfolio generated substantial passive income and exposed INESSOFT to the realities of operating multiplayer software at scale. Shared state had to remain coherent, database traffic had to be kept lean, failures had to be diagnosed with limited visibility, and thousands of concurrent users could expose bugs that never appeared in development.

The lesson was not only technical. It also established a permanent commercial principle: even a strong product needs distribution and marketing. Being early to MXit created an opportunity that later mobile and PC markets did not offer as freely.

The engineering boundary expands beyond the screen.

INESSOFT moved deeper into mechatronics, embedded systems and prototype development. Projects increasingly combined electronics, firmware, communications, software interfaces, data capture and server-side logic. That cross-domain capability later became one of the clearest differentiators of the business.

Prototype devices were taken from concept through working hardware and software, with clients retaining responsibility for final product certification while INESSOFT assisted with the technical path toward it.

Imported components create the foundation for Leobot Electronics.

Electronic parts were imported for a partner supplying school tenders. After the required kits had been assembled, surplus stock remained. At the same time, INESSOFT had developed a reusable ecommerce platform for several clients. The remaining components provided a practical way to test that platform as a real operating business.

A software test becomes a substantial ecommerce and distribution business.

The experiment succeeded. Leobot Electronics became the primary commercial focus, and much of INESSOFT's engineering effort shifted into Leobot's internal software and operating systems. The original ecommerce platform was continuously refined while supporting catalogue management, stock, orders, imports, pricing, customer communication and a growing collection of internal operational tools.

Systems developed around Leobot include supplier and import tooling, sales-growth systems, internal messaging, catalogue administration, stock workflows, school-kit generation and other software required to operate a real electronics business rather than a demonstration storefront.

Devices, communications and server software converge.

IoT work extended the earlier embedded capability into connected devices, telemetry, data logging and remote operational visibility. This period reinforced the need to treat firmware, communications, databases and user workflows as one system rather than isolated technical layers.

CAD design and 3D printing become part of the prototyping stack.

Mechanical design, enclosures, fixtures and iterative physical prototyping expanded the ability to turn an electronic concept into a complete working device rather than stopping at a breadboard or software mock-up.

Materials and process work extend the physical prototyping capability.

Work involving casting, materials and process experimentation expanded INESSOFT’s ability to develop specialised physical prototypes, fixtures, enclosures and product concepts beyond electronics alone. The emphasis remained practical: understand enough of the process to design, build and test the complete solution.

Software, electronics and physical product design operate as one discipline.

By this stage, the company could support projects from early technical concept through electronics, firmware, software, data capture, enclosure and prototype build. This became especially valuable for unusual products that did not fit neatly into a conventional software or electronics supplier category.

The software capability becomes visible again.

INESSOFT now operates publicly through If Not Else Software Solutions CC, focused on custom operational software, embedded-to-server systems, industrial and machine-data integration, SQL reporting, workflow automation, legacy rescue and specialist product development. Leobot remains a closely related operating platform and a source of long-running ecommerce, electronics and fulfilment experience.

This is not a game studio attempting a sudden pivot. It is the continuation of an engineering history dating back to 2011, in which game systems, business software, ecommerce, electronics and physical products progressively converged into the current operational-systems capability.