I'm creating http://www.dwgdrop.com http://www.dwgdrop.com (soon to be DrawVault) we are currently about one month away from a V1.0 launch. Interestingly in an

I'm creating http://www.dwgdrop.com http://www.dwgdrop.com (soon to be DrawVault) we are currently about one month away from a V1.0 launch. Interestingly in answer to your question i'm building an application in the non-developer space as a non developer. I work in the architecture industry & my app is aimed at providing architects, engineers, building contractors and other related fields with an easy way to send and receive drawings and files, and also keep track of revisions to those files. Effectively its a repo for architectural & engineering drawings. I came up with the idea by employing 37 Signals style "scratch your own itch" method. While searching for a solution to replace the tedium of sending through email and local filing that seems commonplace in the industry i found platforms that are similar available for very large scale construction (read 100m, 1b etc) works but didn't scale well enough to be a viable option (price-wise) for small scale to include projects in the order of 500k - 5m etc. I think that we hear and talk about "scaling" in the start-up community but we often overlook the possibility of building apps that "scale down" features from a much larger successful software. These smaller apps could theoretically have an untapped access to consumers/businesses that are out-priced by larger software systems. *Edited for clarity