Route was designed with milestone-based workflow in mind. You create milestones, you set due dates on them, you specify goals for each milestone - at the end you get a nicely delineated route through the project plan. Trello is a more general solution.

OK, I get what you are going after. From your market research (and I'm curious here), do people tend to work better with such deadline-driven approach? My experience with Trello (and other PMs, is that they do not. But we are operating in different markets). Also, who is this made for (who is your market)?

Currently the focus of our attention is on small software companies, but we believe that the milestone-based approach would be beneficial to projects in any industry. Milestones bring visibility - the project route is explicitly defined, everyone on the team sees where the project is headed. The other advantage is flexibility - since the project is divided into smaller parts, it's easier to spot problems as they arise.

Of course, this approach is not for all use cases. For example, it won't work for very short projects - too much hassle setting up all those milestones.

Good points. I appreciate taking the time to explain further. I did not see any trial plans in there, is there one available? I'd like to give it a try.

Route is in the early preview stage, there are no plans yet. Just register and you're set.