We needed a small internal tool for our ops team. Normally that means asking a developer for a form, a backend and somewhere to host it, and then it sits in the queue for a month. We built it as a data app inside Peliqan instead. It reads live data from our connected sources, shows it in a table the team can filter, and has a few input fields so they can correct a wrong value and have it written back to the source system. They open a link, they see their data, they fix it. No SQL, no exports, no coming to us. We have built two more since for other teams, and each took an afternoon rather than a sprint because the connectors and the warehouse were already sitting there. The second one we mostly copied from the first.

We do data work for several clients and needed a consistent way to give each one an Al agent over their own systems without running a different tool per client. With Peliqan we connect a client's sources, decide what the agent can read and write, and hand them access through whatever Al client they prefer. One client runs on Exact Online, another on Odoo, and the setup process is the same for both. Keeping each client's environment separate while reusing the same approach is what makes it work for us at the scale we operate.

We had a handful of Python scripts running in various places that nobody wanted to maintain. Peliqan lets us write that logic as a data app inside the platform, schedule it, and have it push alerts to Slack when something needs attention. The scripts can read from our connected sources and write back to them, so a job that pulls data, checks it, and updates a record now lives in one place instead of three. It's low-code enough that we didn't need a dedicated engineer to keep it going.