Active development · Online2026

BaumdienstFlow

Multi-tenant field operations platform for tree-service companies

My role

Product concept · Domain modelling · Product architecture · Full-stack development · Data model

UX/workflows · Applied AI · Testing · DevOps

Project overview

Tree-service companies work with tree lists and import files, maps, field crews, equipment, working time, reports, documentation and fleet information. These workflows are often separated.

BaumdienstFlow connects them: from the tree register and work site through GIS-supported field work to working time, reports, documentation and operational visibility.

The product logic is grounded in five years of hands-on tree-care experience, not an abstract SaaS concept, but recurring workflows in real field operations.

Domain experience

5 years of hands-on tree-care experience

I experienced the daily workflows of a tree-care company first-hand—from planning, site preparation and team coordination to equipment, working time, documentation and daily reports. BaumdienstFlow automates those exact processes, so its product decisions are grounded in direct field experience rather than assumptions.

Real product screenshots

Two real views from the platform's day-to-day operation.

BaumdienstFlow operations dashboard with staff, site and fleet overview — The operations dashboard brings staff availability, active sites and fleet status into one view.

BaumdienstFlow Workzone board showing active job sites — The Workzone board gives field teams a focused overview of active sites and operational status.

Main operational workflow

From the tree register to operational visibility.

Tree register

Municipal and company tree data

XLSX / CSV / KML import

Structured import into the company context

Work site

Work area, order and documentation

GIS map

Leaflet · OpenStreetMap · Esri imagery

Tree selection

Select and complete a tree directly on the map

Team + equipment

Workers, inventory and handovers in the field context

Field execution

Mobile, offline-oriented Workzone

Daily report / working time

Start · Pause · Stop · Monthly overview

Dashboard / AI

Operational information and scoped queries

Core capabilities

GIS & tree data

Tree-register and work-site import from XLSX, XLS, CSV and KML
GIS maps with Leaflet, OpenStreetMap and Esri imagery
Tree data in the work-site context

Workforce & time tracking

Worker management and role context
Time tracking with start, pause and stop
Monthly timesheets, daily reports and vacation workflow

Inventory & equipment

Inventory and equipment management
Handover, return, assignment and movement history

Fleet & GPS

Fleet data and views
Optional GPS ingest and map view per company

Reporting & operations overview

Work-site documentation and uploads
Daily reports
Dashboard and statistics layer

Applied AI

Company-scoped, read-only operational assistant
Operational queries across workers, hours, work sites, reports, fleet and company knowledge

Platform architecture

Shared platform

Shared multi-tenant operations core

Users/Workers · Work sites/Workzones · Machines · Inventory · Work sessions · Reporting · GPS · Documents · AI infrastructure

BaumdienstFlow

Most complete runtime mode for tree-service companies

BauFlow

Partially developed construction vertical

PersonalFlow

Reduced, partially developed personnel mode

Three real demo workflows

Municipal tree register → field execution

01Import tree data
02Open the work site
03Select a tree on the GIS map
04Perform or complete the work
05Update the daily report and dashboard

Crew operations

01Start working time
02Pause
03Stop
04Review the monthly timesheet
05Request or approve vacation

Operations AI

01An administrator asks an operational question
02The assistant uses only the company context
03Answers concern current workers, sites, hours, reports, fleet or company knowledge

Technical decisions

Why a shared multi-tenant core?

BaumdienstFlow, BauFlow and PersonalFlow are not three separate applications. Shared domains and infrastructure are implemented once; runtime modes configure the operational focus.

Why tenant-aware access?

Company context, roles and data isolation belong to the product architecture, so every operational view and workflow stays within the correct company.

Why a dedicated mobile Workzone?

Field work needs short, role-specific flows. The Workzone deliberately separates those actions from administrative complexity and is designed for offline-oriented work.

Why is the AI read-only and scoped?

The assistant answers operational questions in the relevant company context without autonomously changing data or workflows.

Technology stack

Application

Next.js
React
TypeScript
Tailwind CSS

Data

Prisma ORM
PostgreSQL
Supabase Storage

Quality

Playwright
E2E tests
Smoke tests
GitHub Actions

Deployment

Vercel
Railway
CI/CD

Project status

IMPLEMENTED

Operational workflow for tree data and work sites, including XLSX/XLS/CSV/KML import
Workforce and time workflows with daily reports, monthly timesheets and vacation
Inventory, equipment movement and work-site documentation
Dashboard, statistics and read-only company assistant
Multi-tenancy, RBAC and mode-driven feature configuration
Mobile, offline-oriented Workzone architecture

PARTIAL / OPTIONAL

Municipal-style imports without live synchronization with municipal APIs, WFS or ArcGIS
Worker documents without a complete certificate-expiry workflow
GPS ingest and fleet views are optional or configured per company
Machine inspection fields without an automatic TÜV/service reminder scheduler
BauFlow and PersonalFlow as partially developed verticals

NOT YET IMPLEMENTED / PLANNED

Email-to-Workzone import
Broader external integrations
Further automation where supported by product documentation

What the project demonstrates

BaumdienstFlow demonstrates that I can model a real operational problem from direct domain experience as a complete product: frontend, backend, data model, workflows, multi-tenant architecture, GIS, assets, fleet, applied AI, testing and deployment of a complex full-stack platform.

Need a similar system?

I can design and build a solution around your workflow, team, and business goals.

Discuss your project ↗

← Previous project

BusinessSite RC

Next project →

Piano Core

System architecture

Office Administration

Projects · People · Assets · Documents

→

Multi-tenant Application Core

Auth · Roles · Workflows · Data isolation

→

Workzone

Time · Tasks · Photos · Daily reports

→

Cloud Services

PostgreSQL · Storage · CI/CD

Project status

Built

Multi-tenant company environments
Role-based authentication and authorization
Project and job-site management
Employee, equipment and inventory modules
Mobile-first field Workzone
Working-time and daily-report workflows
Document and photo storage
Four-language interface
Automated E2E and smoke tests

In active development

Expanded operational calculations
Additional reporting views
Further workflow automation
Production monitoring and performance tuning

Planned

More RediOnFlow industry variants
Commercial subscription management
Advanced analytics
Broader integrations for German field-service businesses

Engineering decisions

Why multi-tenant from the beginning?

The product is intended to serve multiple companies and industry variants, so isolation, tenant-aware data access and configurable workflows are foundational—not later add-ons.

Why a separate Workzone?

Field employees need a fast, focused mobile experience rather than the complexity of an administrative dashboard.

Why role-driven workflows?

Permissions shape both data access and the visible process, reducing mistakes and keeping each user focused on their responsibilities.

Challenges solved

01Keeping tenant data strictly isolated
02Connecting office planning with low-friction field reporting
03Designing workflows for different employee roles
04Managing documents and photos alongside structured operational data
05Supporting four languages without duplicating product logic