Skip to main content

1. Executive summary

Copied as written from spryple-analysis.md §1. That section contains observations and our assessment: labels [Observed] / [Inferred] / [Proposed] apply. For facts only, see the Product Owner handbook.

Spryple sells an HRMS + field-force CRM suite for Indian SMEs. It has four products: SprypleHR (web + mobile), SprypleLite (face-recognition attendance with simple payroll), SprypleCRM (field force) and SprypleLMS. The Help Center documents 10 functional areas across 6 audiences and 4 mobile apps.

What Spryple does well:

  1. Configuration depth for Indian SME rules. That includes sandwich leave, lates-to-leave deduction, extra-day pay and week-off penalties, EPF/ESI/PT/TDS, VDA, arrears and different payroll and leave windows.
  2. An attendance → leave → payroll chain that turns punches into payable days.
  3. Field-force tracking (GPS, battery, kms, visits) joined to a lightweight demo-centric sales pipeline.
  4. Consistent approval patterns (submitted → approved/rejected, with history).

Where it is structurally weak:

  1. Policies are not effective-dated. Changes to HR policies, leave configuration and pay structure "do not affect existing employees" [Observed] (A: Employee Mgmt, A: Leave Mgmt).
  2. Configuration is duplicated and contradictory. Probation, notice period, late deduction and default-shift rules each exist in two places.
  3. Leave types and CRM pipeline stages are fixed (10 leave types; 5 demo-centric stages).
  4. Security basics are weak. Every user gets the default password "Welcome1!", credentials are created manually after onboarding, and the "Roles & Permissions" documentation is a copy of "Users Login".
  5. The mobile experience is fragmented across four apps, and the claims app is installed as "Spryple CRM".
  6. The employee lifecycle has gaps: no full-and-final settlement, no letters, no performance management, no recruitment, no tax declarations, and no ECR or Form 16 outputs documented.
  7. Leave eligibility depends on gender and marital status, which is legally and ethically risky.

Our recommendation: keep the chain and the configurability, redesign the configuration model (typed, effective-dated, applicability-based policies), merge the mobile apps, close the lifecycle gaps that matter to SMEs (F&F, statutory outputs, letters), and defer the LMS and the bespoke CRM pipeline until the core is proven. The full disposition is in §10.