Connected to your sources
SharePoint, Google Drive, Notion, email, ERP, CRM or databases. It syncs on its own and respects the source permissions.
Internal knowledge
Your whole company, answering in a single conversation
We build assistants that read your organisation's documents, procedures and data and answer your team with the source in front of them: technical sheets, manuals, contracts, price lists, email history. Private, with role-based permissions and connected to the tools you already work in.
It is not another search box. It is the answer arriving with the page it comes from.
Knowledge assistants
Gather.Connect.Ask.Trust.
A company's knowledge lives scattered across folders, emails, the ERP and the heads of three people. Every repeated question costs minutes for whoever asks and whoever answers. A well-built assistant answers in seconds, cites where it got it and knows how to say "I don't know" when it is not in the sources.
From "ask Marta" to ask the assistant
What changes when knowledge stops depending on who is in the office.
Before
- Hours searching folders and emails
- Procedures only the veterans know
- Different answers depending on whom you ask
- Outdated technical sheets and price lists in circulation
- New hires taking months to become autonomous
- Public AI tools used with internal documents
With a basebcn assistant
- An answer in seconds with the source cited
- Tacit knowledge captured and searchable
- One version of the truth, with a date
- Connected sources: when the document changes, the answer changes
- Onboarding with an assistant that answers everything from day one
- Data inside your perimeter, with role-based permissions
What a basebcn assistant includes
Connection to your sources, cited answers, permissions and a place to ask.
Answers with sources
Every answer links to the document and the passage it comes from, to verify and to trust.
Role-based permissions
Sales sees price lists, admin sees contracts, everyone sees procedures. The assistant never shows what the person could not open.
Where you already work
Available on the intranet, in Teams, Slack or WhatsApp, and through an API for other systems.
What you take away
An assistant in production and the method to keep it useful.
Knowledge map
Which sources exist, who maintains them, how good they are and which to connect first.
Deployed assistant
With your sources connected, scheduled sync and a place to ask.
Permissions layer
Roles and access inherited from your systems, with a log of who asks what.
Quality evaluation
A set of real questions with expected answers to measure accuracy before and after every change.
Usage dashboard
Most frequent questions, answers without a source and missing documents: the best diagnosis of your documentation.
Maintenance guide
How to add sources, correct answers and extend the assistant to other teams.
Who it makes sense for
Teams that answer the same questions over and over.
Sales and support teams
Sheets, prices, terms and arguments at hand during the call or the visit.
Operations, quality and industry
Procedures, regulations, machine manuals and historical job sheets available from the shop floor or the phone.
HR and onboarding
Policies, benefits and internal processes answered without opening a ticket, and new hires autonomous sooner.
How we work
A first useful assistant within a few weeks, extended team by team.
01
Map and priority
We identify the questions that repeat most and the sources that answer them. We pick the first team.
02
Build and evaluate
We connect sources, set up permissions and measure accuracy with real questions until it clears the agreed threshold.
03
Roll-out and extension
We open it to the team, review the usage dashboard every month and add sources and teams by priority.
Frequently asked questions
What we get asked before starting.
Are my documents used to train models?
No. The documents are indexed inside your perimeter and consulted at answer time; the model providers we use work under data processing agreements and without training on your content. If nothing may leave your servers, we can deploy it that way too.
What if the assistant gets it wrong?
Every answer carries its source, so an error is spotted and fixed in the original document. We also measure accuracy with a set of real questions before opening it to the team and after every change, and the assistant answers "not in the sources" rather than inventing.
Do I need my documentation tidy first?
No. We start with what exists, and the usage dashboard itself shows you what is missing and what is duplicated. It is the fastest way to tidy documentation: by what people ask.
What does it cost to run?
The recurring cost is the model queries and hosting, which we size with you by number of people, plus a monthly dashboard review. We give you the figure before starting.
Works with
Custom agents act on what the assistant knows; Sales Hub brings the commercial data into the answers.
Which question does your team repeat every week?
Tell us where your knowledge lives today and who looks for it. We will propose the first assistant and the sources to start with.