Turning repeated Unreal integration problems into a commercial proposition

MESH Interactive did not begin with a business plan. It began with the pain of integrating Unreal Engine systems that had never been designed to work together.

A locomotion framework might be excellent. So might interaction, inventory, weapons, vehicles or AI. The problem appears when several products need ownership of the same character state, input logic, animation behaviour or networking assumptions. A developer can own all the right pieces and still spend months making them behave like one product.

Marc Thornton and Raed Abbas encountered that problem while collaborating on the multiplayer conversion of the Character Interaction framework. Their working styles proved complementary: Raed brought deeper specialist expertise in Unreal networking and replication; Marc concentrated on systems coordination, product thinking, technical operations and the commercial layer around the work.

On 8 December 2018, Marc proposed taking the lessons beyond the immediate project and designing a cleaner reusable foundation. On 11 December, the pair agreed to pursue it as a 50/50 working venture. Marc proposed the MESH Interactive identity two days later and registered meshinteractive.com on 14 December.

The proposition was deliberately pragmatic.

MESH was not claiming that every gameplay system should be reinvented. Where strong marketplace technology already existed, it could be integrated, adapted and replicated. Bespoke functionality could then be built around the parts that genuinely needed to be unique.

The value was in the integration layer: making those parts function coherently inside a multiplayer-ready architecture.

Marc focused on turning that capability into something a studio could understand and buy. He created the name and identity, registered the domain, built the website and email infrastructure, established Discord, developed the positioning and licensing material, and worked on the commercial offer. Raed continued building demonstrations and specialist systems.

Public material eventually showed a broad set of interconnected areas including locomotion, cameras, pickups, save/load, character classes, inventory and equipment, vehicles, interaction, weapons, scopes and ballistics, combat, AI, looting and cooperative and competitive multiplayer.

That breadth needs careful attribution. Marc and Raed did not claim to have authored every underlying feature. MESH combined marketplace and bespoke technology. The proposition was the technical foundation and integration work required to make those systems function together.

The teaser launched publicly on 21 February 2019. The next question was whether studios would pay for the capability.

A small enquiry produced a formal estimate but did not convert. A more substantial opportunity followed in March. The prospective studio wanted to combine several major Unreal technologies, including Advanced Locomotion System, Survival Game Kit and Character Interaction, inside a multiplayer game. An NDA was signed and the discussions moved into detailed discovery covering cameras, character behaviour, inventory, vehicles, weapons, locomotion, interaction, melee, archery, lobby systems and network architecture.

Marc handled much of the client discussion, requirements, commercial framing and scoping while Raed concentrated on the specialist engineering questions.

The engagement exposed a problem that is common in complex technical sales. The client reasonably wanted proof that difficult elements could be solved before committing. The technical team reasonably wanted to demonstrate that capability. Prototype work began around areas including a true-first-person camera.

But the line between proving feasibility and beginning unpaid implementation became increasingly blurred.

By 19 March, expectations around scope, price, proof and deliverables had diverged enough that the engagement ended before any evidenced payment or paid production work began.

That unsuccessful sale became one of MESH’s most useful outcomes.

Today, we would draw the boundary earlier. Initial conversations should qualify the opportunity. Anything requiring meaningful architecture, experimentation or prototypes should move into a paid discovery phase with explicit outputs and acceptance criteria. Production should begin only after that uncertainty has been reduced in a controlled way.

MESH itself remained short-lived. The main build and market-development work ran through 2019, collaboration reduced later in the year and the domain was cancelled in December.

But it proved several things. A difficult one-off integration problem could reveal a repeatable market need. Specialist engineering could be turned into a clearer product proposition. And strong technical work still needs equally strong commercial boundaries around discovery.

That last lesson is now part of how Digital SHIFT approaches bespoke software and technical partnerships: learn enough before committing to the build, but do not disguise significant unpaid engineering as “just one more proof”.