How to write an RFP for IT services that vendors actually answer
Most IT services RFPs get thin, generic responses because they ask the wrong questions. Here is a structure that gets you comparable proposals in two weeks.
Blog
How to write a brief vendors answer, which engagement model fits, what a delivery location changes, and what a profile that gets shortlisted looks like. Written from what we see on the marketplace.
Most IT services RFPs get thin, generic responses because they ask the wrong questions. Here is a structure that gets you comparable proposals in two weeks.
The three ways to buy IT services, what each one costs you in risk and in money, and the questions that tell you which one a project needs.
The sales deck answers the questions the vendor wants you to ask. These are the ones that predict how the project will actually go.
Rates are the obvious difference between delivery locations. Time zones, turnover, data rules and who you can meet in person matter as much, and they move in different directions.
The platform decision gets all the attention, but the scope decides the cost. What to settle before you compare platforms, and the questions to ask the partners who'll build it.
The vendors are in the directory, with every fact labelled with its source. Browse them by service, technology or country, or post your project and let matched vendors come to you.