Lenny Daume
Start a conversation
Mondosano GmbH Logo

Mondosano GmbH

Hamburg

Hands-on CTO for Health SaaS

Hands-on Chief Technology Officer & Head of Product

January 2018 - June 2020
2 years 6 months
Full-time
Product work
Hamburg

Relevance

Why this case matters

The case shows how problem understanding, responsibility, decisions, and implementation came together in this context.

Impact

Took full product, delivery, and engineering responsibility in a hands-on CTO role from initial setup to a scalable SaaS operation.

What carries forward today

Built the delivery and product foundations that later AI-native workflows depend on to stay reliable.

Hands-on CTOProduct ownership0→1 SaaSProduct + deliveryPlatform operationsCI/CDCypress

Defensible proof

0→1

health SaaS built

Developed product model, team, website, customer portal, survey application, and back office under one end-to-end responsibility.

Full-stack

product to operations

Connected backend, frontend, integrations, CI/CD, monitoring, supportability, and AWS operations.

CI/CD

delivery stabilized

Established CircleCI, Docker, Cypress, and clear deployment paths as part of product work.

Where this experience creates value

  • For health and SaaS teams that need product model, multiple web products, integrations, delivery, and operations built together.
  • For build phases where hands-on implementation and CTO/Head-of-Product decisions need to stay close.

Case context

Overview

A health-study SaaS platform had to be built from 0 to 1 in a growing health-tech startup. My responsibility covered product model, team setup, backend, frontend, DevOps, CI/CD, monitoring, and production operations on AWS.

The product landscape included the website, a customer portal as a web application, a survey web application deployed on the web and several tablets, and a call-center back office I implemented with Click2Dial via VoIP and conversation metadata. It also covered configurable online questionnaires, matching systems, Salesforce synchronization, product owner training, and a delivery foundation for further growth.

Responsibility

Activities

  • Hands-on CTO & Head of Product: Product model, technical direction, and team building
  • Agile leadership: Scrum Master, Product Owner Lead, agile coaching for management
  • Product surfaces: Website, customer portal, survey web application across web and several tablets, and call-center back office
  • Platform development: Configurable online questionnaires, matching systems, and a call-center back office with Click2Dial via VoIP and conversation metadata
  • Full-stack engineering: Backend Lead (Java/Scala), Frontend Lead (React/Vue.js), DevOps
  • CI/CD pipeline: Automated deployments, CircleCI, Docker, Cypress tests, quality assurance
  • Product management: Roadmap development, product owner training, website relaunch
  • Data integration: Salesforce synchronization, dashboard development, KPI visualization
  • Team development: Employee coaching, skill development, cross-functional collaboration
  • Test-first product development: frequently used Cypress as the working browser to specify, run, and debug product behavior directly while building

Operating mode

Methodology

  • Product and engineering as one system: product model, architecture, team setup, delivery, monitoring, and operations evolved together
  • Hands-on CTO mode: technical direction was not only defined, but carried through backend, frontend, DevOps, and product decisions
  • Built-in quality: CI/CD, Cypress as a working and test browser, automated tests, reviews, and clear deployment paths created a reliable SaaS delivery base
  • Operability by design: monitoring, data flows, integrations, and supportability were brought into product and architecture work early
  • Product owner enablement: roadmap, requirements, feedback, and delivery capability were connected so the team could operate more sustainably after the build-up phase

Technical context

Technology stack

The tools are not the point by themselves. What matters is which system layers had to work together.

9Areas
46Technologies

DevOps

7
Docker SwarmMavenDockerAWSMonitoringGitPlatform Operations

Messaging & Event Streaming

3
WebhooksClick2DialVoIP

Tools

5
SBTCypressJiraConfluenceSlack

Practices

7
Test-Driven DevelopmentAgile TestingShift-left QualityAgile ToolsProduct OwnershipAgile LeadershipEnd-to-End Delivery

Backend

9
JavaSpring BootScalaPlay FrameworkAkka StreamsGoogle GuiceREST APIsNode.jsJOOQ

Frontend

7
ReactVue.jsJavaScriptTypeScriptHTMLCSSCall Center Backoffice

Databases & Storage

2
MySQLArangoDB

Data & AI

4
GeoJSONConversion AnalyticsSalesforce IntegrationConversation Metadata

CI/CD & Delivery Pipelines

2
CircleCICI/CD Pipeline

Next step

If you need similar responsibility, we can identify the next useful leverage point directly.

Send the situation, goal, and decision in front of you. I will respond personally with a clear view of the value I could add.

Discuss the next leverage point