
Mondosano GmbH
Hands-on CTO for Health SaaS
Chief Technology Officer & Head of Product
Relevance
Why this case matters
This framing makes the decision signal explicit: impact, proof, fit, and AI / delivery relevance for hiring or collaboration.
System impact
Took full product, delivery, and engineering responsibility in a hands-on CTO role from initial setup to a scalable SaaS operation.
AI / delivery relevance
Built the delivery and product foundations that later AI-native workflows depend on to stay reliable.
Proof
0→1
health SaaS built
Full-stack
product to operations
CI/CD
delivery stabilized
Especially relevant for
- Hiring
- Lead developer
- CTO-level
- Fractional build
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, and operations.
The platform included configurable online questionnaires, matching systems, call center integration, and Salesforce synchronization. The work also covered product owner training, agile operating capability, 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
- Platform development: Configurable online questionnaires, matching systems, call center integration
- Full-stack engineering: Backend Lead (Java/Scala), Frontend Lead (React/Vue.js), DevOps
- CI/CD pipeline: Automated deployments, Jenkins, Docker, 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
Operating mode
Methodology
- Product and engineering as one system: product model, architecture, team setup, delivery, 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, 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.
Backend
7Frontend
6Databases & Storage
2Data & AI
1CI/CD & Delivery Pipelines
2DevOps
3Tools
3Practices
1Next step
If you want to explore similar leverage for hiring, collaboration, or a concrete transformation, this is the right starting point.
Send a short note about the situation you are trying to assess. I reply personally and will be direct about fit.