The questions worth asking before plugging an AI into your documentation.
Straight answers and no marketing speak. Missing yours? Write to contact@willsofts.com. Reply within 24 business hours.
01 · YOUR DATA
Where does my data go?
Into a dedicated instance for your company, hosted in Europe. The server sits in Germany, at Hetzner Online GmbH. So you know the country and the name of the host before you sign anything. The sub-processors of your instance are listed in the data processing agreement. Those of this website are on the Privacy page (FR). Your data is never mixed with another customer's data. The questions put to the assistant and its answers are kept 90 days for measurement, then deleted. The language model is never trained on your content. That is in the contract. A data processing agreement (GDPR article 28) and the list of sub-processors are signed before the first document.
Who has access to what?
The assistant only answers from the corpus it was given. For a public help center, that is your public pages. For an internal assistant, it is an authorised corpus with no individual files or named HR data during the pilot. Rights per person or group can be built on request, with enterprise authentication, after assessing your requirements. On the Willsofts side, I am the only one with access to your instance, apart from the technical sub-processors listed in the contract.
02 · WHEN THINGS GO WRONG
What happens if the answer is wrong?
First, the assistant cites the source page of every answer: the reader can check. Second, outside the documentation it refuses and hands over to your team instead of inventing. Third, a battery of questions tests it every week. An invented link or an out-of-scope answer fails the test, and I fix the corpus or the settings. One thing remains true: an assistant faithful to wrong documentation gives a wrong answer and cites a source for it. That is why the pilot starts on your real documents.
Who is responsible if a customer follows a wrong answer?
You remain responsible for your documentation and for the answers that come out of it. I am bound by a best-efforts obligation. My liability is capped at the amount you have actually paid me. That is written in § 09 of the general terms (FR). Every answer cites the page that backs it. Your reader can check before acting.
What if the documentation changes?
The corpus is updated when your documentation changes, at the frequency written in the quote. It is part of the subscription. The monthly review lists the questions left unanswered: that is your list of pages to write. The assistant keeps the documentation alive. It does not replace it.
What if Logan is away?
The assistant runs without me. If I am unreachable, it keeps answering. For the rest, handover to a third party is written in the contract: standard building blocks, complete documentation, an export of your data and configuration at any time, and a handover file another provider can follow. I work alone and it is written down.
How does leaving work?
One month's notice. You get a full export (corpus, configuration, measurements and the conversations of the last 90 days) and the instance is deleted, with a certificate to prove it. Nothing locks you in: the contract states the licences needed for a takeover.
03 · PRICE AND TIMELINE
How is the price set?
It is on request, and the price does not depend on the number of users. I send you a quote with a fixed price after a 20-minute call, before any commitment, based on the size of your documentation. The 30-day pilot is paid at the start, and its amount is deducted from the project if you order the go-live. Then the monthly subscription covers dedicated hosting in Europe, 2,000 answers per month, corpus updates, the weekly check, the monthly review and the handover file. Beyond 2,000 answers, I warn you before anything changes. For the internal assistant, I am looking for a first company to run a pilot priced on request. The pilot is paid at the start and the balance at go-live.
How long does it take?
A reply within 24 business hours, then a 20-minute call and a demo on your documents. The pilot lasts 30 days from the day I receive your documents and your 50 real questions. Go-live follows within two to three weeks if the criteria are met.
How many fewer tickets do you promise?
No number before the pilot. I do not quote industry figures for ticket reduction, because the result depends on each company's documentation. I write the criteria before the work starts (correct and sourced answers, clean refusals, active users, time to answer before and after). I measure for 30 days. The decision report gives you your number, not mine.