I’m putting together a complete solution that lets a repair shop follow every job from intake to payment while keeping an eye on stock levels and active service-plan subscriptions. The project covers both a browser-based interface and a dedicated Android app so technicians can stay productive on the floor or on the road. Core workflow • Admins open or import work orders, assign them to technicians, and monitor progress in real time. • Technicians update status, log parts used from inventory, attach photos or notes, and generate customer-ready invoices on the spot. • A subscription module flags customers whose coverage is expiring and automatically applies plan-based pricing during billing. Reporting requirements The system must produce: • Monthly financial reports that roll up revenue, taxes, discounts, and outstanding balances. • Live repair status reports (open, in progress, awaiting parts, completed). • Inventory usage reports that highlight fast-moving items and low-stock alerts. Key functions to include • Role-based access control strictly for Admin and Technician profiles. • Responsive web frontend plus an Android build that works offline and syncs when a connection returns. • Central database for customers, devices, parts, and subscription plans. • PDF and email output for estimates, invoices, and statements. • Dashboard widgets so Admins can track KPIs at a glance. Deliverables 1. Production-ready Web app (source code, deployment guide). 2. Android application (APK + Play Store-ready bundle). 3. Database schema and seed data. 4. Documentation: user guide, API endpoints, and report setup. 5. One round of post-launch fixes based on agreed acceptance criteria. If you’ve built similar SaaS-style repair, POS, or inventory systems—especially with tools like React, Angular, Flutter, Kotlin, Node.js, or Django—let me know what stack you prefer and how long it would take to hit each milestone. I value clean architecture, unit tests where they matter, and clear communication.