Item — HN Reader

What kind of customer lock-in do you have? Is the API/data format open or closed? Can I easily export my data?

As a customer, I'd be concerned about longevity and data loss if/when you go away or pivot. Knowing that I could export my data, and re-implement my own backend using your open data standard if needed, would go a long way to easing my concerns.

Most customers won't go through the effort to build their own solution, and for those few that do you can easily out-perform with service, experience, and expertise.

You could even offer bespoke integration services...

2 comments

Thanks for the feedback, I think you are raising a valid point

We have built the platform with APIs in anticipaction of integrations with SAP, Pronto, etc. We have also built in functionality to export data out to CSV files. Our market is a mix of big corporates who want the integration with SAP and never want to see out platform and small guys who run their maintenance from checklists and like the platform.

In regards to customer lock in, the system requires physical tags to be fitted to the zerks. Fitting the tags costs man-hours and they only work with our head unit. We think this protects us in the short term, longer term the capture, hosting and reporting on the data is our lock in.

Our customers are not the types to go out and build their own software - they may copy the head unit though..

Anything unique about the head unit you could patent?

We have patents on the head unit and the whole system

Tremendous. Best wishes and much success.

Have you been asked for on prem yet?

On this note, have you explored integrating your hardware/software into customer systems? I suppose customers may have existing logging applications they feed said paper forms into, and if you could feed that directly it would be useful.

The system has APIs, anticipating integration into maitenance platforms like SAP, Pronto etc. We haven't needed to do it yet, but our customers ask us every time.