πŸš€ TRS DevOps - Executive Summary

Report Date: May 13, 2026
Prepared For: Andrew (Owner)
Prepared By: Farhad Irani (CTO)
Period Covered: Q2 2026 Planning
Executive Overview We have 8 software projects in various stages across TRS. Some tools already deployed and working (Operator AI, GPS tracking), others in active development. All technical decisions made, priorities locked in, and execution underway.

Current Status: Two critical projects starting this week. Dashcam 90% complete, Employee App starting. Everything on track, no blockers.
8 Active Projects
2 Critical Priority
1 Week to First Release
90% Dashcam Complete

βœ… Tools Already in Production

Operator (AI Employee Agent)

Status: Deployed and operational via Telegram

Current Capabilities:

  • CRM access and queries
  • Email search and drafting
  • Task execution via shell commands
  • File operations and web research

Usage: Available 24/7 via Telegram - ask it questions, give it tasks, get reports back

Maintenance: Ongoing improvements based on usage logs and feedback (continuous refinement)

Planned Enhancement: GPS tracking integration (see backlog projects below) - will enable "Where is truck #5?" type queries

GPS Fleet Tracking (Internal)

Status: Active for TRS fleet and employees

Current Use: Vehicle tracking via Teltonika devices, employee tracking via GPS Wox mobile app

In Progress: Dashcam integration (90% complete) + multi-company capability for commercial sales

πŸ“Š Project Portfolio at a Glance

Project Priority Status Timeline Business Impact
Employee Hours Tracking App πŸ”₯ Critical Ready to Start 1 week to first release Replace GPS Wox app, extremely simple MVP
Dashcam Multi-Company πŸ”₯ High 90% Complete 4-6 weeks Ready to sell to external customers
Estimating Software Medium Planning 6-9 months Replace WinBid, incremental releases
Submittals App Medium Planning 3-5 months Replace current system (TBD requirements)
Operator GPS Integration Medium Backlog 2-3 weeks AI agent can answer "Where is truck #5?"
Asset Tracking Low Planning TBD Equipment/tools tracking (BitTrip style)
Daily Log Low In Progress Ongoing Brayden's training project
GPS Fleet Tracking Medium Active Ongoing Internal use, foundation for commercial product

🎯 What We're Doing Now (Next 2-3 Months)

Priority #1 Employee Hours Tracking App (Mobile)

Problem: Current GPS Wox white label app has poor interface, employees frustrated
Solution: Dead simple mobile app - just clock in/out buttons. Backend already exists.
Impact: Happier employees, better time tracking accuracy, TRS branding
MVP Build: ~1 week (extremely simple)
Tech Stack: React Native
Team: Farhad (via Cursor)
Cost: $0
Full Timeline Breakdown:
  • Week 1: Build MVP (clock in/out interface)
  • Week 2: Internal testing via TestFlight/Play Store beta
  • Week 3-4: App store approval + employee rollout

The actual app is trivial (just buttons talking to existing backend). The 3-4 week total is mostly app store processes and employee onboarding.

Priority #2 Dashcam System Completion (Can run parallel)

Problem: Dashcam system works but only for TRS, can't sell to others yet
Solution: Add multi-company login + polish interface
Impact: Ready to commercialize, new revenue stream
Timeline: 4-6 weeks
Cost: Development time only
Progress: 90% complete

What's Done: βœ… Hardware working, βœ… Video retrieval working, βœ… GPS integration working

What's Left: UI cleanup + multi-company authentication

πŸ“… What's Coming Next (3-6 Months)

Estimating Software (WinBid Replacement)

Current System: WinBid by Plexxis

Approach: Small incremental releases, test with dev team first

Timeline: 6-9 months for full replacement

Next Step: Need to interview estimating department about pain points and must-have features

Status: Planning phase, not blocking anything else

Submittals App Replacement

Current System: [Existing submittals app - details TBD]

Timeline: 3-5 months

Next Step: Need to document current workflow and pain points

