Website Request for Proposals (RFP)1. DESCRIPTION, PURPOSE AND O.docx

Website Request for Proposals (RFP)
1. DESCRIPTION, PURPOSE AND OBJECTIVES OF WEB
SITE
a. Describe the Web project you wish to undertake. Is it a new
site, a redesign, or an update?
b. What problems will this technology project solve or what
new capabilities will it provide for your organization?
c. If you have made a decision beforehand, indicate whether this
site relies on a database to display information or will be
"static" HTML.
2. BUDGET & COST ESTIMATES
a. Provide a budget range so your solutions providers can scale
their proposal accurately.
b. Indicate whether your organization is ready to start work, or
you have to raise money to begin the project. If you do need to
raise money, vendors may help you describe the project in order
to maximize your chances of receiving funding.
3. TERMS AND CONDITIONS
a. Organization must own or have full access to and have the
right to customize site code.
b. Terms for proposal:
i. Key dates
ii. Proposals should be delivered to __________. Copies should
be ____________(postmarked/ or received) by
______________.
iii. Please provide ______ copies of any proposals submitted.
iv. All proposals must include a statement of authorization to
bid signed by a principal of the responding company
v. All proposals must use the proposal format outlined in this
RFP.
vi. Parties submitting separate proposals may not discuss
pricing information or they will be ineligible to bid on the
project.
vii. Bidder status: bidder must disclose any relevant conflicts of

interest and/or pending lawsuits.
4. BACKGROUND OF COMPANY OR PROPOSED COMPANY
a. Tell vendors about your organization. Provide links to
information on your existing Web site, if applicable. When was
your organization founded? How many staff members does your
organization have?
5. AUDIENCE
a. Define the audience that will be using the site. Do you have a
defined group of users or "stakeholders" who will be regularly
using the site and have different needs?
b. Will the entire site be accessible to the general public?
c. Will logins be required? Will there be a separate section for
“members” or “admins”?
d. Do you need the capability for staff or members to "log in" to
access special information?
6. TOOLS AND FUNCTIONALITIES
a. Essential components: are there certain features that are
essential to any proposal you will consider?
b. Non-essential components: Are there other features of your
site that you would like but are not essential to submitted
proposals?
7. REPORTING NEEDS
a. If the site is database driven, what types of information will
you regularly need to draw from it?
8. SITE SPECIFICATIONS
a. Design parameters
b. Accessibility/Usability
i. Bobby-approved site means it is section 508 compliant
ii. Usability testing mid-stream will validate navigation choices
c. Platform, if applicable
i. Is this a redesign of a current site? If so, in what language is
the current site built? (ex: cold fusion, ASP, PHP,
Dreamweaver)
ii. On what format is the current site hosted? (Ex: NT, UNIX,
Apache)
d. eCommerce

i. Are you using an eCommerce system now?
ii. If so, what are you using?
9. AVAILABLE TECHNOLGY RESOURCES/INTEGRATION
ISSUES
a. Do you have existing pages of Web content that you expect
your Web developer to add to the new site? (Provide a map of
your current site indicating how many pages will need to be
transferred)
b. Do you have existing databases that will need to be imported
or connected to the new site?
c. Do you have existing e-Commerce systems, web forums or
other tools that the new site should be connected to?
10. STAFF RESOURCES
a. Point of contact/ project manager
b. Do you have a "Web team" of technical and non-technical
staff members that will be reviewing proposals? If not, consider
forming one.
c. Do you have a technology staff that vendors should plan to
work with?
11. PROPOSED TIMELINE: (Please indicate the timeline you
expect vendor to adhere to)
i. Develop RFP process (forward email address for questions on
RFP)
ii. RFP release date
iii. Submission of questions on RFP
iv. Notification of Intention to bid
v. Answers to questions emailed to all bidders
vi. Proposals due
vii. Finalist interviews
viii. Proposal award date
ix. Initial meetings
x. Drop-dead Date (no new concepts/functionality added)
xi. Beta site launch
xii. Proposed site launch
12. FORMAT FOR PROPOSALS
1. Executive Summary

