SteveGreaseBoss

thanks.

We saw early on that if we were going to add a computer to grease gun, it had to be very simple and never crash or lose connection. Our operators have zero tolerance for complexity.

What are you trying to track?

awesome thanks. we would love their feedback

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..

ha ha, we have had some interesting experiences explaining at pitch events and to investors.

Our customers like the visibility the software brings to their operation. They keep inventing uses for the data we hadn't thought of - we had a customer who owns an intermittantly used shiploader request a report showing the last greasing of each zerk to be outputted 2 hours before the ship arrives in port, this is so they can prevent unforseen breakdowns while the shiploader is in operation and the costs are high

We still have a few iteration cycles on the hardware ahead of us - reducing size and weight and improving form factor.

cheers, its one of those things that you would never imagine is still a problem