Comments on: Initial recovery.gov pricetag: $9 million (Updated)

By: Timon

Timon — Sat, 11 Jul 2009 05:42:54 +0000

Twitter as we know it was built for about $15-20 million. Google lasted almost a year on $100,000 before taking over the world with $25 million of investor money. This is highway robbery, you could hire 25 PhDs with this. There probably isn't a company in the tech-sector top 100 that had this much money in its first 6 months. This is more like the B series venture investments of extremely promising and innovative companies like Aster Data, 23andme, NanoBio, etc.

What a tremendous starting point for recovery act transparency and efficiency -- they waste vast amounts of money on the mechanism to ensure we don't waste vast amounts of money. It reminds me of the Vietnamese government anti-piracy office, which runs on pirated Windows.

By: Timon

Timon — Sat, 11 Jul 2009 01:42:54 +0000

By: Timon

Timon — Sat, 11 Jul 2009 00:42:54 +0000

By: Nick

Nick — Fri, 10 Jul 2009 20:22:56 +0000

I'm a software engineer who has built web applications for Office Depot, Target, AIG (no I'm not proud of it) and many others. J. Stephens apparently has not worked in the private sector. Even with the requirements that he noted, the price tag on this project can not be described any way other than “theft”. There is a reason that we're not allowed to see what is included in the price tag… because there is nothing they can say to justify the cost that would be believable by anyone who would know better.

By: cordblomquist

cordblomquist — Fri, 10 Jul 2009 20:08:01 +0000

If I make a website that has a 10GB database and another with a 10,000GB database, the cost of the second is not 1000 times that of the first. The second site would perhaps cost more to host, but the software that feeds out the smaller amount of data could serve out the much larger amount just as well. So, it's not fair to say that a federal version of a transparency site should cost 50 times that of a state-level site.

The $300,000 state-level site is also questionable. Building a website that's purpose is to simply display data in a clear way that is easily searched is not an expensive proposition.

The reason this site is going to cost the taxpayers $18 million when all is said is done is because of the convoluted federal bidding process that shuts out all but the most politically connected contractors. This is why a DEFENSE CONTRACTOR is building this website, instead of one of the hundreds of top-tier web software developers in the country.

Perhaps we need more transparency in order to build a good transparency site?

By: cordblomquist

cordblomquist — Fri, 10 Jul 2009 20:07:16 +0000

By: The Agitator » Blog Archive » Afternoon Links

The Agitator » Blog Archive » Afternoon Links — Fri, 10 Jul 2009 17:40:43 +0000

[...] Feds shell out $9 million to build the recovery.gov site. [...]

By: Christopher Dorobek

Christopher Dorobek — Fri, 10 Jul 2009 17:39:37 +0000

Jerry,
You can find the pre-solicitation notice from FedBizOps here:
https://www.fbo.gov/index?s=opportunity&mode=fo...

That is all I have been able to find. If you find a copy of the actual RFP -- or the contract -- I'd love to see it too.

In the meantime, my take on the Recovery.gov contract questions...
http://federalnewsradio.com/?nid=150&sid=1714884

By: J. Stephens

J. Stephens — Thu, 09 Jul 2009 22:50:09 +0000

My off the cuff response is that it doesn't make sense to compare the costs for a website of this size to a state website which serves 1/50th of the users. if it includes database support, video production costs, or hosting capacity it could add up to be quite a bit more than the state's web sites you found that cost $300k. Multiply $300k for one state's worth of viewers by 50 (for 50 states worth of capacity; sorry Guam, DC, et al) and you get $15 million. To be sure, there are economies of scale when you scale up and capacity is just one subset of costs, but you get the point that some of the costs are variable and depend on the number of viewers. Another factor somewhat unique to federal govt. contracting: a fair amount of time and money gets spent complying with and reporting on small business admin. set asides, section 508/ADA disability compliance, and many other standard add-ons the federal government typically requires which the states might not bother with.
So in addition to scaling up the number of users of a federal vs a state system (at least 50 times more capacity is required than for a state system--that means many more servers, splitters, etc.), one should also look at any additional functions/content they are adding in, computer security precautions that exist at the fed level which don't exist at the state level, the need (if any) for people with security clearances for amounts spent on classified projects that doesn't likely exist at the state level, and also the amount of content they have to handle; i.e., the amount of money being spent that they have to track on this website is immense and dwarfs any prior state and federal projects. If they actually need accountants around to monitor things or provide analysis, then that will add up quickly. It all depends on the requirements for the site. Cheers-