Technical Audit & Knowledge Transfer Proposal

Tech2Go
Platform Audit
& Knowledge Transfer

A structured technical audit, complete knowledge transfer, and production-readiness uplift for the Tech2Go field service platform — covering all three portals, VMS integration, and infrastructure.

View Audit Scope → See Timeline →
3
Portals Audited
4 wks
Focused Audit
8 wks
Phased Audit
40
Days (Max)
24/7
Support Included
Executive Summary

Understanding the Tech2Go Platform

What we're taking over, why a structured audit matters, and what success looks like.

Tech2Go is a multi-tenant, whitelabeled field service SaaS platform built and operated by the Tech2Go team. It serves enterprise B2B clients in the pantry and refreshment delivery space — each client runs under their own branding (e.g. Glassworks, Adelphi Business Systems, Blue Harbor Technologies). Within each tenant, the platform manages a network of branches, customers, locations, and touchpoints (pantries, stockrooms, vending units), each serviced by a driver on a scheduled route.

The platform comprises three distinct surfaces: an Admin portal for operational management, a Driver mobile app for field execution, and a Customer portal for client-side visibility — all whitelabeled per tenant. The backend runs on Digital Ocean with separate test and production environments.

Global Nodes AI is engaged to conduct a comprehensive technical audit of the platform and a structured knowledge transfer from the Tech2Go team — producing a clear picture of the architecture, integration landscape, and infrastructure health. This produces a documented foundation that enables Global Nodes AI to take ownership of support, new development, and platform evolution with full confidence. This proposal outlines the scope, team, methodology, deliverables, and timeline.

Why a formal Audit & KT matters

  • → A thorough code audit is needed to identify technical gaps, undocumented logic, and areas of risk before ownership transitions
  • → The platform has experienced production outages caused by database query locks — monitoring is currently missing and must be established
  • → VMS (Vending Management System) integrations across multiple enterprise customer sites are partially documented — a full map is needed before support handoff
  • → No single source of truth exists for architecture, workflow logic, or infra configuration — this audit creates it

What success looks like post-KT

  • → Global Nodes AI team can triage, reproduce, and resolve production issues independently — without relying on the current Tech2Go team
  • → Full architecture documentation exists for all three portals, the API, and each VMS integration
  • → Infra monitoring and alerting is in place covering DB health, API uptime, and deployment pipelines
  • → 24/7 production support is operational from Day 1 post-KT

Known risk areas going into audit

  • → Technical gaps and undocumented logic in the codebase need to be surfaced before any safe transition can happen
  • → Database monitoring is missing — past query lock incidents have caused full API outages
  • → VMS integration architecture is partially documented across enterprise customers
  • → Batch creation module and order fulfillment downstream flow are not yet fully understood
Platform Overview

Three Portals. One Ecosystem.

Each surface serves a distinct user persona and must be independently understood, documented, and supported.

Admin Portal
Admin Portal
Driver App
Driver App
Customer Portal
Customer Portal
Admin Portal

Operational Command Centre

  • Multi-branch management — Atlanta, NYC, Philly, DC, etc.
  • Customer → Location → Touchpoint hierarchy
  • Driver assignment and work management
  • Workflow builder (e.g. White Glove Workflow)
  • Schedule config: daily, weekly, custom
  • Per-touchpoint product list & PAR levels
  • Budget management: cycle-based, customer/location/touchpoint drill-down
  • Batch creation module
  • Work management dashboard
Driver Mobile App

Field Execution Surface

  • Daily pending locations shown on map
  • Navigate to each location with contact details
  • Expand location to see pending touchpoints
  • Per-touchpoint task checklist (assigned by workflow)
  • Photo capture on entry and exit
  • Restock products against PAR levels
  • Add/search products across Associated and All Products
  • Delivery date picker for scheduled orders
  • Confirm service and capture signature
Customer Portal

Client Transparency Layer

  • Visit history: photos, task completion per touchpoint
  • Locations view: touchpoint details + visit history
  • Budget vs Spend: cycle-based financial overview
  • Drill-down: customer → location → touchpoint budget
  • Filter by date range and search across visits
  • Read-only portal — no operational permissions

Infrastructure & Backend

The platform runs on Digital Ocean with separate test and production deployments. The backend exposes a shared REST API consumed by all three portals.

Past incidents include database query lock-ups that brought down the full API — indicating the need for DB-level monitoring and query performance baselines as part of the audit.

Digital Ocean GitHub REST API Workflow Engine Schedule Engine

VMS Integration Layer

Multiple enterprise customers rely on Vending Management System (VMS) integrations — used to manage machine inventory, restock scheduling, and real-time stock level tracking at each site. The audit must map all active VMS integrations, the data flow, and per-customer configuration.

Each VMS vendor has different API models and access patterns. Understanding this layer is a Day 1 priority for the audit.

Stock Sync Restock Triggers PAR Levels Multi-vendor Per-tenant Config
Audit Scope

