Performance Management & OKR Suite

ECOSIRE builds a proper Frappe application — not a bundle of customize-form tweaks — that installs cleanly into your existing bench alongside hrms. It introduces dedicated DocTypes such as Objective, Key Result, KPI Scorecard, Check-in and Review Cycle, each with server-side controllers and hooks.py doc events for validation and rollup. Objectives cascade through a parent/child link so a company-level objective owns department objectives, which own employee objectives; progress rolls up automatically via scheduler events and frappe.enqueue background jobs rather than manual re-entry. KPI scorecards can source their current value from a whitelisted server method that queries live ERPNext data — sales totals, ticket counts, production output — so a metric moves without anyone updating it by hand.

The suite is wired into ERPNext's native appraisal, not bolted beside it. KRA-linked appraisal templates read the employee's approved Key Results and their period progress so the review reflects the OKRs the person actually committed to. Manager and self-review cycles are modeled as their own workflow states with role-based transitions; check-ins are lightweight updates employees log against a key result on a cadence you define. Everything respects Frappe's permission model — we ship role profiles and permission rules so an employee sees their own goals, a manager sees their reports, and HR sees the org. A companion Client Script drives the check-in and cascade UX in the Desk, and every object is reachable through the standard Frappe REST API and our whitelisted methods for dashboards or integrations.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, confirm your cascade depth, KPI data sources, review-cycle stages and role mapping, then build against your Frappe/ERPNext v15 or v16 environment. Typical delivery is 2–4 weeks from confirmed scope. You receive the installable app source, UAT on a staging bench, an agreed go-live window with a rollback plan, and a post-go-live support window — plus the git repository so your team owns the code outright.