Whale turns processes into flows and training. Systematics adds what sits around it: the process map, an owner for each step and the SOP your team follows. The two do different work, so you keep both.
What Whale does and what Systematics adds
Your team draws its diagrams and whiteboards there. You see the whole process around it: each step, who owns it and which tool it runs in.
In Whale
- SOPs and company docs
- MCP connector so Claude reads your docs
- Training flows for onboarding
- Knowledge quizzes
In Systematics
- A map of the whole process, step by step
- An owner on every step
- The SOP your team follows at each step
- Whale named on the steps that use it
Why teams keep Whale
Whale ships training flows and knowledge quizzes for onboarding. Keep Whale for that.
Three steps, and Whale stays put
You change nothing in Whale.
Pick one diagram you keep in Whale
Choose a process your team still opens.
Map it in a guided chat
Each person answers a few questions about their part, and every step gets an owner.
Keep Whale for drawing
Use Whale for whiteboards and diagrams. Use the map for who does what, and the SOP for how.
Before you add the map to Whale
Do Systematics and Whale do the same job?
The Hub (SOPs and docs) plus process maps start at the same jobs. Whale ships training flows and knowledge quizzes for onboarding. You keep Whale for that.
Do I have to stop using Whale?
No. Systematics works alongside Whale, and nothing moves out of it.
Does Systematics connect to Whale?
Systematics connects to other tools through connectors, and we add new ones as we go. Tell us you use Whale and we will say what is possible today.
How do I start with Systematics and Whale?
Map one process in a guided chat, then name Whale on the steps that use it.