CRM and revenue records
Leads, contacts, companies, deal stages, deals, notes, invoices, payments, accounting accounts, and journal entries for lead-to-cash workflows.
Request access to Slab5Operating platform
Slab5 is a workspace-based business operating platform for builders, developers, agencies, and enterprise teams. It combines headless business tools, REST APIs, MCP access where enabled, AgentGrid workflows, Data & Insights, approvals, audit logs, usage metering, and billing controls.
Modules
Leads, contacts, companies, deal stages, deals, notes, invoices, payments, accounting accounts, and journal entries for lead-to-cash workflows.
Queues, tickets, ticket messages, internal comments, SLA-related fields, status, priority, ownership, and customer handoff context.
Sites, collections, structured entries, draft/review/published states, campaigns, marketing posts, and approval-ready content workflows.
Tasks, ownership, due dates, activity records, notes, calls, emails, meetings, agent actions, and links to related resources.
Projects, boards, board columns, project task links, products, roadmap items, releases, calendars, and event timing context.
Asset registration, signed upload/download flows, archive semantics, related-resource links, storage usage, and egress metering.
Capabilities
Define reusable workflows and agents, run them manually or on a schedule, pause for approval, retry failures, and inspect run history.
Use Slab5 as an operational backend for apps, internal tools, vertical assistants, agency workflows, and enterprise pilots.
Turn workspace activity into governed datasets, BI views, metrics, queries, exports, execution jobs, recommendations, and knowledge artifacts.
Use workspace scopes, module enablement, request IDs, audit logs, notifications, usage metering, and billing controls to keep operations inspectable.
Product areas
The workflow control plane inside Slab5 for governed AI and automation.
Workspace-scoped systems of record usable from the console, APIs, and where enabled through MCP or AgentGrid tool access.
Analytics, BI, governance, data agents, and operational reporting over workspace activity.
The governance layer for workspace modules, members, settings, audit logs, usage, notifications, and billing controls.
REST / MCP Architecture
Slab5 gives every workspace a governed business tool plane: REST APIs for apps and integrations, MCP access for agents where enabled, and AgentGrid workflows for repeatable human-in-the-loop automation.
Access and integrations
Test REST endpoints from the console across CRM, CMS, support, tasks, activity, assets, projects, products, calendar, BI, AgentGrid, data agents, notifications, and integrations.
Create, scope, store, rotate, and revoke workspace API keys with secrets shown once and audit events around credential changes.
Configure workspace-scoped MCP access through static tokens or OAuth grants, with revocation paths and client setup docs.
Discover event types, register custom event types, create signed webhook endpoints, send test deliveries, and inspect retry state.
Security and governance
Records are scoped by tenant and workspace, with module gates, role/scope checks, and controlled workspace settings.
AgentGrid workflows can pause for human review before customer-facing, billing, publishing, or executive actions.
Request IDs, audit logs, activity records, run logs, usage events, and notifications make changes easier to investigate.
Usage dimensions cover REST, MCP, webhooks, assets, storage, egress, assistants, Data Agents, AgentGrid, and scheduled work.
Who it supports
Add CRM, tasks, support, CMS, assets, analytics, approvals, audit logs, and usage controls without building every backend primitive from scratch.
Use Slab5 as the governed tool plane behind vertical assistants, with durable business state instead of ephemeral chat state.
Run one workspace per client, reuse campaign and workflow templates, isolate records, and use approval gates for client review.
Govern AI workflows with workspace boundaries, scoped credentials, approval queues, audit logs, request IDs, and usage visibility.
Use cases
Draft content, support responses, summaries, or follow-up actions, then pause for human approval before the workflow continues.
Give vertical AI products durable workspace records, scoped tools, approval gates, run logs, and operational reporting.
Coordinate campaigns, CMS drafts, assets, client approvals, CRM context, tasks, and BI reporting inside isolated workspaces.
Use AgentGrid run history, audit logs, request IDs, credentials, and approvals to inspect what happened and why.
Connect support tickets, CRM context, internal comments, follow-up tasks, SLA risk, and approved response workflows.
Use included app experiences such as FounderOps or MOpsLab to demonstrate vertical tools built on the same workspace foundation.
Implementation
The fastest path is a focused pilot: choose one workflow, map the records and permissions, wire REST, MCP where enabled, AgentGrid approvals, run logs, reporting, and leave the team with a practical rollout plan.
Slab5 beta
Start with one real operating flow: records, REST APIs, MCP access where enabled, AgentGrid approvals, audit logs, and the context business operators need to trust the work.