aaronbuchanan

A bunch of stenciles for wireframing, data & user flow diagrams and more:

Empty Chrome Browser Window: 
https://www.graffletopia.com/stencils/938

Twitter Bootstrap UI: 
https://www.graffletopia.com/stencils/934

Google Web GUI: 
https://www.graffletopia.com/stencils/10431

aaronbuchanan

Purpose Outcome Structure Timing
Having a plan for sales meetings, before the actual meeting will improve your chances of success.

Winging it is not a good strategy. You really need to think in advance what is the Purpose of the meeting and what is the Outcome of the meeting.  You want the Purchase Order (PO) so think about the Purpose and the Outcome.

Be realistic about what can be achieved in the meeting.  Ideally think about what  the customer wants from the meeting - not just what you want. If you draw an analogy with dating - you might want sex on the first date but is it realistic?  Having a clear view on small incremental steps forward towards the end goal is important otherwise you can end up in a protracted Engagement and never get Married (get the sale) or worse still turn the sale off by being too pushy!

Using the POST (Purpose Outcome Structure Timing) tool will help you have more effective sales meetings.
Purpose - what is the reason for the meeting.  If it's a first meeting the purpose might 

aaronbuchanan

https://news.ycombinator.com/item?id=13889155

7 git rules: 

1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line
6. Wrap the body at 72 characters