Selling from Europe, and the things that only matter if you do

Most sales software is built for one market and adapted for the rest. You meet the adaptation in small places. The analysis of your call arrives in English. The price is quoted in a currency you do not invoice in. The consent banner is built so that agreeing is one click and refusing is three, because the site behind it cannot count you until you agree.

Sell is sold under Lithuanian law, and the authority that supervises it is Lithuanian. That does not make it better software. What it does is put a handful of small, checkable facts into the product, each with a limit attached, and every one of them only matters if you are selling from here too.

The analysis is written in the language the call happened in

Call analyses are written in the language the call happened in, Lietuvių, Latviešu, Eesti and Polski among them. The product prints each one in its own name as well as in English, which tells a Lithuanian reader something the word Lithuanian does not: that somebody who speaks it was involved.

Written in, not translated into.

An analysis in translation is a reading of a second document. The transcript went through a machine that made it English, and the analysis was written from what came out. Everything a language keeps at its edges has to survive that extra pass: the conditional that is a polite no, the hedge that means the decision has moved up a floor. What comes back is fluent, and none of the fluency is evidence.

It also breaks the thing you do with an analysis, which is not read it but check it. A line saying the client stalled on price is worth having because you can open the transcript and find the sentence that produced it. In the language of the call that is the same sentence. In translation you are comparing a paraphrase with a paraphrase, and the two agreeing tells you nothing.

The limits. The list is a list: if your calls happen in a language that is not on it, this is a product with a hole in it for you, and better that you find the hole here. The live transcript you watch during a call is your own browser's speech recognition, and on some browsers, Chrome in particular, that means the browser vendor processes the audio. The transcript that lasts is made afterwards by a speech model on our own servers, and it replaces what you saw.

Jurisdiction is a fact, and a fact is not a certificate

The contract is governed by Lithuanian law and disputes go to Lithuanian courts. The Privacy Policy names the supervisory authority rather than gesturing at one: the Lithuanian State Data Protection Inspectorate, Valstybinė duomenų apsaugos inspekcija. A regulator you can name is a regulator you can write to about us.

That is a smaller claim than it looks. It is not a compliance certification: we do not hold SOC 2 and we do not hold HIPAA, and nothing on this site implies we do. If your buyer's procurement requires that posture, buy from the vendor who has it.

The same document does not tell you where the servers are. The field for a hosting region is empty because it has not been verified against the deployment, so the sentence is dropped rather than name a region we would then have to defend. What it does say is that some of the providers it lists sit outside the European Economic Area, chiefly in the United States, and that data reaching them moves under Standard Contractual Clauses or an adequacy decision.

One line in it does more work than the rest: your workspace content is not used to train AI models, ours or anybody else's. The assistant, drafting and summarising work runs through a Claude CLI process on our own infrastructure, one shot at a time, with no conversation history and no session files written by it. Store your own provider key and those requests run on your account instead.

The banner asks once, and takes no for an answer

There is a cookie banner, and this section used to say there was not. That stopped being true when the site started running Google Analytics, and it is further from true now that a Meta pixel tells us which of our own ads brought somebody here. Leaving the old sentence up in an essay about checkable facts would have been the worst kind of small print, so here is the arrangement instead.

The two tags do not behave the same before you answer, and flattening them into one sentence is how this section went wrong the first time. Google Analytics is not fetched until you accept: decline, or leave without answering, and nothing is requested from Google at all. The Meta pixel is fetched when the page opens, which tells Meta your address and which page you are on, and it starts in a refusing state that reports nothing until you accept. We load it early because a pixel nobody outside can detect is a pixel nobody outside can verify, and that is a trade worth printing rather than burying.

Declining costs you nothing, and that is what makes the question honest rather than decorative. We count visits ourselves without cookies whichever way you answer, so a refusal never costs us the count and we are never quietly pushed into nudging you. Accept and Decline are the same size in the same row, there is no close button that leaves the question hanging, and the footer carries a link that clears the decision and asks again.

