They didn't ask for a system. Or a dashboard.

Ballypatrick Stallions in Co. Tipperary stands a roster of show jumping stallions. Orders for stallion services arrive from customers across phone, text, WhatsApp and email, and then have to be coordinated across the yard.

Everything worked, but it worked because people held it. Different staff knew different parts of a given order. Reminders happened when somebody remembered. Payment was chased separately, after the fact.

There was no single place to look at an order and know where it stood. That is fine at low volume and it becomes expensive quickly.

One off and manual orders were the hardest to capture, which is exactly the kind of work that quietly goes unbilled. Reports meant somebody assembling them.

They did not ask us for a system, and they certainly did not ask for a dashboard. We looked at how the operation actually ran and found the real requirement: an order needed to carry itself through the business, and it needed to do that in the channel the customers and staff already lived in.

That channel was WhatsApp. Asking people to log in somewhere new would have failed. So we built around what they already use.

One streamlined view of the operation, where every order can be seen and moved along without ringing around.

Payment taken inside the flow rather than chased afterwards, including the ability to charge manual and one off orders.

WhatsApp integrated across the whole operation, so the right reminder reaches the right staff member and the customer gets their confirmation and updates automatically.

Reporting out of the same data, so the numbers do not need rebuilding by hand.

It is the same method as every project we take on. Understand the operation first. Build second.

The other lesson is about adoption. Software only removes work if people actually use it, which usually means meeting staff and customers where they already are instead of asking them to change habit for your convenience.