Skip to content

Team Structure Overview

Timeless Biotech is a small, focused company. We operate with minimal hierarchy and clear ownership of key areas. This page gives you an overview of who does what.

Company Org Chart

                      Founder / CEO
                           |
          _________________|_________________
          |                |                |
  Founding Machine    Founding          Commercial
  Learning Scientist  Technical Lead      Lead
          |                |                |
    ML / Data         Engineering       Business Dev
    Research          Platform          Partnerships
    Clinical Data     Infrastructure    Clinic Onboarding

We keep the org chart flat because: - We're an early-stage startup where everyone wears multiple hats - Decisions happen faster with fewer layers - Each founding team member has clear ownership of their domain - Cross-functional collaboration is the default, not the exception

Team Composition

Founder / CEO

Sets company vision and strategy, manages board/investors, fundraising, and makes final calls on major decisions. Directly oversees all three functional leads.

Founding Machine Learning Scientist

Owns the data science and machine learning strategy — model development, clinical data analysis, research methodology, and data quality standards. Works closely with providers to ensure the de-identified data collection meets both clinical and ML requirements.

Founding Technical Lead

Owns the MenoTime platform end-to-end — architecture, backend (FastAPI/Python), infrastructure (AWS), database, deployments, and security. Responsible for technical decisions, code quality, and system reliability.

Commercial Lead

Owns business development, clinic partnerships, provider onboarding, and go-to-market strategy. The bridge between the product and the clinics that use it.

How the Team Works Together

Technical Lead ↔ ML Scientist

In constant collaboration on: - Data model design and schema changes - De-identification pipeline and data quality rules - Infrastructure needs for ML workloads - API design for data collection endpoints

Technical Lead ↔ Commercial Lead

Coordination on: - Provider feature requests and support issues - Deployment timing (clinics need advance notice) - Platform reliability and uptime - Technical requirements for clinic onboarding

ML Scientist ↔ Commercial Lead

Partnership on: - What data clinics can realistically provide - Data collection form design and validation - Research partnership scoping - Provider feedback on data workflows

Founder/CEO + All Leads

Weekly sync to cover: - Company updates and milestones - Cross-functional decisions - Prioritization and roadmap - Strategic direction

Decision-Making & Authority

Clear Ownership

Each function has clear ownership to avoid "who decides?" confusion:

Area Owner Approver
Platform architecture Founding Technical Lead Founder/CEO if major trade-offs
ML models & data science Founding ML Scientist Founder/CEO (strategic)
Clinical data model Founding ML Scientist Founding Technical Lead (technical feasibility)
Infrastructure & security Founding Technical Lead Founder/CEO (final call)
Clinic partnerships Commercial Lead Founder/CEO
Provider onboarding Commercial Lead Founding ML Scientist (data requirements)
Feature prioritization Founder/CEO (input from all leads)
Hiring Founder/CEO Relevant lead (domain fit)
Budget & fundraising Founder/CEO —

Escalation

Decisions are made at the lowest appropriate level: - Each lead decides within their domain - Cross-domain decisions involve the relevant leads - Founder/CEO makes final calls on strategy, budget, and major trade-offs - The whole team shapes values and culture together

If you're unsure who decides something, ask the Founder/CEO.

Team Size

We're a founding team — lean and focused:

  • Founder/CEO
  • Founding Machine Learning Scientist
  • Founding Technical Lead
  • Commercial Lead
  • Total: 4 founding members

As we grow, each lead will build out their respective teams.

Values & Culture

Our team shares these values (see welcome for full definitions):

  1. Patient-First: Everything we do ultimately serves patients and providers
  2. HIPAA-Always: Security and privacy are non-negotiable
  3. Move Fast with Guardrails: We move quickly but responsibly
  4. Openness & Transparency: We trust each other and share openly
  5. Continuous Learning: We invest in growth and knowledge-sharing

These values shape how teams interact, how we make decisions, and how we treat each other.

Remote / Distributed

Most of the team is distributed across US time zones: - Some early birds in EST - Core group in PST - A few remote workers

We operate asynchronously where possible: - Meetings happen during core hours (roughly 10 AM - 4 PM PT) - Async standups available in #engineering - Important decisions documented in email/Asana for people to review

Time zones are a feature (customer support coverage), not a bug, but we work hard to keep the team connected.

Physical Spaces

  • San Francisco office: If you're in the area, we have desk space and meet up occasionally
  • Default: Work from wherever is most productive (home, coffee shop, coworking space)
  • In-person meetings: We do an occasional all-hands in person (1-2x per year) and encourage quarterly team offsites

Last updated: February 2025