Answers spread across files
Staff search several folders or ask a colleague because the approved answer is hard to locate.
SPECIALIST SERVICE
RAG Implementation for Internal Knowledge and Document Q&A
Useful answers should point back to approved knowledge.
Build a bounded internal question-and-answer route around the documents your team approves. We define the source set, test supported and unsupported questions, and agree who checks the result before handover.
THE KNOWLEDGE PROBLEM
Find the approved answer without losing its source.
A document assistant is useful when the team knows which material it may use and can inspect what supports an answer.
Outdated versions in use
An old document can look authoritative unless the source set and update responsibility are clear.
Questions without a source
A fluent answer is difficult to check when it does not point back to the material that supports it.
HOW THE ANSWER IS BUILT
Retrieve evidence, then answer within its limits.
RAG connects retrieval from an approved source set to answer generation. The source, access and review rules matter as much as the model.
Approved source set
Choose readable, authorized documents and define which versions belong in the knowledge base. Scans and regulated material need separate review.
Indexing and retrieval
Prepare the agreed text for search, then retrieve relevant passages when someone asks a question. Retrieval quality is checked against sample questions.
Source-grounded answers
Use retrieved passages to draft an answer with a route back to its approved source, so a person can inspect the context.
Unsupported-question fallback
When the material does not support an answer, show a clear no-answer or human handoff instead of presenting a guess as fact.
Document refresh
The Updating Knowledge Base package adds a defined refresh for additions, changes and removals from one agreed folder. It is separate from the Pilot.
One approved action
The highest package adds one named, authenticated tool action under agreed approval rules. Document Q&A alone does not grant write access.
Compare the existing Internal Knowledge solution for the three package baselines. Refresh and approved actions are distinct capabilities with their own scope.
DISCOVERY TO HANDOVER
Test the knowledge route before staff rely on it.
Authorized access, usable documents and a named reviewer are needed before planning. The written scope sets the acceptance and review points.
- 01
Discover
Identify the questions staff ask, document owners, approved sources, access route and a named reviewer.
- 02
Scope
Confirm readable pages, permissions, refresh needs, acceptance questions, exclusions and fees in a written Order Summary.
- 03
Build
Prepare and index the agreed documents, connect the chosen internal route and configure source-grounded answers with a no-answer path.
- 04
Evaluate
Test retrieval, answer support and fallback against 25 agreed questions, including cases the documents cannot answer.
- 05
Handover
Review results with the named owner and document source updates, human review and the agreed operating responsibilities.
APPROVED PACKAGES
Choose the document capability you need.
These are the current one-time Internal Knowledge starting packages. The written Order Summary confirms the final scope, delivery estimate and fees.
Document Q&A Pilot
$1,90012–20 business days
Grounded answers from approved clean-text documents through one internal access route. Document refresh is a separate scope.
Limit: Up to 20 clean-text documents / 100 pages; 25 questions including no-answer cases
Outside baseline: Automatic document refresh, scans, row-level permissions or regulated data.
Updating Knowledge Base
$3,25018–25 business days
Document Q&A Pilot, plus refresh from one agreed folder and one Slack or Telegram access route.
Limit: Same 20-document/100-page/25-question baseline
Outside baseline: Multiple folders, unrestricted permissions or write actions.
Knowledge + One Approved Action
$4,50020–25 business days
Updating Knowledge Base, plus one defined, authenticated action with human approval where needed.
Limit: Same Q&A baseline; exact approved action is named in scope
Outside baseline: Unlimited actions/tools, SSO or regulated-data handling.
Across these packages: up to 20 approved documents and 100 readable pages total, tested with 25 agreed questions including no-answer cases. Scans, row-level permissions, multilingual content and regulated data need separate scope. See all approved package pricing.
Before you choose a package: Fees are one-time USD starting prices for the specified baseline, not automatic combined quotes. Agreed tests, one in-scope revision, handover and 30 days of correction for confirmed implementation defects are included. Hosting, model/API usage, third-party subscriptions, messaging and applicable taxes are separate unless agreed in writing. Payment: projects below $1,500 use 50% at kickoff and 50% at acceptance; projects of $1,500 or more use 40% at kickoff, 40% at a defined demonstrated test milestone and 20% at accepted handover. Final scope, supplier identity, delivery estimate, milestones and fees are agreed in a written Order Summary. Read full working terms.
COMMON QUESTIONS
Know what the documents can support.
The starting scope is deliberately bounded so sources, fallbacks and human review can be checked together.
- What is RAG, and does it train a model on our files?
- Retrieval-augmented generation (RAG) finds relevant passages in an approved document set and supplies them as context for an answer. The scoped build uses those sources at answer time; model training is not part of these packages.
- Which documents fit the starting packages?
- The shared baseline is up to 20 approved, readable clean-text documents and 100 pages total. Scans, multilingual content, row-level permissions and regulated data require separate scope.
- Will answers always be correct?
- No. We test 25 agreed questions, including no-answer cases, and provide a fallback when the approved material does not support a response. People still review important decisions and source accuracy.
- What happens when a document changes?
- The Document Q&A Pilot does not include automatic refresh. Updating Knowledge Base adds a defined add, change and remove refresh from one agreed folder and one named Slack or Telegram team route.
- Can the assistant update a business system?
- Only the Knowledge + One Approved Action package adds one specifically named, authenticated action, with human approval where required. Unrestricted tools, multiple actions and SSO are outside its baseline.
- Who controls access and reviews sensitive answers?
- Your team supplies authorized access and a named reviewer. The chosen internal route, permitted sources, approval points and handover responsibilities are agreed in writing. Row-level permissions and regulated-data handling need separate assessment.
START WITH ONE PROCESS
Start with the knowledge your team already approves.
We will first confirm the process, tools, sample inputs, volume and feasibility—then recommend the smallest useful build.