Onboard OS: durable client-onboarding workflows

Client onboarding moves between intake forms, files, tasks and reminders. When a step fails or a handoff stalls, the team needs to know what happened and what still needs attention.

I designed and built an internal demonstration that keeps a record of each workflow step. Private intake uploads, background workers and timers support the process, while exception handling makes blocked work explicit.

Commands are designed so a retry does not duplicate the intended action. Connections to external tools have explicit states, and actions stay pending until the required connection checks are complete.

The implementation uses Postgres to track state and includes Docker deployment, readiness checks, encrypted backups and controlled recovery.

This is an internal workflow demonstration. It shows how I structure intake, retries, recovery and handoffs so a team can understand the state of the work.

The illustration below shows the intended experience: a client sees the next onboarding step while the team sees what needs attention.