Re: Subcontractor's pickup lines, NOT to use!
My biggest pet peeve is not addressing what I ask for, and being to vague. Not that I require deep detail, but some would be nice.
For instance if someone is familiar with Aweber, but has not fully utilized it I want to know that. It won't necessarily stop me from working with them, but it may get them fired if they can't perform and they led to me to believe they could. Anyone who works with a platform like Aweber knows there are different aspects to it, and while it is not hard to teach someone to use and I would certainly be willing to do so as long as they are upfront with me in regards to their skill level with Aweber. So if they could just say something along the lines of, "I am familiar with Aweber and have done x, y, and z with it (they could also add) but I am willing to learn more if needed." That would be sufficient.
I will overlook a typo and even a grammar error as long as it's not overtaken with them. I am not perfect and I do not expect those who work with me to be perfect, but if you are claiming to be an editing/proofreading/grammar expert then of course I will judge your skills a little more tightly in that regard.
But like I said my biggest pet peeve is not addressing my questions. Even with Clients it's a huge problem. People are so busy, and I've been guilty myself of this same thing so I know how easy it is to overlook something.
A few tips that I have picked up:
1. Don't respond to an RFP when you are not focused or are busy with something else.
2. Don't respond to an RFP when you are rushed.
3. Don't respond to one when you are sleepy/tired.
4. Proof your response. Review and double check it against the RFP.
5. Have someone else proof it and double check it against the RFP if you feel you just have to respond now and maybe are not on top of your game at that moment.
|