Index / Work / TaskFlow — Internal Operations Platform
TaskFlow — Internal Operations Platform
Sole architect and developer
One platform covering the operational work a small company actually runs on — Kanban projects, attendance with face verification, leave, petty cash, purchases and invoices, plus a separate portal for clients.
- Client
- Internal
- Industry
- Enterprise Operations
- Role
- Sole architect and developer
- Platform
- Web
- Stack
- Flask · Firestore · APScheduler · Python · Vercel
- Dated
- 2026-03-15
- Kanban projects with tasks, labels, comments and activity history
- Attendance with face-verified check-in
- Leave management with monthly balances and carry-forward
- Petty cash, company purchases and invoice tracking
- Client portal on a separate identity path — no internal data visibility
- Composable custom roles built from per-feature permissions
- Scheduled overnight auto-checkout
- Holiday calendar excluded from working-day calculations
① Challenge
These functions are normally four or five separate subscriptions that do not talk to each other, and none of them fit how the company actually worked. Attendance in particular needed to be verifiable without a hardware terminal, and clients needed visibility into their own projects with no view of internal HR or finance data.
② Solution
A blueprint-per-feature layout so each area stays independently maintainable, over a hand-written data-access layer rather than an ORM. Permissions are granular per-feature booleans instead of fixed job titles, so custom roles can be composed without code changes. Clients authenticate through an entirely separate identity path, which makes cross-visibility into internal data structurally impossible rather than a matter of careful filtering. A scheduled job closes out forgotten check-outs overnight.
③ Result
A running internal platform of roughly 9,900 lines across 15 feature modules and 28 collections, replacing several separate subscriptions with one system.