What our own counting sees, since you are entitled to know before you answer: which pages were opened, how far down them you read, and where they were clicked, aggregated into a heatmap. It runs against a fingerprint that is salted and rotates at midnight rather than a cookie, and it stands down entirely for Do Not Track and Global Privacy Control. It stays off the signed-in workspace, and so does the Meta pixel, which is not merely switched off there but never loaded at all: loading the script is itself what tells Meta which page you opened, so an account you pay for stays out of an advertising network entirely rather than quietly.

What is stored in your browser is still a short list: a short-lived sign-in token and a rotating refresh token in local storage, your theme, navigation and table layout choices, the backend's cross-site request protection cookies where a session is involved, your answer to the banner so we stop asking, and, only if you accepted, the measurement cookies that answer buys. Clearing your browser storage signs you out, resets those preferences and brings the question back.

The tax is in the price, not in the checkout

Every price on this site carries the same line, and the line says the price excludes VAT. The rate is printed beside it, which is the whole trick: you read the tax next to the number, not at the last screen of a checkout.

The Terms carry the rest: taxes are added where due, and if you are VAT registered in another EU member state you give us your number and the reverse charge applies. None of that is unusual. Being told before you have entered a card is.

Usage based pricing already asks you to trust an estimate of what a month will cost. A tax that turns up at the last screen, on top of an estimate, is where the trust goes. So the line sits under the plan grid, on the card the configurator recommends, under the comparison table, and in the pricing FAQ, where the question gets a plain no.

One thing to notice, since you are entitled to notice it: the plan prices are written in dollars.

You are the merchant of record, which is a right and a duty

Payments run on Stripe Connect direct charges. Your client's charge is made on your own connected Stripe account, and Stripe pays out to your own bank. There is no balance of yours sitting here for us to hold.

Our fee is a percentage of each charge plus a fixed amount, on top of Stripe's own fees. The figures are on the pricing page and on the Stripe integration page.

The duty half is what a marketing page usually leaves out. The statement descriptor is yours, and so is the obligation to the payer. Payouts, disputes and refunds are Stripe's, on your account, and we do not sit in the middle of them. The onboarding is Stripe's too: their form, and their identity checks.

Card collection is still being switched on in this deployment, so ask us about timing before you build a quarter around it. Nothing here moves money while you are not looking. Autopilot is off until you turn it on, and switched off it does nothing and costs nothing. Turned on it drafts: the job that reads an invoice past its due date writes the note, with the amount and the date in it, and waits for you, whatever your other settings say.

What none of this is

Small facts, each of them checkable, none of them a certificate. A European jurisdiction is not a security posture, and a named regulator is not an audit. What they tell you is who you are dealing with, under whose law, on what terms, and where the money goes on its way to your bank.

Your workspace has a documented API that covers everything you put into it, including taking your data back out, on a key scoped to that workspace alone. Leaving is not a conversation you have to have with us.

If you sell from Vilnius, Riga, Tallinn or Warsaw, the quickest test is to run one call through it. Sign up on the free plan, which needs no card, take a call, and read the analysis in the language you took it in.

Questions this raises

Is my data hosted in the EU?

The Privacy Policy does not say, and the empty field is why: a hosting region goes in there once it has been verified against the deployment, and not before. What the document does carry is a table of the service providers we use, by name and by what each one handles, and the statement that some of them are established outside the European Economic Area, chiefly in the United States, with data reaching them under Standard Contractual Clauses or an adequacy decision. Your workspace content is not used to train AI models, ours or anybody else's.

Is the call analysis translated into Lithuanian, or written in it?

Written in it. The analysis is produced in the language the call happened in, from that call's own transcript, in any of the languages the product publishes, Lietuvių, Latviešu and Eesti among them. The copilot answers you in whatever language you write to it in. If your calls happen in a language that is not on that list, the analysis will not arrive in it, and that is worth knowing before you sign up rather than after.

Who is the merchant of record when my client pays an invoice?

You are. Payments run on Stripe Connect direct charges: the charge is made on your own connected Stripe account and Stripe pays out to your own bank, so we never hold your money. The duty comes with the right. The obligation to the payer is yours, payouts, disputes and refunds are Stripe's on your account, and the onboarding is Stripe's form and Stripe's identity checks. Card collection is still being switched on in this deployment.