@Phil_Seeman and @Bastien_Siebman, I copy and will try to keep these more strict in the future. I am getting close to making the call to bring my team (small of 9, web publishing start-up) over to Asana after about 2 years of demoing. I have been impressed that after initially thinking Asana was too limited to meet some of the more complex workflows and data handling I need, in the end, I find it actually standing out for reasons of excellent UI, integrations (such as both of yours), flexibility, and intuitive design.
I will just add one more thing as this is to Phil your last point, as I’m moving along in Flowsana too and really happy about both your Subtask Template, and Dynamic Duration workflow (which incidentally I have not seen in any other apps, but such a useful feature!):
In this post:
Towards the bottom there is an image of how you allow for new projects naming to be created based on a Task which has a status change leading to that. You probably already thought of this, but if you could consider in your roadmap a way to generate subtasks based off a Task name, perhaps not based on a template in this situation, I think that would be useful. I want to add that I much prefer your current set up, as I have a routine process where I need 5 distinctly build subtasks to repeat generate out of a template, and you offer that now, very exciting!
Thanks again guys and see you in another, more on-topic 
, post!