← All blueprints
Client Onboarding Tracker
Client onboarding lives in one person's head, and things fall through the cracks.
Every new client moves through the same stages and checklist, so onboarding no longer depends on one person's memory.
- No.
- 006
- Department
- Ops
- Build time
- 1–2 hrs
- Difficulty
- Intermediate
- Team size
- 2–25 people
- Replaces
- Rocketlane
Parts
- 1
Stages
Kickoff, setup, training and live, or whatever your process actually is.
- 2
Client cards
Each client shows its owner, start date and checklist progress.
- 3
Handoff
When a checklist is done, the client moves on and the next owner is notified.
- 4
Checklist templates
The same steps every time, editable as you learn.
Data model
- Client { name, owner, stage, started_at }
- Stage { name, position, checklist_template[] }
- Task { client_id, stage_id, title, done_at?, done_by? }
Build prompt
Build an internal tool for my team: "Client Onboarding Tracker".
The problem: Client onboarding lives in one person's head, and things fall through the cracks.
Who uses it: a team of 2–25 people.
What it should do:
- Stages: Kickoff, setup, training and live, or whatever your process actually is.
- Client cards: Each client shows its owner, start date and checklist progress.
- Handoff: When a checklist is done, the client moves on and the next owner is notified.
- Checklist templates: The same steps every time, editable as you learn.
Data:
- Client { name, owner, stage, started_at }
- Stage { name, position, checklist_template[] }
- Task { client_id, stage_id, title, done_at?, done_by? }
Constraints:
- Built for one team inside one company. Simple sign-in (or none), no billing, no multi-tenant setup.
- Fast, calm and obvious enough that teammates need zero training.
- Data must persist and be shared across the team.
- Ship the simplest version that works, then tell me what you'd add next.Works with Claude, ChatGPT, Cursor, Lovable, Replit or Type.
Variations
- A read-only progress page for the client
- Flag anyone stuck in a stage for more than a week
- Average time-to-live per stage, to find the bottleneck
A new blueprint every week
Sent on Sundays. One tool per email.
More blueprints
Approval Workflow
Purchase requests get lost in Slack, and nobody knows who approved what.
- No.
- 007
- Dept.
- Ops
- Build
- 1–2 hrs
- Replaces
- Kissflow
Project Status Board
Every Monday I rebuild the same status report from scratch.
- No.
- 008
- Dept.
- Ops
- Build
- 1 hr
- Replaces
- Monday.com
Simple CRM
We pay for a giant CRM and use about ten percent of it.
- No.
- 001
- Dept.
- Sales
- Build
- 2 hrs
- Replaces
- HubSpot