Tag Info

The terms don't really matter unless you have a big legal budget to fight it out in court. More useful is to have staged payments and withhold those payments if you aren't satisfied. As an example, you might specify that 50% is paid at "feature complete", 25% at completion and the remaining 25% some time after delivery, when the quality can be properly ...

See, outsourcing is not bad, however it is not a silver bullet either. You can not just hand over the specs to your developer and hope that everything will turn out good. You need to be participating in many activities which are involved in software development. Now you have mentioned two points: Uptime - First you can arrive to a feasible uptime. Don't ...

I don't know about this being the optimal approach, but here is a sales strategy that has worked for us in the past for getting a new product off the ground: Visit businesses in your target market. If it's big business you will probably need to do some research on who to present to. If it's a small enough business you can probably walk in the front door ...

Books: Two books that I know of that give specific step-by-step, actionable road maps for how to do this best are The Entrepreneur's Guide to Customer Development - www.custdev.com - by Brant Cooper and Patrick Vlaskovits and Ash Maurya's Running Lean - www.runningleanhq.com. For example in the custdev book you first validate your core hypotheses regarding ...

Since you clarified to state mainly BETA testing... my suggestions would be to try to give as much information as possible. Let them see what you are working on / fixing / changing per feedback. I think that this helps them know that their time is actually valuable. If your site has badges, subscription or something else for users, offer them something ...