Thank you for your comments.

You bring up two good points….

Many RFPs are not detailed. In fact, I have found several which do not offer a website address or clear information as to what they want completed. I personally prefer to respond to RFPs which offer good information because this, I believe is a reflection on the client themselves and how well they work. However, those who just write, ‘I want a blog’ or ‘I want to market my articles’ NEED a VA to help them sort through what it is they are actually seeking to do. I send a warning, though. I once responded to an RFP about setting up a blog and spent in inordinate amount of time explaining the process only to find out that the PC was really only ‘picking my brain’ for information. She set up the whole thing on her own based upon the information I provided and never contracted with me.

I suggest doing the best you can with the information offered in the RFP and explain your reply that you are interested in the work and can offer to help the PC increase sales (for example), but you need more information.

As for your other point about having unrealistic requirements…this is true as well. I see many RFPs which have low budgets for technical work, etc. Personally, I won’t compromise on the value and the experience I offer my clients. I clearly explain my rates in my reply to the RFP and offer a discount for block time contracted. The old adage…”you get what you pay for holds true!” And sure there are other VAs who are willing to come in lower for the same work I do. But I want to partner with a client and not just do the work. I believe that is what a virtual assistant is all about. I don’t want to be perceived as just a ‘cost savings’. I suggest applying for those RFPs with interesting projects and offer your rates within that reply. With all the experience you offer and the ‘what I can do for you’ explained in your reply, you should be able to get across the message that contracting with an experienced VA is an investment and not simply an expense.

Janine