01
What Caddi is and how the workflow starts
Caddi is an AI workflow-automation platform focused on repetitive back-office work. Instead of beginning with a blank workflow canvas, the operator can demonstrate a process through narrated screenshare, answer follow-up questions about exceptions and let Caddi turn that process into a governed loop.
Caddi's official launch announcement is dated August 24, 2026, with later Product Hunt attention. The useful product distinction is the authoring model: the user teaches the job much like they would teach a new hire, while the system converts that knowledge into repeatable automation.
02
Discover, teach, build and automate
Caddi currently frames the product around discover, teach, build and automate. Discovery surfaces repetitive work; teaching captures the real process and decision logic; building turns it into a loop; and production runs are logged for review.
Caddi says deterministic code handles repeatable execution while AI is used where judgment is required. That matters because the platform is not positioning every production step as an unconstrained model decision. Exceptions still need to be taught and risky actions should be validated on representative cases.
03
Caddi pricing as reverified on August 31, 2026
Caddi's dedicated pricing page now lists the Individual plan at $0 for one user, with 200 credits per month, 10 active loops and 30 days of run history. The page explicitly says there is no trial clock and no Individual overage; users upgrade when they need more credits or loops.
Team is listed at $250 per user per month with 1,000 credits per user and 20 active loops; Business at $6,500 per month with 20,000 credits and 100 active loops; and Enterprise uses a custom annual agreement starting from larger allowances. For the detailed limits and overages, see the Caddi pricing guide.
04
Integrations, permissions and security claims
Caddi's public pages currently disagree on the headline integration count: the homepage advertises 150+ integrations while the technology page says 75+. Treat those numbers as changing marketing snapshots and verify the exact product/action needed. First-party pages show examples across Microsoft 365, Salesforce, DocuSign, NetDocuments, SharePoint, Clio and other operations software.
The technology page says Caddi connects through OAuth and SSO, runs under the connected user's existing credentials and logs actions for audit. It also states SOC 2 Type II and zero-data-retention terms for OpenAI and Anthropic calls. Those are first-party security claims; regulated teams should still review the current Trust Center and contractual scope.
05
Best-fit workflows and important limitations
Document filing, client intake, inbox triage, CRM updates, payment reconciliation and cross-system synchronization are strong documented examples. The common pattern is a stable process with explainable rules and clear escalation points.
Caddi should not be treated as a general-purpose autonomous employee that can safely improvise across any system. A screenshare captures the visible path, but production quality depends on teaching exceptions, scoping permissions and validating run behavior. For a practical rollout sequence, continue with How to Use Caddi.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.