frederick
Well-Known Member
- Reaction score
- 154
- Location
- Phoenix, AZ
So you want to win a government RFP/RFQ. It's not something you can just jump into. It takes some work to know the process, and sometimes who you know really helps. So how should one go about getting in to the bidding process. I do a lot of bidding for Schools and City departments. And this is what I've learned to get me considered, and some times, the contract.
This first part is about writing your bid. I'll add more about how to go about visiting the person who advertised the bid, and other things later.
Writing The Proposal
It starts with the learning of how to write in a professional tone and using a specific format. Find a place that teaches you how to write a Proposal/Quote. It is and isn't like writing a quote for a B2B, this is B2G which means politics. Learning how to write out a bid is your first stop on the road, there is a flow of how they are supposed to be written out. To help you out...this is our flow of each bid.
Section 1 (Submission Details): Who are you, where are you located, deadlines, contact person w/ phone number, any clarifications you think would help you.
Section 2 (Executive/Business Summary): This is a brief overview about your company, and any requirements you might have. Things like access, or you will only work between 9-5, etc. If you don't say what your requirements are, don't complain when they say all work must be done at 2AM.
Section 3 (Business Background): So now they know who you are, and who your company is. But what products, services, and market sector do you work in? "I work in IT" is a wrong answer. Things like "We provide Managed IT Support Services to the Phoenix Metropolitan Area for small and medium-sized businesses." Professional, and says it all. Next, what's your background, been servicing the area for 10 years? Put that down. If you have a client that you service, that requires similar services, put that down. It has to speak to the person you are bidding to. So any experience you have that relates directly to what is being asked of you needs to go here. If you have any experience with working with the government, this also helps. Veteran Owned Businesses get moved up the list. Also minority owned, women owned, and disabled persons (veteran or not) also get moved up the list for selection. The government likes working with these businesses cause it makes them look like they actually care, whether they do or not. It's politics.
Section 4 (Detailed Specifications of the job): If you haven't visited the prospect, talked to them, or even gotten details on what all is needed, then don't even submit your proposal. What they advertise is a brief (even if it seems detailed), it's not. This section is the meat of your potatoes. If it isn't long, detailed, and addresses everything, then don't submit.
You need to include drawings (if applicable) for wiring, setting up AP's, etc. This is where programs like Power Point become awesome. They want to see pictures, have a visual of what it is that it's going to look like. Having a before and after is up to you. I love doing a before and after, that way they can see the changes.
Your action plan, with milestones, to include requirements, tolerances, functionality, etc. If you are doing an evolution proposal, write it out in phases, and detail how each phase works, what will be available at each step, etc. Details and pictures help. Make sure they can understand how the whole thing is going to flow. Include deadlines, processes, equipment, personnel requirements, client requirements (maybe they will have take Tuesday off or something).
Service levels, this one is important if you are doing a LTS bid. At what point do third party vendors get involved, or what all are you going to cover, and therefore, anything outside of your realm needs to be covered by someone else. I saw a bid one time for this school. The proposer said he would cover only workstations, no networking or servers...needless to say, he didn't get the bid.
Section 5 (Constraints): List them. Be thorough. If, for any reason, you see there will potential issues that the requester should be aware of, list it, and why it is important. The more you list, the better you might look. If you are not upfront about this stuff, be prepared to lose the bid. Things like the requester wont have X, Y, Z during the service, or because of the current CAT 3 running, installing the 10Gb hardware would be pointless are important. You can also put these in Section 4, and if you do, mention them with a blurb here as well.
Other things are travel/expenses, licensing rights, upgrade and modification costs, and sometimes the unforeseeable if you were denied access to an onsite survey (more on this later).
Section 6 (Terms and Conditions): How much are you going to charge? Contract Length (if they didn't mention how long)? What is their exit strategy? Warranties, renewal options, service levels, etc. All of it goes here. And...if you don't deliver or make deadline what do you lose?
These three are the big ones:
1) What is your quote? It better be a solid number. If you, for any reason tell them $10,000, and not $10,000 per month of contract...HA!!! I laugh at you. Also, if you tell them $10,000, and then hand them a bill for $12,000, be prepared to go to get in trouble. What are the financing options as well? With some project contracts, I've done a 30% now, another 30% mid way (assuming I've met deadlines up to this point), and then the final 40% at the end.
2) What is their exit strategy? If you give them no way out, your proposal will be tossed in to the furnace. This is a bigger thing for LTS contracts. But basically it boils down to either a mutual agreement, or if you don't live up to your promises, your gone.
3) Missed deadlines/failure to deliver. If you go over a project by 3 days, how much do you have to pay them? Remember, your affecting their productivity, efficiency, work flow etc. It really depends on the job, and scope. If you are doing something that severally affects their ability to work, be prepared to pay some employees paychecks. If you are doing something simple like replacing old VoIP phones with new ones, the impact will be less, assuming the old phones still work kind of thing. Also, if you are proving LTS, so say, maintaining their network and systems, ensure in section 4 you established priority levels for service. And if you stated that if their whole net goes down, you'd be there in 5 minutes, and you show up in 15, state what you lose. If you are willing to roll the dice, don't get in to the contract business. Be prepared to propose to lose a lot.
Section 7 (Why they should choose you): Seriously, what makes you the perfect candidate? What is your end-game or angle? What do you get out of this contract? This is used to gauge what is important to your company.
If you have any questions about how to write a proposal/quote, don't hesitate to contact me.
This first part is about writing your bid. I'll add more about how to go about visiting the person who advertised the bid, and other things later.
Writing The Proposal
It starts with the learning of how to write in a professional tone and using a specific format. Find a place that teaches you how to write a Proposal/Quote. It is and isn't like writing a quote for a B2B, this is B2G which means politics. Learning how to write out a bid is your first stop on the road, there is a flow of how they are supposed to be written out. To help you out...this is our flow of each bid.
Section 1 (Submission Details): Who are you, where are you located, deadlines, contact person w/ phone number, any clarifications you think would help you.
Section 2 (Executive/Business Summary): This is a brief overview about your company, and any requirements you might have. Things like access, or you will only work between 9-5, etc. If you don't say what your requirements are, don't complain when they say all work must be done at 2AM.
Section 3 (Business Background): So now they know who you are, and who your company is. But what products, services, and market sector do you work in? "I work in IT" is a wrong answer. Things like "We provide Managed IT Support Services to the Phoenix Metropolitan Area for small and medium-sized businesses." Professional, and says it all. Next, what's your background, been servicing the area for 10 years? Put that down. If you have a client that you service, that requires similar services, put that down. It has to speak to the person you are bidding to. So any experience you have that relates directly to what is being asked of you needs to go here. If you have any experience with working with the government, this also helps. Veteran Owned Businesses get moved up the list. Also minority owned, women owned, and disabled persons (veteran or not) also get moved up the list for selection. The government likes working with these businesses cause it makes them look like they actually care, whether they do or not. It's politics.
Section 4 (Detailed Specifications of the job): If you haven't visited the prospect, talked to them, or even gotten details on what all is needed, then don't even submit your proposal. What they advertise is a brief (even if it seems detailed), it's not. This section is the meat of your potatoes. If it isn't long, detailed, and addresses everything, then don't submit.
You need to include drawings (if applicable) for wiring, setting up AP's, etc. This is where programs like Power Point become awesome. They want to see pictures, have a visual of what it is that it's going to look like. Having a before and after is up to you. I love doing a before and after, that way they can see the changes.
Your action plan, with milestones, to include requirements, tolerances, functionality, etc. If you are doing an evolution proposal, write it out in phases, and detail how each phase works, what will be available at each step, etc. Details and pictures help. Make sure they can understand how the whole thing is going to flow. Include deadlines, processes, equipment, personnel requirements, client requirements (maybe they will have take Tuesday off or something).
Service levels, this one is important if you are doing a LTS bid. At what point do third party vendors get involved, or what all are you going to cover, and therefore, anything outside of your realm needs to be covered by someone else. I saw a bid one time for this school. The proposer said he would cover only workstations, no networking or servers...needless to say, he didn't get the bid.
Section 5 (Constraints): List them. Be thorough. If, for any reason, you see there will potential issues that the requester should be aware of, list it, and why it is important. The more you list, the better you might look. If you are not upfront about this stuff, be prepared to lose the bid. Things like the requester wont have X, Y, Z during the service, or because of the current CAT 3 running, installing the 10Gb hardware would be pointless are important. You can also put these in Section 4, and if you do, mention them with a blurb here as well.
Other things are travel/expenses, licensing rights, upgrade and modification costs, and sometimes the unforeseeable if you were denied access to an onsite survey (more on this later).
Section 6 (Terms and Conditions): How much are you going to charge? Contract Length (if they didn't mention how long)? What is their exit strategy? Warranties, renewal options, service levels, etc. All of it goes here. And...if you don't deliver or make deadline what do you lose?
These three are the big ones:
1) What is your quote? It better be a solid number. If you, for any reason tell them $10,000, and not $10,000 per month of contract...HA!!! I laugh at you. Also, if you tell them $10,000, and then hand them a bill for $12,000, be prepared to go to get in trouble. What are the financing options as well? With some project contracts, I've done a 30% now, another 30% mid way (assuming I've met deadlines up to this point), and then the final 40% at the end.
2) What is their exit strategy? If you give them no way out, your proposal will be tossed in to the furnace. This is a bigger thing for LTS contracts. But basically it boils down to either a mutual agreement, or if you don't live up to your promises, your gone.
3) Missed deadlines/failure to deliver. If you go over a project by 3 days, how much do you have to pay them? Remember, your affecting their productivity, efficiency, work flow etc. It really depends on the job, and scope. If you are doing something that severally affects their ability to work, be prepared to pay some employees paychecks. If you are doing something simple like replacing old VoIP phones with new ones, the impact will be less, assuming the old phones still work kind of thing. Also, if you are proving LTS, so say, maintaining their network and systems, ensure in section 4 you established priority levels for service. And if you stated that if their whole net goes down, you'd be there in 5 minutes, and you show up in 15, state what you lose. If you are willing to roll the dice, don't get in to the contract business. Be prepared to propose to lose a lot.
Section 7 (Why they should choose you): Seriously, what makes you the perfect candidate? What is your end-game or angle? What do you get out of this contract? This is used to gauge what is important to your company.
If you have any questions about how to write a proposal/quote, don't hesitate to contact me.