2. Technical Volume
a. Web development process: explain the process you will
follow to build the Web site, including major milestones and
evaluation
b. Address usability standards and testing
c. Address any important technology information and
specifications used in your solution (languages, platform, etc.)
3. Management Volume
a. Organizational structure: communication process; including
lines of reporting and any special tools used.
b. Schedule of deliverables; include major milestones and
testing proposal.
4. Budget Volume
a. Break down cost by production hours, tools and
functionalities
b. Maintenance and support: identify any costs that should be
assumed as part of the site and ongoing costs for maintenance
and support we need in the future.
c. License fees: identify the costs we will need to pay to
develop or host the site.
d. Hosting: identify whether we must or are highly encouraged
to host with your company. If hosting is provided as an option
or requirement, provide pricing options.
e. Training and Style Guide: identify costs to train our staff to
use site tools and provide a style guide.
f. Other charge areas: Please identify whether there will be
other expenses, consulting fees, future work, etc. to complete
this project.
5. Attachments
a. Qualifications and Experience: relevant case histories with
information on accessing online demos or examples
b. Biographies of all who will work on account

c. Professional references
RFP for Phone System
ABCD PVT. LTD. TELECOMMUNICATIONS SYSTEM
PRIVATE
Introduction
ABCD Pvt. Ltd. requires an integrated voice connectivity
solution for their Thapathali branch.
This is a request for proposal to provide the equipment and
services outlined in Section II - System Requirements. ABCD
Pvt. Ltd. of Thapathali will award this contract on a competitive
basis.
Instructions for Completing the Proposal
The proposal needs to answer all questions listed in Part I -
Project Description. Be as brief and accurate as possible.
Submit three copies of your proposal.
Proposal Deadline
All proposals must be hand delivered no later than 5:00 PM,
Wednesday, MMMMDDYYYY Submit your proposal to ABCD
Pvt. Ltd. at the following address:
ABCD Pvt. Ltd.
Street Address
City, Anchal

Attn.: xxxxxxxxxxx
(999) 999-9999
Or
Mail an e-copy to [email protected]
Project Evaluation
Each submittal will be evaluated on a competitive basis against
other proposals submitted by other interested applicants.
Meetings between the vendor and ABCD Pvt. Ltd. to review the
proposals will be scheduled and confirmed by xxxxxxxxxxxxxx.
Proposal Schedule
The schedule for the Telecommunications System Projects is as
follows:
MMMM DD, YYYY
Request for Proposal faxed to vendors
MMMM DD, YYYY
Proposals Due
MMMM DD, YYYY

Project Evaluation Period by ABCD Pvt. Ltd.
MMMM DD, YYYY
Meetings with Vendors to Review
Proposal
MMMM DD, YYYY
ABCD Pvt. Ltd. visits local client provided as reference
MMMM DD, YYYY
Contract awarded
MMMM DD, YYYY
System is installed and operating
PART I – PROJECT DESCRIPTION
1. Project Liaison. Designate a contact person who will serve
as the liaison between ABCD Pvt. Ltd. and your organization
for all matters pertaining to this proposal. Include the person’s
name, title, mailing address, direct telephone line, and fax
number.
2. Other Participants and Description of Involvement. Identify
and describe any additional parties and services to be involved
in carrying out this proposal. Include the person’s name, title,
mailing address, direct telephone line, and fax number.
3. Project Description. Provide a detailed description of
equipment and services following the requirements outline
format.
4. Total Cost. Identify the total cost with a breakdown by
activity and equipment. This should be provided in the form of
an Excel spreadsheet by outline activity (i.e., 1.1.3 = $ ###.##
or 1.1.4 = included).

5. Project Management Plan. Provide a detailed and
consolidated description of how your organization plans to
manage the installation and maintenance of the service that is
being proposed.
6. Project Start Date. Describe steps taken to ensure a start-up
date which will allow you to complete the project on time.
Describe the expected availability of equipment and personnel
as of that date to support the proposal.
7. Additional Benefit to ABCD Pvt. Ltd. . Describe what the
applicant proposes to perform that will especially benefit the
system users and/or make the proposal stand out from other
applicants. This may include outstanding features of the
system, integration, guarantee project timeliness, etc.
PART II - SYSTEM REQUIREMENTS
Phones
Console
Display
Standard
Total
Switch
Voice Mail

Total ports
I. Telephone System
A. PBX Switching Equipment
1. The proposed PBX shall be a stored program system, with a
fully digital switching matrix and program control.
2. The proposed PBX shall have a digital CPU capable of no
less than 500 Busy Hour Call Attempts to handle projected call
volumes
3. The proposed PBX shall have the ability to “field upgrade”
the system processor to support Computer Integrated
applications.
4. The PBX system, as configured and proposed, shall be
capable of “virtually non-blocking” communications, capable of
400 simultaneous conversations.
5. The proposed system shall have demonstrated support for
industry standard interfaces including TSAPI and TAPI
6. The proposed system should support LCR
7. The proposed system should include remote system
administration capability
8. The PBX switching cabinet should provide for physical
security
9. The administrator console, if external to the switch, will be

