Wednesday Wisdom: Steve Jobs

I love this quote. Too often I think we make technology because we can and then look for an application, instead of looking for a need and then filling it with new technology.

Proposal Writing: Reviewing the Request for Proposal (Part 2)

In yesterday's blog, I discussed the first steps to evaluating a RFP. Today I'll wrap up the best practices for completing that initial assessment.

Just to recap, in yesterday's post I discussed:

• Your initial read-through of the proposal, noting the submission requirements
• You've assembled your team and assigned every line-item in the RFP
• You've set and internal deadline for your team members to prepare their questions
• A designated person has been identified to submit the questions and distribute the answers

Before You Submit the First Question

Submitting questions can be the first impression your organization makes on a potential customer. Before a single question is submitted, someone has to review each question and ensure it's in the form of a question (not just "CPU"). You want to present a professional appearance. 

All questions should be in the same font and the same style of bullets (or no bullets at all). And you must get the customer's name right. If ABC Corp. goes by "ABCC" in their RFP, that's what you have to refer to them as. Not ABC Corp., ABC, not the Awesome Blue Caterpillar Corp., and, please, not ABCD, ABCB or anything else that mangles their name.

When you read the RFP, you'll need to take special note of two things in regards to questions:

1. What is the policy on contacting the customer? Do all communications go through the same person? Is there a notice that contacting other employees is grounds for your proposal to be dismissed?
2. Are Q&A going to be distributed to all vendors?

You'll need to inform your entire team if there are restrictions on who can be contacted at the customer's organization. This means your network guru can't pick up the phone and call their network guru, even if they know each other. If this RFP is from a customer you're currently doing business with, you need to assure that anyone already working with the customer understands the new RFP can't be discussed outside of the RFP instructions. If possible, use employees from your organization that aren't already working with the customer to complete the RFP.

Don't run afoul of the customer's policies before you've even submitted a proposal. You don't want to be disqualified.

If the Q&A are going to be distributed to all vendors, you may need to discuss a "question strategy" with your team. You may want to word your questions carefully. For example, instead of asking "will your accept proposals for 17 inch monitors instead of 15 inch monitors," you may want to be generic and ask "will you accept proposals for items that exceed the specifications requested". You may want to conceal your strategy from competitors, or you may not want them to even know you're responding to the RFP. So don't show all your cards if the questions will be shared, and assure that no question you submit identifies your company by name or product or service.

I've noticed a lot of RFPs don't specify if Q&A will be shared among vendors. Some don't specify a date the customer commits to having all questions answered. In this case, I highly recommend you call the RFP contact (following the RFP instructions) and ask for the answers to both.

Th Clock is Ticking

Because RFP's often have a short turn-around-time, and the Q&A can make the difference in how your team responds, or if they chose to not respond. Your team may also need to submit follow-up questions, so time is a big factor in the Q&A:

• Get line-item owners to commit to submitting questions by an internal deadline
• Submit questions to the customer as soon as possible
• Assure that answers to the questions are distributed to the entire team, and as quickly as possible
• Let team members know to submit follow-up questions by an internal deadline that assures you meet the customer's question deadline

Did you have any idea that there could be so many steps just to get through the Q&A process? I promise if you follow these best practices, you won't regret it. This will give your organization an edge when you begin crafting the proposal.

Proposal Writing: Reviewing the Request for Proposal (Part 1)

I've been asked before if I had a proposal format that someone could use to respond to a Request for Proposal (RFP). The answer is no, and you shouldn't look for someone else's proposal as a formatting guide. The only thing that determines the proposal's format.

For this discussion, I'm using the term RFP, but the same advice holds true for:

• Request for Information (RFI)
• Request for Quote (RFQ)
• Request for Bid (RFB)
• or any other type of request you receive as a vendor that is an opportunity to demonstrate your qualifications, services and/or products to a current or potential customer.

The same advice can be applied to a proposal from the public or private sector.

I've seen RFPs run upwards of 100 pages, contain a dozen spreadsheets to be completed, and require as many as 30 forms and attachments. The first thing you need to do when considering a RFP is to read the whole thing, highlighting (either physically or online) all of the items that pertain to the response format, including the media the customer wants the proposal in, how many copies, due date and time, mandatory forms and spreadsheets, restrictions on page length or attaching marketing material, etc. This should give you a good idea about the effort it will require to respond to the RFP.

It may seem like that is all that is involved in an initial assessment of a RFP, but I can share some additional best practices here to completing an assessment that will give you an edge when responding to the RFP.

The Online RFP

Increasingly, companies, government organizations and other public entities are using online RFP process. Typically this will require the vendor to register and receive a log in to the customer's RFP website. This website may have the RFP files for download, it may also have relevant policy documents available, or it could be an online tool (program) that requires you to complete the individual questions or requirements directly online.

Most of the time, the customer will also have a file that contains all of the online questions that vendors can download and use as a working document. Sometimes this is in the form of a spreadsheet, and the vendor can upload his answers to the online tool.

It;s extremely important in this case to understand what restrictions are on each item in the online tool. This can include the number of characters allowed in an answer, if an answer can only be a number, if the answer must be selected from a drop-down list (such as Yes/No), or if the vendor can insert an attachment to go with the answer.

This holds true for any spreadsheets you must complete whether or not the proposal is to be entered online.

Sometimes the customer will ask that the final proposal files be uploaded to a website, without requiring input to each item. Either way, you need to get instructions on who you can call if there are technical problems. I've had more proposals than I want to remember that encountered problems at the final stage of online submitting. I could write a book on the online proposal process and how it differs from a more conventional proposal process (and I just might do that), but for now I'll proceed with the steps to complete an initial assessment of a RFP.

Assessing the Work Required

Once you understand the format the proposal has to adhere to, the deadline, and the media the proposal is to be delivered on, you need to have one other item before you can proceed in developing initial assessment on the proposal: the customer's deadline for questions to be submitted and the process involved.

Depending on the size and structure of the organization you work for, you may have a proposal manager or a project manager to assist in the process. I'm assuming in this example that you don't have any help like that and have to do the proposal/project management yourself. If a proposal/project manager is working with you, the same steps would be involved but you'd be able to divide the labor involved.

Next, you need to assign every item in the proposal to a person. That's important because a person can be held accountable but it can be much harder if a task is assigned to a group or department. This also assures that at the beginning of the process yo're identifying everyone who would need to be involved. You don't want to find out later that a key person or group was left out.

Distribute the proposal and a summary of the basic information you've gathered to the team you've assembled. Explain when questions are due, and set an internal deadline for all team members to have their assigned sections reviewed and any questions documented.

I've found it's much more efficient if one person is responsible for assimilating the questions and presenting them to the customer (in whatever format is required), and then distributing the answers received to the whole team. I've learned from doing hundreds of proposals that all of the questions and answers (Q&A) need to be distributed to the entire team. The answer to one question may impact items assigned to other team members.

That's all for today, but tomorrow I will outline best practices for the remaining steps for completing the initial RFP review.