Written lovingly by Jake Stride on April 29th, 2008.
When launching a new product, such as Tactile CRM, I have found there are two main areas that you need to work on. The first is obviously writing the software itself and the second is marketing that product and getting people to use/pay for it.
Tactile CRM has been live for a couple of months now and we are really pleased with the number of people signing up (we are currently on target for our projections). The main push now is twofold - development and sales/marketing - and more around the sales/marketing side of the application than the development.
Don’t get me wrong, Tactile CRM is an awesome piece of software from a technical/engineering perspective - it is really well built, easy to expand and add to, and the feedback we get from users is excellent. Obviously as Senokian we are comfortable with the development of an application like this as we do it on a regular basis for customers.
The new and unknown area for us however is the sales/marketing side of things. Adwords, and exhibitions/trade shows are easy to cost/plan, the difficult part is getting the buzz around the product - people and sites talking and discussing your application.
So far we have had a reasonable amount of success with our marketing, the graph below shows two decent spikes. The first was getting mentioned in the Amazon AWS newsletter, the second appearing on the new Google Solutions Marketplace. Both of these obviously drove a decent amount of traffic and sign ups to the site, however we need more people to talk about Tactile CRM.

Currently I am working on getting coverage on ReadWriteWeb and TechCrunch. Which brings me on to my current dilemma. Do we add new features we think are useful, or go for the bigger ones that are likely to get more press coverage (and still be useful in the long run).
I’m thinking things like the Google Contacts API integration we did - we were doing import work that people had asked for and at the same time Google launched the new API. As a result we were the first CRM system to implement it and a few people picked it up. ReadWriteWeb included us in an article on Socialprise and helped to drive more traffic to the site. This wasn’t a feature people request but one we added for PR purposes.
So the dilemma I now face is should the next set of features we add be for PR/marketing purposes or customers. I know the answer to this question when a product has reached critical mass is to add features for users but as we are not there yet, the PR/marketing drives the users and is the most important thing at the moment.