Tatiana Botero

Product · Operations · Systems

I turn complicated business problems into products that make the operation work better.

Enterprise products · 0→1 · B2B / Vertical SaaS · AI · Operations

Explore my work My story

A little about me

Curiosity is what brought me into product.

Before product, I studied culinary arts. I loved experimenting with flavors and textures, recreating dishes, questioning what wasn’t working, and changing one thing at a time until it got better.

When I moved into product, that instinct felt familiar. I wanted to understand how the business worked, how everything connected, where things broke, and what we could improve.

Different ingredients. Same curiosity.

My story

My path into product

My scope grew as the questions I owned got bigger.

I started by learning how a complex operation worked. Each role expanded the question I was responsible for answering.

  1. 2018
    UnderstandAnalystUnderstand the businessFusion CX
  2. DeliverProduct ownerTurn complexity into requirementsFusion CX
  3. OwnProduct managerOwn the systemFusion CX
  4. BuildCo-founder + productBuild for a marketMOM Seguros
  5. ScaleSenior product managerScale operationsFusion CX
  6. Today
    LeadProduct + GTMFind what is worth buildingStealth Telecom Technology

Case studies

Culinary arts taught me to experiment, diagnose, and improve.

  1. 01Fusion CX · 2018 to 2025

    One employee. Multiple teams. Different versions of the truth.

    • Recruitment
    • HR
    • Training
    • Operations
    • Quality
    • IT
    • Finance
    • Payroll

    One employee

    Different versions of the truth

    The same employee existed differently depending on which department you asked.

    • 2,000+ employees
    • 7 locations
    • 20+ client programs
    Explore case study

  2. 02MOM Seguros · 2022 to 2023

    We made insurance easier to buy. But did that make people want to buy it?

    20K downloads

    in the first month

    Attention is not the same as Product-market fit

    The product got attention. The harder question was whether attention would translate into behavior.

    • 20K downloads in the first month
    • 6 insurance partners
    • Best Startup of the Year recognition
    Explore case study

  3. 03Stealth telecom · 2025 to present

    Everyone has problems. Which ones are actually worth building a product around?

    • Painful
    • Recurring
    • Valuable
    • Repeatable

    Potential product

    My work starts before the roadmap.

    • Customer discovery
    • Product strategy
    • Vertical SaaS
    Explore case study

  4. 04Tempo · 2026 · Side project

    Your calendar says you’re free. But are you actually available?

    CalendarAvailable ✓
    Reality
    • Back-to-back meetings
    • Mentally tired
    • Personal priorities still waiting

    Available time is not the same as Available capacity

    An empty hour on a calendar doesn’t necessarily mean someone has the mental capacity to use it well.

    • AI product exploration
    • User research
    • Product discovery
    Explore case study

How I think

Principles I keep coming back to.

More on how I think
01Requests aren’t requirements.

A request is evidence about a need, not automatically the solution.

02Not every problem needs software.

Sometimes the right fix is process, ownership, training, policy, or capacity.

03Understand the system before optimizing one part.

A local fix can create friction somewhere downstream.

04Adoption is part of the product.

A system people don’t trust or use hasn’t solved the problem.

05AI isn’t automatically the solution.

I start with the workflow, then decide whether AI has a useful role.

06Shipping isn’t the outcome.

What matters is what changed for users and the business.