MMDock.
πŸ‡ΊπŸ‡Έ EN
Talk on Telegram
All articles

Research

An order should have a reason

Execution improves when the plan is visible before the first order.

On this page

Start before the order button

A buy or sell instruction says little about why a trade should happen now, how much should be visible, or what price boundaries matter. Those decisions belong in the plan.

Make the constraints visible

Total amount, price range, number of orders and duration shape an execution task. Reviewing them together helps an operator identify conflicting assumptions before committing to the workflow.

Choose the rhythm deliberately

Time-sliced and iceberg modes are different ways to organize execution. They are useful when their behavior fits the task, not simply because an order can be split into more pieces.

Keep the result connected to the plan

After the task, compare actual orders and fills with the original intention. A coherent execution workflow supports both preparation and review.

Explore MMDock execution planning to see how the controls fit together.

MMDock | An order should have a reason