Skip to content
Psi* Psi* psi*

Workflows

Workflows

Section titled “Workflows”

The current public workflow is intentionally simple to explain:

  1. Lead Intake
  2. Campaign Manager
  3. Outbound

That sequence is a packaging choice, but it also reflects real operational boundaries.

Why the workflow is split

Section titled “Why the workflow is split”

psi* treats multi-stage revenue work as a chain of responsibilities instead of one undifferentiated assistant surface. Each module owns a different part of the workflow:

  • Lead Intake improves and routes the starting signal
  • Campaign Manager builds readiness
  • Outbound turns ready work into drafts and sends

Workflow principles

Section titled “Workflow principles”

Handoffs should be explicit

Section titled “Handoffs should be explicit”

psi* favors clear module-to-module transitions so downstream work can trust what upstream work has already established.

Review should remain visible

Section titled “Review should remain visible”

The workflow does not assume that every decision can be hidden behind a single automated chain. Review posture remains part of the operating model.

Runtime and workflow execution should be durable

Section titled “Runtime and workflow execution should be durable”

The platform is designed around real execution surfaces, not only browser-local state.

How to use this page

Section titled “How to use this page”

Use the product pages if you want the commercial story for each module. Use the architecture page if you need the shared vocabulary and technical posture that supports the workflow.