Run the demonstration without us in the room
Enablement exists so your engineers can answer a customer question on the call, rather than booking a follow-up with the vendor.
Everything that arrives once you sign
Demo environment
A working instance with sample projects already configured, so nobody builds a demonstration from an empty database.
Technical training
Six modules covering sources, recognizers, classification, masking, deployment and how to run a demonstration.
Certification path
For the engineers who will lead implementations rather than sit alongside them.
Escalation route
A defined path to vendor engineering for anything that outruns your team, open from your first deal.
The training curriculum
Six modules, built around what a customer actually asks during an evaluation rather than a feature tour.
Connecting sources
Folders, mail, databases and cloud services. Which credentials each connector needs, what read-only access covers, and how sampling keeps a first scan quick on a large repository.
Recognizers and dictionaries
What ships by default, how to add a pattern for a customer's own identifier format, and when a keyword dictionary beats a regular expression.
Classification design
Setting up classes against a customer's policy, writing the queries behind them, and explaining why a document landed in a given class.
Masking and anonymization
Binding profiles to user groups, the difference between masked output and anonymized substitutes, and which one a testing team actually needs.
Deployment
Sizing a server, on-premises against cloud, where the index sits, and answering the residency question a privacy officer will ask.
Running a demonstration
The sequence that works, which is to connect one real source, scan it, show what surfaced, then mask it in front of them. Roughly forty minutes.
Escalation boundaries
You hold the customer relationship and the first two support lines. Anything that turns out to be the product itself goes to vendor engineering, and you stay informed rather than handing the account over.
Escalation is open from your first deal. Nobody expects a new partner to diagnose an indexing fault alone.
| Situation | Who handles it |
|---|---|
| Customer question on configuration | Your team, first line |
| Source will not connect | Your team, second line |
| Scan results look wrong | Your team, escalation available |
| Suspected product defect | Vendor engineering |
| Feature request from a customer | Vendor engineering |
| Security advisory or patch | Vendor engineering |
Collateral, branded as yours
Ready to use
- Product overview and capability summaries
- Deployment and architecture explainers for technical buyers
- Regulatory mapping across the three markets
- Demonstration script with a suggested running order
Built with you
- Sector material for the verticals you sell into
- Responses for tenders and security questionnaires
- Joint positioning where you bundle implementation services