Getting scoping help for a Company Brain trial

Who should request scoping help

• Support, customer success, onboarding, implementation, RevOps, or operations owners.
• Teams with repeated issues caused by unclear steps, exceptions, handoffs, or escalation rules.
• Teams willing to provide ordinary confidential operational source material and review the output seriously.

What to include in the scoping request

• Your work email, name, company, and the team corpus you want help scoping.
• Whether source material is available and whether enough relevant artifacts can be assembled.
• Whether a reviewer or process owner is confirmed, identified, or still needs to be found.
• What would make the output useful this week.
• LinkedIn, current tools, and the cost of getting the process wrong are useful but optional for the first request.

Trial limits

Free trials are fair-use limited so the preview stays fast and sustainable. Every extraction checks available Company Brain credits before processing: it starts when the balance covers the estimate; otherwise the product shows the additional shortfall and offers top-up when available, a smaller corpus scope, or Company Brain support. There is no arbitrary one-run limit, so later extractions proceed whenever available credits cover them. If actual usage holds an output pack, the pack is preserved and unlocks after a sufficient settled top-up.

Not a fit yet

• You want a broad company-wide knowledge cleanup.
• You cannot provide source files.
• No one can review the extracted output.
• You need live integrations, SSO, billing, or enterprise controls before testing the core artifact-to-knowledge-pack workflow.