4 ms·
I am not going to say that I agree or disagree with this methodology, but let me give you some context. Traditionally, getting into the GSA schedule is a lot of
by rburhum 11y ago
I am not going to say that I agree or disagree with this methodology, but let me give you some context. Traditionally, getting into the GSA schedule is a lot of work and it takes a lot of time. So much indeed, that it doesn't make sense for most startups to do this.
For some startups in the Govtech space this makes more sense. It is a way to hack the procurement process. I would happily get one of our devs to put something together that uses our Open Source codebase and solves this "challenge" than to spend months navigating all the bureaucracy to get in the schedule.
Somewhere around $50b/year go through the GSA schedule (http://www.gsa.gov/portal/content/198473 http://www.gsa.gov/portal/content/198473) so, IMHO, anything that makes this process easier is a step in the right direction against traditional vendor lock-in.
- cjoh 11y agoUnfortunately the schedule 70 provision in this RFQ requires that you both get your devs to put something together using your open source codebase, AND spend months navigating all the bureaucracy to get on GSA schedule 70.
- ewams 11y agoThis is not open to anyone, you still have to be gsa sched 70.