I think you're trying to solve a valid problem - i.e. allowing Excel type data to be manipulated/formatted more easily than Excel (or similar tools) currently allow. And I think you have a cool product, but...
But I don't think this is a solution to that problem for most people who have that problem.
My previous job involved a lot of Excel work (so I became fairly good at it) and it also involved interacting with people (often clients) who used Excel occasionally and really werent very proficient at using it. So for simplicity, lets imagine the world of excel users is made up entirely of those two types, and lets call them A and B respectively.
Types As don't need this service - they can do all the things you showed in Excel quickly (using keyboard shortcuts etc), using formatting codes (even though Excel format codes are clunky. eg. SSN format code is: ###-##-####).
Type Bs do need your service. But will they use it? If they use Excel rarely then is it worth the overhead of knowing how to use a separate service (even a simple one)? If they can't figure out how to use Excel codes then are they the type of person who will be interested in exploring new services? (note, this is about the type of person, not about how simple your service is)
OK, so the world of Excel users is not as simple as the A/B world that I describe. There is no doubt another type C somewhere between the two who might value this - but how many of those are there? My gut says 'not many', but I don't have data. Can you describe to me your archetypal customer?
Making this an Excel plug-in might solve this overhead problem somewhat, but even then, the latter issue still remains.
I am probably type C. I think type C might be quite big.
The type of person who can't program a blog but can & will install a Wordpress if she can find decent instructions because blogger doesn't let her do XYZ.
The type of person who can & will use forum code but can't use html/css.
The type of person that can & will set up a hosted online shop but can't alter the code.
Basically, if the problem exists & the excel solution is not something that you would just come across in excel without knowing, it comes down to what solution you do come across.As an online app, this might have a better chance of being that.
The second thing is this: would you (A) prefer to explain to your clients (B) how to use the excel solution or send them a link to this?
But I don't think this is a solution to that problem for most people who have that problem.
My previous job involved a lot of Excel work (so I became fairly good at it) and it also involved interacting with people (often clients) who used Excel occasionally and really werent very proficient at using it. So for simplicity, lets imagine the world of excel users is made up entirely of those two types, and lets call them A and B respectively.
Types As don't need this service - they can do all the things you showed in Excel quickly (using keyboard shortcuts etc), using formatting codes (even though Excel format codes are clunky. eg. SSN format code is: ###-##-####).
Type Bs do need your service. But will they use it? If they use Excel rarely then is it worth the overhead of knowing how to use a separate service (even a simple one)? If they can't figure out how to use Excel codes then are they the type of person who will be interested in exploring new services? (note, this is about the type of person, not about how simple your service is)
OK, so the world of Excel users is not as simple as the A/B world that I describe. There is no doubt another type C somewhere between the two who might value this - but how many of those are there? My gut says 'not many', but I don't have data. Can you describe to me your archetypal customer?
Making this an Excel plug-in might solve this overhead problem somewhat, but even then, the latter issue still remains.