An acquisition can transfer a company or a product asset. It does not automatically create a product that people can operate, improve or trust.
The Skillogs record starts with that practical gap. C3 acquired Skillogs in 2020, but the product still needed a technical foundation, a delivery plan and a route for schools to move onto the new system. The work was not limited to replacing code. Product choices, engineering priorities, release decisions and school onboarding had to be owned together.
One operating line
The signed 2020 agreement established a dedicated delivery team and CTO office. In practice, that meant one function could connect the business need, the technical plan and the work needed to make a release usable for institutions.
This matters when a product has inherited constraints. If product strategy, architecture and delivery are split between separate owners, the first release can become a sequence of handoffs. Decisions arrive late, onboarding becomes a rescue task and technical debt sets the boundaries of the next product.
The Skillogs engagement took a different route. The record describes a new implementation built from the ground up, followed by school onboarding without disruption. It then continued through feature work, a separate certification layer and native mobile applications.
Delivery continues after launch
A launch is only one point in the operating life of an institutional product. After launch, teams still need to decide what to extend, what to support and what to hand over.
The public opening of the Learning Certifications Platform in November 2022 is one visible point in that longer delivery sequence. The signed licensing framework from November 2024 is another historical record of how the commercial arrangement developed. Neither point proves the current state of every module or present-day commercial activity. Together, they show that the work moved beyond a one-off rebuild.
What the case supports
The useful lesson is not that every acquired product needs the same team or process. It is that ownership needs to be explicit.
For a product inherited through acquisition, the first questions are practical:
- Who owns product and technical decisions through the next release?
- How will users, institutions and data move into the new system?
- Which parts of the product are safe to extend, and which need replacement?
- What does a complete handover include besides source code?
The Skillogs record supports a case for accountable CTO-led delivery across those questions. It does not establish the current operating status of the product after the documented engagement.