provided by the vendor complete with software
10. The proposed system shall have intercom capability
(user/group programmable voice/ring)
11. Speed dial capability of 300 system numbers that are not
affected by user speed dial
12. Conference call capability, internal/external mixture, 10
parties
13. System must comply with ICM/Q.SIG standard for
international expandability
14. System shall provide digital audio interface or
music/advertisements on hold
a) Optional second channel for background music
B. Attended console
1. Digital instrument with digital display
2. Programmable BLF/DSS keys. Ability to support 100
programmable keys
C. Telephone Station Equipment
1. Except for Analog/Fax/Modem ports, all station equipment
should be digital to the station desktop
2. Station equipment should be modular and support the
addition of headset adapters and PC dialing interfaces (TAPI) as
required (up to all stations)
a) Conform to industry standard interface as defined by

Plantronix
b) The existing installed Plantronix headsets devices should be
reusable
3. Display equipped stations should have the ability to display
ANI and DNIS information and alphanumeric identifiers, date
and time, internal caller ID, message quantity, and queue status
4. Digital telephones shall be configurable to support ACD
functions via software/configuration changes
5. The following telephone equipment station should include,
but not be limited to:
a) Plentiful keys for telephone lines and special features to
include:
(1) Variable volume control
(2) Do not disturb capability
(3) Follow me functionality
(4) No less than 4 programmable buttons for speed dialing
(5) Visual indicator for voice messaging that provides one touch
access
(6) Ability to handle three incoming lines
(7) Ability to handle three way conferencing
(8) Two-way speaker for hands free operation and speaker
button

(9) Mute capability for conversation privacy
(10) Automatic re-dial capability
(11) Pick-up capability
(12) Transfer and Hold as separate functions
(13) Headset button and mute button
b) Modular capability to support asynchronous data transfer
c) Non-proprietary interface
D. Voice Messaging/Call processing Server
1. The voice messaging/server shall be manufactured by the
PBX manufacturer
2. Voice messaging server must provide digital integration
3. Minimum of 32 port capacity
4. System failure should default to attendant console
5. System must have a minimum of four-tier decision tree on
auto attendant main menu
6. User recordable system prompts
7. Software for both messaging and call processing/automated
attendant/audio text shall be included in the proposed
configuration
8. System software programmable for the following features
shall be included:

a) Call forward
b) Pager alert
c) Fax on demand
d) Multiple follow me
e) Forward to group
f) Ability to add message header
g) Ability to save messages to a separate space
h) Five programmable message greetings
i) Busy greeting
j) User selectable date and time stamp
k) Call recording capability
9. Multilingual prompts and TDD support should be available as
optional features
10. Optional message queuing, camp busy
11. Message exchange or “networking” shall be included in each
voice mail processor proposed
a) Message transfer between identical vendor voice messaging
(option for transfer to alternate vendor voice messaging)
12. System administrator
a) System shall provide on-board reporting capability for usage

(bill back reports), call processing applications, and security
b) Additional administrator functions to include
(1) Number of messages per box
(2) Message roll-over by time and/or quantity
(3) Variable message length
(4) Remote administration
13. Message mailbox security shall include (at a minimum)
a) Variable password length
b) Minimum password length
c) Encrypted password storage (on disk)
d) Message retention for locked mailboxes
e) Configurable logon attempts (“Hacker lock”)
14. Industry standard hard drive capable of 50 hours of storage
(minimum of 10 hours for Los Angeles)
15. Programmable backup feature using industry standards
E. UPS/Power backup
1. Minimum 2 hour power backup for each switch proposed
F. Serviceability
1. Warranty service is to include 24-hour support, 7 days per

