The way we got our first users for Woobius was that some of the initial team were architects, and we had strong links with a number of architecture firms. So wh

The way we got our first users for Woobius was that some of the initial team were architects, and we had strong links with a number of architecture firms. So when the product was barely useable, we deployed it and got them to start trying it out. There followed a frantic search for a decent host when we realised that those people were using Woobius for real live projects and they'd get rather annoyed if it suddenly vanished in a hard drive crash or the like. Anyway, to cut a long story, since Woobius is a naturally viral tool (see http://danieltenner.com/posts/0009-how-to-make-your-application-viral.html http://danieltenner.com/posts/0009-how-to-make-your-applicat... ), it spread from that initial kernel, with effectively no marketing. If you don't have strong connections to potential users of your product, I would advise building a different product.