The catalogue work looked across local systems, public OSS/self-hostable products, builder and registry sources, and commercial benchmarks. Finance and CRM/RevOps were then read as vertical lanes, with shortlist logic and evidence gaps made explicit.
Source: SaaS catalogue + vertical reports.
Existing systems can provide control references. The client ledger and Actionist evidence layer remain authoritative.
A catalogue entry is useful when it clarifies a data model, UI surface, workflow, or deployment substrate. It becomes risky when it silently becomes a dependency or an authority for money, consent, or client state.
Fit is not approval.
| Candidate / family | Useful surface | Best use in the Actionist model | Boundary / current posture |
|---|---|---|---|
| Chatwoot | Inbox, support, customer/lead communication, SLA surface. | CRM/support operation and approval/read-back patterns. | Candidate reference; license, data, tenancy, and adaptation still need gates. |
| listmonk | Consent-aware email campaigns and engagement. | Messaging authority and campaign state. | Useful subsystem; not a client truth source without reconciliation. |
| AFFiNE / SISO Docs | Knowledge/workspace and document context. | Brief, evidence, and client-facing knowledge surfaces. | Reference/substrate; permissions and tenancy remain important. |
| Teable / Baserow | Database/view/CRUD kernel. | Read-only UI/CRUD first pilot and schema-bound internal tools. | Candidate; provider/data boundaries must be explicit. |
| Postiz | Social publishing and campaign orchestration. | Approval → publish → report atom. | Candidate; external side effects require approval and rollback. |
| Hi.Events / Cal.diy | Events, booking, schedule, attendee/revenue surfaces. | Scheduling and coordination atoms. | Candidate; payment and calendar read-back need direct evidence. |
| Payload / Frappe | Content, CRM/ERP, metadata-driven schema and workflow. | Client-owned data/deployment boundary and scaffolding reference. | Strong references; not automatically Actionist-compatible. |
| Activepieces / Atomic CRM | Workflow/pieces and compact relationship models. | Automation and CRM event crosswalk experiments. | Candidate; connector/action authority must be bounded. |
They received separate 440–540 line research lanes.
The finance lane built a 15-rank candidate matrix, local-first inventory, reusable-block mapping rules, and a non-negotiable control contract around evidence, reconciliation, approval, and the client ledger.
The CRM lane inventoried local SISOCRM/Payload/Chatwoot/listmonk/voice/Postiz/Hi.Events and deep-read Twenty, Frappe, Espo, Suite, ERPNext, Activepieces, Atomic, Cal.diy, Mautic, n8n, Baserow, and pretix.
Payload, Chatwoot, Activepieces, Atomic CRM, Frappe, Cal.diy, Hi.Events, and ERPNext emerged as validation candidates—not build recommendations.
Open full CRM lane ↗Candidate block → vertical atom → evidence gate.
Useful for communication, consent, SLA, and campaign events. The Actionist layer still owns approval, audit, and client-specific policy.
Useful for read models and schema-bound CRUD. Write authority and migrations must be explicitly scoped.
Useful as workflow references. Connector actions and external effects need an Actionist authority contract.
Useful for schedule/attendee loops. Read-back and payment state remain direct-source questions.
Useful data-model references for lead, account, pipeline, and renewal. Avoid inheriting their whole product surface.
Useful approval→publish→report atom. The irreversible action requires explicit review and recovery.
Local report copies live under the pack.
Local estate, public map, priority matrix, reusable-block crosswalk, coverage ledgers, handoff.
Open full catalogue ↗Candidate matrix, control contract, admission/staged adaptation/rejection gates, pilot framework.
Open finance report ↗Local inventory, candidate dossiers, event crosswalk, validation shortlist, moat hypothesis.
Open CRM report ↗Industry/team/use-case/idea catalogue and pilot archetypes from the AM lane.
Open vertical room ↗Choose a source above. The local reader loads the original report.