week
2. Remote maintenance and repair capability
3. Response time
a) Critical function turnaround not to exceed one hour
b) Emergency turnaround not to exceed 4 hours
c) Standard turnaround not to exceed 48 hours (2 business days)
4. Lock contract for a five year maintenance agreement cost
5. Define coverage for in-house administration
6. Major/minor alarms should be automatically reported to the
Vendor Customer Service resources without manual call (via an
automated process)
7. Revision upgrades due to system usability to be at no cost
and to include training
8. System should have an administrative/maintenance
management interface. Interface should provide for the
following:
a) Customer moves, adds, and changes to site equipment. The
ability to make these changes shall be available during the
warranty period
b) System should have multilevel security
c) System should provide for management of LCR
tables/updates

d) System should provide for remote maintenance/management
with appropriate security
e) System reporting should be industry standard data format
G. Applications
1. Automatic Call Distribution (ACD) software shall be
included for a minimum of 15 agents
2. Real time display of ACD agent status is required
3. Customized reporting of ACD events for agents, trunk, and
call events requirement for a minimum period of 7-14 days
(historical)
II. Add-On Equipment
A. CTI Application Server
1. In addition to TAPI-based desktop control, vendor should
demonstrate a server based CTI system capable of skills based
routing
2. Server shall communicate with intelligent PC/Agent
workstations to provide a GUI interface or queue status and
permit “on the fly” redirection or reservation of calls in queue
B. Vendor to provide a packaged service solution including long
distance services, digital and voice
C. Demonstrate capability to support worldwide franchise
locations, with both voice and data
D. Development of package models to support franchise
network including the disposition of current equipment

III. Facilities
A. Facilities requirements shall be determined by a site review
of each facility. The following elements should be estimated on
the assumption that existing station and LAN cable will be
reused and that the vendor will “tone and tag” equipment for re-
use. New cable to existing sites will be negotiated following
the site review.
1. Environmental considerations to be define on initial site
inspection
a) Convection cooling preferred. If not, provide yearly
environmental costs
B. Negotiated price for additional cabling will be frozen not to
exceed contract price
IV. Additional requirements
A. System life cycle upgrades
1. Training provided at no charge
2. Upgrade schedule not to exceed specified contract cost
B. Training
1. Provide training for two system administrators. Training
package to include any follow up training
2. End user training (system and voice messaging)
a) Provide training beginning one week prior to system cutover

b) Provide training for a minimum of two weeks post system
cutover or until 90% of the users are trained
C. Documentation
1. Two sets of full system administrator manuals
2. End user voice messaging and system manuals as required
over the system life cycle
D. Installation
1. The voice messaging shall be in-house a minimum of 5 days
prior to cutover for the following purpose:
a) Programming/recording of system prompts
b) Developing of main menu
c) Set up and installation of user mailboxes
2. Voice messaging shield during system cutover
3. System cutover not to exceed 48 hours. Cutover to begin on
a Friday at 18:00 hours
E. Current telephone equipment
1. Broker by incoming vendor.
F. Our current long distance provider is xxxxxxxxxxxxxxx.
Page 1 of 4 R equest For Proposal version20100310

R equest for P r oposal (R F P )
P ur pose
W orld C ommunity G rid is seeking proposals from research
organizations interested in harnessing
the immense power of I nternet-connected computers to
accelerate humanitarian research. Our goal
is to support innovative efforts that will benefit most from this
technology and promise to deliver
significant results on the most pressing issues facing the global
community. T o meet this goal,
W orld C ommunity G rid plans to implement as many as five
research projects per year.
B ack gr ound
G rid technology joins together many individual computers,
creating a large system with massive
computational power that exceeds the power of a few
supercomputers. T his capability can be
applied, on a global scale, to very large and complex problems
for the benefit of humanity.
I n 2003, the I B M C orporation was one of the sponsors of a
smallpox study that took advantage of
grid computing. T his study, using today’ s largest available
supercomputers, would have taken
years to complete. W ith grid computing, this study was
completed in less than six months and
identified 45 potential smallpox-treatment candidates.
W or ld C ommunity G r id: A P hilanthr opic I nitiative

A s a result of the smallpox study success, I B M sought
partners to create W orld C ommunity G rid as
a wholly philanthropic initiative, with the vision that it would
be the world’ s largest public
computing grid tackling projects for the benefit of humanity. T
he name was chosen carefully to
represent the endeavor’ s reach (worldwide), its volunteer and
scientific collaboration (community),
and its technical underpinnings (grid computing).
W ith technology and funding provided by the I B M C
orporation, W orld C ommunity G rid is making
grid technology available to public and not-for-profit
organizations to use in humanitarian research
that might otherwise not be completed due to the high cost of
the computer infrastructure required
in the absence of a public grid.
W orld C ommunity G rid is designed as a resource for research
done with a philanthropic or
humanitarian purpose and will only be available to projects
conducted for public and not-for-profit
purposes. I t will serve as a useful tool for the completion of a
certain stage of research, hastening
the progress of projects into further phases of development. R
esults must be made available to the
global research community by the sponsoring research
organization and remain in the public
domain.
B ecause projects must serve to promote human welfare directly
or indirectly, it is anticipated that
projects in the following disciplines will be run on W orld C
ommunity G rid:

