PANDA: Digital Transformation and CTO-as-a-Service

PANDA Tierversicherung offers digital, sustainable pet insurance for dogs and cats, developed in partnership with InterRisk Versicherungs-AG. 

They emphasize transparent, fair coverage, including “protection budgets” for diagnostics and treatment, accident coverage, and international travel protection. Their mission is to provide optimal insurance driven by a genuine love for animals and a desire for product clarity.

Prior to our engagement, PANDA was facing a critical bottleneck. They were in a rapid transition phase requiring heavy backend development and automation but lacked the technical leadership to manage it. The infrastructure was unstable, often requiring manual restarts of the customer portal every few days.

The organization faced a fragmented operational reality:

• Role Ambiguity: The technical leadership gap required a hybrid solution combining the roles of Tech Lead, Architect, CIO/CTO, and Project Manager.
• Operational Friction: Processes were handled largely via email with “open scope” tasks, leading to frequent scope creep and a lack of clear documentation.
• Legacy Debt: There was significant legacy code and reliance on third-party vendors where integration errors and regressions were common.

The objective was to stabilize the ship while simultaneously building for the future – securing a trusted partner to take ownership of end-to-end development under strict time constraints.

Civitta acted not just as an outsourcer, but as a strategic “Inside-Out” partner. To address the chaotic environment, we moved beyond simple staff augmentation to a CTO-as-a-Service model. We recognized that PANDA didn’t just need code; they needed process organization and a bridge between business goals and technical execution.

Our strategy focused on three pillars:

1. Triage and Stabilization: We immediately separated “Development” (important strategic work) from “Support” (urgent fixes). We utilized existing vendors for urgent fixes on systems they built, while our core team focused on stabilizing the platform and developing new features.
2. Process Professionalization: We transitioned the workflow from chaotic email chains to structured Project Management using Jira and Confluence. This included introducing proper documentation for critical business areas like MTA documents and revocations.
3. Quality Assurance (QA) First: We introduced a rigorous QA process to stop the cycle of constant regressions. This ensured that new features shipped were stable, protecting the product from issues caused by third-party integrations.

We provided a comprehensive technical ecosystem, covering strategic leadership and hands-on engineering:

1. Strategic CTO & Governance
       – Vendor Management: Coordinated with third-party vendors to define responsibilities, enforce code quality, and ensure the resolution of previous errors.

       – Tech Roadmap: Developed the technical vision, ensuring alignment between business goals (CxO level) and IT infrastructure.

       – Process Documentation: Established documentation standards and tracked history to prevent knowledge loss.
   

2. Platform Engineering & Development
       – Infrastructure Stabilization: Set up and launched replica databases to optimize data retrieval directly from Insly, removing load from critical systems.

       – Node.js + React Development: Full-stack development including refactoring, optimization, and test coverage.

       – Admin UI Creation: Developed a specialized Admin UI with CRUD capabilities, empowering non-technical team members to manage features without developer intervention.

       – Data Migration: Successfully imported historical data from legacy DB and implemented a UI to interact with it.

3. Automation & Intelligence

       – OCR & LLM Integration: Switched to new OCR/LLM solutions to improve data quality and resolve long-term data ingestion issues.

       – BI & Analytics: Assisted in setting up PowerBI dashboards for better business intelligence visibility.

Despite a highly pressured and unstable environment, our intervention delivered critical stability and operational maturity:

• Platform Stability: We achieved a stable platform where the customer portal no longer required frequent restarts. Features shipped under our new QA protocols experienced zero regressions.
• Operational Efficiency: By introducing the Admin UI and improving OCR data quality, we reduced the manual workload on the operations team and streamlined data entry.
• Vendor Accountability: We successfully managed third-party partners, ensuring they fixed historical errors and clearly defined the responsibilities between the business, the dev team, and external support.
• Business Continuity: We successfully released the updated platform and completed necessary data migrations, allowing the business to continue growing its subscriber base without technical interruption.

1. Strategic Separation of Streams: In complex legacy environments, it is vital to separate “Urgent” (Support) from “Important” (Development). By splitting these streams, we ensured that strategic goals progressed even while fires were being put out.
2. Process over Code: The biggest “tech” debt is often “process” debt. Introducing Jira, documentation, and proper scope definitions was as critical as the code itself. Educating the client on the difference between email orders and structured backlog management is essential for long-term success.
3. Proactive Scope Management: In environments with frequent changes and legacy code, “open scope” tasks carry high risk. Future engagements require strict definitions of Done (DoD) and acceptance criteria to manage expectations and ensure 100% completion rather than 80-90%.
4. The “Integration” Challenge: Success in InsurTech requires deep integration into the client’s business logic. We learned that proactive collaboration with claims handlers and business teams is necessary to define logic early, preventing rework.