Hebbian

For small teams

The founder stops being the wiki.

Small teams move fast and forget everything. What one person knows sits in their inbox and their head, and the team should not depend on one head.

Works inside the AI tool you already use, such as Claude Desktop, Claude Code or Cursor.

For teams of 10 to 50. Example: the 14-person Support team at Touchgrass Software, a made-up company, in Austin.

Setting up
Ready
  1. Sign up with your personal email
  2. Connect Gmail or Notion, or upload a file
  3. Ask your first question

Support team · Example company

A normal week

A week on the Support team.

The Support team at Touchgrass Software, a made-up company, has 14 people in Austin. This is a normal week with Hebbian.

  1. Monday

    Tyler Brooks, team lead

    Tyler connects Gmail and uploads the escalation path. The notes land in the Support drawer, where someone would look for them.

  2. Tuesday

    Nicole Harris, Support

    A customer reports a double-booked job. Nicole asks in Claude Desktop and gets the steps, with the notes they came from.

  3. Wednesday

    Tyler Brooks, team lead

    Claude Desktop saves Tyler’s new outage reply to his Professional memory, with an undo. He shares it with the team when it is ready.

  4. Thursday

    Nicole Harris, Support

    Nicole asks when the release cutoff is. The answer comes from the Engineering notes her role opens.

  5. Friday

    The whole team

    Tyler is out. A customer escalates, and the team asks who to call. The escalation path answers, not Tyler’s phone.

How you use it

One memory every AI tool reads.

Connect Hebbian to the AI tool you already use, then work there. Your team asks from Claude Desktop, Claude Code or Cursor, or any tool that connects over MCP. The answer comes from the team’s own notes, with the notes it used. The Hebbian app is for setup, admin and reading what is in memory.

Yours and the team’s

Everyone keeps their own memory too.

The team memory belongs to the company. Each person gets a Professional memory next to it, and anyone can add a Private memory. Both belong to that person, even when the company pays. Nothing moves into the team’s memory unless they share it.

Who opens it
The Support team memoryThe whole team
Tyler’s Professional memoryOnly Tyler
Tyler’s Private memoryOnly Tyler
Nicole’s Professional and Private memoryOnly Nicole
Nothing moves into the team’s memory unless they share it

Trust

Where your memory lives.

Hosting

Hosted in the EU, with primary storage in Frankfurt.Hosted in the EU, with primary storage in Frankfurt. Our US region is not open yet and opens on request. Until we move your data there, it is hosted in the EU. Contact us to set a date. Some processing runs outside the EU. The sub-processor list names each provider.

Kept apart

Your company memory is kept apart from every other company, enforced server-side. Access is set per team, down to a single note.

Export

Owners can export the company memory as Markdown at any time, and each person can export their own memories.

Trust center →

Start on your own, today.

Sign up with your personal email, name your company and connect your first tool. No kickoff call needed.

See the small teams track →

Growing past this? See the next step →

Ask Hebbian