The winning statement!
This is one of several issues that we see a lot now, where the techies try to sell a product based on techie things.
Again, sell the sizzle, not the sausage!
You're absolutely right. Unless you're offering something to a very technical market, no one cares about the technical side of things.
99% of the time clients don't care what goes on behind the scenes, all they care about is, does it solve their problem (I've done some business analysis and requirements gathering on other projects).
Sadly, the way I've expressed some of my communication on here hasn't reflected how I'd present it to potential customers. In my mind I've segregated my customers and this place into two separate audiences and communicated to them individually. I'm not saying I've done that well btw, I clearly have not.
My ideas, the app, my website copy are evolving each day the more feedback I'm getting. The current iteration of my website copy doesn't have a single reference to the technology used.
I'm not at a point where I'm ready to share the website just yet, as it's still very much a work in progress, as is everything about the app (and I'm aware you can't ask for website reviews without paying), but here's an example of some of the things it's highlighting at the moment;
- Uncover hidden insights into employee mood
- reduce turnover by up to 20%
- increase ROI and profit
- happy employees are 12% more productive
- potential savings of £2,000 per employee annually
I also have a savings calculator that shows potential savings based on number of staff and current staff turnover rates, and shows workings out based on % improvement in productivity and % reduction in staff turnover and explains how we got to those figures.
I'm by no means saying I know 100% what I'm doing, or that there's not improvements to be made. Just trying to highlight that I'm not approaching this from what you might call a 'typical techie' mindset. I've worked alongside marketing agencies for almost 20 years now, and you pick up a thing or two. However, knowing the theory and applying it are two different things I'm still learning.
I'm not standing still either. This isn't a case of me treating the project I've built like a baby and ignoring the feedback that others have been generous enough to provide. The feedback I've received on here, and via other sources is constantly forcing me to evaluate the app, it's features, the target market, the message.... everything.
While I've moaned that some of the feedback on here has been negative at times, those same people have also provided some excellent feedback and valid concerns that I'm not ignoring. The point I'm making, and hopefully it's helpful to others that might read this is, people are going to give you feedback that you might not agree with, but do not dismiss it, look into it, question it, why don't you agree with it, can you work around it, how valid it is. Unless you're building something to solve your own problems, you've got to listen to what people are saying.