SiteFlow

Overview

SiteFlow is a multi-tenant construction operations platform built to connect what happens on the construction site with what happens in the office. The product is designed across three connected experiences: a central admin portal for platform and organization management, a tenant dashboard where construction companies manage their projects and operations, and a mobile application for field workers and supervisors. Awwam is designing and building the product end to end, from product definition and UX/UI through web, mobile, backend architecture, and infrastructure.

The Challenge

Construction operations are spread across the office, project sites, supervisors, workers, equipment, and multiple disconnected tools. Attendance may be recorded separately from project activity, equipment information can live in spreadsheets, and field teams often rely on messages and manual reporting. SiteFlow was designed to create one connected operating system where construction companies can manage their business centrally while field teams can capture real activity directly from the site.

What We Built

• Platform administration

  A central admin portal for managing organizations, platform users, projects, configuration, and the overall SiteFlow environment.

• Tenant management

  Give each construction company its own operational environment with isolated projects, teams, workers, equipment, materials, and business data.

• Project operations

  Manage construction projects, sites, teams, budgets, locations, and day-to-day operational activity from one tenant dashboard.

  

• Workforce and attendance

  Manage workers and teams while capturing attendance and working activity through field-ready workflows using location and other supported verification methods.

  

• Field mobile application

  A mobile experience for workers and site teams to interact with SiteFlow directly from the construction site instead of relying on office-based systems.

• Equipment management

  Track construction equipment, assignments, readings, daily activity, maintenance, locations, and operational alerts.

• Materials and resources

  Organize materials and project resources so construction teams can maintain a clearer picture of what is being used across their projects.

• Operational reporting

  Turn field activity and operational records into information project managers and company teams can use to understand what is happening across their sites.

  

• Roles and permissions

  Control access across platform administrators, tenant teams, project members, supervisors, and field workers based on their responsibilities.

• Location-aware operations

  Use project locations and geofenced areas to support field workflows that depend on where workers and operational activity take place.

Product Screens

Our Role

• Product definition
• UX/UI
• Web application
• Mobile application
• Backend
• Architecture
• Infrastructure

Technology

• Next.js
• React Native
• Expo
• TypeScript
• Fastify
• PostgreSQL
• Prisma
• Redis

Outcome

SiteFlow is being built as a connected operating layer for construction companies, bringing platform administration, tenant operations, and field activity into one system. Instead of separating office management from what happens on site, the platform gives each side the tools they need while keeping the underlying operational data connected.

Engineering decisions

• Why three connected product experiences?

  SiteFlow serves different users with fundamentally different responsibilities. Platform administrators need centralized control, construction companies need a complete operational dashboard, and field workers need a simple mobile experience designed for the construction site. Separating these experiences keeps each workflow focused while allowing them to operate on the same platform.

• Why multi-tenant architecture?

  SiteFlow is designed as a platform for multiple construction companies. Each tenant needs its own projects, people, equipment, materials, and operational data while the platform maintains centralized administration and shared infrastructure.

• Why React Native and Expo?

  Field workers and supervisors need to interact with SiteFlow away from a desk. React Native and Expo provide a dedicated mobile experience while allowing the product to share TypeScript-based patterns and backend contracts with the web applications.

• Why PostgreSQL?

  Construction operations involve interconnected entities such as projects, workers, attendance, equipment, assignments, maintenance, materials, and financial or operational records. A relational database provides the consistency and relationships required for this type of business system.

• Why location-aware workflows?

  Some construction workflows depend on physical presence at a project site. SiteFlow uses project locations and geofencing as part of its field operations so that location can become a reliable input to supported workflows rather than relying entirely on manual reporting.