of 4 Request For Proposal version20100310
• New and existing infectious disease research: Research on
cures for HIV and AIDS,
Severe Acute Respiratory Syndrome (SARS), malaria, and
others.
• Genomic and disease research: Studies that seek to identify
the functions of the proteins
that are coded by human genes and how they might relate to
cures for common diseases.
• Natural disasters and hunger: Earthquake predictions,
information on improving crop
yields and livestock production, and evaluation of the supply of
critical natural resources
such as water.
• Environmental Research: Meteorology and severe weather
prediction, pollution
remediation, climate modeling, and others.
Research that has the potential to assist economically
disadvantaged communities and those in
developing countries or to provide the initial research that can
open new fields of inquiry will have
priority.
Technical Requirements
Projects must meet three basic technological requirements, to

ensure benefits from grid computing:
1. Projects should have a need for millions of CPU hours of
computation to proceed.
However, humanitarian projects with smaller CPU hour
requirements are able to apply.
2. The computer software algorithms required to accomplish the
computations should be such
that they can be subdivided into many smaller independent
computations.
3. If very large amounts of data are required, there should also
be a way to partition the data
into sufficiently small units corresponding to the computations.
Ideally, existing application software would meet the above
requirements. However, if existing
software does not already meet the required characteristics,
there may be technical modifications or
alternatives that could satisfy the requirements. In order to
meet the goal of opening new areas of
inquiry, World Community Grid will seek at least one project
each year that has a viable research
proposal yet requires technical support to develop application
software. The assessment of the
project usually will require technical discussions with World
Community Grid’s technical teams to
explore the possibilities and effort required to adapt the
project’s computational tasks to best exploit
the grid. This will ultimately be a factor in deciding whether to
proceed with a particular project.
Selection Criteria

Projects must meet the following Selection Criteria:
1. Project has specifically stated goals and anticipated results
and explains how the work will
significantly contribute to the eradication of human suffering or
benefit humanity. World
Community Grid welcomes projects that demonstrate the
potential to assist economically
disadvantaged communities and developing countries, or to
provide the initial research that
can open new fields of inquiry that benefit humanity.
Page 3 of 4 Request For Proposal version20100310
2. Project meets grid computing technical requirements and is
grid-enabled. The project shows
evidence that the project results will be accelerated by the use
of grid computing technology.
3. Project has adequate funding to complete the proposed
research and leverage World
Community Grid.
4. Project is not already running on another grid or
supercomputer.
5. Sponsoring research organization has the capacity to
complete the project and maximize the
use of the results generated through World Community Grid.
6. All information in the proposal is complete and accurate.

These criteria will be used for the first phase of proposal
review.
Review Criteria
Proposals that meet all selection criteria will then be evaluated
according to the following Review
Criteria:
1. How important is the proposed activity to advancing
knowledge and understanding within
its own field or across different fields?
2. What may be the benefits of the proposed activity to society?
Will there be a benefit for
economically disadvantaged communities or those in developing
countries?
3. What impact can World Community Grid have to accelerate
the research or reduce costs?
4. Is the proposed method or approach reasonable?
5. To what extent does the proposed activity suggest and
explore creative and original
concepts?
6. Will the results be disseminated broadly to enhance scientific
and technological
understanding?
Final decisions for all applications are at the sole discretion of
World Community Grid.

RFP Process
The following is the process that World Community Grid’s
project team will follow in reviewing
and approving proposals, as well as preliminary information on
the process that will take place once
a proposal is selected.
1. Research organizations are invited to visit
www.worldcommunitygrid.org and download a
copy of the Request for Proposals and the Proposal Application.
2. Once downloaded, the research organization completes the
required information (including
Attachment A: Affirmation of Non-Discrimination and Patriot
Act Compliance) and sends
it, via email, to [email protected] Submissions should not
contain confidential
information of the research organization. Once a proposal is
selected for World Community
Grid, summary information will be made available on the web
site.
3. In cases where similar proposals are received from different
organizations, the one received
first, based on the date and time stamp of the e-mail, will
receive preference, if all
Page 4 of 4 Request For Proposal version20100310
requirements have been met by both proposals. World
Community Grid staff may also

