Menu

Product development / Design systems / Platform engineering

Launchpad.

The design.
The software.
The system behind both.

We created Launchpad to turn complex digital businesses into connected experiences. It brings together the way we design a product and the technology we use to build, deliver and evolve it.

Cloudflare-powered software. Deployed into Kajabi. Developed through real client work.

01 / The starting point

The same problems.
A better foundation.

A creator’s business is more than a website. It can be a storefront, a learning platform, a content library and a member community, all at once.

Our delivery work kept exposing the same friction: disconnected journeys, repeated development and customisations that became harder to maintain as a business grew. Kajabi provided the business platform. We wanted more control over the experience around it.

Launchpad grew from that problem. The aim was to make the underlying work reusable while giving each business room to look, feel and operate differently.

02 / What we created

Two disciplines.
One connected system.

Launchpad Design defines the experience. Launchpad Software makes it work and gives it a foundation for continued development.

The experience

Launchpad Design

Start with the business, the audience and the journey. Translate those decisions into a blueprint for the platform.

  • Discovery & strategyGoals, audiences, content, brand and the actions that matter.
  • Reusable design foundationsPage structures, interface patterns and brand rules that can be adapted across projects.
  • Working prototypesConnect public pages, offers, onboarding and member areas, then test the journey before refining it.

From a business problem to an experience people can use.

The engineering

Launchpad Software

Turn those blueprints into functioning platforms using shared source code, configurable components and supporting cloud services.

  • A common component libraryBlocks, sections, snippets, scripts and styles shared across builds.
  • The Launchpad EngineA compiler that assembles source and configuration into website, landing-page and marketplace/product themes.
  • Delivery & operationsCloudflare-hosted assets, stylesheet distribution, site registration and versioned theme delivery.

From a blueprint to software that can be built and maintained.

03 / How it works

Built together.
Delivered in layers.

The theme installed in Kajabi is one part of Launchpad. The shared software and Cloudflare services around it are part of the same system.

Design & build

  1. 01Business blueprintJourneys, brand & configuration
  2. 02Shared libraryBlocks, sections & source code
  3. 03Launchpad EngineCompile & package a theme

Deployment & delivery

CloudflareThe supporting software

Workers and storage deliver shared assets and customer stylesheets, supported by registration and update services.

KajabiThe customer experience

The compiled theme is installed into the customer’s site, connecting its design with Kajabi content, products and member journeys.

System overview: the build process produces the Kajabi theme; Cloudflare services support the deployed experience.

Rocket: keeping the design connected

Rocket brought together a stylesheet updater, cloud storage and delivery, with Mission Control registering customer sites. It addressed a practical question: how can a shared styling system support different customer brands beyond the initial installation?

04 / Research & development

The difficult questions
became the work.

Launchpad developed through successive prototypes and releases. The research was in how these parts could work together under real platform constraints.

01

How do you reuse a system without repeating the same design?

What we explored

Separate brand rules, page structures and configurable blocks. Test them through working prototypes for different customer journeys.

What we learned

Reuse needs to happen beneath the finished experience. A shared foundation still has to leave room for a business’s identity.

02

How do you build beyond the limits of the host platform?

What we explored

Work within Kajabi’s Liquid templates while moving shared scripts, styling and supporting services into a cloud-delivered layer.

What we learned

A hybrid architecture creates more possibilities, but also makes compatibility, loading behaviour and platform changes part of the engineering work.

03

How do you improve shared software without breaking individual sites?

What we explored

Develop common-source compilation, versioned builds and a stylesheet update workflow. Test changes against different configurations.

What we learned

Compilation reduces repeated assembly; it does not remove the need for release checks, migration testing and a clear separation between shared and customer-specific code.

05 / The next question

Built from experience.
Still evolving.

Launchpad gave us more than reusable components. It changed how we connect design decisions, software and the work of operating a product.

The work brought together blueprints, a shared component engine, compiled Kajabi builds and Cloudflare delivery services. Those foundations inform the Group’s ongoing platform work.

Where we are exploring next

Our next research asks how AI-assisted development can evolve this system: understanding existing components, rebuilding where needed and making upgrades easier to evaluate. Reliable end-to-end upgrade automation remains work to prove through testing.

Explore our client delivery work Back to our work

Our track record

Experience earned
by doing the work.

Client delivery. Products of our own. The everyday work of making them run. Each gives us a different perspective on what makes technology useful.

Explore our delivery track record

  • Grounded in real businesses

    Our team’s work connects brands, creators and educators with their audiences, through digital platforms and the systems behind them.

  • Built and operated by us

    We live with the products we create. Supporting them beyond launch informs the decisions we make on the next one.

  • Turning experience into what’s next

    Recurring problems become reusable technology. The questions still unanswered become the starting point for our research.