Use case · New-client onboarding

We map it once. Then Robal owns the sequence.

Drop Robal into Plan Mode and it goes read-only — asks the questions, proposes the steps, shows you the spec. Nothing fires until you say 'ship it'. Then it commits the process and works it across the week, pausing only at the gates you set.

An example thread — cleaned up, not staged.

#people-opsRobal, Maya

Maya · founder15:20

New client just signed — kick off onboarding?

RobalApp15:20

RobalApp15:21

Done.

✓Sent the branded welcome · scheduled week-1 intros in parallel

✓Waiting on their portal connect — will nudge on day 2

✓Kickoff email drafted — held for your approval

Say the word.

Inside Robal — the process view.

Process · new-client onboardingRobal

1 · Branded welcomesent✓ done

2 · Portal connectwaiting · nudge day 2

3 · Kickoff emailyour approvalawaiting you

Designed in Plan Mode · 1 gate · restart-safe

1 gate

your approval, where it matters

restart-safe

never drops a step

read-only

designed before it runs

Onboarding is the same multi-step dance every time, and it still eats a day. Co-design it once in Plan Mode — Robal proposes the steps, you approve — then it runs the durable process: waits that span days, parallel set-up, retries, and your sign-off at the one gate that matters. It survives restarts and never drops a step.

See it close one of yours.

Bring a real one to the demo and we'll run it live.