Technical answers from your documentation.
With a link to the source.
TechBuddy is an AI assistant for technical support and service. It searches your manuals, resolved tickets and internal procedures and shows which document each answer comes from.
Used by teams at
Manufacturing and service companies
The information exists, but it is split across documents, systems and people.
Manuals sit on a shared drive, fixes for older faults live in service tickets, and some procedures are known only to experienced technicians. Finding the right answer takes a long time, and when an expert leaves, their experience goes with them.
What it usually looks like
of a technician's working time can go on searching manuals and tickets and asking colleagues.
can go into tracking down a single technical answer when there is no shared source.
is typically how long it takes before a junior technician works independently.
What TechBuddy does
- Searches manuals, resolved tickets and recorded experience at the same time.
- Shows the document and page behind every answer.
- Colleagues look up routine answers themselves, so experienced technicians have more time for harder cases.
How deployment works from the first meeting to daily use
For the first version, your public website and the documents you already have are enough. Data does not need to be moved or reworked.
Intro meeting
We show TechBuddy on concrete examples and discuss what you need to solve. The meeting takes 30 minutes and is free.
Handing over material
Manuals, standard operating procedures (SOPs), resolved tickets and your public website. TechBuddy works with documents as they are; you don't need to rewrite them.
Pilot on your data
We usually have a first working version ready within a week. Your team tries it on its own questions and gives us feedback. The pilot does not commit you to continuing.
Rollout
We add the remaining material, open TechBuddy to more teams and connect your systems. Usually within two months of the start of the pilot.
Operation and adjustments
We run the service. Questions your material can't answer show you where the documentation is missing information.
Pilot
We set it up on part of your data. Your team tries it on real questions, and you decide from the results whether to continue.
Full rollout
We connect all sources and open TechBuddy to every team that will use it.
Supported technologies
SQLand moreAnswers you can check against the source, without building or running the system yourself.
Answers with a link to the source
It answers technical questions from your material and shows where each step comes from. When the answer isn't in your material, it says so.
- Built for technical material. Works with tables, schematics and error codes, not just running text.
- Every answer is sourced. You see the manual page or ticket the answer is based on and can open it in one click.
- Several sources at once. Searches manuals, tickets, emails and catalogues in different formats together.
TechBuddyError A14 indicates a sensor connection issue.
- 1. Restart the device and check the power supply [1]
- 2. Inspect connector C_27 for a loose contact [2]
fewer inbound support calls
At heat pump manufacturer ACOND, a customer-facing assistant answers repeated questions that used to end up on the phone. The support team did not have to grow to handle them.
Read the case studyA one-month pilot on your data
The pilot runs for about a month on your documents, for a small fee. At the end you decide whether to continue.
TechBuddy is developed by a team that has delivered data and AI projects since 2016.
Built by DataSentics, a Czech data and AI company, now part of the Bull group.
10
years of data and AI projects
300+
delivered projects
Customer deployments and their results
Technical support for an HPC platform
TechBuddy answers from the extensive product documentation of an HPC platform and helps the support team handle the volume of questions. Story in preparation.
Coming soonAn internal assistant over technical know-how
Czech ventilation and heat-recovery manufacturer ATREA is rolling TechBuddy out over its documentation and technical know-how. Story in the making.
Coming soonAn indicative savings estimate based on your team's numbers
Enter rough numbers for documents, people and questions. The estimate shows the time saved, a suggested plan and its price.
Your situation
PDFs, Excel spreadsheets and a wiki – several formats.
The more sources and formats, the longer searching takes today.
€83,000estimated annual saving
after TechBuddy fees
4,318
hours a year
≈ 2.5
full-time equivalents
7.9×
ratio of savings to TechBuddy cost
With a high volume of questions and information spread across many sources, the time saved tends to be greatest.
Suggested plan
Starter · €1,000/month
What the estimate leaves out
Information in one place
Answers are searched for in one place instead of across drives, tickets and emails.
Fewer interruptions for experts
Experienced technicians don't have to answer colleagues' and customers' repeated questions.
Captured experience
Experience from resolved cases stays searchable when people leave.
An indicative estimate, not a quote. We assume 15–35 minutes saved per answered question and 3–8% of expert-team capacity released (a technical expert in Central Europe costs ~€40,000 a year fully loaded, i.e. ~€22/hour), and we subtract the suggested plan's annual fee. Documentation beyond the plan: one-off credits of €30 per 1,000 pages. We'll prepare the calculation for your operation at the first meeting.
Compared with generic AI tools and in-house development
| Criterion | ChatGPT / Copilot | Build in-house | TechBuddy |
|---|---|---|---|
Your technical data Manuals, tickets, wikis, SOPs | Public web, uploaded files, possibly Microsoft 365 | ~Possible, takes several months of development | Connects existing sources without moving data |
Verifiable citations Every answer points to a source | Source often missing or not linked to a specific page | ~Depends on build quality | Page, ticket, or doc cited every time |
Technical content Tables, schematics, error codes | General-purpose; handles tables and schematics only partly | ~Needs its own processing for tables and schematics | Processing of tables, schematics and error codes is part of the product |
Time to first value From kickoff to working assistant | ~Immediately, but without your technical material | An estimated 12–18 months | First version within a week, full rollout usually within 2 months |
How do I fix error A14 on the Pro model?
Generic chat
Guess without a sourceError A14 can have several causes. Try restarting the device and checking the cabling.
TechBuddy
With sourceError A14 signals a sensor issue. Check connector C_27 and the sensor power supply.
Service manual PMT32 · p. 12
For general questions, all three options work. The differences show on questions where the answer has to come from your documentation and have a traceable source.
Frequently Asked Questions
Answers to the questions we are asked most often.
We support:
- Technical documentation (PDF, Word)
- Resolved tickets (Excel, CSV, JSON, Jira, SAP)Daktela, Helios
- Internal wiki and articles
- Training materials (PPTX, videos)
- Websites (selected domains that we load regularly)
- Schematics and drawings (common image formats)
Have a different type of data? Send us a sample and we'll check whether TechBuddy can process it.
Have more questions? Contact us