Status: Planning phase, requirements gathering needed

⏸️ Projects on Back Burner (Lower Priority)

Operator - GPS Tracking Integration

What: Add GPS tracking queries to Operator (which is already operational - see Tools in Production above)

Why: Ask questions like "Where is truck #5?" via Telegram instead of opening dashboard

Timeline: 2-3 weeks (after Employee Hours App complete)

Note: Operator is live and working now (CRM, email, tasks). This just adds GPS as another capability. We continuously improve Operator based on usage logs.

Asset Tracking (BitTrip-Style)

Equipment and tools tracking across job sites. Can integrate with employee hours app later. Timeline TBD.

Daily Log App (Brayden's Training Project)

Deployed on Fly.io. This is intentionally a learning project for Brayden - not urgent. Farhad mentoring him on proper development workflow.

βœ… Technical Approach (Locked In)

Decision 1: Mobile App Framework

Choice: React Native (cross-platform development)

Why: Industry standard (Meta, Microsoft, Shopify), fastest to market (3-4 weeks), single codebase, native performance, huge ecosystem

Timeline Impact: MVP in 3-4 weeks vs 8-10 weeks with separate native apps

Decision 2: Development Approach

Choice: Farhad handles internally via Cursor (no contractor needed)

Why: App is extremely simple - just clock in/out buttons. Backend already exists.

Budget: $0 (handled internally with existing resources)

Timeline Impact: 1 week to build, 3-4 weeks total with app store approval. Can work on Dashcam in parallel.

🎯 Current Execution Plan

Priority Sequence (Locked In)

  1. Immediate (This Month): Employee Hours App + Dashcam completion (running parallel)
  2. Next (Q3): Estimating Software (WinBid replacement) - incremental releases
  3. Following: Submittals App, Operator GPS, Asset Tracking

Note: This sequence optimizes for employee satisfaction first (immediate pain point), then commercial revenue (dashcam sales), then operational efficiency (estimating). Will adjust if business priorities shift.

Budget Status

βœ… No additional budget required for current priorities

  • Employee Hours App: $0 (handling internally)
  • Dashcam Completion: $0 (internal work)
  • All work within existing resources

If scope changes or timelines need acceleration, we'll flag budget needs in the next update.

⚠️ Risks & Mitigation

Risk Impact Mitigation
Too many projects at once Nothing gets completed βœ… Clear prioritization: Employee App + Dashcam first, others wait
Resource constraints Projects take longer than estimated Consider contract developers for parallel work
Employee App adoption Employees resist new app Beta test with small group first, iterate based on feedback
Dashcam sales No customers buy it Low risk - have TRS as proof of concept, proven ROI

πŸ“ˆ Success Metrics

πŸ“±

Employee Hours App

βœ… App in TestFlight/Play Store
βœ… 80%+ employee adoption in 30 days
βœ… Positive employee feedback

πŸ“Ή

Dashcam System

βœ… Multi-company login working
βœ… 1 external customer in 60 days
βœ… $500-1,000/month from first customer

⚑

Overall DevOps

βœ… 2 major projects per quarter
βœ… Projects within 20% of timeline
βœ… Team satisfaction maintained

πŸ“Œ Bottom Line (TL;DR for Andrew)

  • Status: Everything on track. Tech decisions made, priorities set, execution started. Dashcam 90% complete, Employee App starting this week.
  • Budget: $0 additional spend needed. Handling all current work with existing resources.
  • Timeline: Employee Hours app built in 1 week, both projects done in 4-6 weeks total. Then we move to Estimating Software.
  • What You'll See in 3 Months:
    • Employees using new hours tracking app (better experience, less complaints)
    • Dashcam system ready to sell (first revenue-generating customer)
    • Operator answering "Where are our trucks?" via Telegram
    • Estimating software Phase 1 launched (replacing WinBid incrementally)
  • FYI: If business priorities shift (e.g., need Estimating faster, new urgent project), just let Farhad know and we'll adjust the plan and show you the tradeoffs.