5 ms·

llarsson, I think you are spot on with this comment :-) Also thank you for the advice. We have indeed gotten a good response in the less-technical, but more bu

llarsson, I think you are spot on with this comment :-) Also thank you for the advice. We have indeed gotten a good response in the less-technical, but more business oriented, RPA developer community, as an addition to appealing to the traditional software developers. (Many data scientists can obviously appreciate the idea, but the added value of this kind of tool is not that high, if you already have a routine for doing custom models & analytics) Still, we have also faced situations, where the users have been too non-technical. I think the jury is still out on, whether these kind of solutions can be easily used by the average accountant or a business analyst.

llarsson 6y ago
For those last ones, try to figure out if there are a few systems that they commonly use and make integrations with those and be able to provide some kind of answer to interesting queries. It's great that you have a general solution, but even those need to be made into specific products and services that non-technical people can appreciate for the value they bring. And the message needs to be crystal clear for them, because a general solution is too broad. "This will analyze your customer behavior and tell you which ones will likely order new units from you next month or quarter, and how much." A broad and general tool like yours does not, in itself, solve the problems for them, so you have to help them understand what it can do.