9. Title & number every mockup screen
(Make it easy to refer a screen in a vendor’s estimate!)
8
10. Explain what you show!
(Explain every detail that goes into your mockup and make it the detailed functional
requirement document. Better yet, record it in your own voice and send it out along
with your requirement document.)
9
11. Take expert help, for planning!
(Get the technical, information and visual design done by someone you can sit across
the hall. Offshore the execution. Near shore the planning!)
10
12. Ask for scenario based estimates!
(Ask for estimates that represent different tradeoffs between features count, depth or
cost)
11
13. English (beep) English!
(If you are a non-native English speaker and/or if your English is not good, proof-read
your requirements document with someone who is!)
12
14. Send a response template!
(Avoid the nightmare of comparing proposals with diverse sections, depth and style. Make your
own template and share it with vendors.!)
13
15. Don’t be greedy!
(You cannot get the best code at the cheapest price within the shortest time!)
14
16. Set Milestones
(Make every vendor comply with milestones – For Questions, Case Studies, Estimations,
Proposals and References. Ad hoc process would not allow you to compare vendors in every
stage.)
15
17. Hard to remember all these points?
Take ContractIQ’s hands-on vendor selection plan. We’d do it the right way for you!
16
http://www.contractiq.com