RFPs typically specify technical performance requirements. They should also clearly delineate areas of responsibility and detail what you expect from the vendor, including system architectures, labor, and even trash removal. But don't over specify in your RFP, warns Buiton. We don't accept a statement that a particular software event has to happen within two seconds. We do accept a statement that says that the overall throughput of the system has to be 60 units per hour.
Suppliers can then either agree to each term or they can disagree and suggest substitutions.
This approach, says Bauer, will give you a notion about which suppliers are going to be real sticklers about the contract, and which suppliers might be more amenable to your terms and conditions. Typically an IT professional, untrained and inexperienced in high-tech contracts, and lacking in negotiating skills. Inc. When it comes time to issue the contract itself, attach the RFP as an addendum. The contract is the binding agreement, but the RFP is the list of promised deliverables or services that the supplier must live up to. After issuing the RFP, hold a suppliers' conference.