Define the journey
Model the onboarding as data — client, checklist item, document, milestone — with states that reflect your real process.
Client onboarding
Coordinate multi-step onboarding — intake forms, document checklists, internal tasks, status communication — as one tracked application.
For: Agencies, consultancies, and service businesses · Example concept
The problem
Onboarding spans forms, checklists, and follow-ups across tools. Status is assembled manually and every new client restarts the improvisation.
What it produces
- Onboarding status is always one look away
- Clients see consistent communication at every step
- The process becomes an asset you refine and reuse
data: client_onboarding
| client | milestone | owner | state |
|---|---|---|---|
| Northwind | Contract | s.amari | done |
| Helix Co | Intake form | r.dube | waiting |
| Acme Ltd | Kickoff | unassigned | blocked |
- 1 Capture intake
- 2 Assign owner
- 3 Advance milestone
- 4 Send status update
automation · resumable · schedulable
Pipeline board
Client detail
Intake form
screens · connected to data and automations
How it comes together
Screen each side
Internal screens show the pipeline and blockers; intake forms capture client input into the same model.
Automate the follow-through
Automations advance milestones, assign tasks, and send status updates — the follow-through is defined in the automation.
The pieces involved
- Client, milestone, and checklist data
- Pipeline and client-detail screens
- Intake and update forms
- Milestone and reminder automations
Other concepts
Is this your problem?
Waitlist teams will help shape which application concepts we prove first.
Join waitlist