facilitate and encourage collaboration between and among
organizations submitting
complimentary proposals.
4. World Community Grid’s project team will review each RFP
response and pre-qualify it for
running on World Community Grid based on the six selection
criteria provided above.
During this step, the project team may contact the research
organization for more
information, if necessary.
5. If a proposal is complete and it is determined that the
application described in the proposal
meets the six selection criteria for World Community Grid, then
it will be evaluated by a
World Community Grid review committee.
6. External subject matter experts will review all qualified
RFP’s submitted by research
organizations on a quarterly basis. Updated information on the
schedule for reviewing and
selecting proposals will be posted on
www.worldcommunitygrid.org.
7. If World Community Grid accepts an application, then the
World Community Grid project
team will contact the research organization to inform them that
the application has been
accepted. Final decision for all application decisions are at the
sole discretion of World
Community Grid.
8. Once the acceptance is mutual, World Community Grid and
the research organization both
sign a Project Hosting Agreement.

9. Following the signing of the Project Hosting Agreement,
World Community Grid’s project
team schedules the application to run on World Community
Grid and builds a project plan
with the research organization.
10. Following the conclusion of the project, the research
organization will make results
produced by World Community Grid freely available to other
research organizations as
provided in the Project Hosting Agreement.
11. World Community Grid will work collaboratively with
research organizations to encourage
public visibility and high participation in the grid project as
well as wide dissemination of
research findings and impact.
Contact Information
Please send any questions to [email protected] with your name,
email address, and
telephone number. Additional information and FAQs are
available at
www.worldcommunitygrid.org.
Request for Proposal (RFP) Template
Project Title
Company Background [Insert a concise paragraph outlining
your company’s background. Four to five sentences is a typical

length for a small or medium-sized company.]
Project Description [Insert a summary of your project, including
the problem/opportunity, goals/objectives and any information
that will help the vendors understand the need for the project.
Be sure not to outline specific requirements in this section. A
small project may consist of eight to10 sentences while a larger
project could be several pages in length.]
Design Requirements [Insert an outline of any requirements that
pertain to the design of the project. This could vary depending
on the type of project. For example, a website or marketing-
related project may include information regarding branding
standards or a style guide, whereas an IT project may include
information pertaining to how the project deliverable will
operate. Length varies widely based on the type of project.]
Technical and Infrastructure Requirements
[Insert any technical or infrastructure-related requirements,
such as a server or database configuration. Length varies
depending on the type of project.]
Functional Requirements
[Insert an outline of all the functionality you would like your
project to have and include a short description. For example, an
e-commerce project may include a catalog, shopping cart, order
history and a related products page. Length varies widely based
on the type of project.]
Estimated Project Duration
[Insert the estimated duration of the project or the required
completion date.]
Assumptions and Agreements
[Insert a list of any assumptions or agreements the vendors must
meet. For example, you may want to indicate that bids cannot
exceed a certain amount, that the proposals will not be returned
or that you reserve the right to dismiss any proposal for any
reason. Length varies depending on the type of project.]
Submission Information[Insert the deadline for submission and
the mailing and/or e-mail address]

For Additional Information or Clarification
[Insert a list of contacts who will be available to clarify any
questions regarding the RFP. It is not uncommon to have
separate contacts for specific disciplines; for example, one
contact for technical questions and another for marketing
questions.]
Basis for Award of Contract
[Insert a short paragraph or list that outlines your evaluation
criteria. It is not uncommon to list the weight that each criterion
holds in relation to the others.]
Anticipated Selection Schedule
[Insert the schedule for your selection process.]

Website Request for Proposals (RFP)1. DESCRIPTION, PURPOSE AND O.docx

Recommended

Recommended

More Related Content

Similar to Website Request for Proposals (RFP)1. DESCRIPTION, PURPOSE AND O.docx

Similar to Website Request for Proposals (RFP)1. DESCRIPTION, PURPOSE AND O.docx (20)

More from celenarouzie

More from celenarouzie (20)

Recently uploaded

Recently uploaded (20)

Website Request for Proposals (RFP)1. DESCRIPTION, PURPOSE AND O.docx