Test Analect against your own documents and questions.
Agree a representative document set and the questions that matter to your team. The pilot compares answer quality, token use and storage requirements, then gives you the evidence to decide whether to proceed. We apply the same measurement approach to your material; we do not promise your numbers will match ours.
Three things, nothing more
- A representative slice of documents — a few hundred pages is plenty, and it should include the awkward formats, not only the clean ones
- The questions your teams actually ask of them, chosen before you see any fragments
- Known-correct answers where you have them, so the report can score correctness rather than only agreement
- A view of current AI spend, or a provider bill export, for Forecast
Requesting a conversation commits you to nothing. Scope and fee are agreed in writing before any work starts.
Request a scoping conversation
Scope, test, review, decide
Scope
We agree the slice in writing: which documents, how many, which questions, which models, and the baseline to compare against — including your current retrieval workflow where you have one.
Test
We decompose the slice, run the questions against every agreed route, and weigh the storage under both retain-source and replace-source scenarios.
Review
A written report: every number with its unit, the method, the acceptance criteria we agreed at the start, and the questions where fragments did no better. It is yours whatever you decide.
Decide
You decide whether to proceed to production. Choosing not to is a normal outcome and costs you nothing further.
What a pilot commits either side to
The specifics — document count, question count, models, duration and fee — are set in the scoping document for your pilot. What does not vary is below.
| Fee | Fixed, quoted and agreed in writing before any work starts. The fee is set from the scope: number of documents, number of questions and number of models tested. |
|---|---|
| Scope limits | Document count, question count and models are capped in the scoping document. Anything beyond the cap is a change we agree and price, not a surprise on the invoice. |
| Your data | Handled under a written agreement covering where it is processed, who can access it and how long we keep it. Pilot material and anything derived from it is deleted on the schedule set in that agreement. |
| The baseline | Agreed before testing. Where you have an existing retrieval workflow, it is one of the baselines — comparing only against a model reading whole documents is the easier test and we do not rely on it alone. |
| Acceptance criteria | Set with you at scoping, so the result is judged against a standard chosen before anyone saw an outcome. |
| What you receive | A written report covering answer quality against each baseline, token use with its categories stated, storage under both retention scenarios, and the questions where the approach did not help. |
| The decision | Yours. If you proceed, we scope production implementation separately. If you do not, the report is still yours and there is nothing further owed. |