the lectern banner

By Steve Kelman

Blog archive

Innovation at a 95-percent discount

CTO Todd Park

U.S. CTO Todd Park oversees and champions the Presidential Innovation Fellows program.

In a recent conversation with a senior administration official, I was told about an accomplishment of a program started last August called the Presidential Innovation Fellows. This effort, run out of the office U.S. Chief Technology Officer Todd Park, brings about 20 smart people from the private sector to work in the government for a 6-month stint to jump-start a specific innovation initiative in cooperation with an agency. (FCW previously covered the program here.)

One of these innovation fellows, whose normal job involves website design, has been working on an initiative called RFP-EZ, which is an application to help companies who have never done business with the government before – especially startups with innovative solutions to government problems – walk step by step through the federal procurement process.

The idea to do this is itself a great one, and I will be following with interest as this is rolled out, to see if this helps improve access for small commercial companies in the federal marketplace. However, I bring this up in this post for a different reason – the Innovation Fellow’s work to develop the application itself. The idea for doing this predated the Innovation Fellows program, and this first-round fellow was brought in to help actually develop the application. As I understand it, the agency working on scoping out the project, based on their own past experience contracting for applications such as these, thought the application would cost north of a million dollars to develop. However, based on his own experience with web design, the Innovation Fellow estimated this would involve around $50,000 of time and could be done in a very short period  – and proceeded to do exactly that (he didn’t charge the government, since he was already a fellow).

This is an example of a phenomenon that one doesn’t run into all the time, but that happens often enough to be a source of real worry and of a need to dig more deeply to draw some lessons. It is not unheard of that situations arise where people from the commercial IT industry, outside the normal world of government contracting, either actually develop, or present a case after the fact for why it would have been possible to develop, applications meeting the same specs for a tiny, tiny fraction of what the government pays – not 10 percent less or even 20 percent less, but 95 percent less.

It is of course possible that in some of these cases, there are security or other issues that are not taken into account, and I feel relatively confident that these situations are the exception, not the rule. Nonetheless, I raised this issue with a group of contracting officers with whom I had coffee before Christmas, and one person told me that at his previous organization (in the intelligence community) they actually had a little office that looked at much lower-cost alternatives to approaches the agency was planning to use for developing applications, and that this office did at times find examples of ways to get applications developed for a fraction of what the government had been assuming it would be paying.

I think we need to try to peel the onion a bit on this. We do typically have competition on developing these applications, so there should be an incentive for a vendor to bid a much lower-cost solution. Is the problem that small commercial companies which might provide dramatically cheaper alternatives don’t want to get involved in the federal marketplace?  Or what?  Perhaps a good first step would be for the Innovation Fellow involved in RFP-EZ to come forth and, in a non-threatening way, explain the differences in assumptions or mindset or whatever between him and the government/contractor folks that produced this big gap in expectations of what it would take to develop this application.

Posted on Jan 08, 2013 at 12:09 PM

The Fed 100

Save the date for 28th annual Federal 100 Awards Gala.


  • computer network

    How Einstein changes the way government does business

    The Department of Commerce is revising its confidentiality agreement for statistical data survey respondents to reflect the fact that the Department of Homeland Security could see some of that data if it is captured by the Einstein system.

  • Defense Secretary Jim Mattis. Army photo by Monica King. Jan. 26, 2017.

    Mattis mulls consolidation in IT, cyber

    In a Feb. 17 memo, Defense Secretary Jim Mattis told senior leadership to establish teams to look for duplication across the armed services in business operations, including in IT and cybersecurity.

  • Image from

    DHS vague on rules for election aid, say states

    State election officials had more questions than answers after a Department of Homeland Security presentation on the designation of election systems as critical U.S. infrastructure.

  • Org Chart Stock Art - Shutterstock

    How the hiring freeze targets millennials

    The government desperately needs younger talent to replace an aging workforce, and experts say that a freeze on hiring doesn't help.

  • Shutterstock image: healthcare digital interface.

    VA moves ahead with homegrown scheduling IT

    The Department of Veterans Affairs will test an internally developed scheduling module at primary care sites nationwide to see if it's ready to service the entire agency.

  • Shutterstock images (honglouwawa & 0beron): Bitcoin image overlay replaced with a dollar sign on a hardware circuit.

    MGT Act poised for a comeback

    After missing in the last Congress, drafters of a bill to encourage cloud adoption are looking for a new plan.

Reader comments

Wed, Jan 9, 2013

A relationship with an employee is radically different than a relationship with a contractor- superior in many ways. There is likely not enough consideration of this when deciding how to fulfill requirements. However, one question: who supports this thing when the employee (or fellow) moves on to other things?

Wed, Jan 9, 2013 Steve Kelman

Thanks for these comments; I agree with both. Chris, yes this is anecdotal and may be exaggerated. But there are enough of these stories out there -- and if this is even ROM correct -- we as a community need to learn more about why this can be happening.

Tue, Jan 8, 2013

Steve - I think you are on the right track, as usual. It would be great to look at this solution more closely and I absolutely love the idea of the Government having an innovation office that looks at how to develop (and procure) innovative, small solutions at the fraction of the cost. I think that this RFP-EZ is a case where the application is fully developed and it would meet all requirements to make it 'go live.' I also think that this application was developed cheaply but will be more costly to 'make live' because of Security / C&A (required on all enterprise applications), 508 compliance, rigorous performance testing, etc. Developing an application and making it public/enterprise ready and security is often not taken into account during development. All of that said, more innovation fellows and small innovative developed solutions will drive more competition and get results into production more quickly!

Tue, Jan 8, 2013 Chris Hamm Arlington VA

This feels a little nit picky, but I want to parse a minor detail. By using an anecdote of cost estimate (e.g., one person said it would cost $1M), I would have a hard time claiming $950K in savings. One person's comment is not exactly a proven estimation approach. With that said, the cost to developing applications in the federal environment is very, very inflated. I love the idea of rapid bursts of development teams that are not constrained by all the bureaucracy.

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above

More from 1105 Public Sector Media Group