Case Study: CARPL.ai

Context

CARPL.ai develops an AI platform for radiology workflow automation and clinical quality improvement. The company was expanding its product capabilities and exploring opportunities to deploy the platform across external ecosystems, including integrations with organizations such as GE.

I joined the company for a six-month period to help stabilize engineering operations, clarify the product and platform narrative, and review the underlying technology architecture.

At the time, the product had strong technical foundations, but engineering execution and product articulation had not yet matured to support the next stage of platform expansion.

Friction

Several structural issues were slowing the team's ability to execute and scale.

Engineering Execution

Development work was not consistently organized into structured planning cycles.

Features sometimes moved into development without clearly defined requirements, and the workflows connecting subtasks were not always documented. This made coordination harder and reduced predictability in delivery.

Organizational Structure

A large portion of engineering responsibility and operational knowledge was concentrated in a single contributor.

While the team was technically capable, this concentration of knowledge created execution risk and limited the team's ability to distribute ownership effectively.

The organization also needed stronger day-to-day engineering coordination.

Product and Market Narrative

CARPL.ai was pursuing opportunities to deploy its platform through external partnerships.

However, the product offering had not yet been clearly articulated in a way that external partners or investors could easily understand.

Key elements such as target customer, benefits, product packaging, pricing model, and architectural components needed to be clearly defined.

Technology Architecture

The platform architecture had evolved organically during early product development.

While the system functioned well, several foundational aspects had not yet been formally documented:

  • System architecture
  • Core data model
  • Feature-level development effort
  • Technology cost visibility

This made roadmap planning and external communication more difficult.

Intervention

The engagement focused on introducing structure in three areas.

Objective 1 — Align engineering execution with product planning

Engineering work was reorganized around structured development cycles.

This included:

  • Organizing engineering tasks into pre-planned sprint cycles
  • Requiring clear requirements before development began
  • Defining workflows for subtasks
  • Assigning ownership before execution started

These changes improved coordination and made delivery more predictable.

Objective 2 — Clarify the product offering

A structured articulation of the CARPL.ai platform was developed to support external conversations.

The product narrative addressed several core questions:

  • Who is the platform for?
  • What benefits does it deliver?
  • How is the offering packaged and branded?
  • How is it priced?
  • What architectural components define the platform?

This allowed the company to communicate the platform more clearly when engaging with partners and investors.

Objective 3 — Establish architectural and development visibility

The underlying technology architecture was documented to support planning and decision-making.

Key outcomes included:

  • A clear system architecture diagram
  • A defined data model
  • The ability to derive feature-level development effort from JIRA estimates

This provided leadership with a clearer understanding of engineering investment and roadmap feasibility.

Structural Changes

By the end of the engagement:

  • Engineering work moved toward structured sprint-based planning
  • Product features entered development with clear requirements and defined workflows
  • Operational knowledge began to spread across the engineering team
  • The CARPL.ai platform offering was clearly articulated
  • Architecture and data models were formally documented

Outcomes

These changes positioned CARPL.ai to:

  • Engage external partners with a clearer product narrative
  • Plan engineering work with greater delivery predictability
  • Evaluate technology investment with better architectural visibility

The engineering organization moved closer to a structure capable of supporting platform integrations and continued product expansion.