Company dossierUpdated 04 Nov 2026

Est. 2018 · Lyon

We built the tool we kept rebuilding by hand.

Treeline is an operations workspace for teams who run the unglamorous middle of a business: orders, handoffs, approvals, the work between the work. It started in a Lyon apartment with a script and a notebook. The product has been rewritten four times; the reason for it hasn't.

Still shipping weeklyPrivately held41 countries
Company register2026
Founded
2018 · Lyon
First commit
14 Feb 2018
Team
14 · 6 countries
Customers
2,300 teams
Status
Independent

No board seat sold · No growth targets

The timeline

The story, chapter by chapter

Five moments that changed the shape of the company — told with the photographs we still have, and the placeholders for the ones we don't.

Chapter 1 of 5: The notebook
Archive scanFig. 01 / 05
Fig. 01CSS placeholder

2018 · Archive

Lyon, France

The apartment where the first script was written, photographed before the desks arrived.Placeholder illustration

2018 · Lyon, France

A failed handoff, a weekend script, and eleven colleagues.

Treeline began in a one-bedroom apartment in Lyon after a failed handoff quietly took down a customer's Monday. Maya and Idris, then ops engineers at a logistics company, wrote a small script to make the next failure visible before it happened. Eleven colleagues asked for it the same week.

There was no pitch deck, no name and no plan to leave their jobs. Just a notebook of things that kept breaking in the same order, and the stubborn idea that they could be fixed in the same place.

“We weren't trying to start a company. We were trying to stop rebuilding the same spreadsheet every Monday.”

Maya Roussel · Co-founder
People
2
Desks
1
First users
11

What didn't change

Four rules we wrote in 2018 and still use.

They began as a list on the studio wall. They're now the only document every new hire signs on day one — not because they're elegant, but because they've survived every hard call since.

Last reviewed Jan 2026 · signed by all 14
  1. 01

    Write it down

    Decisions

    A decision that only lives in a meeting isn't a decision. Every product call gets a one-page brief with the trade-offs included, and anyone can challenge it in writing.

    In practiceThe brief ships with the feature, forever.

  2. 02

    Ship the boring fix

    Reliability

    The exciting feature is rarely the one customers stay for. We fix the slow export, the confusing error and the flaky sync before we add another surface to maintain.

    In practiceEvery incident gets a public postmortem within 48 hours.

  3. 03

    Small on purpose

    Independence

    We grow when the work demands it, not when a spreadsheet says we should. Staying independent means we can say no to the wrong customer, the wrong hire and the wrong quarter.

    In practiceNo sales team. No growth targets. Profitable since 2024.

  4. 04

    Design is not decoration

    Craft

    The interface is where the promise gets tested. If a screen needs a manual, the screen is wrong. We write the empty state, the error state and the keyboard path before we ship.

    In practiceNo feature ships without a first-run and an empty state.

The next chapter is being written in public — releases, incidents and the occasional correction included.

Signed

The 14 people at Treeline