What the Audit Covers

Six structured audit areas — each producing documented output that feeds the KT and ongoing support readiness.

Area 01

Codebase & Architecture Review

  • Pull and review the latest codebase from the shared GitHub repository
  • Map the full repository structure — frontend, backend, mobile app
  • Identify framework versions, dependency health, and deprecated packages
  • Document API design patterns, authentication model, and data flow
  • Review multi-tenancy implementation (branch → customer → location → touchpoint hierarchy)
  • Identify any hardcoded config, secrets, or environment-specific coupling
Area 02

Workflow & Schedule Engine

  • Document how workflows are defined, stored, and assigned to touchpoints
  • Map task types: photo capture, product restocking, checklist items
  • Understand schedule repeat logic: daily, weekly on a specific day, custom
  • Document "next due" calculation and how the driver app consumes the schedule
  • Review batch creation module — how bulk route or work order generation works
  • Map the order creation flow: driver → order → delivery date → fulfillment
Area 03 · Priority

VMS (Vending Management System) Integration Architecture

  • Enumerate all active VMS integrations across the current customer base
  • Document per-integration approach: data sync frequency, API or webhook model
  • Map the stock level, restock trigger, and PAR level sync flow for each integration
  • Identify per-customer VMS configuration stored in the platform
  • Assess whether VMS data feeds real-time PAR-level recommendations to drivers
  • Document failure modes and fallback if VMS sync is unavailable
Area 04 · Priority

Infrastructure & Monitoring Audit

  • Map Digital Ocean topology: droplet/cluster configuration for test and production
  • Audit database setup — managed DB vs. self-hosted, engine version, backup policy
  • Identify any existing monitoring tooling (Datadog, New Relic, DO monitoring, or none)
  • Review DB query performance — identify long-running queries that caused past outages
  • Audit deployment process: is there a CI/CD pipeline or are deploys manual?
  • Assess secrets management, environment config, and SSL/TLS setup
Area 05

Bug Backlog & Issue Tracking Review

  • Obtain and review the existing issue tracker from the current vendor
  • Categorise open bugs: P1 production-critical, P2 functional, P3 cosmetic
  • Identify issues that overlap with infrastructure or VMS integration gaps
  • Validate reproducibility of open bugs in the current production environment
  • Produce a prioritised remediation backlog for the Global Nodes AI team
Area 06

Support Process & Run-Book Definition

  • Define incident severity levels (P1–P4) and response SLAs
  • Create run-books for the most common failure scenarios (DB lock, API down, driver app sync failure)
  • Define escalation paths: India offshore → US nearshore → client stakeholder
  • Establish on-call rotation covering weekends and US public holidays
  • Set up alerting channels and communication protocols with Brian's team
Engagement Team

Two Team Configurations

Available for both the Audit phase and the ongoing Retainer. Both configurations include Eddy as Product Manager and 24/7 support post-audit.

Team dedicated to executing the Audit & KT engagement. Costs based on $20/hr · 8hr/day. Choose based on audit pace and timeline.

⚡ Focused — 4 Weeks

Audit Team A

Faster audit — 20 working days. Two engineers run in parallel, covering codebase and infra simultaneously. Higher weekly spend, shorter calendar time.

E
Eddy — Product Manager
Stakeholder management · delivery oversight
No cost
TL
Technical Lead
Architecture · KT sessions · audit ownership
FS
2× Full-Stack Engineers
Code audit · gap analysis · run-books
DO
DevOps Engineer
Infra audit · CI/CD · monitoring setup
On demand
🗓 Phased — 8 Weeks

Audit Team B

Relaxed pace — 40 working days. One engineer runs sequentially, fitting around the Tech2Go team's schedule. Lower weekly spend, but longer duration means higher total.

E
Eddy — Product Manager
Stakeholder management · delivery oversight
No cost
TL
Technical Lead
Architecture · KT sessions · audit ownership
FS
1× Full-Stack Engineer
Code audit · gap analysis · run-books
DO
DevOps Engineer
Infra audit · CI/CD · monitoring setup
On demand

Required participation from the Tech2Go team

A successful KT requires active participation from key stakeholders on the Tech2Go side. The following roles should be available during the audit period:

Brian (Decision Maker) Ben (Project Owner) Tech2Go Tech Lead Tech2Go Dev Team (2–3 sessions) Infrastructure / DevOps Contact

We will prepare a structured list of technical questions in advance of each KT session to minimise the time burden on the Tech2Go team.

Audit Methodology

A Four-Phase Audit Framework

Structured across 20 working days. Documented deliverables at each stage. Minimal disruption to the Tech2Go operational team.

1
Days 1–5
Access & Alignment
  • Obtain credentials for all three portals
  • Access Digital Ocean and codebase
  • Review existing issue tracker with Ben
  • Schedule all KT sessions with Tech2Go team
  • Confirm VMS integration list
