About PersoScan

One of the places it runs is selp.life, where a visitor has to say where something hurts before anything else can happen. Dropdowns of anatomical terms did not work there. A body you can rotate and tap did, immediately, on phones, with no instructions.

The same problem turns up in commerce. Stores selling supports, braces and recovery gear inherit their catalogue structure from the supply side, because that is how the boxes arrive, and then a shopper turns up thinking about one body part. Four menu items, and nobody tells you which of them has a knee sleeve in it.

A body map removes that translation step. Click where it hurts, land on the right collection. That is the entire idea, and it is small enough that we would rather do it properly than bolt nine other features on top.

It is not a medical device. All it records is where somebody pointed. It will not tell you what is wrong, how bad it is, or what to do about it. Anything past the pointing is your clinical workflow.

We do not publish conversion numbers we cannot stand behind. You will not find a "37% uplift" on this site. We have a handful of deployments, not a statistically useful sample, and a number pulled from one store would be marketing rather than evidence. When we have data worth showing, it will come with the sample size attached.

It is not right for every catalogue. If your products have nothing to do with the body, or you stock under roughly twenty of them, a body map is decoration. We say so on the comparison page, and we would rather lose the sale than install something that sits there unused.

We are small. That means you talk to the people who build it, and it also means we are not going to pretend to be an enterprise vendor with a support organisation behind a ticket portal.

Setup help is included on every plan, and it is not a courtesy line. The embed is never what goes wrong. It is the mapping, where one zone quietly points somewhere almost empty and the whole feature starts looking broken. We would rather spend an hour in your spreadsheet than watch you launch that.

The widget also runs unlicensed, with a small watermark, for as long as you like. Build the entire integration, test it against your real catalogue, and decide afterwards. That order suits everybody.