The words we use.
The terms you will meet across Babav, in plain language.
Curator
A named expert who decides what belongs in their knowledge bases and outcomes, and approves what goes in. Curators share in the subscription revenue their knowledge generates, and can offer consulting at a rate they set.
Domain
An area of expertise, such as GTM, FinOps, strategy or legal. Every knowledge base and outcome belongs to one.
Groundedness
How closely an answer is supported by the knowledge it drew on. Babav shows a groundedness score, names its sources, and says “I don’t know” when the knowledge isn’t there.
Knowledge base
The documents and sources behind an answer, curated by an expert or an organization.
Knowledge library
Where curated knowledge lives: the Babav Library, an organization’s own library, or a personal one. Knowledge bases and outcomes are attached from a library to a workspace.
Knowledge value score
How each document is assessed against what a knowledge base already holds, so duplication and dead weight are removed rather than stored.
Outcome
A ready-to-run piece of high-value work, such as an investor diligence report, a cloud cost analysis or a contract review. It is an expert’s method, curated so anyone can apply it: it asks for what it needs, checks with you along the way, and leaves you with a defined result. The word keeps its everyday meaning too: the outcome is where the value of knowledge sits, which is why Babav is built around them.
Pricing stages
How Babav is priced, in four stages. Explore: free, as a guest or with a free account that keeps and exports your work. Create: subscribe for a 30-day free trial to build your own knowledge bases, outcomes and workspaces. Grow: $100 per seat per month for the next three months. Compound: $200 per seat per month from month five. Paid plans are never metered; free use carries a fair daily limit.
Visual answer
A visual alongside the written answer, not instead of it. Relationships you would otherwise hold in your head are drawn out, with the same sources behind every claim.
Workspace
Where a team works in Babav: its conversations, its own knowledge bases and outcomes, and those attached from the libraries.