LeaflandKerala

Problem

Farm operations spread across spreadsheets, calls, and memory

LeaflandKerala coordinates farms, sales, and field staff across multiple districts, but that coordination lived in spreadsheets, phone calls, and whoever happened to remember what was agreed. There was no shared system of record — no way for staff to log in, see current farm and sales data, and act on it without waiting on someone else to relay information.

Solution

A proper ERP: authenticated, structured, and built for daily use

I built LeaflandKerala as an authenticated ERP application rather than a public marketing site — a real login system, role-based access for employees versus admins, and structured data models for farms, sales, and operations underneath. The interface is deliberately calm and utilitarian, since this is a tool staff open every day, not a page visitors browse once.

Key features

What the platform does

• Secure employee login with role-based access control
• Centralized tracking for farms, products, and sales activity
• District-level reporting across the regions the business covers
• Self-service onboarding for new employee accounts
• Responsive layout so field staff can use it from a phone

Approach

Development approach

I started by mapping how farm and sales data actually flowed through the business day to day, rather than assuming a generic admin-panel structure — an internal tool only earns its keep if it matches how people already work. Authentication and role permissions were designed in from the start rather than bolted on, since this system holds real operational data across many districts and employees.

Result

One system of record instead of scattered spreadsheets and calls

The finished platform gives LeaflandKerala a single, secure system that staff across districts log into daily — replacing scattered spreadsheets and phone calls with data everyone can see and trust.