Functional platform · Online2026

BaumdienstFlow

Multi-tenant operations platform for field-service companies

Role

Product Architecture · Full-stack · Data Model · UX · DevOps

Visit live project

01

Project overview

BaumdienstFlow is a SaaS platform that connects office administration with teams working on job sites. It replaces fragmented paper, spreadsheet and messaging workflows with one structured operational system.

The administration side manages projects, sites, employees, roles, tasks, equipment, inventory, documents, working time and business calculations. The mobile-first Workzone gives field employees only the information and actions relevant to their role.

The architecture is designed as a reusable RediOnFlow foundation, supporting specialized variants such as BaumdienstFlow, BauFlow and PersonalFlow while keeping every company’s data and workflow isolated.

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.

02

Real project media

Real photographs and screenshots for this project will be added here.

03

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

04

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

05

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.

06

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

07

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

08

What it demonstrates

BaumdienstFlow demonstrates my ability to translate real field operations into a secure, testable and scalable SaaS product spanning administration, mobile workflows, data architecture and production delivery.