Working MVP / Active Product Development
HoursKZ
A Telegram-first workforce operations platform for small cafés, restaurants, and service businesses in Kazakhstan and the CIS.
Overview
A Telegram-first workforce operations platform for small cafés, restaurants, and service businesses in Kazakhstan and the CIS.
Context
The product is shaped around a low-friction employee experience and a browser dashboard for administrators who need reliable operational oversight.
Problem
Small service businesses manage staffing, hours, approvals, and payroll preparation across fragmented chats and spreadsheets.
My Responsibility
- Product definition and workflow design
- Requirements and prioritization
- Business-to-engineering translation
- Browser-based QA and production troubleshooting
Approach
- Map daily staffing, hour submission, approval, and payroll-preparation flows
- Separate quick operational entry from administrator review
- Design for permanent and temporary employees with role and permission controls
Solution
- Telegram Bot API employee experience and web dashboard
- Employee and administrator registration, authentication, and password recovery
- Daily hours, shift start/end, approvals, work history, checklists, schedules, time-off, and shift coverage
- Weekly and monthly hour limits, planned-versus-actual comparison, notifications, audit history, and Excel exports
Product or Delivery Decisions
- Calendar scheduling starts with the day and daily coverage; exact hours remain secondary
- Table scheduling supports detailed start/end times and rapid editing for payroll review
- Technical context includes Supabase, Prisma, Railway, webhooks, and controlled production deployment
Validation
- Browser-based workflow QA across employee and administrator journeys
- Review of operational edge cases, permissions, and production troubleshooting paths
Outcomes or Intended Outcomes
Validated capability
A product model that joins employee-facing messaging with administrator controls and auditability.
Planned functionality
Roadmap items are evaluated through active product development and are not represented as released functionality.
Expected impact
More timely operational records and clearer preparation for hours review and payroll workflows.
Current Status
Working MVP / Active Product Development. Public descriptions distinguish validated capability, prototypes, expected impact, and planned functionality.
Confidentiality Note
Publicly shown as a product overview only. Operational data, infrastructure identifiers, credentials, internal URLs, and customer information are not published.
Related Capabilities
- AI Product Development
- Operational Automation
- Prototyping, QA and Validation