Use cases

The value of GuruSup Brain is not any single source. Slack has the conversation, Notion has the write-up, HubSpot has the deal, and a PDF has what was actually signed. Each tool can answer part of a question. Brain keeps what it learned from all of them in one memory, so your assistant can start from the whole picture.

These examples are illustrations. Each one says what the person asks, what Brain can bring together, and what to set up. Brain returns evidence with references, and your assistant writes the answer from it. What comes back depends on what your sources contain. If the evidence is not there, the assistant is told to say so.

Prepare for a renewal call

The person asks their assistant: "I have a call with Acme tomorrow. What's the current state of their renewal?"

What Brain can bring together

• The deal in HubSpot: its stage, the linked contacts and the recent activity.
• What the team said about Acme in Slack, including an argument about discount that never reached the CRM.
• The account plan in Notion.

What to set up

1. Connect HubSpot and approve access in setup. Your existing deals that are not archived come in, not only new activity.
2. Connect Slack and invite the app to the customer channels. Slack does not bring in earlier history, so invite it early.
3. Connect Notion and share the account plan pages.

Members who should get this answer need access to the categories the material sits in, for example sales and customers. See Roles.

Check what was actually agreed

The person asks: "What discount did we offer Globex, and is it in the signed contract?"

What Brain can bring together

• The deal and its notes in HubSpot.
• The discussion in Slack where the discount was negotiated.
• The signed contract, which lives nowhere but a PDF.

What to set up

1. Connect HubSpot and Slack as above.
2. Upload the signed contracts as files. PDFs, Word files and ZIP archives are accepted. See Content types and limits.
3. Check the usage estimate in the upload dialog before you confirm. Scanned PDFs without a text layer are skipped and shown as Unsupported.

If the contract and the chat disagree, Brain can raise a conflict for an admin. See the fifth example.

Find out whether we have seen this incident before

The person asks: "Checkout is timing out again. Has this happened before, and what fixed it?"

What Brain can bring together

• Alerts or incident events your own tools sent to Brain through a webhook.
• The Slack thread where the team debugged it last time.
• The runbook page in Notion.

What to set up

1. Create a webhook source and point your monitoring or incident tool at its URL. If you set a signing secret, your tool signs each request.
2. Connect Slack and invite the app to the incident channel.
3. Connect Notion and share the runbooks.

Brain reads the webhook data when it arrives. Only what your tool sends is learned, so send the fields a person would need later, such as a title and a description.

Onboard someone new

The new hire asks: "How do we handle expense approvals, and who do I ask if it's over budget?"

What Brain can bring together

• The policy in the Notion handbook.
• The PDF version of the policy that HR keeps.
• A recent Slack answer from finance about an exception.

What to set up

1. Connect Notion and share the handbook.
2. Upload the PDFs that live outside Notion.
3. Connect Slack and invite the app to the finance help channel.
4. Invite the new hire as a member and grant the categories they should see. Members only get answers from the categories an admin has granted them.
5. Optionally, set up the person who owns expenses as a Brain contact. If Brain has nothing, the assistant may offer to ask them, and the new hire follows the request under My requests.

Settle two versions of the same fact

The person asks: "What is our current price for the Pro plan?"

What Brain can bring together

• The pricing page in Notion, updated last quarter.
• A price list PDF you uploaded, dated earlier.
• A Slack message where someone says the price changed.

When one source clearly replaces another, for example with a later date or an explicit correction, Brain treats the newer one as current. When two sources really disagree and Brain cannot tell which is right, it raises a conflict.

What to set up

1. Connect the sources as above.
2. Keep an eye on Conflicts in the sidebar. An admin settles the case: confirm one alternative, say each is true in a different context, write the correct statement, or dismiss it. The admin can also Ask a contact.

See How conflicts work and Resolve conflicts.

Turn a recurring analysis into a skill

The person asks: "Give me the weekly health summary for my accounts, the way we did it last time."

What Brain can bring together

• Deals and activity from HubSpot.
• Product usage figures that your own system sends through a webhook.
• The week's customer conversations in Slack.

What to set up

1. Connect HubSpot and Slack, and create a webhook source for the usage data.
2. Write the steps of the analysis as a skill: a set of instructions the assistant can load when a task matches. A user can ask their assistant to send a skill to Brain, or an admin can import one.
3. A skill sent by an assistant arrives as Pending. An admin reviews it on Skills and approves it. Until then the assistant cannot use it.
4. Write a clear description. The assistant decides whether to load a skill by reading its description.

Choose what to connect first

Start with two or three sources that answer one real question. Add more once you see what comes back. Check Ingest to confirm content was learned, and keep an eye on usage. See Usage and limits.

Related