Carry a data security product already in production
GEODI has an installed base, a documented feature set and vendor engineering behind it. What it needs across North America is people who know their local buyers.
- Territory
- Canada, the United States and Mexico
- Deal protection
- Acknowledged within five business days
- Support model
- You hold first and second line
- Commercial terms
- Set per agreement rather than by published tier
- Customer ownership
- Accounts you bring stay yours
- Nothing signed until
- Stage three of five
Why this sells right now
Quebec Law 25 landed with teeth. Ontario put cyber security on a statutory footing for public bodies. State privacy statutes keep arriving in the United States, and Mexican organizations face the same discovery question under LFPDPPP.
Every one of those conversations opens the same way, with a buyer who cannot say where their personal data is. That is a discovery problem before it becomes a policy problem, and it is a short path from there to a paid engagement.
| What you sell into | Trigger |
|---|---|
| Municipalities | Access to information requests arriving on a statutory clock |
| Healthcare | Health information spread across scanned intake records |
| Financial services | Cardholder data scope reduction ahead of assessment |
| Legal and professional | Client material sitting in shared drives after a migration |
| Any regulated firm | An audit finding that nobody could inventory personal data |
Four ways to work with us
The arrangement follows what your business already does, rather than a tier you have to climb into.
Resellers
You sell the licence and hold the customer relationship. Implementation is yours where you have the capability, and ours where you would rather it was not.
Managed service providers
You run discovery and classification as an ongoing service inside your own practice, against customer environments you already administer.
Systems integrators
You bring GEODI into a larger privacy or security programme, usually alongside policy work the customer has already commissioned.
Technology alliances
You integrate GEODI with a product of your own, where discovery output makes your platform more useful to a shared customer.
Named partners in each category will be listed here as agreements are signed.
Deal protection
Register an opportunity and it is recorded against your organization on the submission date, with acknowledgment inside five business days.
Customer ownership
Accounts you bring stay yours. Non-circumvention runs through the distribution agreement rather than sitting in a marketing promise.
Demo environment
A working instance with sample projects already configured, so your engineers can run a customer demonstration without us in the room.
Technical enablement
Six training modules covering sources, recognizers, classification, masking, deployment and how to run a demonstration, with a certification path.
Vendor escalation
You hold first and second line. Anything that turns out to be the product goes to vendor engineering and you stay on the thread.
Co-selling early
First opportunities usually run jointly, so your team sees how the technical conversation goes before running one alone.
Support, divided two ways
You hold the customer relationship throughout. Nothing about an escalation hands the account over.
Three products, one engine
Most engagements start with the platform and grow into the content packs once a compliance deadline appears. The language model layer tends to sell itself after a buyer watches a search return an answer pulled out of a scanned document.
| Product | What it is |
|---|---|
| GEODI DSPM | The discovery, classification, masking and remediation platform |
| GEODI Q | The language model layer for natural language questions against indexed content |
| Regulation content packs | Compliance mappings, report templates and prebuilt content covering more than 35 countries |
Commercial questions, answered before you ask twice
The things resellers actually want to know on a first call.
What margin do partners get
Commercial terms are agreed partner by partner and stay confidential under the distribution agreement, so a discount grid is not published here. They are discussed once mutual non-disclosure is in place, which happens at stage two of five rather than at contract stage.
What shapes them is the volume you commit to, whether you deliver implementation yourself, and how much of the support load your team carries.
Is there a minimum revenue commitment
There is no published floor. The conversation at stage two covers the volume you realistically expect, and the terms follow from that rather than from a threshold you have to clear first.
Are there named tiers
No. The arrangement follows the partner type that matches your business rather than a ladder with badges attached. Terms are set per agreement.
How is a partner deal protected
Register the opportunity and it is recorded against your organization on the submission date, with acknowledgment inside five business days. Where a second partner approaches the same account later, the registered entry is the reference.
Do we need certified engineers before we can sell
You need one named technical contact who completes enablement. Certification is a path rather than a gate, and vendor engineering is available on escalation from your first deal onward.
Who holds the customer contract
You do. Renewals and commercial terms with the end client stay with you, and escalation to vendor engineering never moves the relationship.
Fit, and the cases we turn down
Naming the second column saves everybody a quarter of wasted pipeline.
Fits well
- You already sell security or compliance services
- Your customers face privacy or audit obligations
- You have technical staff who can run a demonstration
- You work with public sector, healthcare or financial accounts
Fits poorly
- You want a product to resell with no delivery capability
- Your accounts have no regulatory pressure
- You need the vendor present on every call indefinitely
- You want exclusive rights over a whole country
Before any paperwork
Name a few accounts you already serve that could not currently say where their personal data sits. That is usually enough to know whether this fits.