If you're looking for ball-park figures, if I was given a brief of 'Recreate KickStarter' I'd quote somewhere in the region of £5-10k for a fully bespoke ASP.Net MVC 3 web app. Agencies would obviously be higher.
You'd trust a project as large as Kickstarter to a freelancer? It's your funeral![]()
All of that would be the problem of the person who hired you. As the developer your job is to meet the requirements of the system.If you were recreating a website (service), like KickStarter, why would you bother?
...
£5-£10k is very cheap for a site like Kickstarters. Incredibly cheap.
All of that would be the problem of the person who hired you. As the developer your job is to meet the requirements of the system.
I agree, I would be charging in the region of £25-30k for a project more bespoke than Kickstarter.
How long would it take you to complete the project...roughly?
Also with a project that size, a deliverable would agreed, anything more asked for along the way would be charged extra, it's very easy for goal posts to move on large projects and easy to blow budgets.
This is a major problem with a project this size.
I'd be interested to hear your thoughts on the feasibility of doing such a large project in many small iterations. Surely the development team can release an iteration for client inspection, the client comes back with "I want herp added" to which you can reply "Well we can add that in the next iteration and it will cost you X extra".
...doing such a large project in many small iterations. Surely the development team can release an iteration for client inspection, the client comes back with "I want herp added" to which you can reply "Well we can add that in the next iteration and it will cost you X extra".
It's at that point you want the client to put ideas forward, not when you are mid way through the project.
Thesnipergecko - you've got it all arse backwards. Iterative development is specifically to tackle the problems you are highlighting. The client will, and should be welcomed to, make changes to the design throughout the development of the application. To tell them they must do all design up front is a failure. i.e. It will result in nothing but a failure.
Granted, the first iteration or two (or even three or four) will not deviate from the larger plan - the shorter the iterations the less of them will change. But as things come together, there will be many things that come up that just could not be seen at the start of the project. Working to small iterations means this will not be distruptive. You'll only be working on the next most important piece, and if your iterations are short enough, any change can wait until the next iteration anyway.
Technical problems arise, usability issues that couldn't be seen even with a magic crystal ball will crop up, they cannot be avoided no matter how much you scare the client into doing all design up front.