2
Days 6–15
Deep Technical Audit
  • Codebase walkthrough: frontend, backend, mobile app
  • KT session 1: Architecture & API design
  • KT session 2: Workflow engine & schedule logic
  • KT session 3: VMS integrations deep-dive
  • Infrastructure audit: DO topology, DB config, monitoring gaps
3
Days 16–30
Documentation & Monitoring
  • Author Architecture Document for all portals
  • Document VMS integrations with data flow diagrams
  • Set up DB monitoring and API uptime alerting
  • Draft prioritised gap and remediation backlog
  • Author run-books for critical failure scenarios
4
Days 31–40
Review & Handoff
  • Present all deliverables to Ben for review and sign-off
  • Walkthrough with Global Nodes AI support team
  • Confirm support rotation and escalation paths
  • Activate monitoring and alerting in production
  • Final KT session: open Q&A (recorded)
Deliverables

What You Receive

Every deliverable is a working document — not a deck. Designed to live in your team's wiki and be used operationally.

Platform Architecture Document

  • Full system overview: all three portals, data model, and API design
  • Workflow engine and schedule engine internals documented
  • Budget cycle engine and tenant onboarding flow
  • Identified gaps, risks, and recommended improvements

VMS Integration Map

  • All active VMS integrations documented with data flow diagrams
  • Per-integration sync model, config, and failure modes
  • Onboarding steps for new customers with new VMS setups

Infrastructure Audit Report

  • Digital Ocean topology, DB configuration, and backup policy
  • DB performance risks and monitoring setup recommendations
  • CI/CD pipeline assessment and deployment hardening plan

Support Run-Books & KT Recordings

  • Run-books for critical failure scenarios (API down, DB lock, sync failures)
  • Escalation matrix with SLA definitions
  • All KT sessions recorded, timestamped, and shared with Ben's team
Audit & KT Timeline

A Four-Phase Audit

Two pace options — same scope, same deliverables. Choose based on the Tech2Go team's availability.

Week 1
Access & Alignment
  • Credentials & portal access obtained
  • Codebase and DO access granted
  • KT session calendar agreed
  • Existing issue tracker reviewed
Brian · Ben · Product Manager
Week 2
KT Sessions
  • KT 1: Architecture & API
  • KT 2: Workflow & Schedule engine
  • KT 3: VMS integrations
  • Infra topology walkthrough
Tech Lead · Tech2Go Team
Week 3
Deep Audit
  • Full codebase review & gap analysis
  • DB query performance analysis
  • VMS integration code review
  • Infra audit: DO + CI/CD
Tech Lead · DevOps
Week 3–4
Docs & Run-Books
  • Architecture Document authored
  • VMS Integration Map drafted
  • Run-books created
  • Monitoring setup deployed
All team
Week 4
Review & Handoff
  • All deliverables reviewed with Ben
  • Support rotation activated
  • Escalation paths confirmed
  • Global Nodes AI declared primary
Product Manager · Ben
Development Timeline

Estimated Engagement Timeline

Audit runs first. Development work streams begin post-audit and continue as an ongoing engagement.

Audit & KT
Maintenance Setup
Maintenance & Support
New Feature Development
Infrastructure
Integration Stabilization
Month 1
Month 2
Month 3
Month 4
Month 5
Month 6+
Pricing

Audit & Retainer Pricing

Part 1 — Audit (one-time, fixed fee)
⚡ Focused — 4 Weeks
$14,500
Fixed fee · all deliverables included
  • ✓Platform Architecture Document
  • ✓VMS Integration Map
  • ✓Infrastructure Audit Report
  • ✓Support Run-Books
  • ✓KT Session Recordings
🗓 Phased — 8 Weeks
$14,500
Same fixed fee · relaxed pace
  • ✓Platform Architecture Document
  • ✓VMS Integration Map
  • ✓Infrastructure Audit Report
  • ✓Support Run-Books
  • ✓KT Session Recordings
Part 2 — Monthly Retainer (post-audit, ongoing)
⚡ Full Capacity Team
$17,600 / mo
5 members · 22 days/mo
Eddy — Product ManagerNo cost
Technical Lead$3,520 / mo
2× Full-Stack Engineers$7,040 / mo
React Native Engineer$3,520 / mo
QA Engineer$3,520 / mo
DevOps EngineerOn demand
✓ 24/7 production support included
🗓 Lean Team
$14,080 / mo
4 members · 22 days/mo
Eddy — Product ManagerNo cost
Technical Lead$3,520 / mo
1× Full-Stack Engineer$3,520 / mo
React Native Engineer$3,520 / mo
QA Engineer$3,520 / mo
DevOps EngineerOn demand
✓ 24/7 production support included
Next Steps

Ready to Get Started?

Once the audit is complete, Global Nodes AI and the Tech2Go team will align on the transition plan, support model, development priorities, and team configuration — before any ongoing engagement begins.

hello@globalnodes.ai +1 (818) 217 0878