Helping Netomnia Evolve ODIN, the Platform Behind 3 Million UK Full-Fibre Installations

The Brief

Netomnia is one of the UK's most ambitious fibre network operators, building at serious pace and scale. As the business grew, ODIN became a key internal platform for managing the work behind network rollout and ongoing maintenance.

They needed experienced developers who could join an established team and start contributing quickly. Not a detached agency model, and not a lengthy onboarding exercise: a capable technical partner with strong expertise, able to work inside an existing product environment and add value from the outset.

This was a good fit for mmtm: stepping into a live product, understanding the context fast, and supporting delivery of meaningful improvements.

The Challenge

ODIN sits close to the operational core of the business. It supports the practical work of planning, building and maintaining fibre infrastructure, which means changes cannot be treated lightly.

The challenge was not simply to add development capacity. It was to do so in a way that respected the complexity of the platform, the pace of the business, and the number of teams relying on it.

That meant working in a codebase already in motion, delivering improvements without disrupting live operations, and making decisions that would hold up across a broad set of users and stakeholders.

It also meant navigating the realities of a growing organisation. ODIN had to serve planners, surveyors, network builders, internal operations teams, build partners and the wider commercial side of the business, while continuing to evolve as Netomnia expanded and later merged with brsk.

Our Solution

We joined Netomnia as an extension of their internal team, providing senior engineering support across the ongoing development of ODIN.

From the start, the focus was practical: understand the product quickly, fit into the existing delivery rhythm, and help move important work forward without adding friction.

Feature Development

We contributed to the continued development of ODIN, helping deliver new features and improvements across the platform.

Because the product is tied so closely to day-to-day operations, that work had to be grounded in how teams actually use the system. Good delivery here meant more than writing clean code. It meant making sensible product decisions, understanding operational dependencies, and building changes that worked in the real world.

Ongoing Support

Alongside roadmap work, we helped support ODIN as a live and evolving platform.

That included refining existing functionality, resolving issues and strengthening areas of the product where reliability and clarity mattered most. In an environment like this, ongoing support is not secondary work: it is part of what keeps the business moving.

Working Across Stakeholders

A major part of the engagement has been translating needs from across the business into focused technical delivery.

ODIN touches a wide group of people, each with different priorities and pressures. Our role is not just to build, but to help create alignment: taking operational requirements from multiple sides of the business and turning them into coherent scopes to deploy meaningful improvements inside the platform.

That becomes ever more important as Netomnia continues to grow and the brsk merger introduced further complexity, new relationships and a broader operational picture.

ODIN Today

ODIN remains a central part of how Netomnia runs its network build and maintenance operations.

Our work helped Netomnia add experienced engineering capability to a business-critical platform without slowing down delivery or creating unnecessary process. For businesses with an established product and an internal team already in place, that is often where mmtm is most useful: stepping into complexity, getting to grips with it quickly, and contributing where it counts.