Founder sales workflow

A founder can use Slab5 by giving an MCP agent scoped credentials across Tasks, Support, CRM, CMS, Files and Media, Activity Log, and Data & Insights.

Use case

The founder is running a small operating workflow. One agent helps triage support, update CRM, prepare content, link assets, create tasks, and inspect analytics objects without receiving control-plane admin rights.

Prompt

In the workspace, summarize today's support tickets, create follow-up tasks for urgent cases, update CRM opportunities tied to those customers, draft a CMS changelog entry for fixed issues, link relevant screenshots or invoice assets, and create a BI query stub for activation.

Flow

1. list_support_tickets for urgent or open cases.
2. add_support_ticket_comment for team-only triage notes.
3. create_task for customer or product follow-up.
4. search_companies, search_contacts, list_leads, or create_deal when a support case has sales impact.
5. create_entry for a changelog or help-center draft.
6. search_assets or create_asset_upload_intent for screenshots, invoices, or launch assets.
7. log_activity for decisions and customer-facing changes.
8. run_bi_query or create_bi_dashboard for activation metrics.

Scoped credential

Enable only the modules the agent should use. For a broad founder workflow, use:

support:read
support:write
crm:read
crm:write
tasks:read
tasks:write
cms:read
cms:write
assets:read
assets:write
activity:read
activity:write
bi:read
bi:write

Keep settings:admin off. The founder can still manage workspaces, modules, API keys, MCP clients, billing usage balance, webhooks, audit, and usage from the control plane.

Verify

• Every write returns a request_id.
• Audit and usage events exist for the MCP tool calls.
• The agent cannot call disabled modules or scopes it was not granted.
• Billing usage balance and cap state are visible from the control plane during workflow testing.