finnKnowledge and AI
Give good answers somewhere to go.
Connect approved knowledge to current business records, useful drafts, and actions your team can review.
“Prepare a quote using our wholesale prices.” To help, AI needs more than a folder of files. It needs the right price list, the right customer, and a clear boundary between preparing a proposal and sending it.
Give each source a job.
An approved policy explains what the business allows. A customer record identifies who you are serving. An order system shows what has already happened. A previous conversation provides context. Treating all four as interchangeable text makes it harder to spot an outdated answer.
In an illustrative wholesale workflow, a sales presentation might contain an old discount example. The current approved pricing policy should control the quote. When two sources conflict, show the conflict to the person who owns the decision instead of silently choosing the more convenient answer.
Make the draft easy to inspect.
A useful quote draft identifies quantities, prices, assumptions, and any exception needing approval. A property report should identify its reporting period and the records behind it. A small calculator should make its inputs visible rather than conceal assumptions in a polished total.
Finn’s Library brings uploaded and agent-created artifacts together. The point is to help a team find the work again, review it, and continue the conversation. Naming a file well and connecting it to the request can matter more than adding another dashboard chart.
Keep access attached to the person.
A shared knowledge base does not mean every employee should see every document. A location manager may need operating procedures without access to another property’s customer records. Test with the roles that will actually use the workflow, including someone who should be denied access.
Keep the same care when selecting AI processing. Finn AI Gateway applies model access, data, and spending rules to requests routed through it. Those controls do not automatically cover unrelated AI tools used elsewhere in the company.
Let the conversation continue.
The first draft is rarely the end. “Use the new quantity.” “Explain the difference.” “Send it after I approve.” Each follow-up should make clear which artifact or proposal is being changed. Before an external action, check the current record and the relevant approval again.
Start by connecting one maintained knowledge source to one useful output. Put an owner in charge of keeping that source current. When the team can find the answer, inspect the draft, and take the next permitted action without reconstructing the request, the knowledge base has become part of everyday work.