These aren’t case studies — we don’t publish results before a client confirms them, and we’re not going to invent partner ones. They’re the three situations we’re set up for.
The introducerA chartered accountant in Pune closes the year for a retailer with two shops.
Stock is in a sheet, sales are in a book, and the two don’t agree until March. The accountant doesn’t sell software and shouldn’t have to. They make one introduction, sit in on the first call if they want to, and hear from us when the work is scoped, when it’s signed and when it goes live. If a referral fee is agreed, it’s paid when the client pays us.
The studioA design studio in Bengaluru wins a brand and a website.
Six months on, the client asks for a customer portal and an app, and the studio has no developers. We build it under the studio’s name or ours — the studio decides — against a written scope the studio has read first. The studio keeps the relationship. We keep the code working, and the support tickets come to us.
The implementerA systems consultant in Hyderabad has four restaurant clients on paper tickets.
They want EzyResto in the kitchens but not the support desk. We supply the product, the training and second-line support with a name and a number. The consultant does the site visits, the menu setup and the first-line calls. What each side earns is on paper before the first install.
Not on this page: platform and technology partnerships — payment gateways, hosting, marketplaces. We don’t run a programme for them. If you think there’s a genuine fit, write anyway; we read everything.