Enter at least two characters

← All projects

Skillogs

An acquisition transferred the product. The next task was to make it operable under new ownership.

After C3 acquired Skillogs in 2020, SKWD took the CTO role, replaced the inherited implementation and onboarded C3 schools within three months without disruption. The engagement continued through product strategy, delivery systems, new features, LCP and native mobile applications before the complete product estate and operating knowledge were handed over.

  1. 01
    Problem

    Problem and people

  2. 02
    Product model

    System and scope

  3. 03
    What exists

    Working artifact

  4. 04
    Next test

    Field evidence

  5. 05
    Field proof

    Adoption and outcomes

  6. 06
    Repeatability

    Repeatable growth

The acquisition transferred ownership. Product and delivery still had to be rebuilt.

C3 had used the earlier Acarya platform before acquiring Skillogs in May 2020. A public January 2020 announcement recorded 350 C3 students on that system and a plan to reach 2,000 students in the following school year. The acquisition created a fixed delivery window: the product needed a new technical foundation, clear ownership and a school-ready release before the next intake. SKWD treated onboarding as part of product delivery, not as a separate activity after the build.

Separate participants

Operating gapNo accountable route from acquisition to launch

The business had acquired a platform, but the product, technical and onboarding decisions still needed one owner and one delivery sequence.

Hover to explore. Click an item to keep it selected.

What breaks

SKWD made strategy, product, engineering and delivery one responsibility.

SKWD did not continue the inherited implementation as a maintenance assignment. The CTO office defined the product and technical strategy, organized engineering priorities, and owned delivery through release and school onboarding. It also created the tools, working methods and decision routines the team needed to keep product work, releases and operational feedback moving in the same direction. The team performed a full technical overhaul and built the new Skillogs implementation from the ground up.

Participants

Shared operating layerNew Skillogs implementation

A multi-tenant learning system built for institutional programs, content, participation, progress and skills.

Hover or focus to inspect. Click to hold.

System outcomes

Connected modules

  • 01Web and blended learning

    Courses, live and asynchronous sessions, content, tests and progress

  • 02Back-office operations

    Institutions, tenants, users, roles, content and access

  • 03Skills and collaboration

    Skills context, messaging, comments and discussion

  • 04Certification

    A separate LCP product for certification management

  • 05Mobile learning

    Native iOS and Android access connected to Skillogs

  1. 01Take ownership

    Put product and technology decisions under the CTO office.

  2. 02Reframe

    Define the platform around C3 schools, users and the launch deadline.

  3. 03Build

    Replace the inherited implementation with the new Skillogs product.

  4. 04Onboard

    Configure institutions and move schools without disrupting their onboarding process.

  5. 05Extend

    Use operating feedback to add features, LCP and native mobile applications.

  6. 06Hand over

    Transfer the delivered product estate, tools and operating knowledge.

The initial release became the base for continued product delivery.

The first delivery was the new Skillogs web platform and a school onboarding process that ran without disruption. Work then continued through product strategy, feature development, delivery tooling, LCP and native mobile applications. Public product artifacts confirm that the customer-facing systems reached operation. SKWD leadership and the signed delivery archive establish the build and delivery responsibility.

  • 01 / LaunchNew Skillogs platformC3 schools

    Institutions moved onto a new multi-tenant learning implementation without onboarding disruption.

  • 02 / EnableDelivery tools and working methodsProduct and engineering teams

    Strategy, decision routines, release practices and purpose-built internal tools supported both the process and the product.

  • 03 / OperateWeb, blended learning and back-office operationsAdministrators and educators

    Courses, classroom and remote activity, content, participants, institutions and progress followed one operating system.

  • 04 / CertifyLearning Certifications PlatformC3 Institute and certification teams

    LCP provided a separate system for certification management.

  • 05 / MobilizeNative iOS and Android applicationsLearners

    Profiles, content, progress, notifications, skills and Open Badges became available through native applications.

  • 06 / SupportProduct operationsSkillogs and C3

    Architecture, maintenance, release work, support and feature delivery continued after launch.

  • 07 / CompleteFull product handoverC3 and the receiving organization

    The completed product estate, delivery knowledge and supporting material were handed over at the end of the engagement.

Delivered product system

Artifact available

Skillogs web, back office, LCP and native mobile

Public records show the released products. This page does not reproduce private interfaces or contractual material.

  • New multi-tenant Skillogs implementation and uninterrupted school onboarding
  • Web learning, blended delivery and institutional back-office operations
  • Product and delivery strategy supported by team tools and working methods
  • LCP built from the ground up and publicly launched in November 2022
  • Native iOS and Android applications connected to the web platform
  • Multi-year feature, architecture, maintenance, release and support record
  • Complete delivered product estate and operating knowledge handed over
  1. 01

    Acquisition premise

    C3 could use Skillogs as its institutional EdTech capability.

    C3 had already used the earlier platform and acquired the business ahead of a larger school-year rollout.

    C3 and Skillogs public acquisition history
  2. 02

    Technical decision

    The inherited implementation required a full overhaul.

    SKWD leadership chose a new implementation rather than extending the acquired codebase into the launch release.

    SKWD leadership statement and delivery archive
  3. 03

    Delivery model

    SKWD took the CTO role and built from the ground up.

    Product, architecture, engineering and onboarding were organized under one accountable delivery function.

    SKWD leadership statement and signed CTO office record
  4. 04

    Extended scope

    The engagement continued into certification and mobile.

    SKWD built LCP and the native iOS and Android applications as new products connected to the wider Skillogs ecosystem.

    SKWD delivery archive, public LCP record and application stores
  5. 05

    Completion

    The engagement ended with a complete handover.

    The delivered products, tools, documentation and operating knowledge were transferred when the project concluded successfully.

    SKWD leadership statement and delivery archive

