Trakia
System Architect / Lead Engineer
An internal operations platform built to run an agency's day-to-day: QR-plus-GPS-verified staff attendance, live location tracking for field team members, per-client content/marketing delivery tracking against subscribed service packages, and a full back office for invoicing, expenses, payroll, and double-entry accounting.
- Client
- A service agency. An internal tool, not public.
- Problem
- Staff attendance, client work and the accounts lived in separate apps and spreadsheets.
- What I built
- One internal system: attendance checked by QR code and GPS, live location for field staff, tracking of each client's monthly deliverables, and invoicing, payroll and accounting.
- My role
- System Architect / Lead Engineer
- Timeline
- January to June 2026. In daily use.
- Stack
- Node.js, Express, MongoDB, React, Vite, Tailwind, Socket.IO, Leaflet, AWS S3
Problem
Running a service agency day-to-day means juggling problems that don't share one tool: are field staff actually where they say they are, is a client's monthly content package on track, and do the books balance at the end of the month. Trakia answers all three from one internal system instead of a spreadsheet, a separate attendance app, and an accountant's own ledger kept apart from everything else.
Approach
A Node/Express/MongoDB API backs a single React admin app used internally by the team: attendance and live GPS tracking for field staff, rendered on a clustered Leaflet map with full location-history playback per person; a per-customer marketing tracker generated directly from what that customer's subscribed service package actually includes, so "this month's deliverables" is derived from the package rather than a manually maintained checklist; and a full back office (invoicing, expenses, payroll runs, and a double-entry accounting ledger), so the operational and financial pictures live in the same system instead of two.
A hard problem I solved
The concrete problem was making staff attendance trustworthy without any hardware: no fingerprint scanner, no badge reader, just a phone. Check-in requires two independent proofs at once: scanning a static QR code tied to the office, and a GPS reading within a configurable radius of the office's coordinates, computed with the Haversine great-circle formula rather than a naive flat-plane distance. Both checks run server-side, not trusted from the client, so knowing the QR code alone doesn't let someone check in remotely, and being physically near the office alone doesn't work without the code either. The system also enforces exactly one check-in per person per day.
Status
Internal tool, not publicly released. Built between January and June 2026 across both the API and admin app, and currently used to run day-to-day agency operations.
Technology
- Node.js
- Express
- MongoDB
- React
- Vite
- Tailwind
- Socket.IO
- Leaflet
- AWS S3
Private/internal project, no public link.
Hiring a developer? Get the checklist first
20 checks founders can run before they sign: questions to ask on the first call, who should own the code and accounts, and what senior remote developers cost in 2026. A free two-page PDF, plus three short emails from real builds. Unsubscribe any time.
Need something similar built?
I build and run products like this for founders and businesses worldwide, from architecture to deployment.
Or tell me about your project →Related: MVP Development for Startups