Enterprise licensing
We built it, so we can answer for it.
Every product in the portfolio is ours: our code, our roadmap, our people. That means the security review is answered by the people who wrote the thing being reviewed — and when your environment needs something the product does not do yet, including running inside your own infrastructure, that is a build we can quote rather than a request we have to decline.
How it works
Five stages, no surprises.
Fit
A conversation about where the time actually goes. We will tell you if none of the portfolio fits — that answer costs you an hour instead of a quarter.
Trial
A small group, real work, a fixed window. Enough people to see whether the habit sticks, few enough that nothing needs signing off first.
Review
We answer the security and data questions in writing, per product: what is captured, where it is processed, how long it is kept, who can reach it, and what happens when you stop. We wrote the code, so the answers come from us rather than a vendor questionnaire.
Settle where it runs
Today everything runs in our cloud. If your environment has to hold the data instead, we scope that build and quote it before anything is signed — so you are agreeing to a timeline and a price, not to a promise that it will be sorted out later.
Licence, rollout and support
One agreement covering every product you take: one supplier, one invoice, one renewal date. Then installation onto managed estates, configuration against your own tools, onboarding for the teams using it, and a named contact when something breaks.
What we won’t claim
We will not tell you a product holds a certification it does not hold, or that a control exists because it is on a roadmap. If a product is in private beta, we will say so on the page you are reading.
We will not describe a pilot as a deployment, or a friendly early user as a reference customer. When we have named customers to share, they will be named.
And we will not tell you a product runs on-premise when what we mean is that we would build it for you. Today it is hosted by us. The build is real and we will quote it — but the two are different sentences and we will use the right one.
The reason is straightforward: everything on this list gets checked eventually, and the checking usually happens after the contract is signed.
Questions
The ones we get asked first.
Do you build these products yourselves?
Yes. Every product in the portfolio is built in house — our people, our codebase, our roadmap. They carry their own names because that is what the teams using them call them, but there is one company behind all of them, and it is the one you sign with.
Why do they have separate names and sites?
Because a QA lead adopting a screen recorder and a sales director adopting call coaching are not the same buyer, and neither of them wants a suite. Each product stands on its own. What you get by taking more than one is a single agreement, not a bundle you did not ask for.
Can we run this in our own environment?
Not off the shelf — today every product is hosted by us, and we would rather say that plainly than imply otherwise. But we build these products, so an on-premise deployment is engineering work we can take on rather than a capability we lack. Tell us what your environment requires and you will get a scope, a price and a timeline, not a maybe.
What does a licence cover?
Seats or teams for the products you take, the deployment and configuration work to get them running, onboarding for the people using them, and an agreed support route. Pricing depends on the products, the number of people and whether you are running it yourself — we will quote it plainly.
Can we run a trial before committing?
Yes, and we would rather you did. A short trial with a real team tells you more than any demonstration.
Where is our data processed?
In our cloud, and we answer it per product in writing before you buy — what is captured, where it goes, how long it is kept, and which third-party services are involved in transcription and analysis. If any of that is a blocker for your organisation, say so early: it is usually the thing an on-premise build is meant to solve.
What about certifications?
We will tell you exactly which controls and certifications each product holds today and which it does not. Where something is not in place, you will get a straight answer and, where we have committed to one, a date.
Start with the security questions.
Send us the ones your organisation always asks. We will answer them per product, in writing, before anyone talks about pricing.