Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In the early days, we had a policy that we would not respond to RFP's. The time required vs. value does not make sense for startups (unless you've already been told you'll win and the RFP is just a formality).


> The time required vs. value does not make sense for startups (unless you've already been told you'll win and the RFP is just a formality).

That's also true for more-established companies, who often are just column fodder so that the procurement people can say that they've done their due diligence.


We've taken that attitude to on some RFPs. Occasionally we have responded with a "We aren't able to respond because ...." letter.

Basically tell them why its not worth your while to respond.

I believe that in a couple of cases, this may have caused the customer to rethink and then come back again later with an easier RFP.


Out of interest, how many times did you faux-offer an RFP, knowing that you would win?


Just once. We had to fill out the paperwork for their procurement and compliance teams, but I don't think it was a public RFP.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: