ConceptShare began as a solution to the problems we had sharing ideas, and the frustrations of communicating changes to creative work.

We used email, instant messaging, fax and even courier to share design concepts. It was difficult to communicate changes to visual designs with text. We were frustrated with going back and forth to just to explain how we wanted changes done.

Design stakeholders all had different ways of reviewing, marking up and commenting on changes. The more people on the project, the more disjointed the conversation became. Team members added later in projects were not privy to the conversations that preceded them.

Then there were the face to face meetings. They broke the creative flow of designers, and the combined productivity cost of everyone in the room wasted too much resources. Often enough they didn't have concrete agendas or timeframes, and led to design by committee and false consensus.

We knew we had to do something to solve these problems, and ConceptShare was born.

Developing ConceptShare was a unique chicken and egg scenario. We were in an interesting situation where we needed the application to help build the application. Luckily, we each understood the problems from our experiences as developers, designers, account managers and clients. We matured the application as we used it to design itself, websites, booth designs and cards. Feedback from customers has also been invaluable, so drop us a line.

Our Principles

• Build engaging user experiences
• Simple products that solve real problems
• Help customers save time and money
• Blur the line between desktop and web based applications
• Encourage community participation