Mindtickle

Getting the right, current, approved material in front of the seller: a central library, search and recommendations in deal context, versioning and expiry so outdated decks disappear, approval workflows, templates that keep the brand, and content in several languages.

0 — A shared folder of files with no versioning, no search beyond file names and no statement on approvals or expiry.

3 — A central library with folders and full-text search, but old versions stay in circulation, there is no approval step, and personalised copies cannot be traced back to the master.

5 — A library with versioning and expiry dates, approval before publishing, permissions by team or region, content recommended by deal stage or CRM field, and German as a supported content and interface language.

8 — Superseded versions replaced everywhere they were shared, brand-locked templates sellers can personalise within limits, content tagged by language and market, compliance review workflows with an audit trail, and usage per asset reported back to the content owner.

10 — Content governance a regulated industry can rely on: every shared copy traceable to its approved master, automatic retirement of expired claims, a documented review log per asset, and export of the full library with its metadata and version history.

The shared space with the customer: digital sales rooms, mutual action plans, proposals and trackable links — judged on what the buyer is told about being tracked and whether tracking can be limited, because the people opening the room are another company's employees.

0 — Links or rooms that track opens and time per page with no statement of what is recorded or whether the recipient is informed.

3 — Digital sales rooms or tracked links with engagement analytics marketed as "buyer intent", a privacy policy that covers the vendor's own website only, and no setting to limit tracking.

5 — Digital sales rooms with shared content, a mutual action plan and comments, the engagement data recorded per visitor documented, a consent or notice step for recipients available, and tracking switchable per room or link.

8 — Rooms in the customer's branding and own domain, access controls (email verification, expiry, download blocking), anonymous or aggregate-only analytics as an option, a retention period for visitor data stated, and the vendor's role as processor for visitor data set out in the DPA.

10 — Engagement designed around the buyer's rights: tracking off or aggregate by default until the seller enables it with a recorded notice, visitors able to see and delete what was recorded about them, a TDDDG and GDPR assessment published, and room content and history exportable for both sides.

Making sellers ready: onboarding paths, courses and certifications, role-play and practice with feedback, and call recording or conversation analysis where offered — judged on whether recording respects that every participant in a German call has to consent.

0 — No training features, or call recording offered with no statement on participant consent.

3 — Courses and quizzes in a basic learning area, and call recording or AI role-play marketed without saying how participants are informed or how long recordings are kept.

5 — Onboarding paths with courses, quizzes and certifications, practice exercises with manager feedback, and — where calls are recorded — a documented consent announcement for all participants and a stated retention period for recordings.

8 — Training linked to content and deal stages, AI role-play with the scoring criteria described, manager coaching workflows, recording consent configurable per country with external participants able to decline, transcripts deletable on request, and German supported for transcription and training content.

10 — Readiness that can be evidenced and defended: certifications tied to measurable skills, scoring models documented in a form a works council can review, recordings and scores restricted to defined roles, retention configurable per data type, and every coaching feature usable without recording calls.

What the platform measures and concludes — content usage and influence on revenue, seller activity and AI-generated scores or recommendations — and whether the customer can see how a score is built, limit what is measured about individual sellers, and switch AI features off. A system that rates employees is a co-determination matter in Germany.

0 — Seller scores, rankings or AI insights marketed with no statement of what they are computed from or who can see them.

3 — Dashboards on content usage and seller activity, AI features described as benefits, but no documentation of inputs, no way to restrict individual-level views, and no model provider named.

5 — Content usage and engagement reported per asset and team, AI features each described with purpose and inputs and switchable per account, individual seller reports limited by role, and the AI model provider or subprocessor named.

8 — Analytics configurable to team-level aggregation, AI outputs shown with their sources, customer data excluded from model training by default and stated so, EU processing available for AI features, and documentation aimed at works council agreements.

10 — Measurement the people measured can trust: every metric and score defined publicly, individual-level tracking off until enabled by policy, access to individual data logged, AI features off by default until the customer enables them, and the vendor's EU AI Act position published.

Fitting into the seller's day and the company's stack: CRM integration in both directions, email and calendar add-ins, Microsoft Teams and Office, single sign-on and provisioning, an API — and getting content and history out when the contract ends.

0 — No integrations and no API; content is shared by downloading and re-attaching files.

3 — A Salesforce or HubSpot connector and a browser extension, with no statement of which data flows in which direction, and no export beyond single files.

5 — Documented integrations with Salesforce, HubSpot and Microsoft Dynamics, Outlook and Gmail add-ins, Microsoft Teams, SSO via SAML, and engagement data written back to the CRM record.

8 — SCIM provisioning, a documented REST API with webhooks, integrations with the e-signature, CPQ and learning tools named, field mappings configurable, and bulk export of content library and analytics.

10 — Integration and exit designed in: a versioned API with a deprecation policy, deletion that propagates to connected systems, and a documented exit process that hands back content with versions, rooms, training records and analytics in open formats.

Who the contracting entity is, where content, buyer engagement data and call recordings are stored and processed, and who the subprocessors are — including the transcription and AI providers that recordings and documents are passed to. Independently sourced by the sovereignty pipeline.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and transcription or AI processing of unclear location.

3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent, or recordings and documents are transcribed or analysed outside the EU without saying so.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — transcription, AI, email tracking, support access — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations including transcription and AI providers, and a DPA covering buyer engagement data and recordings.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, transcription and AI features running within the EU on providers the customer can see, and certification published.

Whether a buyer can compute the real annual cost from public pages alone: the per-seat price and which roles need a seat, platform fees, minimum seat counts, which modules (content, rooms, training, coaching, AI) are bundled, and the minimum term.

0 — No public prices at all; every tier is a sales conversation.

3 — A starting price exists, but which roles need a paid seat, minimum seat counts or which modules a tier includes are unstated — the invoice is unknowable.

5 — Tier prices public per seat with the main features per tier, but at least one commonly needed piece (platform fee, viewer or creator seats, coaching or AI add-on, CRM integration) is unpriced.

8 — Every tier priced publicly with seat types and minimums, add-on and module prices listed, implementation fees stated, minimum term and VAT treatment given.

10 — Complete price computability: the annual invoice derivable for a given number of sellers, content creators and managers, with every module, add-on, platform fee and overage published.