Case study 01 of 09

AttendEase

College management and attendance platform

A college management and attendance platform I helped build as a Flutter developer and went on to own as Product Manager.

• Role: Flutter developer → Product Manager
• Organisation: Pexus Tech
• Period: 2022 – Now
• Domain: EdTech · attendance and college operations
• Scope of involvement: Product ownership (owned the product across its lifecycle)

In numbers

• 500+: staff and teachers use AttendEase
• 8,000+: students on the student portal
• 5+: educational institutions
• 35%: better responsiveness and data sync (as developer)

Overview

AttendEase is a college management and attendance platform at Pexus Tech. Staff and teachers use it for biometric attendance tracking and reporting, and students use its student portal.

It is also the clearest record of my path into product: I first worked on it as a Flutter mobile developer, then owned it as Product Manager.

Product challenge

Institutions rely on attendance and college records every day, and each one brings its own requests. The product has to keep absorbing those requests while scope, quality and launch readiness stay under control.

My role

Product ownership across the lifecycle. Engineering, QA and the security team built, tested and assessed the product; I owned definition, scope decisions, delivery coordination and launch timing.

• As a Flutter developer: built and deployed AttendEase to Google Play and the App Store, integrating Spring Boot backends.
• As Product Manager: owned the lifecycle across requirements, feature development, delivery and quality.
• Led client requirement elicitation and authored the SRS and PRDs for the student portal and AttendEase feature requests.
• Defined acceptance criteria for each requirement, giving engineering and QA a clear basis for sign-off.
• Ran change control in ClickUp, recording in-scope and out-of-scope decisions in sprint and PI plans.
• Coordinated security risk analysis (VAPT) and set launch timelines from the findings; planned data migrations during server and database moves.

Key features

• Student portal: built from scratch, now serving 8,000+ students across 5+ educational institutions.
• Biometric attendance tracking and reporting for staff and teachers.
• Cross-platform mobile apps on Google Play and the App Store.
• Feature requests specified through SRS and PRDs, covering functional and non-functional needs.

Product thinking

Having built the mobile app, I bring implementation context into product decisions: what a requirement means for the backend and the app, how to write acceptance criteria engineering can build against, and how to sequence releases around security findings and data migrations.

• Requirements captured as functional and non-functional needs, each with acceptance criteria.
• Change requests weighed in sprint and PI planning rather than absorbed silently.
• Launch readiness tied to VAPT findings and migration windows.

Outcome

AttendEase is used by 500+ staff and teachers, and its student portal serves 8,000+ students across 5+ educational institutions. Earlier, as the developer, I integrated Spring Boot backends for a 35% improvement in responsiveness and data sync.

Skills demonstrated

Product lifecycle ownership · Requirements elicitation · SRS & PRD authoring · Acceptance criteria · Change control · Release readiness (VAPT) · Data migration planning · Technical fluency (Flutter, Spring Boot)