Fidloy
Relationship infrastructure for customer-facing businesses.
The system remembered every transaction.
But we still forgot the customer.
Someone could visit KBL Bites or KBL Coffee 10 times and still walk in as a stranger.
That question became Fidloy.
What if the business could remember who just walked in — their visits, spending, loyalty, preferences, and relationship with the business — and give staff that context when it actually matters?
We're now building Fidloy as relationship infrastructure for customer-facing businesses.
Sign-up is finally open, and I'm looking for people willing to try it — especially restaurant, café, and retail owners.
I don't need compliments. I want to know where you get confused, what feels unnecessary, and whether you'd actually use it.
7 Comments
The shift from a transaction system to remembering the customer is the interesting part. The real test will be whether that context actually changes how staff serve returning customers enough to become part of the daily workflow.
Exactly. We’ve seen that customer recognition adds another layer to service. Fidloy supports Wallet passes, NFC, QR, phone lookup and even caller recognition. In your view, which approach would feel most natural for staff during a busy shift?
In our case, phone lookup works well, but during busy shifts staff may not always use it. Website orders already identify returning customers automatically. We’re now integrating our calling system with the POS identification module, so when a customer calls, their existing profile can be recognized automatically before the order is created. The goal is simple: recognition should happen naturally, without adding another task for staff.
Thank you Aryan for the contribution 🙏 reach us on : myfidloy@ gmail