Skip to content
StartFree Trial
Sales preparation · practical guide

Prepare the sales call from the documents you will need.

A buyer asks about the volume tier, a technical detail or the notice period. The useful preparation is knowing which current document supports your answer, and which questions still need a decision.

Thalassa Assistant ·

Five document types. Five buyer questions. One source map.

1. Build a small, current document pack

Start with the buyer's situation and the purpose of this call. A discovery conversation needs different evidence from a negotiation over an existing offer. Select only files you are authorised to use, and check the version and effective date before searching them.

A starting pack for a B2B sales call
DocumentCheck before the call
Proposal or quoteBuyer, scope, exclusions, validity and the version actually sent.
Price listCurrency, taxes, volume thresholds and effective date.
Product specificationThe exact model, variant, supported conditions and revision.
Contract or framework agreementThe applicable clause, amendments and order of precedence.
Delivery and service termsWhat is a commitment, an estimate or still subject to confirmation.

A larger folder is not automatically a better knowledge base. Put superseded versions aside and name the current files clearly. If the proposal and framework agreement disagree, resolve the conflict before treating either as authority.

2. Map questions to a file and page

Write five questions this buyer could reasonably ask. Use their language: “Does that price apply at 500 units?” is easier to prepare for than a label such as “commercial terms”. For each question, record the source location and any condition that changes the answer.

Illustrative example · not a customer claim

Question: Does the quoted tier apply to this order?

Source: Current price list, page 4, volume table.

Check: Quantity, currency, effective date and the buyer's agreement.

Decision needed: An exception below the published threshold needs commercial approval.

You can use this template in a plain text file or spreadsheet: Question | Document and version | Page or section | Conditions | Decision owner. Leave a field empty when you do not know it. That gap is a preparation task, rather than a reason to improvise a number.

3. Separate facts from commitments

A document can establish the published price; it cannot give you permission to approve a new discount. A technical specification can establish a tested condition; it may not confirm a custom integration. Mark the boundary between an answer you can support and a commitment someone else must approve.

Before the meeting, agree who owns each open decision and when it can be answered. During the call, a precise follow-up is useful: “The published tier starts at this quantity. I will confirm the exception with our commercial lead by tomorrow.” Use a deadline you can actually meet.

4. Rehearse the questions that change the deal

Run a short practice conversation with a colleague, or with a tool using your selected documents. Include one price question, one scope question and one deliberate document gap. Practise checking the source before speaking, explaining the relevant condition and giving a clear follow-up when a decision is missing.

If you use Thalassa Assistant, add the authorised files to its local knowledge base and use a briefing or rehearsal to prepare. During a permitted conversation it can draft answers from those files and show their source. Automatic answering is optional and off by default. Source references help you verify a draft; they do not make it infallible.

5. Check the answer, then close the gaps

Keep the applicable document version and page in view when you give a price, clause or specification. Check units, exceptions and scope. If the source does not support the answer, say what remains open and who will confirm it. After the call, update your question map and send only commitments you are authorised to make.

Thalassa searches the knowledge base on your computer and uses cloud services for transcription and answers. Use assistance and transcription only where the participants' permissions and your organisation's rules allow them. Read the published data path before using confidential material. Audio is not archived; the transcript is deleted after the meeting. Saved notes, debriefs and session metadata are separate.

Questions before your first trial

Which files can I use?

The app supports PDF, Word, Pages, Markdown, text, Excel and CSV files. Check permissions first. Plan limits and scanned-PDF handling are listed on the product page; password-protected files cannot be read.

How can I evaluate it?

Choose a permitted meeting or practice call, prepare the five-question source map and check the drafts against the documents. The free first meeting includes up to 15 minutes of live answers, five preparations and about 100 pages, with no card required. That is a trial allowance, not a promise of any sales outcome.

Which business plan fits recurring calls?

Standard is €39 per month plus VAT, with 30 meeting-hours and a 300-page knowledge base. It does not include debriefing. Professional and Premium have different limits and include debriefing. Rehearsals and generation use the applicable meeting-time budget. Review current terms on the pricing page.

Try the workflow with your own sales documents.

See how Thalassa Assistant supports preparation and permitted sales conversations.

Explore sales-call support