The same delivery created business, operating and learner value.

01

C3 leadership

  • One accountable CTO function after the acquisition
  • A new platform aligned to the next school-year deadline
  • Product strategy and delivery tools that supported continued development
  • An EdTech capability carried into the later Imparare transaction
  • A completed engagement with the full delivered estate handed over
02

Schools and educators

  • Institutional onboarding onto the new Skillogs release without disruption
  • Web, classroom and remote learning activity in one operating system
  • Back-office control of institutions, users, content and access
  • Continuing feature delivery and product support after launch
03

Learners and certification teams

  • Web and native mobile access to the learning experience
  • Support for blended learning across in-person and remote activity
  • Progress, skills and Open Badge features in the released applications
  • A separate platform for certification management

The evidence is a completed enterprise engagement and a later transaction.

The project is presented as completed client delivery, not as SKWD-owned intellectual property. Public sources establish the acquisition, institutional use, released products and C3’s later transaction into Imparare. Signed agreements establish the multi-year CTO, product, delivery, engineering, maintenance and support relationship without requiring public disclosure of contract values. SKWD’s project record confirms successful completion and full handover.

May 2020C3 acquisition of Skillogs
City of Antony and Skillogs company history
The acquisition set the business context and the deadline for the new platform delivery.
3 monthsNew platform and uninterrupted school onboarding
SKWD leadership statement and delivery archive
The CTO model joined strategy, product, engineering, delivery and rollout under one deadline without disrupting onboarding.
November 2022Public LCP opening and C3 transaction
French public record and transaction reporting
Certification software reached operation in the same period that C3 joined Imparare.
iOS + AndroidReleased native applications
Apple App Store and Google Play
The mobile product became a public operating artifact connected to Skillogs.
Client and product owner
C3 / Skillogs, now part of Groupe Imparare

SKWD is presented as CTO and product engineering partner, not as the owner of Skillogs.

defined
Engagement model
CTO office and dedicated product engineering

The work connected product leadership, architecture, engineering, onboarding, maintenance and support.

defined
Commercial record
Multi-year signed relationship

The relationship is documented. Contract values, revenue shares and annex terms are not public case-study content.

defined
Engagement completion
Completed and handed over

The project concluded successfully and the full delivered product estate was transferred. No active SKWD operating role is claimed.

defined

The launch gate was passed when C3 schools moved onto the new platform.

Validation gate

The new owner could operate the acquired EdTech business on a new product foundation.

Passed for the delivered scope

What must be true

  • defined
    Product replacement

    The inherited implementation was replaced by a new Skillogs platform built under the SKWD CTO office.

  • defined
    Institutional rollout

    C3 schools were onboarded onto the new version within the three-month delivery window without disruption.

  • defined
    Product extension

    The delivery continued into LCP and released native iOS and Android applications.

  • defined
    Ownership boundary

    Skillogs remains third-party intellectual property and is now part of Groupe Imparare.

  • defined
    Project completion

    The complete delivered product estate, supporting material and operating knowledge were handed over successfully.

Required owner

C3 leadership, school teams and the SKWD CTO office.

Stable onboarding gave the team room to keep improving the product.

C3 schools completed onboarding without disruption. After that initial chain was working, SKWD continued to add features and improve the product through live operating feedback. The work expanded into LCP and the native applications while the same delivery strategy, team tools and release routines supported the process behind the product.

The project closed with the complete product estate handed over.

The engagement was completed successfully. SKWD handed over the delivered platforms, applications, tools, documentation and operating knowledge. C3’s later acquisition through Imparare provides the wider business outcome around the work, while the case study remains precise about ownership: Skillogs belongs to Groupe Imparare, and SKWD’s role was the completed CTO, product and delivery engagement.

The Skillogs engagement is the reference for CTO-led product overhaul.

01

SKWD carries in

  • CTO ownership across product, architecture and engineering
  • Experience replacing an inherited implementation before launch
  • Delivery strategy, team tooling and operating methods built around the product
  • Delivery across web, certification, mobile, maintenance, support and handover
02

This venture adds

  • A product and technical audit tied to the acquisition thesis
  • One release plan for rebuild, migration and onboarding
  • An accountable product engineering function around the new owner
03

External proof needed

  • A defined business owner and launch deadline
  • Access to the inherited product, team and operating constraints
  • Authority to make product, architecture and delivery decisions

Next step

Turn an acquisition thesis into a stable product and a controlled handover.

Bring the inherited product, business objective and launch constraint. SKWD will define the CTO responsibility, delivery strategy, overhaul boundary and path from first release to handover.

Skillogs is a Groupe Imparare product. C3 acquired the earlier Skillogs business and platform in 2020. SKWD leadership and signed delivery records establish SKWD’s CTO, product, delivery and build role, the uninterrupted school onboarding, continued feature development and the successful full handover. Public sources independently confirm the acquisition, institutional use, LCP launch, mobile applications and C3’s later transaction into Imparare. The page does not claim that SKWD currently owns or operates Skillogs.