Commercial
Customer References
How to get a customer reference for Kavanah, what we can and cannot share, and what you can verify about the product without waiting for one.
Last updated: July 28, 2026
Kavanah is in an early-access phase. We are deployed with early customers and partners, but we do not have publicly nameable customers or published case studies, and this page does not pretend otherwise.
References are arranged individually, with the referencing customer's consent, at the point in an evaluation where they are decision-relevant. We do not publish customer names, logos, or quotes without written permission — including yours, if you become a customer.
1. What we can provide today
| Format | What it is |
|---|---|
| Reference call | A call with an existing customer in a segment comparable to yours — similar team size and use case — arranged under mutual NDA where either side requires it. Typically offered once a technical and security review is underway, so the reference is answering a real question rather than an early one. |
| Pilot introduction | An introduction to a customer running a pilot, if that is closer to where you are. We will say plainly that it is a pilot and how far along it is. |
| Live workspace walkthrough | A walkthrough of a real production workspace with our product team — the working system with real usage, not a scripted demo environment. |
Availability depends on the referencing customer, so we cannot promise a specific company, industry, or headcount in advance. If we do not have a comparable reference, we will tell you that rather than substituting a less relevant one.
2. What we do not do
These are commitments about how we treat our customers' confidentiality. They are the same commitments we make to you.
- No unattributed testimonials. We do not publish anonymized quotes, “a leading agency” style attributions, or composite customer stories. If a quote is not attributable and approved, it does not go on our site or into a deck.
- No customer names without written consent. Names and logos are used only with written permission, for the specific use permitted, and permission can be withdrawn.
- No pilot presented as a completed case study. We do not describe in-flight or early deployments as finished outcomes, and we do not publish measured results — adoption numbers, time saved, ROI — that we cannot substantiate.
- No reference used as a sales lever. Customers are asked, not volunteered. A customer who declines is asked again no sooner than the next renewal cycle, if at all.
3. How to request a reference
Process
Send the request to your point of contact, or through /contact. We identify a customer whose deployment actually resembles yours, ask them, and come back to you with either an introduction or a clear no. We will not chase a customer who has declined, and we will not stall a request by leaving it open indefinitely.
Because a reference costs a customer their time, we ask for it once an evaluation is far enough along that the answer changes something — usually after a technical review and a security review. If you need proof earlier, section 5 lists what you can verify immediately.
What to send
The more specific the request, the better the match. Useful details:
| Detail | Why it helps |
|---|---|
| Segment and industry | Lets us match on the constraints that actually differ — regulated vs. not, agency vs. in-house, client-facing vs. internal. |
| Team size and rollout shape | A 12-person rollout and a 200-person rollout raise different questions; matching on size makes the call useful. |
| Primary use case | Client delivery, engineering delivery, portfolio management, and AI-agent-heavy workflows exercise different parts of the product. |
| The questions you want answered | Send them ahead. It lets us find a customer who can answer them, rather than one who will simply be complimentary. |
| Constraints (NDA, no-competitor, timing) | Tells us who we cannot approach and how quickly we need to move. |
4. Reference-call ground rules
- Direct, usually 30 minutes. You and the referencing customer, scheduled between you once the introduction is made.
- No Kavanah staff on the line unless both sides want us there. The default is that we introduce and step out, so the customer can answer candidly — including about what has not gone well.
- Mutual NDA where required. Either party can ask for one before the call, and we will paper it.
- One call per evaluation, and reciprocity. We ask that the call not be recorded or shared without the customer's consent, that it stays inside your evaluation team, and that repeat requests go back through us. If you later become a customer, we may ask you the same favor — and you are free to decline.
5. Proof you can evaluate without a reference
A reference is one input, and in an early-access phase it is the scarcest one. Everything below is verifiable today, on your own timetable, against your own criteria.
| Evidence | Where |
|---|---|
| A proof of concept on your own data | The strongest evidence available to you: run the product against your real workflows. /poc |
| Security and compliance artifacts | /trust, /security, /continuity, and the pre-answered questionnaire at /rfi. Artifacts released under NDA are requested from /trust. |
| Functional documentation | What the product does, at the level of detail an RFP asks for: /capabilities, /frd, and /fsd. |
| The public API and specification | Inspect the integration surface directly, before you commit: /docs, with the machine-readable specification at /openapi.yaml. |
| Commercial terms in writing | List rates, seat definition, and billing terms: /pricing-sheet. |
6. Becoming a reference
If you are a customer and willing to act as a reference, the arrangement is deliberately light and entirely revocable:
- You approve every introduction in advance — who is asking, what they want to know, and when.
- You choose what may be used publicly: nothing, your name, a quote, or a written story. Anything published is approved by you in writing first, and withdrawn on request.
- We cap how often we ask, and we brief you before every call so you are not answering cold questions.
- In return: a direct line to the product team, early visibility of the roadmap, and priority input into what we build next.
To opt in, or to withdraw at any time, email support@kavanah.ai.
Request a reference
Send your segment, team size, use case, and the questions you want answered through /contact, and we will tell you honestly whether we have a comparable customer to introduce you to.
If you would rather not wait on someone else's calendar, start a proof of concept at /poc — evidence from your own data outranks evidence from ours.
Questions from a security, privacy, or procurement team? Email security@kavanah.ai. For SOC 2, penetration-test, or questionnaire artifacts shared under NDA, use the request forms on the Trust & Compliance page.