Product-led software company pack

What each client fills in

Business name

How messages sign off.

Owner’s email

Gets the summaries and the cases a person must handle.

Team channel

The Slack channel that hears about it.

AI model

The model the client’s key can use.

Topics

Comma-separated, the team’s own: billing, booking, complaint, technical, sales.

Owner’s mobile

Texted when something needs a person now.

When a person replies

One sentence the customer reads: “We answer within one working day.”

The accounts it needs

Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.

• 

  In the client’s Stripe dashboard: Developers → API keys → Create restricted key. Give it only what the steps need: Customers write, Payment Links write, Prices read, Invoices write, and Webhook Endpoints write for the triggers. Leave “IP access” empty: Thrum has no fixed addresses, so a key locked to IPs fails every call.

• 

• 

• 

  In the client’s HubSpot: Settings → Integrations → Private Apps (Legacy apps) → Create → scopes crm.objects.contacts.write, and for the triggers crm.objects.contacts.read, crm.objects.deals.read and tickets → copy the access token. A private app needs no HubSpot review.

• 

  In the client’s Slack: api.slack.com/apps → Create New App → OAuth & Permissions → add the chat:write scope (and channels:history, plus groups:history for a private channel, for the message trigger) → Install to Workspace → copy the Bot User OAuth Token. Invite the app to the channel.

• 

  In the client’s Intercom: Settings → Integrations → Developer Hub → New app (for their own workspace, no review) → Authentication → copy the access token. The conversation trigger needs the app to be allowed to read conversations.

• 

  platform.claude.com → Settings → API keys → Create key, in the workspace that bills this client.

• 

  In the client’s Zendesk: Admin Center → Apps and integrations → APIs → Zendesk API → enable Token access → Add API token. The triggers make webhooks, which needs an admin’s email and token.

After you install it

It lands switched off. The client’s checklist holds exactly this:

1. Connect the client’s Stripe, for “A payment fails”
2. Connect the client’s Resend (email), for “Tell the customer, kindly” and “Tell the owner”
3. Connect the client’s Twilio (SMS), for “And by text”
4. Fill in Business name (How messages sign off)
5. Fill in Owner’s email (Gets the summaries and the cases a person must handle)
6. Connect the client’s Stripe, for “An invoice is paid”
7. Connect the client’s Resend (email), for “Thank the customer”
8. Connect the client’s HubSpot (optional: the step can be turned off instead), for “Mark them a paying customer”
9. Connect the client’s Slack, for “Tell the team”
10. Fill in Team channel (The Slack channel that hears about it)
11. Connect the client’s Intercom, for “A new conversation comes in”
12. Connect the client’s Anthropic, for “Sort the message”
13. Connect the client’s Twilio (SMS), for “Text whoever is on call”
14. Connect the client’s Slack, for “Post to the team”
15. Fill in AI model (The model the client’s key can use)
16. Fill in Topics (Comma-separated, the team’s own: billing, booking, complaint, technical, sales)
17. Fill in Owner’s mobile (Texted when something needs a person now)
18. Connect the client’s Zendesk, for “A ticket is opened” and “Acknowledge it”
19. Connect the client’s Anthropic, for “Sort the ticket”
20. Fill in Topics (Comma-separated: billing, bug, how-to, account)
21. Fill in When a person replies (One sentence the customer reads: “We answer within one working day.”)