Omnilogic Labs

CASE // LEADERSHIP DEVELOPMENT // BUILD

One system underneath twenty-four shapes.

A global leadership-development and AI-adoption firm had a proven methodology at real scale — thousands of participants, well over a hundred workshops, programs running across four continents in eight languages. What it did not have was one system. The method had been prototyped as roughly two dozen standalone apps, with an ERP alongside for the business side. Powerful in pieces, unmanageable as a whole.

We consolidated it into a single multi-tenant platform organized around the firm's method — not around the accident of how each piece was first built — and migrated in phases so the firm kept running underneath the whole time.

MULTI-TENANTCONSOLIDATIONCONNECTOR-FIRSTGLOBAL / MULTILINGUAL
FIG. TWENTY-FOUR_INTO_ONE
REF: CASE-LP-00Exploded assembly: two dozen independent prototype apps converging into one coherent platform

01 // The problem

Every new idea had become its own disconnected tool.

The firm had everything except coherence. A methodology that worked, a global program that filled, a roster of trainers delivering it in eight languages — and underneath, roughly two dozen apps that had each been spun up to chase a single idea, plus an ERP carrying the business side.

No shared users. No shared content. No single place that was the product. Each tool was correct in isolation and useless as a whole: a participant in one app did not exist in another, the method lived differently in each, and there was nowhere to stand and see the firm as one operating system.

REF: CASE-LP-01
// STARTING STATE
SCALE: THOUSANDS OF PARTICIPANTS
PROGRAM: 100+ WORKSHOPS
REACH: 4 CONTINENTS // 8 LANGUAGES
SYSTEMS: ~24 STANDALONE APPS + 1 ERP
SHARED: 0 USERS // 0 CONTENT // 0 SOURCE OF TRUTH

02 // The approach

FIG. PLATFORM_SPINE
REF: ARCH-LP-01Layered stack: content and user management as the spine, the firm's framework and trainer tooling built on top

Architect around the method, not the accident.

We designed a single multi-tenant platform to absorb the scattered prototypes and the ERP's relevant functions into one coherent system — organized around the firm's proprietary method rather than around the order in which each piece happened to be built.

The architecture treats the platform as a company portal. Content management and user management are the spine; the firm's framework, the trainer-facing tooling, and program delivery are built on top of that spine. The whole thing serves three audiences at once — corporate buyers, a reseller and trainer network, and individual educators — under one tenancy model.

Where two systems needed to talk, we favored standard connectors over bespoke agents, so the platform stays maintainable as it grows rather than accreting a new layer of one-off glue.

PRIN-01
hub

One spine

Shared content and user management as the platform's backbone — one identity, one library, everything else hangs off it.

PRIN-02
schema

Method as model

A data model that holds the firm's framework and trainer surfaces directly, rather than approximating it across two dozen schemas.

PRIN-03
cable

Connectors over agents

Standard, inspectable integration paths instead of bespoke automation — the kind of decision that keeps a platform maintainable at scale.

03 // What we built

A phased consolidation, sequenced to keep the lights on.

We scoped the work in phases — framework first, then the operational and trainer surfaces, then migration of the existing prototypes — so the firm keeps running while the platform comes together underneath it.

PHASE-01
account_tree
PHASE 01 // FRAMEWORK

The method, first

Model the firm's framework as the platform's core — the one structure all twenty-four shapes were really expressing — with content and identity underneath it.

PHASE-02
groups
PHASE 02 // SURFACES

Operate and deliver

Build the operational and trainer-facing surfaces on the spine — program delivery, the trainer network, and the business functions the ERP used to carry alone.

PHASE-03
swap_horiz
PHASE 03 // MIGRATION

Absorb the prototypes

Migrate the existing apps and ERP functions into the platform, retiring each only once its replacement is live — disruption-free, at four-continent scale.

What the platform carries

  • One tenant model serving corporate buyers, a reseller and trainer network, and individual educators
  • Shared content and user management as the single source of truth
  • The firm's proprietary framework modeled natively, not approximated
  • Trainer-facing tooling and program delivery built on the same spine
  • Connector-first integration with the systems that stay
  • Multilingual from the foundation — eight languages, not a translation bolt-on
FIG. PHASED_MIGRATION
REF: PLAN-LP-01Phased migration timeline: framework, then operational and trainer surfaces, then prototype migration, with the firm running throughout

04 // What made it hard

Finding the one model underneath twenty-four shapes.

The difficulty in a consolidation like this is not building new features. It is honoring a methodology that already exists in twenty-four different shapes and finding the single model underneath all of them.

We had to reconcile the client's own product language with the structure their work had actually taken, then design a data model that could hold all of it without flattening what made the method distinctive. The temptation in every consolidation is to standardize the texture away; here the texture was the product.

And it had to happen without disruption. Migration at four-continent, eight-language scale — with thousands of live participants and a full workshop calendar — was the constraint that shaped every decision. That is the knob worth turning: not what to build, but in what order, so the firm never feels the floor move.

FIG. ONE_MODEL_RESOLVED
REF: CASE-LP-04Signal extracted from noise: a single coherent model resolving out of two dozen scattered forms

05 // Outcome

Twenty-four apps and an ERP, replaced by one maintainable platform.

A single multi-tenant platform built around the firm's proprietary method, designed to carry its existing scale — thousands of participants and a global, multilingual workshop program — on one maintainable system.

The outcome figures here are directional, and the firm's method and identity are withheld by agreement. We're happy to talk through the architecture in more detail under NDA.

PROTOTYPE CONSOLIDATIONCONTENT + USER MANAGEMENTPHASED MIGRATION
REF: CASE-LP-05
// END STATE
SYSTEMS: ~24 APPS + ERP -> 1 PLATFORM
ORGANIZED AROUND: THE FIRM'S METHOD
CARRIES: GLOBAL // MULTILINGUAL SCALE
MIGRATION: NO DISRUPTION TO LIVE PROGRAM
// NEXT

Powerful in pieces? Let's make it one system.

If your product is really two dozen tools in a trench coat, the work is not more features — it's finding the one model underneath and consolidating onto it without stopping the business. That is exactly the kind of knob we know how to turn.

Start a conversationarrow_forwardBack to all work
Leadership Platform — One system underneath twenty-four shapes — Omnilogic Labs