Quoting Project

I have been looking for some guides on quoting a project. Well, I swear that I have seen it thousand times when I didn't really looking for it. But somehow, when I try to look for it, it is not much reliable, or at least believable source on the net that talk about how to quote a project.

Which is really strange.

Still, here are some information I manage to grab by googling around. Not much, but hopefully something to start with... well if someone could chip in to share on their experience in quoting a project, would be really appreciated. :-)

There are 2 podcasts from Freelancing on Rails, talking on Quoting a Project, part1 and part2, and also a podcast on Contract and Agreement , almost exactly what I need at the moment. But the download is still in progress due to my pathetic bandwidth, so can't say if it is really helpful at press time, we will see.

Freelanceswitch site offer a few tips on this as well.

• 9 factors to consider when determining your price.
• Hourly vs Fixed Pricing.
• The price is right
• Even a calculator just to guide to on calculating hourly rate.

And here is an dated discussion in the popular Joel on Software Discussion Group.

But still, I remember I have seen much much more people talking about how to quote their project on the net, just don't know where they are hiding, hmmm...have to dig deeper.


Update
Now, here are more tips on quoting/pricing a project.

• Blue Favor's Pricing a Project.
• How to set a price for Web project Well, this is more for Web design work, but still can be a reference I think.
• How to Charge, A rather old article from Ellen Rohr, but still relevant I think.

Well, the danger is now I get more articles and guides to read that I might spent more time on it than actually working on the project..haha.

The BareNaked App...

Carson System (guys who developed DropSend ) are coming up with their new application, Amigo.
Inspired by 37 Signal's getting real process, they go on to blog about the steps to get their new app running in BareNakedApp,

"documenting some of the little steps, including estimating timelines and costs, picking freelancers, branding, naming, and legal decisions" as mentioned in WorkHappy.net

I have only read about 5 to 6 posts, from the initial wireframe design to hiring freelance developer and designer. Some cost estimation of the project as well. And reading their blog is like seeing a baby grow up in front of you (though that is other people baby), something like Start-up-Truman-show? :-)

Seriously, the blog is really informative and inspiring for all the wannabe start up. And make sure to start reading them from the beginning.

Lesson for startup...

here's nothing particularly grand about making money. That's not what makes startups worth the trouble. What's important about startups is the speed. By compressing the dull but necessary task of making a living into the smallest possible time, you show respect for life, and there is something grand about that.

Well said, I think Paul Graham latest essay "The hardest lesson for startup to learn" again prove to be spot on. Though I have some reserve about 'nothing particularly grand about making money', :-).

37signals...

Has been reading Loud Thinking and Signals vs. Noise. Of course, with all the hypes now surrounding 37 signals and Ruby on Rails, almost everyone read them.

But, I remember I have read it somewhere a motto or slogan or something similiar of 37 signals, which is really inspiring, and which I think is actually the origin of their latest effort Getting Real and earlier Defensive Design for the Web.

I have searching for it high and low by googling for "37 signals motto", "37 signals slogan", etc... but just could not see it anywhere, not even by searching it in SVN. Just when I thought that I would not be able to find it again, somehow, I found it by googling for "37 signals manifesto"!! Of course, it is not motto, not slogan, but manifesto! :-)

So, here, if you are looking for the link as well...

37Signals Manifesto