Here is the step-by-step process I followed to create my latest software product. It took less than 24 hours, with a total budget of less than £50.

On Monday evening, while working on the Help Guide for my new Flash Video Wizard software , I thought it would be a real time-saver to have quick way to create windows icon files. The eBookcompiler software I use to make all my Software User Guides, eBooks and other tools (like the Profit Calculator and Auction-O-Matic) requires a specific type of windows icon file to be used which is limited to just 16 colours.

I did a search on google, and couldn't find a simple, cheap and easy-to-use windows icon creator, that worked with the compiler so I decided to create the tool myself and make it available to others.

I started this project on Tuesday morning, (this week) - and had it completed less than 24 hours later.

By completion, I mean I had the software developed, debugged, came up with a product name, registered a domain, created a sales page, and placed the product on the web for use.

Here's how I did it.

Product Name: Icon Magician

Product Description: Software tool for Product Developers and eBook Publishers to create windows icons quickly and easily.

Profit Potential: Created mainly for viral marketing purposes, at some stage offer for sale with resale rights. May also sell the products source code to other product developers who want to add a branded version of product to their catalogue, or who also want to benefit from viral marketing.

Development Process:

• Found need for specific tool.
• Searched web for similar tool. Found none.
• Wrote out the specifics of what I wanted to the tool to do.
• Wrote a project description.
• Posted project description to www.scriptlance.com to find a programmer to develop it.
• Within minutes of posting project description, received several bids. Accepted bidder to do project for $50. (£26.80)
• Went to www.123reg.co.uk and began search for unused domain name suitable for product. (£8.99)
• The name I wanted was already registered, so I used the free name suggestion tool at www.nameboy.com and decided upon IconMagician.com
• Scriptlance developer sent me first draft of program one hour after he accepted project. I tested the program, found a few areas for improvement, and sent back to developer.
• Developer made changes and sent them to me. I tested, and approved, and paid developer. Entire process took 5 hours.
• Created the eCover and Header Panel graphics (and a windows icon!)
• I continued to test and make minor cosmetic changes to the program I had developed.
• Created a simple sales message for the Icon Magician software..
• To get the product on the web quickly, placed the program in the online shop of www.Nick-James.com, and then used URL re-direction feature at 123-reg to forward www.IconMagician.com to correct page at Nick-James.com.
• Tested the ordering process.
• Began viral marketing promotion.
• Total time invested in project: 3 hours
• Total expense: £35.79

Other Details

In the past few weeks I have developed several small projects like this following basically the same process as detailed above. Here's what I have learned:

1. Coming up with a simple idea for a tool that has a very specific (and simple) purpose is the first step. The tool must be easy to use, easy to understand, and require little or no support.

2. The second step is writing program specifications in a way that www.scriptlance.com programmers can understand well enough to be able to quickly get the project done.

3. It helps if you can provide the programmer an example of what you want the project to look like, along with very clear details of what the program can do. The better detail and examples you provide, the better the results you get.

4. Choosing a quality programmer from all that will respond to your project proposal can be difficult. You'll often get 30 or more responses, all promising quality work at low prices. On the internet, anyone can make promises. For best results, look for programmers with high feedback scores, avoid the rest.

5. Before accepting a bid, ask how long to get the work completed. If it more than a few days, either you have the wrong programmer or the wrong project.

6. Before you pay the programmer, have them send you the program, and test, test, test. Make sure the program works the way you want. And if you need changes, ask for them before you pay. If the changes are well beyond the original specs, offer to pay extra.

7. If the project is done to your satisfaction - pay quickly, and post positive feedback for the programmer. This keeps the programmer happy. Important if you plan to use them again for future projects.

Success with these kinds of projects hinges on choosing simple projects that have a very clear purpose. Easy to use, easy to understand, little or no support.

Avoid the complex projects - they almost always fail.