Back to the blog
TROT Blog

What is a commando run?

May 3, 2025 · TROT

Intro

We don't build TROT as we go along.

We work in short, intense, ultra-focused cycles. We call them commando runs.

So what exactly is a commando run?

A commando run is a short, intense format, entirely geared towards results.

At TROT, we use it to unlock an entire block of development in record time, usually between 3 and 6 full days.

Not to look good. Not to brainstorm for months. Just concrete work.

Where, when, with whom?

Every commando run takes place away from the office, somewhere neutral, cut off from daily routine.

No Slack. No parasitic meetings. No distractions.

We choose a place where we can think, decide and produce. It's almost a retreat... but one where you ship.

Why this format? Because stepping outside the usual setting is the best way to create a bubble of total concentration.

No interruptions. No multitasking. Just one objective, one team, one deadline.

And a healthy pressure: the pressure to come out with something real.

On the team side, we bring together only the expertise needed to see it through:

👉 Product, to define what we build, and why.

👉 Development, to make it real, fast and well.

👉 UX, so that it is clear, fluid and usable from the very first tap.

👉 User support, to carry the voice of the field and real needs.

👉 Growth, to anticipate how we launch the feature.

👉 Design, so that every screen is legible, logical and true to the TROT world.

No observers. No extra layers.

Everyone is there for a reason.

Everyone delivers.

What we come to do, and how we organise ourselves

A commando run exists to produce a working version of one precise block of the app: a new feature, a UX improvement, a technical adjustment, an API integration...

Before starting, we prepare what we call a roadmap. We always begin with a concrete problem, raised from the field or reported by users.

Then we define the use cases: who is affected, in what situation, with what needs. After that we chain it together: we design, we code, we test, we ship.

And all of it within the allotted time.

The deal is clear: at the end of the run, it is shipped.

Not "in progress". Not "to be reworked". Working.

That is what lets us move fast, without compromising on usefulness.

Why this format?

Because we are a startup.

And when you are building an app like TROT, every day of development is expensive.

Every decision has to be prioritised, tested, validated.

No scattering. No postponing what matters.

We want a startup rhythm, not an endless roadmap that never moves.

A commando run is the opposite of inertia.

No infinite loops. No specifications as long as your arm.

Just a clear sequence:

👉 a problem from the field → a useful solution → a product that evolves.

And above all, we know there is only one real way to test an idea: to hold it in your hands.

At the end of a run, we show it, we test it, we adjust it.

And we move forward. For real.

What makes the TROT team expert at this?

Because this format is nothing new to us.

At TROT, commando runs are not a method we are trying out: they are our working culture.

The team members have run more than 120 commando runs in 5 countries, across 36 different projects.

Mobile apps, voice assistants, bots, AI, web platforms, deep learning clusters, connected games...

They have designed, developed and delivered, at a tight rhythm, with the best experts on every assignment.

That is what allows us, at TROT, to ship faster, test earlier and build better. We are not trying to do what everyone else does.

We do it better. And we do it now.