.svg)
Where do your processes live?
Usually across Slack, Drive, an old wiki, and two people’s heads. Here they sit next to the projects they describe.
What can you do with knowledge & capture?
SOPs from a recording
Screenshots and steps, drafted for you.
Meeting notes, written
Transcripts and summaries on the account.
Action items to tasks
Linked back to where they came from.
Publish when ready
To a help center or a client portal.
How does team knowledge stay useful?
Processes live next to the work, stay current, and answer questions with citations.
How does the knowledge base stay current?
Writing it is no longer a separate job: re-record a process when it changes.
- Review datesThe system checks them for you.
- Re-record, not rewriteRun the process, get a new draft.
- Requests show the gapsWhat people ask is what is missing.
How do people find answers?
Benny searches your articles, notes, and recordings and cites his source. He only sees what the person asking can see.
Why would the team actually contribute?
Because it is not extra work. Recordings become notes, and notes become tasks.
What happens to a meeting after it ends?
You get a transcript, a summary, and action items you can turn into tasks, filed under the right project.
Who can see what, and what does the AI do with it?
- Benny only sees what you are allowed to see.
- Answers come from your workspace, not the internet.
- Every screen checks permissions, feature settings, and plan.
- Internal, client portal, and public help center are separate choices.
Can we bring what we already wrote?
Yes. Bulk import checks each file, keeps a history, and recovers from a bad run.
Imports from Notion, Confluence, Google Docs, Slack canvases, CSV
Is this an internal knowledge base or a public help center?
Both, from one source. Articles are internal by default, and any of them can publish to a portal or the help center.
Inside knowledge & capture.
Knowledge base
Articles with templates, categories, and review dates.
SOP capture
Record a real run in the browser and get a draft procedure to edit.
Meeting recordings
Transcripts, summaries, and action items, filed on the account or project.
Notes
Rich text, shared or personal, with action items that turn into tasks.
Public knowledge base
The articles you choose to publish, no login needed.
Help center
In-app help for the screen you are on.
Across the workspace
Finished work becomes documentation.
Recordings, captured processes, and notes all keep a link to where they came from. One article then feeds Benny, the client portal, and the help center.
What this removes
Documentation as a separate chore, and an assistant that does not know how you work.
What knowledge & capture connects to.
One workspace, so the records here are the records everything else reads.
Questions people actually ask.
Don't see your question? Contact us
Is this an internal wiki or a customer help center?
Both. Articles are internal by default, and you choose which go to a client portal or the public help center.
How do articles stay current?
Review dates the system checks, re-recording when a process changes, and repeat requests that show what is missing.
Does the AI train on our content?
No. Answers come from your workspace, cite their source, and only use what the person asking can see.
Can we import from Notion or Confluence?
Yes. Bulk import checks each file, keeps a history, and lets you recover from a bad run.
Do I need Capture to use the knowledge base?
No. You can write articles directly. Capture just saves you the writing.
How is this different from Notion or Confluence?
Those tools sit beside your work. Here articles live on the same records, publish to the right client portal, and answer the requests waiting for them.
Ready to crack the chaos?
One workspace for projects, clients, finance, and everything in between. Every plan starts with a 30-day free trial, no credit card needed on core.