Skip to content

Case file 01 · Platform

SEGISPRO

One operational platform connecting HSE talent, clients, planning, documents and service delivery.

  • SvelteKit
  • TypeScript
  • NestJS
  • PostgreSQL
  • Azure Blob
  • WebSockets

The challenge

HSE operations crossed recruiting, professional records, client requirements, work orders, planning and billing. When each step lives in a different document or conversation, the team loses traceability and repeats verification work.

SEGISPRO public product presentation and operational workflow
Public presentation rendered from the local product; it explains the workflow without exposing client data.

The approach

I shaped the product as role-aware workflows backed by a NestJS API and a SvelteKit application. PostgreSQL holds the operational model, object storage protects files, and background jobs, notifications and real-time events move long-running work without blocking the interface.

Key decisions

  1. Separate the SvelteKit client from the NestJS API so each side can evolve around a clear contract.
  2. Keep sensitive documents in object storage and expose them through short-lived signed access.
  3. Automate repetitive synchronization and document workflows without removing human approval points.

Technical architecture

Full-stack architecture designed and built end to end by me.

  1. 01 Product experience SvelteKit · TypeScript

    Role-aware workflows for operations, professionals and clients.

  2. 02 Application API NestJS

    Business rules, permissions and process orchestration.

  3. 03 Operational data PostgreSQL

    Shared model for talent, clients, services and billing.

  4. 04 Files and events Azure Blob · WebSockets

    Protected evidence, notifications and real-time updates.

Modules

What the product is made of, as its own screens divide it.

  • 01 HSE talent

    Professional profiles, documents, availability and payments.

  • 02 Clients & contracts

    Accounts, sites and the contracts that frame each service.

  • 03 Planning & work orders

    Calendar planning turned into orders with evidence attached.

  • 04 Billing

    Service billing and professional payouts from the same records.

  • 05 Reports & statistics

    Activity, dashboards and exports for operations and management.

  • 06 Notifications

    In-app notices and WhatsApp templates for every process step.

  • 07 Backups & manual

    Scheduled backups and the built-in user manual.

Before → after

  • Before

    Professional records scattered across files.

    After

    One traceable professional profile.

  • Before

    Planning disconnected from execution.

    After

    Work orders connected to evidence and follow-up.

  • Before

    Repeated manual document verification.

    After

    Controlled workflows with explicit approvals.

Technologies

  • SvelteKit
  • TypeScript
  • NestJS
  • PostgreSQL
  • Azure Blob
  • WebSockets

The wider toolkit

  • Drizzle ORM
  • BullMQ
  • Passport
  • JSON Web Tokens
  • Swagger
  • Chart.js
  • D3
  • FullCalendar
  • ExcelJS
  • Azure AI
  • Microsoft Graph
  • Google Calendar
  • Vitest
  • Lucide

Brand marks from Simple Icons; concepts without one are drawn in-house.

Project log

Nov 2025 → Oct 2026 · 12 active months

886 commits
2 repositories
12 active months
Nov 2025 Busiest month: May 2026 · 158 commits Oct 2026
  • app app · 669 commits Nov 2025 → Oct 2026
  • api API · 217 commits May 2026 → Oct 2026

In the tree

  • 49 routes
  • 60 API controllers
  • 19 migrations
  • 76 test files
  • 1993 tracked files

Read from the local Git history on Oct 6, 2026. Aggregates only.

The outcome

The resulting platform connects the operating chain in one product: from a professional profile to planning, evidence and follow-up. The local Git snapshot covers 740 commits across two codebases and 44 product routes, reflecting a system grown through sustained operational use.

Private codebase — this file shares the thinking, not the source.