About Maestro

Why we built Maestro.

We built the layer we wished existed when our own studio was running on eight tools and using none of them well.

A note from the founder

Most software wants to be the answer. We just wanted a conductor.

In 2023 our studio had thirty people, eight project tools, and a private spreadsheet maintained by our COO that tracked which conversation lived in which tool. We'd tried everything. We'd migrated to ClickUp. We'd migrated off ClickUp. We'd built Notion databases that took two weeks to set up and one Friday afternoon to abandon.

The problem wasn't the tools. Linear was great. Notion was great. Google Calendar was, fine. The problem was that they didn't talk to each other, and every workaround we tried — Zapier chains, Slack channels with strict naming conventions, weekly digests typed by hand — became one more thing to maintain.

So we stopped trying to replace tools and started building the layer above them. Something that reads from all of them, orders their output in time, and writes changes back where the work actually lives. We called it Maestro because a conductor doesn't replace the musicians — they bring an orchestra into one rhythm.

Three years and four thousand teams later, that's still all Maestro does. Keep what works. Connect the rest. Quiet confidence, by design.

— Marit Bakker, founder and CEO

How we work

Four principles. The same four we built into the product.

Orchestration, calm power, composability, and focus aren't just product pillars — they're how we run the company.

Orchestrate, don't replace

We don't try to be the one tool that does everything. We pick what we're best at and bring the rest into rhythm.

Calm power

Decisive without being loud. We ship without ceremony, sell without urgency theatre, and answer support without canned phrases.

Composable

Our team, our stack, our process — all built so a piece can be swapped without the rest collapsing. No single point of importance.

Focus

One priority per quarter. One meeting per week. One source of truth per question. The rest tucks away until it's needed.

The team

Fourteen people, eleven time zones.

We're remote-first, async by default, and we hire for craft over credentials.

2024
Founded in Amsterdam
14
People, remote-first
11
Time zones, async by default
50+
Countries with paying teams
It's the first tool that doesn't fight my other tools.
Sarah Chen
Founder
Acme Studios

Want to help us build the conductor?

We're hiring across engineering, design, and customer engineering. Remote, async, calm.

See open roles Try Maestro