Methodology
How scores are made
Every number on this site comes from a published rubric, a named bench of AI judges, and public evidence you can open. This page is the whole method — weights included.
What this is — and is not
- It is an AI-assisted analysis of public evidence. A panel of AI judges reads what a vendor publishes and scores it against a rubric anyone can read.
- It is not a hands-on test. Nobody here has used the product. Every reading is made from the vendor’s own public pages, captured and dated. These are not hands-on tests, and they are not human reviews.
- It is not a collection of user reviews. No stars from a crowd, no incentivized ratings, no vendor-submitted testimonials count towards any score.
- Scores are opinions; facts are cited and correctable. A score is the panel’s judgement and is labelled as such. Every fact behind it cites the captured source it was read from, and anyone can report an error in any of them.
Where the facts come from
The evidence is the vendor’s own public surface: pricing page, security and compliance pages, legal terms, subprocessor lists, documentation. Each page is captured with its date and a content hash, and the capture is what the judges read — not a memory of it.
Facts are extracted from those captures and then verified in an independent second pass against the same source. A fact that does not survive that pass is not shown anywhere on this site and never reaches the judges:
- a claim we could not find again in the source is removed — especially in the strict classes, pricing and compliance, where a wrong price or a wrong certification is not a rounding error;
- a claim the operator has suspended after a report is out of the sheet until the report is decided;
- evidence older than 90 days, or pricing older than 30 days, keeps its place and carries its date — age is a warning, not a reason to hide something.
What we remove is the claim, not the page. A product is only kept off the site when there is nothing to print: no proven fact, no judge, no verdict. Otherwise the page goes up without the unproven line, and a section called “What we left out” names every hole, with a button asking you for what we are missing. Send it with the page it can be read on and it goes through the same checks as anything else.
How a fact is proven
The vendor’s own page has to show it. Every page we capture is kept as a screenshot of the page as it rendered. Code, not a model, looks for a fact’s quoted passage in the visible text of that screenshot. A passage that is not visible on the page as captured proves nothing, and the fact is not shown.
Or the vendor’s own structured data has to state it. Many vendors also publish machine-readable data about themselves in their pages (schema.org markup: JSON-LD, Microdata or RDFa), such as their legal name, registered address or prices. We keep that markup with the capture of the page it came from. Code, not a model, reads facts from it, only facts about the vendor and its product and never contact details or people. The second AI reading and the audit then check each such fact against the markup instead of a screenshot. Where the visible page says something else, the visible page wins and the structured value is not shown. A fact proven this way says so on its source record: “From the vendor’s structured data on [page], captured [date]”.
An AI model has to confirm it. An AI model then reads the quoted passage and confirms that it supports the value we print. Where a mistake would hurt a vendor — pricing, compliance, legal, subprocessors and sovereignty, and any statement adverse to the vendor — that is not enough: a second AI reading, by a model that sees only the cropped screenshot and not the text the first one read, checks the same value, and the two have to agree. If they do not agree, or either cannot tell, the fact is not shown. A sovereignty dimension without that agreement reads “Unknown”.
Judges score from the same proven facts the page prints. Where they found no public information on something, they say so — that is a statement about the evidence we hold, not about the product. Absence is never printed as a product fact. Names of people, read from an imprint or a privacy policy, are never shown at all; they serve only to tie a product to its legal entity.
Provenance is an editorial classification. The provenance class (EU-Made, EU origin foreign-owned, UK / wider Europe, Rest of world) is our editorial classification by the registered seat and ownership of the vendor. UK / wider Europe is a vendor seated in the United Kingdom or in another European country outside the EU, the EEA and Switzerland. Provenance unknown means the vendor has not been classified yet: a product found by our own discovery or added on a vendor’s listing request starts there, and its class is never guessed. The class is separate from the sourced sovereignty dimensions below, and it can be reported like any fact.
What we leave out. A fact that is not proven is not shown — not hedged, not badged, not marked as doubtful. Absence is never printed as a product fact either. Where we found nothing about pricing or compliance, “What we left out” says that we found no public information on it on the pages we read, and lists those pages. Where facts were read but could not be confirmed on the vendor’s page as captured, it says that instead. The page itself stays up: leaving out one claim is not a reason to withhold everything else we can show.
Measured error rates
Every week a random sample of published facts from each class below is read once more, by a third AI model that took no part in publishing them and is told nothing about how they were read. It sees only the sentence we print and what it rests on, a screenshot passage or the vendor’s markup, and marks it right or wrong. A wrong fact comes off the page at once, and the other facts on its page are checked again.
For each class we count the last 30 facts audited. When 5 or more of them are wrong, the whole class is left out of every page until a fresh 30 have been audited with at most 4 wrong. The same fresh audit is needed before launch and whenever the way facts are checked changes.
| Class | Wrong | Audited | Audited between |
|---|---|---|---|
| statements adverse to the vendor | 1 | 30 | 9 Nov 2026 – 16 Nov 2026 |
| pricing | 2 | 30 | 9 Nov 2026 – 16 Nov 2026 |
| compliance | 0 | 30 | 19 Oct 2026 – 16 Nov 2026 |
| legal | 0 | 30 | 9 Nov 2026 – 16 Nov 2026 |
| subprocessors | 0 | 30 | 19 Oct 2026 – 16 Nov 2026 |
| sovereignty: legal entity | 0 | 30 | 9 Nov 2026 – 16 Nov 2026 |
| sovereignty: hosting location | 0 | 30 | 2 Nov 2026 – 16 Nov 2026 |
| sovereignty: hosting options | 0 | 30 | 8 Nov 2026 – 16 Nov 2026 |
| sovereignty: open source | 0 | 30 | 8 Nov 2026 – 16 Nov 2026 |
| sovereignty: data processing agreement | 0 | 30 | 8 Nov 2026 – 16 Nov 2026 |
| sovereignty: transfer impact assessment | 1 | 30 | 8 Nov 2026 – 16 Nov 2026 |
How the panel scores
Every criterion is scored from 0 to 10 against published anchors: the rubric says in words what a 0, a 3, a 5, an 8 and a 10 look like. The anchors are printed under every score on every product page.
Every judge is an AI persona with a name, a version and a published stance. Each one scores every criterion independently; only the weights differ. When two judges are 3 or more points apart on the same criterion, the page prints the disagreement instead of averaging it away.
A judge’s bottom line is the weighted mean of their criterion scores. The panel rating is the mean of every judge’s bottom line. Pricing transparency is skipped in that weighting when the vendor publishes no price at all — it is still reported, and the page says so. The same holds for any criterion a judge found no public information on: it reads “not rated — no public information” and does not count, because a page that is silent about a feature is not a product without it. A judge gives a bottom line only when the criteria they could rate carry at least 50 % of their weighting. The category median printed beside a rating is the median panel rating of every rated product in that category.
How to read the stars
Stars are the panel’s opinion on a published scale. They run from 0 to 5 in half steps and are the 0–10 score halved. 5 means the rubric’s top anchor is met on the evidence we hold; 0 means the bottom anchor. Each star resolves to a score against written anchors, and each reason cites the page it was read from.
Not rated. A product is only given panel stars when its page rests on at least 1 captured source page and at least 3 proven facts. Below that, the page shows “Not rated — too little public evidence” instead of stars, the panel’s reasoning stays readable, and the product is left out of the category median. Few stars mean a weak reading of the evidence; they never stand in for missing evidence.
Sovereignty. Sovereignty is computed from 6 sourced dimensions, listed below. It is shown as stars only when all 6 are proven on the vendor’s own pages. Otherwise the page says how many of the 6 are proven. A dimension we could not prove is left open — it is never counted as zero.
The “European sovereignty” criterion in a judge’s scores is something else: that is the panel’s opinion, scored against the rubric like every other criterion.
How sovereignty is scored
The sovereignty score runs from 0 to 10 and is built from 6 dimensions, each read from the vendor’s own pages and proven like any other fact. A dimension we could not prove adds nothing and is shown as not determined, never as a bad value.
| Dimension | Scores | Points |
|---|---|---|
| Legal entity | Registered in the EEA or Switzerland: 2; elsewhere in wider Europe: 1 | 2 |
| Hosting location | EU only: 4; EU by default: 2 | 4 |
| Hosting options | Self-hostable: 1; EU region selectable: 1 | 1 |
| Open source | Open source (copyleft): 1; Open source (permissive): 1 | 1 |
| Data processing agreement | Published, self-serve: 1 | 1 |
| Transfer impact assessment | Published: 1; Not needed, no transfer outside the EU/EEA: 1 | 1 |
The vendor’s words, our label. An AI model copies what the page states — the registered address, the place the data is hosted, the licence as named — word for word. The jurisdiction, the hosting location and the licence class are then derived from those words by our own code, with fixed rules, so the same words always get the same label:
- EU or EEA, plus Switzerland, counts as Europe. Data hosted in Norway, Iceland, Liechtenstein or Switzerland is hosted in Europe; a location that names only countries outside these, and not the EU or Europe, is outside the EU.
- A qualifier makes “EU only” into “EU by default”. “Mainly”, “by default”, “usually” and words like them (in English, German and French) mean some data may sit elsewhere, so the page earns EU by default, not EU only. So does a statement that names a country outside Europe next to a European one.
- The legal entity is placed by its registered address or register entry. A company in the EEA or Switzerland scores 2 points, one elsewhere in wider Europe (the UK, for example) scores 1.
- Licences fall into four classes. Copyleft (GPL, AGPL, MPL, EUPL and the like) and permissive (MIT, Apache, BSD and the like) are open source and score; source-available licences (Business Source, SSPL, Elastic and the like) and proprietary software do not.
- A transfer impact assessment counts only when it is the vendor’s own, for its own transfers of customer data outside the EU/EEA. A TIA feature the product sells to its customers is not one. A vendor that states it transfers no customer data outside the EU/EEA needs none, and scores the point.
Each dimension is audited on its own. In the error-rate audit above, every sovereignty dimension is its own class with its own window, so wrong readings of one dimension take only that dimension off the pages. A reading that counts against the vendor (hosting outside the EU, for example) is audited with every other adverse fact, in the adverse class.
Who owns a vendor, and which subprocessors can reach the data, are not part of the score. Ownership still informs the editorial provenance class.
Weights per judge
These are the weights in force, read from the same configuration the pipeline scores with. A higher number means that criterion moves that judge’s bottom line more.
Absence Management rubric v2
| Criterion | The Team Lead v1.0 | The Managing Director v1.0 | The Payroll Accountant v1.0 | The Data Protection Officer v1.0 | The HR IT Integrator v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Entitlements & German leave rules | 2.0 | 3.0 | 2.0 | 0.5 | 1.0 | 2.0 |
| Requests, approvals & team calendar | 3.0 | 2.0 | 0.5 | 1.0 | 1.5 | 1.0 |
| Sick leave, eAU & continued pay | 1.0 | 2.5 | 2.5 | 2.0 | 1.5 | 3.0 |
| Payroll handover, time tracking & API | 0.5 | 1.5 | 3.0 | 1.0 | 3.0 | 2.0 |
| Health data, access & works council | 1.0 | 1.0 | 1.0 | 3.0 | 1.5 | 2.0 |
| European sovereignty | 0.5 | 1.0 | 1.0 | 3.0 | 2.0 | 1.5 |
| Pricing transparency | 0.5 | 2.0 | 1.0 | 0.5 | 0.5 | 2.0 |
The judges and the criteria
The Team Lead · Approves leave for twelve people across two shifts and finds out about clashes too late. Wants requests and approvals on the phone, a named substitute on every request, minimum-staffing warnings before approval, and a team calendar that shows who is away without showing why.
The Managing Director · Runs a forty-person company in two federal states without an HR department and is liable when leave is calculated wrong. Wants part-time entitlements prorated correctly, the right public holidays per site, carry-over that lapses only after employees were told, and the eAU handled without a phone call to every health insurer.
The Payroll Accountant · Closes payroll in DATEV every month and corrects whatever arrived late. Wants absences exported with the right payroll codes, the eAU result attached to the sick day, the six-week continued-pay limit counted per illness, and past months locked once they are paid.
The Data Protection Officer · Treats every sick day as special-category data, because the law does. Asks who can see a reason or a certificate, how long absence records are kept and deleted, whether access is logged, where the data is hosted, and which subprocessors send the push notification that says someone is ill.
The HR IT Integrator · Wires the absence tool to payroll, time tracking, the identity provider and the calendar. Wants a documented API and webhooks, maintained connectors for the named German payroll systems rather than a CSV, SSO, and balances that agree with the time-tracking system on both sides.
The Skeptic · Knows "eAU supported" can mean a photo upload, "DATEV integration" can mean a CSV, and "GDPR-compliant" can mean every manager sees every diagnosis-adjacent note. Reads for who actually retrieves the certificate, which leave rules are computed rather than typed in, and whether the carry-over expiry notice exists at all.
Entitlements & German leave rules · Whether the tool computes leave the way German and Austrian law and contracts do: entitlements per contract and working-time model, part-time proration, carry-over and expiry with the required notice, public holidays per federal state, half days and hourly leave, and special leave types.
Requests, approvals & team calendar · The everyday flow: an employee requests leave on a phone, the right person approves, a substitute is named, and the team can plan around it — judged on configurable approval chains and on what colleagues are allowed to see.
Sick leave, eAU & continued pay · Sick notifications and the German electronic certificate of incapacity: whether the tool retrieves the eAU from the health insurer itself or through a named payroll system, how sick days are counted towards the six-week continued-pay (EFZG § 3) and BEM (SGB IX § 167) thresholds, and how child-sick days and certificates from private insurance are handled.
Payroll handover, time tracking & API · Getting absences into the payroll run with the right codes and keeping balances consistent with time tracking: exports or integrations for the payroll systems German companies use, time-account interaction, and an API.
Health data, access & works council · What the tool does with data that is health data in law (GDPR Art. 9): who can see a sickness reason or certificate, how long absence records are kept, whether access is logged, and whether the vendor documents what a works agreement on absence recording needs.
European sovereignty · Where absence and sickness data lives, who the contracting entity is, and who the subprocessors are — including email, push-notification and support providers. Independently sourced by the sovereignty pipeline; dimensions the evidence does not establish are unknown, not non-European.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per employee or per user, which features (eAU, payroll export, time tracking) sit in which tier, minimum users and the minimum term.
Accounting rubric v2
| Criterion | The Bookkeeper v1.0 | The Tax Adviser v1.0 | The Auditor v1.0 | The Founder v1.0 | The Integrator v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Bookkeeping core | 3.0 | 2.0 | 2.0 | 1.5 | 1.5 | 1.5 |
| GoBD, immutability & audit | 2.0 | 2.5 | 3.0 | 1.5 | 1.5 | 2.5 |
| Tax handling & filings | 2.0 | 2.5 | 2.0 | 2.5 | 1.5 | 1.5 |
| Receipts, banking & matching | 2.5 | 1.5 | 1.5 | 3.0 | 2.5 | 1.0 |
| Tax adviser handoff | 1.5 | 3.0 | 1.5 | 1.5 | 2.0 | 1.5 |
| European sovereignty | 0.5 | 0.5 | 1.5 | 0.5 | 1.0 | 1.5 |
| Pricing transparency | 1.0 | 1.0 | 0.5 | 2.0 | 1.0 | 2.0 |
The judges and the criteria
The Bookkeeper · Posts the month and closes it. Wants a real ledger with SKR03/04, recurring entries, cost centres and a close that locks. Judges receipt capture by how many exceptions are left after the automation, not by the demo video.
The Tax Adviser · Closes the year for forty clients and needs the books to arrive in a form DATEV accepts, receipts attached. Reads "export to CSV for your Steuerberater" as an admission that nobody asked one. Wants scoped access and a clean period handover.
The Auditor · Arrives with a Betriebsprüfung and asks for the data export and the Verfahrensdokumentation. Wants postings that cannot be altered after the fact, corrections booked as reversals, a complete change history, and retention that survives the full statutory period.
The Founder · Runs a twelve-person company and does the books on a Sunday. Wants bank feeds that match themselves, invoices out in a minute, and the VAT return submitted without learning ELSTER. Will pay for the hour saved, and notices when the headline price was not the invoice.
The Integrator · Connects the books to the shop, the payment provider and the payroll system. Wants a documented API, e-invoicing both directions, and imports that reconcile rather than duplicate. Reads a Zapier logo as an outsourced integration.
The Skeptic · Has seen "GoBD-konform" printed on pages that offer no documentation to back it, and wants the feature that makes it true. Also reads for the booking limit, the tier where DATEV export appears, and what an extra bank account costs.
Bookkeeping core · Double-entry, the chart of accounts (SKR03/SKR04), postings, journals, opening balances and period closing — the ledger underneath the pretty screens.
GoBD, immutability & audit · Whether the record survives a tax audit: unalterable postings, complete change history, retention across the statutory period, and a Verfahrensdokumentation the vendor actually supplies.
Tax handling & filings · VAT logic and the filings that follow: UStVA, ELSTER submission, EÜR or Bilanz, OSS for cross-border sales, and reverse-charge handling.
Receipts, banking & matching · How evidence and money get into the ledger: bank feeds, receipt capture, OCR, matching rules, and whether the digital receipt is legally sufficient on its own.
Tax adviser handoff · How the books reach the Steuerberater — DATEV above all — and whether the adviser can work in the system rather than around it.
European sovereignty · Where the books live and who could be compelled to produce them — plus, uniquely here, whether statutory retention survives leaving the vendor. Independently sourced by the sovereignty pipeline. Dimensions not proven either way are unknown, not non-European.
Pricing transparency · Whether a business can compute the real annual invoice — including the bookings, users, bank accounts and adviser access they actually need — from public pages alone.
AI Agents & Assistants rubric v1
| Criterion | The Head of IT v1.0 | The Data Protection Officer v1.0 | The Automation Lead v1.0 | The Customer-Service Director v1.0 | The Works Council Member v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Data use, training & retention | 2.0 | 3.0 | 1.0 | 2.0 | 2.5 | 2.5 |
| Models & processing location | 2.0 | 3.0 | 1.5 | 1.5 | 1.5 | 2.5 |
| Admin, identity & access controls | 3.0 | 2.0 | 1.5 | 1.5 | 2.5 | 2.0 |
| Integrations, connectors & knowledge | 2.5 | 1.0 | 3.0 | 2.5 | 0.5 | 1.5 |
| Agent capabilities & guardrails | 1.5 | 1.0 | 3.0 | 3.0 | 1.5 | 2.5 |
| European sovereignty | 1.5 | 3.0 | 1.0 | 1.5 | 2.0 | 2.0 |
| Pricing transparency | 1.5 | 0.5 | 1.5 | 2.0 | 0.5 | 2.0 |
The judges and the criteria
The Head of IT · Has to roll an AI assistant out to eight hundred staff without a second shadow-IT wave. Wants SSO and SCIM, groups that decide who gets which model, agent and connector, answers that respect SharePoint permissions, audit logs for the SIEM, and a deployment option that is not "trust us".
The Data Protection Officer · Signs the DPA and gets asked where a prompt goes. Wants every model provider named as a subprocessor with its region, training excluded for all of them, retention the company controls, and an EU-only switch that also covers agents and connectors — not just the chat window.
The Automation Lead · Builds the agents that file tickets, draft offers and chase approvals across the ERP, CRM and wiki. Wants tools and actions with scoped permissions, MCP and an API, approval steps before anything is sent, run logs, and a way to test an agent before the whole company uses it.
The Customer-Service Director · Runs a contact centre with forty agents and wants half the routine calls and chats answered by an AI agent. Wants handover to a human with the full context, actions in the order and ticket systems, evaluation before go-live, and a price per conversation the CFO can forecast.
The Works Council Member · Has a co-determination right the moment a tool can monitor staff, and an AI assistant logs every prompt. Wants usage reports that can be aggregated or pseudonymised, prompt logging rules set out in writing, a human approving what agents do to colleagues, and no training on staff input.
The Skeptic · Has read "European AI" on a wrapper that sends every prompt to a US model, "agents" that are saved prompts, and "we never train on your data" with no word on the model provider behind it. Asks which model answers, where it runs, what it may do unsupervised, and what a thousand seats cost.
Data use, training & retention · What happens to prompts, uploaded files, connected data and outputs: whether any of it trains a model (the vendor's or a model provider's), how long it is kept and where logs live, whether zero-retention is available, and whether a data processing agreement covers it.
Models & processing location · Which models sit behind the product and who runs them, where inference and storage happen, whether the customer can pin processing to the EU, choose or exclude model providers, bring its own model or key, or run the product in its own cloud or on premises.
Admin, identity & access controls · What the IT department controls: SSO and SCIM provisioning, roles and groups, which models, agents and connectors each group may use, retrieval that respects the permissions of the source system, audit logs, usage reporting, and policies such as data-loss prevention — and whether reporting on staff use is scoped and documented.
Integrations, connectors & knowledge · How the product reaches company knowledge and systems: connectors to file stores, wikis, mail, CRM, ticketing and ERP, how fast and how completely they sync, the API, support for open protocols such as MCP, and how the assistant cites the sources it answers from.
Agent capabilities & guardrails · What an agent can actually do and where it stops: multi-step tasks, tool use and actions in other systems, scheduling and triggers, human approval before consequential actions, run logs, evaluation and testing before release, and the limits the vendor states rather than hides.
European sovereignty · Who the contracting entity and the parent company are, where customer data is hosted, and who the subprocessors are — model providers above all, then hosting, search, telephony and email. Independently sourced by the sovereignty pipeline; for an AI product the model provider is a subprocessor, so a European interface over a non-European model counts as such.
Pricing transparency · Whether a company can compute the real annual cost from public pages alone: price per seat, per agent, per conversation or per usage unit, what is included in each tier, usage limits and overage, which models, connectors or agents cost extra, minimum seats and term.
AI Meeting Assistants & Notetakers rubric v1
| Criterion | The Management Consultant v1.0 | The Sales Team Lead v1.0 | The Works Council Chair v1.0 | The Data Protection Officer v1.0 | The IT Lead v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Recording, transcription & languages | 3.0 | 2.5 | 1.0 | 1.0 | 2.0 | 2.0 |
| Summaries, action items & meeting knowledge | 3.0 | 2.5 | 1.0 | 1.0 | 1.5 | 2.0 |
| Integrations, API & workflow | 1.5 | 3.0 | 0.5 | 1.0 | 2.5 | 1.0 |
| Consent, participant rights & works council | 2.0 | 1.5 | 3.0 | 2.5 | 2.0 | 2.5 |
| Retention, AI training & administration | 2.0 | 1.0 | 2.5 | 3.0 | 3.0 | 2.5 |
| European sovereignty | 1.5 | 1.0 | 2.5 | 3.0 | 1.5 | 2.0 |
| Pricing transparency | 1.5 | 1.5 | 0.5 | 0.5 | 1.5 | 2.0 |
The judges and the criteria
The Management Consultant · Partner at a twelve-person management consultancy in Munich with six client calls a day, half in German, half in English, and workshops in the client's meeting room. Writes the minutes at night and wants that to stop. Wants accurate German transcripts with the right names, minutes by meeting type with decisions and action items, capture of in-person workshops without a laptop on the table, and a promise in writing that client conversations train nobody's model.
The Sales Team Lead · Leads eight account executives at a software vendor for the German Mittelstand. Discovery calls run on Teams and Zoom, and the CRM is only as good as the notes someone found time to type. Does not want a coaching platform that scores the team: wants the call summary, next steps and the fields that matter written into HubSpot after every call, a follow-up email draft, and prospects told politely that the call is recorded.
The Works Council Chair · Chairs the works council of a machine builder with 2,300 employees in Baden-Württemberg. Management wants a notetaker in every Teams meeting; the council has to agree to it under § 87 BetrVG first. Wants to know who is told that a recording runs and who can say no, whether talk time or engagement scores per person exist and can be switched off for good, how long recordings are kept, and material the vendor provides for a works agreement.
The Data Protection Officer · Data protection officer of a private bank in Frankfurt that falls under DORA. Has to write the data protection impact assessment before the first recording. Reads the subprocessor list before the feature page, because the language model that reads the transcript is a processor too, and wants its name and region, contractual exclusion from training, retention and deletion by policy, voice profiles explained, and a DPA that matches what the security page claims.
The IT Lead · Head of IT at a 450-person engineering services firm on Microsoft 365, where a dozen employees already signed up for free notetakers with their work address. Wants one tool for everyone instead: single sign-on and SCIM, admin policies for when the assistant joins and what may be shared outside the company, retention set centrally, audit logs, Teams and SharePoint working properly, and a seat price that holds at four hundred users.
The Skeptic · Has seen "99% accuracy in 100 languages" turn a German meeting into English nonsense, a bot that joined a meeting its owner never attended and mailed the summary to every guest, and an action item no one in the room had agreed to. Asks which model wrote the summary and where it runs, whether each statement can be traced to the transcript, who told the external participants, what "we do not train on your data" covers in the DPA — and how the archive leaves.
Recording, transcription & languages · How the conversation gets in and how faithfully it is written down: a bot that joins Zoom, Microsoft Teams, Google Meet and Webex, botless capture from a desktop or mobile app, in-person meetings and phone calls, file upload, live transcription, speaker identification and names, the languages supported with German stated, meetings that switch language, custom vocabulary for names and jargon, timestamps linked to the recording, and editing of the transcript.
Summaries, action items & meeting knowledge · What the tool makes of the transcript: summaries and minutes by meeting type with editable templates, decisions and action items with owners and due dates, summaries in the meeting's language or a chosen one, follow-up emails, clips and highlights, search across all meetings, questions answered over the archive with citations back to the transcript passage, shared team folders or channels, and the minutes exported to Word, PDF or a wiki.
Integrations, API & workflow · How the notes reach the place where work happens: calendar connection with rules for which meetings are recorded, CRM fields filled from the call (HubSpot, Salesforce, Pipedrive, Microsoft Dynamics), project and task tools, Slack and Microsoft Teams channels, Notion, Confluence and SharePoint, Zapier, Make or n8n, a documented REST API and webhooks, an MCP server for AI assistants, and browser extensions and native apps.
Consent, participant rights & works council · Whether every person in the meeting knows and can decide, and whether the tool can be introduced under German co-determination: a recording notice to all participants including external guests, consent or opt-out before the recording starts, a visible bot or a stated notice for botless capture, rules for when the assistant joins automatically, stopping and deleting a recording on request, per-person analytics (talk time, sentiment, engagement scores) off by default or switchable per organisation, material or a template for a works agreement (Betriebsvereinbarung, § 87 (1) no. 6 BetrVG), and support for a data protection impact assessment.
Retention, AI training & administration · What the employer can govern: retention periods and automatic deletion of recordings, transcripts and summaries, whether audio and video can be discarded after transcription, sharing defaults and link permissions, customer content excluded from model training by contract, the AI and transcription providers named with their region and their own retention, encryption, single sign-on (SAML), SCIM, roles and workspaces, admin policies on auto-recording and sharing, audit logs, export of the whole archive, and security certifications such as ISO 27001 and SOC 2.
European sovereignty · Who the contracting entity and the parent company are, where recordings, transcripts, summaries, voice profiles and account data are stored and processed, which language model and transcription providers read them and where, and who the other subprocessors are (hosting, email, support, analytics and payment tools). Independently sourced by the sovereignty pipeline. A conferencing platform outside Europe that the customer already uses is part of the meeting, not counted against the notetaker; where the notetaker stores and processes the conversation is.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per seat and tier, what counts as a seat (every invited user, only recording users), transcription minutes or credits included, storage limits, which features (CRM integrations, API access, SSO, custom retention, EU hosting, AI credits) cost extra, the free tier and its limits, monthly versus annual billing, minimum seats and VAT.
Appointment Scheduling rubric v1
| Criterion | The Practice Owner v1.0 | The Salon Owner v1.0 | The Sales Team Lead v1.0 | The Independent Consultant v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Booking page & client experience | 2.5 | 2.5 | 2.0 | 3.0 | 1.0 | 1.5 |
| Calendar sync & availability rules | 2.0 | 1.5 | 2.5 | 2.5 | 2.0 | 2.0 |
| Team, staff & location scheduling | 2.0 | 2.5 | 3.0 | 0.5 | 2.0 | 1.5 |
| Reminders, payments & no-show protection | 3.0 | 3.0 | 1.0 | 2.5 | 2.0 | 2.5 |
| Integrations, API & data export | 1.0 | 1.0 | 3.0 | 1.5 | 2.5 | 2.5 |
| European sovereignty | 2.5 | 1.0 | 1.0 | 1.0 | 3.0 | 2.5 |
| Pricing transparency | 1.0 | 2.0 | 1.0 | 2.0 | 0.5 | 2.0 |
The judges and the criteria
The Practice Owner · Runs a physiotherapy practice with six therapists, two treatment rooms that must not be double-booked, and a front desk that spends its mornings on the phone. Wants patients to book and reschedule online, SMS reminders that cut the no-shows, rooms and therapists checked together, and patient data that stays in Europe under a data processing agreement the practice can show.
The Salon Owner · Owns two hair and beauty salons with eleven stylists and a Saturday that is booked out by Wednesday. Wants every service with its own duration and price on one booking page, clients who pick their stylist, a deposit for colour appointments, a fee when someone does not show, and a monthly bill that does not grow with every chair.
The Sales Team Lead · Leads fourteen account executives in three time zones and gets every demo request from the website. Wants inbound demos routed by company size and region, round-robin that is fair and can be checked, two-way sync with Outlook and Google so nobody is double-booked, a video link in every invite, and the booking written into the CRM before the call starts.
The Independent Consultant · Sells coaching sessions and workshop days on her own and books clients from Germany, Austria and Switzerland. Wants a booking page that looks like her own website, payment taken when the session is booked, a buffer after every call, her private calendar respected, reminders she never has to send herself, and a price that makes sense for one person.
The Data Protection Officer · Signs off booking tools for a group of medical and legal practices, where an appointment alone reveals who is a patient or a client. Wants the contracting entity and hosting named, every subprocessor listed down to the SMS gateway and the email service, calendar access limited to what booking needs, and bookings and customer records that can be exported and deleted on request.
The Skeptic · Has seen "free forever" booking pages that put the vendor's logo in front of every client, SMS reminders that turn out to be credits sold separately, round-robin and payments locked in the top tier, and calendar sync that reads far more than free and busy. Reads the price list for what scales per seat, the subprocessor list for where the reminders are sent from, and asks how the bookings get out again.
Booking page & client experience · What the person booking sees and can do: a booking page with the services or meeting types on offer, their durations and prices, booking questions, an embed or widget for the business's own website, time zones and languages, group or class bookings, and links to reschedule or cancel without calling.
Calendar sync & availability rules · How the product knows when someone is free: two-way sync with Google, Microsoft 365 and Outlook, iCloud or CalDAV, conflict checks across several calendars, working hours and exceptions, buffers, minimum notice and booking windows, daily limits, and rooms or equipment that must be free as well.
Team, staff & location scheduling · How bookings are shared out across more than one person: staff profiles and the services each offers, round-robin and collective (all-hands) meetings, routing forms that send a booking to the right person, several locations, roles and permissions for admins and staff, and single sign-on for larger teams.
Reminders, payments & no-show protection · How the product keeps a booked slot from turning into an empty one: confirmations and reminders by email and SMS, payment or deposit at booking, cancellation and late-cancellation policies, fees for no-shows, waiting lists that refill cancelled slots, and follow-ups after the appointment.
Integrations, API & data export · What the product connects to and how the data gets out again: video-meeting links (Zoom, Teams, Google Meet), CRM and marketing tools, automation platforms (Zapier, Make), a documented API and webhooks, website and app-store integrations, and an export of bookings and customer records.
European sovereignty · Who the contracting entity and the parent company are, where booking and customer data is hosted, and who the subprocessors are: hosting, the SMS gateway, email delivery, payment providers, video tools and analytics. Independently sourced by the sovereignty pipeline; booking data names who sees a doctor, a lawyer or a therapist and when, so the whole chain counts, not only the database.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user, staff member, location or calendar, what the free plan covers, which features (SMS reminders, payments, round-robin, SSO, branding removal) sit in which tier, the cost of SMS credits and payment fees, setup and minimum term.
Billing & Invoicing rubric v1
| Criterion | The SaaS Founder v1.0 | The Finance Lead v1.0 | The Billing Engineer v1.0 | The Service-Business Owner v1.0 | The Tax Adviser v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Plans, pricing models & subscription lifecycle | 3.0 | 1.5 | 3.0 | 2.0 | 0.5 | 1.5 |
| Invoices & e-invoicing compliance | 1.5 | 2.5 | 1.0 | 3.0 | 3.0 | 2.0 |
| Cross-border VAT & tax handling | 2.0 | 2.0 | 1.5 | 1.0 | 3.0 | 2.0 |
| Payment collection, dunning & portability | 2.5 | 2.0 | 2.5 | 2.5 | 1.0 | 2.5 |
| Revenue reporting & accounting handoff | 1.5 | 3.0 | 2.5 | 2.0 | 2.5 | 2.0 |
| European sovereignty | 1.0 | 1.5 | 1.5 | 2.0 | 2.0 | 2.5 |
| Pricing transparency | 2.0 | 1.0 | 0.5 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The SaaS Founder · Runs a twelve-person SaaS that sells to companies in nine EU countries and is about to add a usage-based tier. Wants plans, trials and price changes without a developer sprint, reverse charge that is right without thinking about it, failed cards retried before they turn into churn, and a billing bill that does not grow faster than revenue.
The Finance Lead · Closes the month for a software company with eight million euros of recurring revenue. Wants MRR that reconciles with the ledger, deferred revenue scheduled rather than estimated in a spreadsheet, a journal or DATEV export the accountants can book without retyping, and dunning that stops before it reaches a key account.
The Billing Engineer · Wires billing into the product and gets paged when a webhook goes missing. Wants a documented API for usage events, idempotent webhooks, entitlements the app can read, a sandbox that behaves like production, and a migration path that moves subscriptions and payment tokens out again if the company outgrows the tool.
The Service-Business Owner · Runs an IT service company with two hundred maintenance contracts, hosting packages and monthly retainers, all billed to German businesses. Wants contract terms and price increases handled by the system, SEPA direct debit with mandates, e-invoices that public-sector customers accept, a DATEV export for the tax adviser, and customer data kept in Europe.
The Tax Adviser · Advises software and subscription businesses and sees what their billing tools get wrong at the year-end audit. Wants sequential numbering and credit notes instead of edited invoices, XRechnung and ZUGFeRD now that the B2B e-invoice is mandatory, VAT IDs checked before reverse charge is applied, and a merchant of record that says in writing which tax it owes.
The Skeptic · Has seen "automated recurring revenue" turn into a tool that takes a percentage of every euro billed and keeps the payment tokens when the customer leaves. Reads "e-invoicing ready" that means a PDF, "global tax compliance" with no word on who is liable, merchant-of-record terms that let the vendor change fees at will, and subprocessor lists that stop at the hosting provider — and asks what leaving would cost.
Plans, pricing models & subscription lifecycle · How the product models what is sold and to whom: plans, add-ons and price points, trials, upgrades and downgrades with proration, usage-based and seat-based pricing, contract terms and renewals, quotes, and a self-service portal where the customer changes or cancels their own subscription.
Invoices & e-invoicing compliance · Whether the invoices the product issues are legally valid where the customer is: mandatory invoice content, sequential numbering, credit notes and cancellations instead of edits, retention and archiving to GoBD, and structured e-invoices (XRechnung, ZUGFeRD/Factur-X, Peppol) for business customers and public bodies.
Cross-border VAT & tax handling · How the product gets tax right when the seller sells across borders: VAT rates per country and product type, reverse charge for business customers with VAT ID validation (VIES), the EU One-Stop-Shop, US sales tax — or, for a merchant of record, which tax liability it takes on in its contract and which it leaves with the seller.
Payment collection, dunning & portability · How invoices turn into money: which payment providers and methods the product works with, SEPA direct-debit mandates, automatic retries and dunning sequences, payment reconciliation, collections handover — and whether the seller can move subscriptions and stored payment details to another provider.
Revenue reporting & accounting handoff · What finance gets out of billing: MRR, ARR, churn and cohort reporting, revenue recognition and deferred revenue, the export or sync to the accounting system and to DATEV, CRM and data-warehouse integrations, an API and webhooks, and a complete export of customer and subscription data.
European sovereignty · Who the contracting entity and the parent company are, where customer, invoice and payment data are hosted, and who the subprocessors are (hosting, payment providers, tax engines, email delivery). Independently sourced by the sovereignty pipeline; billing data is personal and financial at once, so the whole chain counts, not only the database.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: platform fee, percentage of billed revenue or per-invoice fees, which modules (revenue recognition, e-invoicing, tax, extra gateways) cost extra, overage above a revenue band, setup and minimum term, and the merchant-of-record fee where it applies.
Business Email & Office Suites rubric v1
| Criterion | The Small Firm Owner v1.0 | The IT Administrator v1.0 | The Public Sector IT Lead v1.0 | The IT Service Provider v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Mail, domains & deliverability | 2.5 | 2.5 | 2.0 | 2.5 | 1.5 | 2.0 |
| Calendar, contacts & office apps | 2.5 | 2.5 | 2.5 | 2.0 | 1.0 | 1.5 |
| Security, encryption & compliance archiving | 2.0 | 2.0 | 2.5 | 2.0 | 3.0 | 2.5 |
| Administration, identity & partner management | 1.0 | 3.0 | 2.5 | 3.0 | 2.0 | 1.5 |
| Migration, open standards & exit | 2.0 | 2.5 | 2.5 | 2.5 | 2.0 | 3.0 |
| European sovereignty | 1.5 | 1.5 | 3.0 | 1.5 | 3.0 | 2.5 |
| Pricing transparency | 2.0 | 1.0 | 1.0 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The Small Firm Owner · Runs a tax and accounting firm of twelve in Lower Saxony. Every member of staff lives in Outlook, the shared "kanzlei@" mailbox is the busiest address in the office, and the meeting room is booked by shouting across the corridor. Wants mail on the firm's own domain that arrives, a shared calendar and address book on every phone, a move from the old provider that does not lose a single client thread, and a per-user price that is still the price in the second year.
The IT Administrator · IT administrator at a machine builder in Baden-Württemberg with three hundred mailboxes, an on-premises Exchange that reaches end of support, and Active Directory as the source of every account. Wants Outlook to keep working without a plug-in nobody maintains, shared mailboxes and room booking, single sign-on and directory sync, mobile devices that can be wiped, an API for provisioning, and a migration that moves calendars and permissions, not only mail.
The Public Sector IT Lead · Head of IT at a district administration in Bavaria with eleven hundred staff, told by the council to leave Microsoft within three years. Has read what Schleswig-Holstein did and what it cost. Needs mail, calendars and documents that a whole administration can work in, open formats and open source where possible, BSI C5 or ISO 27001 on paper, a provider whose owners answer to European law only, and an exit plan before the contract is signed.
The IT Service Provider · Runs a six-person IT service company in Austria that looks after mail for forty client firms, from a two-person architect's office to a hotel group. Spends Mondays on mails that landed in spam and phones that stopped syncing. Wants one partner console for every client, DKIM and DMARC set up without a ticket, migrations it can run itself, support that answers within the hour, and margins it can calculate before it quotes.
The Data Protection Officer · Data protection officer for a group of nine medical practices in North Rhine-Westphalia, where a referral letter sent by mail is patient data under professional secrecy. Reads the subprocessor list and the transparency report before the feature page, asks who at the provider can open a mailbox and under which law, and wants encryption the practices can actually use with outside doctors, archiving that satisfies the tax office, and a data processing agreement that names every server.
The Skeptic · Has seen "hosted in Germany" from a provider whose spam filter and support desk sit in the United States, "Exchange-compatible" that meant IMAP with a calendar plug-in, and a first-year price of one euro that became seven. Asks which protocols Outlook really uses, whether the archive would survive a tax audit, what the certification actually covers — and how ten years of mail, calendars and contacts would leave.
Mail, domains & deliverability · How well the mailbox itself works: custom domains and their DNS set-up, aliases, catch-all, shared and functional mailboxes, distribution lists, mailbox and attachment size limits, IMAP, POP3, SMTP and Exchange ActiveSync or MAPI for Outlook, web and mobile apps, spam and malware filtering, SPF, DKIM, DMARC and MTA-STS, out-of-office and server-side rules, send limits, and the delivery reputation of the sending infrastructure. A self-hosted groupware is judged on the mail server it ships; a suite whose mail app is only a client for another server scores at the level of that client.
Calendar, contacts & office apps · What the office plans and writes with: shared and team calendars, free/busy lookup, meeting invitations across providers, room and resource booking, shared address books and a company directory, CalDAV and CardDAV or ActiveSync for phones, Outlook calendar sync, tasks, online office documents with co-editing, file storage that comes with the suite, video meetings and chat inside the bundle, and the desktop and mobile apps.
Security, encryption & compliance archiving · How mail and documents are protected and kept: TLS enforced in transit, encryption at rest, end-to-end encryption or S/MIME and PGP, who at the provider can read a mailbox, two-factor authentication and passkeys, phishing, malware and account-takeover protection, audit-proof archiving that meets GoBD, retention policies and legal hold, eDiscovery, backups and restore of deleted mail, a transparency report on authority requests, and certifications (ISO 27001, BSI C5, SOC 2) with their scope.
Administration, identity & partner management · How an IT team or an IT service provider runs it: an admin console for users, groups, mailboxes and domains, admin roles, single sign-on (SAML or OpenID Connect), sync with Active Directory, Entra ID or LDAP, SCIM provisioning, mobile device policies and remote wipe, audit logs of admin and user actions, usage reports, a documented API for provisioning, multi-tenant or reseller accounts for partners managing several customers, and the support channels and response times per plan.
Migration, open standards & exit · How the organisation gets in and out: migration from Exchange, Microsoft 365, Google Workspace or another IMAP provider with a documented tool or service, mail, calendars and contacts carried over, coexistence during a move, standard protocols (IMAP, CalDAV, CardDAV, JMAP, open document formats) rather than proprietary ones, export of a mailbox and of the whole organisation in standard formats (mbox, EML, PST, ICS, vCard), open-source code or a self-hosted edition, what happens to data when the contract ends, and how domains and DNS are handed back.
European sovereignty · Who the contracting entity and the parent company are, where mailboxes, calendars, contacts, documents and backups are stored and processed, who at the provider or its subprocessors can access them, and who the subprocessors are (data centres, spam filtering, support, payment, AI features). Independently sourced by the sovereignty pipeline. An EU data region offered by a non-EU parent is part of the chain, not the whole of it. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user or mailbox per tier, storage per user, what shared mailboxes, aliases and extra domains cost, which features (archiving, office apps, SSO, advanced security, more storage) cost extra, the first-year discount and the regular price after it, minimum users and term, monthly versus annual billing, and VAT.
Business Instant Messaging rubric v2
| Criterion | The Team Lead v1.0 | The Security Officer v1.0 | The Works Council Advocate v1.0 | The Compliance Counsel v1.0 | The Platform Engineer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Channels, threads & search | 3.0 | 1.0 | 1.0 | 1.0 | 1.5 | 1.5 |
| Encryption & access control | 1.0 | 3.0 | 1.5 | 1.0 | 1.5 | 1.5 |
| Retention, discovery & co-determination | 1.0 | 1.5 | 3.0 | 3.0 | 1.0 | 1.5 |
| Deployment & data custody | 0.5 | 2.0 | 1.5 | 1.5 | 3.0 | 1.5 |
| Integrations & extensibility | 2.5 | 0.5 | 0.5 | 0.5 | 2.5 | 1.0 |
| European sovereignty | 0.5 | 2.5 | 2.5 | 2.0 | 1.5 | 1.5 |
| Pricing transparency | 1.5 | 0.5 | 0.5 | 1.0 | 1.0 | 2.0 |
The judges and the criteria
The Team Lead · Runs a distributed team and needs the tool people actually open. Wants threads that stay readable, search that finds last spring's decision, and channels that can be tidied without losing history. Unmoved by feature lists that do not survive a busy Tuesday.
The Security Officer · Assumes the archive will one day be read by someone it was not meant for. Wants end-to-end encryption that ordinary users survive, device verification, sessions an admin can revoke, and a plain statement of what the vendor cannot decrypt.
The Works Council Advocate · Knows that a chat log is a record of who spoke to whom at what hour. Wants presence a person controls, no individual activity scoring anywhere, retention that deletes rather than hides, and analytics that can be switched off across the organisation.
The Compliance Counsel · Will one day have to produce this archive, edits and deletions included, to a regulator or a court. Wants legal hold, an export a lawyer can work from, retention per channel, and an audit trail that survives the admin who made the change.
The Platform Engineer · Would rather run it than rent it, and wants to know whether that is a supported deployment or a hobby build. Cares about open protocols, federation, a plugin system with real permissions, and an upgrade path that does not orphan the customisations.
The Skeptic · Reads for the message-history cap, the tier where SSO appears, and what "unlimited" excludes. Has seen "end-to-end encrypted" mean direct messages only, on request, with search disabled — and wants that sentence found rather than assumed.
Channels, threads & search · The daily surface: channel model, threading, mentions, files, and whether search can find a decision made eighteen months ago.
Encryption & access control · What is encrypted and against whom, plus who can reach which room. Judged on documented mechanism, since "encrypted" in this category usually means the vendor holds the keys.
Retention, discovery & co-determination · The archive as a legal object: retention policies, export for discovery, audit, and the monitoring features a works council will ask to have switched off under BetrVG §87(1) no. 6.
Deployment & data custody · Whether the customer can hold their own archive: self-hosting, private cloud, open source, federation, and what an exit actually looks like.
Integrations & extensibility · Bots, webhooks, app framework, identity — whether the chat becomes the place work is noticed, and whether that is buildable without a partner agreement.
European sovereignty · Where the archive and its metadata live, who the contracting entity is, which subprocessors touch it. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.
Pricing transparency · Whether a buyer can compute the annual invoice for their headcount — including the retention, compliance and guest features they actually need — from public pages alone.
Business Intelligence & Dashboards rubric v1
| Criterion | The Finance Controller v1.0 | The Managing Director v1.0 | The Data Analyst v1.0 | The IT Administrator v1.0 | The SaaS Product Lead v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Data sources, connectors & refresh | 3.0 | 2.5 | 2.5 | 1.5 | 2.0 | 1.5 |
| Dashboards, charts & interactivity | 2.5 | 3.0 | 1.5 | 1.0 | 2.0 | 1.0 |
| Self-service analysis & shared metrics | 2.0 | 1.5 | 3.0 | 1.0 | 1.0 | 2.0 |
| Sharing, scheduled reports & embedding | 2.0 | 2.0 | 1.5 | 1.5 | 3.0 | 1.0 |
| Access control, administration & portability | 1.5 | 1.0 | 2.5 | 3.0 | 2.5 | 3.0 |
| European sovereignty | 2.0 | 1.5 | 1.0 | 3.0 | 1.5 | 2.5 |
| Pricing transparency | 1.5 | 2.0 | 1.0 | 1.5 | 2.0 | 2.0 |
The judges and the criteria
The Finance Controller · Head of controlling at a 250-person machine builder in Baden-Württemberg. Closes the month from DATEV, the ERP, the CRM and a dozen Excel files that colleagues still mail around, and spends two days a month copying numbers into the management report. Wants the sources connected and refreshed on a schedule, one definition of contribution margin on every page, a report that prints cleanly for the advisory board, and data that stays where the auditors expect it.
The Managing Director · Runs a 40-person service company with HubSpot, an online accounting tool, a help desk and a project management app, and no one whose job is data. Wants revenue, pipeline, utilisation and open tickets on one screen in the office and on their phone, set up in an afternoon from ready-made connectors, a weekly summary in the inbox on Monday morning, and a price that does not double when the whole team wants to look.
The Data Analyst · The first data hire at a Hamburg e-commerce scale-up, with orders, marketing spend and customer data landing in a PostgreSQL warehouse every night. Answers the same question three times a week because every department computes revenue differently. Wants a SQL editor and a query builder for colleagues, metrics defined once in a model that lives in Git, natural-language questions that show the query they ran, and a way out that does not mean rebuilding every dashboard.
The IT Administrator · IT lead at a mid-sized healthcare supplier whose reports touch customer, pricing and employee data. Is asked to approve a BI tool after a department has already started a trial. Reads where extracts and caches are stored, whether the tool reaches the ERP database through a gateway or wants it opened to the internet, whether sales sees only its own region, and whether single sign-on and an audit log come with the plan or behind a sales call. Prefers an edition they can run themselves.
The SaaS Product Lead · Product lead at a Vienna software company selling fleet management to 600 business customers, each of whom asks for reports the team keeps building by hand. Wants dashboards embedded in the product under its own brand, every customer seeing only their own rows, customers building their own views without a ticket, and an embedding licence whose cost they can put into the product's price before signing.
The Skeptic · Has seen "connect any data source" on a tool with eight connectors and a CSV upload, "self-service" that ends with every department defining revenue its own way, "free viewers" that need a paid licence to open a shared link, and "AI insights" that never show the query. Asks where the extracts are stored, whether dashboards and definitions can be exported in a format another tool reads — and what leaving would cost.
Data sources, connectors & refresh · Which data the product can reach and how it stays current: native connectors to databases and warehouses (PostgreSQL, MySQL, SQL Server, BigQuery, Snowflake), to business applications (accounting, ERP, CRM, shop, help desk, ad platforms) and to files and spreadsheets (Excel, CSV, Google Sheets), live queries versus imported extracts, scheduled and incremental refresh with its minimum interval, joining data from several sources, light data preparation, access to databases behind a firewall (gateway, SSH tunnel, IP allow-list), and a generic REST or custom connector for what is not listed.
Dashboards, charts & interactivity · What can be built and how readers use it: the range of chart types, tables and pivot tables, maps, KPI tiles with targets and comparisons, dashboard layout, filters and date controls that apply across a dashboard, drill-down and drill-through, cross-filtering by clicking a chart, templates for common sources, mobile and TV display, theming to the company's design, number formatting and localisation (decimal comma, currencies, German date formats), and accessibility of the result.
Self-service analysis & shared metrics · Whether people outside the data team can answer their own questions and whether everyone gets the same answer: a visual query builder, a SQL editor for analysts, calculated fields and formulas, a semantic layer or data model where metrics such as revenue or churn are defined once and reused, metric definitions under version control (Git, dbt integration), questions in natural language with the generated query shown, forecasting and anomaly detection with the method stated, and notebooks or Python for deeper analysis.
Sharing, scheduled reports & embedding · How results reach the people who need them: sharing a dashboard with colleagues and with external parties, public or password-protected links, scheduled reports by email or chat (Slack, Microsoft Teams) as PDF, image or data, threshold alerts, comments and annotations, export to PDF, PowerPoint and Excel, embedding dashboards in an intranet, a website or the company's own software product, white-label options, and per-customer data separation for embedded use.
Access control, administration & portability · What a company needs before it gives the tool to everyone, and what leaving would cost: roles and folder or workspace permissions, row-level and column-level security, single sign-on (SAML, OpenID Connect) and user provisioning (SCIM), audit logs and usage analytics, content certification and lifecycle, environments for development and production, a public REST API for administration and content, export of dashboards and definitions in a reusable format, open-source code, and a self-hosted or on-premise edition the customer runs on its own servers.
European sovereignty · Who the contracting entity and the parent company are, where the connected business data is queried, cached, extracted and stored, and who the subprocessors are (hosting, query engine, AI model providers, email delivery of reports, support and payment tools). Independently sourced by the sovereignty pipeline; a BI tool reads revenue, customer and employee data from many systems, so every place a copy or cache lands counts, not only the account database. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per creator or editor seat and whether viewers are free or paid, capacity or usage pricing (rows, refreshes, queries, AI credits), which features (row-level security, SSO, embedding, API, more connectors, faster refresh) sit behind a higher tier or "contact sales", the price of embedding for external users, the self-hosted edition's licence, the free tier and its limits, minimum term and setup.
Business VPN & Zero Trust Access rubric v1
| Criterion | The IT Lead v1.0 | The DevOps Engineer v1.0 | The MSP Technician v1.0 | The Operations Manager v1.0 | The Information Security Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Access model & connectivity | 3.0 | 3.0 | 2.5 | 2.5 | 1.5 | 1.5 |
| Identity, access policy & device posture | 2.5 | 2.5 | 2.0 | 2.5 | 3.0 | 2.0 |
| Logs, audit trail & incident response | 1.5 | 1.5 | 1.5 | 1.0 | 2.5 | 2.5 |
| Deployment, API & administration | 2.5 | 3.0 | 3.0 | 2.0 | 1.5 | 1.5 |
| Architecture, reliability & security assurance | 1.5 | 2.0 | 1.5 | 1.0 | 2.5 | 3.0 |
| European sovereignty | 1.5 | 1.0 | 1.5 | 1.5 | 3.0 | 2.5 |
| Pricing transparency | 2.0 | 1.0 | 2.0 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The IT Lead · Head of a three-person IT team at a 140-person mechanical engineering firm with two plants and a sales office in Vienna. The VPN still runs on the firewall, and every update of it is a weekend. Wants a client that installs through Intune and connects on its own, sign-in with Microsoft Entra so a leaver loses access the same day, the ERP and the file server reachable without opening the whole network, a fixed IP for the supplier portal, and a price per user that survives the next budget round.
The DevOps Engineer · Platform engineer at a sixty-person software company with servers at Hetzner, a Kubernetes cluster on AWS and a bastion host everyone shares a key for. Wants a mesh that reaches every server and cluster without inbound ports, access policies kept in Git and applied with Terraform, SSH access tied to the identity provider, connectors that run as containers, and a published architecture that says what the vendor's relays can see.
The MSP Technician · Senior technician at an IT service provider in Hamburg that looks after thirty clients, from tax advisers to a dental chain. Each client has its own remote access, set up by whoever was on site that year. Wants one console with a tenant per client, gateways and users added in minutes, access logs a client can be shown after an incident, billing per tenant, and prices per user that can be quoted without calling the vendor first.
The Operations Manager · Runs operations at a fifty-person consultancy where a third of the work is done by freelancers on their own laptops and the rest of the team travels to client sites. Has no IT department, only an external provider billed by the hour. Wants each freelancer to reach one project system and nothing else, access that ends with the contract, a setup a non-specialist can follow, and no call to the helpdesk from a hotel lobby.
The Information Security Officer · Information security officer at a regional energy supplier that falls under NIS2 and was asked by its auditor who could reach the control systems last year. Wants access granted per resource, not per network, device checks before a connection, every access and admin change in a log that reaches the SIEM, an independent audit of the product, and the identities and logs kept in Europe by a vendor whose subprocessors are listed.
The Skeptic · Has seen "zero trust" on a VPN that still drops every user into the whole office network, "no logs" from a vendor that keeps every connection for a year, and a remote access tool that locked out the whole company when its own control plane went down. Asks who can see the traffic and the metadata, what keeps working when the vendor is offline, whether the audit was published or only announced — and whether the network could be moved to a self-hosted server.
Access model & connectivity · What the product connects and how: a managed gateway VPN with shared or dedicated gateways and dedicated static IPs, a peer-to-peer mesh between devices and servers, access per application or resource (ZTNA), site-to-site links between offices and cloud networks (AWS, Azure, Google Cloud), connectors behind a firewall without inbound ports, the protocols (WireGuard, IPsec, OpenVPN, a vendor protocol), split tunnelling and full tunnelling, always-on and auto-connect, clients for Windows, macOS, Linux, iOS, Android and ChromeOS, the gateway and relay locations, NAT traversal and relays, and access for contractors without a managed device.
Identity, access policy & device posture · Whether access follows identity and the state of the device rather than the network: single sign-on with Microsoft Entra ID, Google Workspace, Okta or any OIDC/SAML provider, SCIM or directory sync so a leaver loses access, multi-factor authentication, groups and per-resource access policies, least-privilege defaults, device posture checks (operating system version, disk encryption, EDR or MDM status, managed device certificates), just-in-time or time-limited access with approval, session lifetimes and re-authentication, and access revoked when a device is lost.
Logs, audit trail & incident response · What can be seen and proven afterwards: connection and access logs (who reached which resource from which device, when), admin and configuration audit logs, how long logs are kept per plan, log export and streaming to a SIEM (Splunk, Microsoft Sentinel, Datadog, an S3 bucket), alerts on unusual access, a view of active sessions and the ability to end them, DNS logs where DNS filtering is part of the product, and what the vendor states it does not log, such as the content of traffic.
Deployment, API & administration · How the product is rolled out and run by a small IT team or a service provider: time to the first connection, deployment of clients through MDM (Intune, Jamf, Kandji) with preconfigured settings, a central admin console, a documented REST API, a Terraform provider or configuration as code, roles for administrators, several teams, sites or customer tenants in one account, a multi-tenant console for managed service providers, a self-hosted or on-premises edition, the update process for clients and gateways, and support channels and hours.
Architecture, reliability & security assurance · How the product is built and how its claims are proven: a published architecture showing what the coordination servers, relays and gateways see, whether traffic passes through the vendor or end to end between devices, encryption and key management, open-source clients or servers, independent security audits and penetration tests with reports or summaries published, a vulnerability disclosure or bug bounty programme, high availability and failover of the vendor's control plane, what happens to existing connections when the vendor's service is down, the vendor's own public status page and incident history, and an SLA.
European sovereignty · Who the contracting entity and the parent company are, where account data, user and device identities, connection logs and configuration are stored and processed, which party runs the coordination servers, relays and gateways the traffic passes through, and who the subprocessors are (hosting, identity, email, support and payment tools). Independently sourced by the sovereignty pipeline. Gateway and exit locations outside Europe are part of what the product does and are not counted against it; where the logs and identities are stored and who processes them is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user or per device and tier, minimum seats, what dedicated gateways, static IPs, extra networks or sites cost, which features (SSO, SCIM, device posture, log streaming, longer retention, site-to-site) need a higher tier, the free tier and its limits, the price of a self-hosted or on-premises licence, monthly versus annual billing, minimum term and VAT.
Cloud Storage & File Sharing rubric v1
| Criterion | The IT Lead v1.0 | The Data Protection Officer v1.0 | The Architecture Practice Partner v1.0 | The Tax Adviser v1.0 | The Agency Producer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Sync, clients & file access | 2.0 | 1.0 | 3.0 | 1.5 | 2.5 | 1.0 |
| Sharing & external collaboration | 1.5 | 1.5 | 2.5 | 3.0 | 3.0 | 1.0 |
| Encryption, key custody & recovery | 2.5 | 3.0 | 1.5 | 2.5 | 1.0 | 2.5 |
| Administration, audit & governance | 3.0 | 2.0 | 1.0 | 1.5 | 1.5 | 1.5 |
| Export, API & self-hosting | 2.0 | 1.0 | 1.5 | 1.0 | 2.0 | 3.0 |
| European sovereignty | 1.5 | 3.0 | 1.0 | 2.5 | 1.0 | 2.5 |
| Pricing transparency | 1.5 | 0.5 | 1.5 | 1.5 | 2.0 | 2.0 |
The judges and the criteria
The IT Lead · Runs IT with one colleague for a 180-person machine builder with three sites and a sales office in Poland. Is retiring the old file server and wants every account provisioned from Entra ID, team folders that stay with the company when someone leaves, an audit log they can hand to the auditor, a lost laptop wiped remotely, and a way back to the last clean state if ransomware ever encrypts a share.
The Data Protection Officer · External data protection officer for a hospital group, two care providers and a payroll bureau, where the files are patient letters and salary statements. Reads who holds the keys before the feature page, asks whether end-to-end encryption survives a share link and the office editor, and wants the subprocessor list, the storage location and the contracting entity in writing before a single folder moves.
The Architecture Practice Partner · Partner in a 25-person architecture practice in Hamburg whose CAD and BIM models run to several gigabytes each, worked on from the office, from home and on the building site. Needs files on demand so laptops do not fill up, sync that sends only what changed, a drive letter the CAD software accepts, phones that open plans offline in a basement, and structural engineers who can pick up a folder without an account.
The Tax Adviser · Runs a tax practice with eleven staff and 400 clients, bound by professional secrecy under §203 StGB. Receives receipts, payslips and annual accounts from clients who will not install anything, and sends back drafts that must not end up in a forwarded email. Needs upload links, shares with expiry and passwords, a record of who downloaded what, and a provider that cannot read the files it stores.
The Agency Producer · Producer at a 30-person video and design agency in Cologne that sends cuts, layouts and raw footage to customers every day and collects their feedback. Wants review links that play in the browser, comments on the file, transfers of 100 GB that do not stall, freelancers added for one project and removed after it, connections to Slack and the project tool, and a storage bill that does not jump when one shoot fills a terabyte.
The Skeptic · Has seen "end-to-end encrypted" on a service that switches it off for shared folders, "hosted in Germany" on storage whose accounts and support run from the US, and "lifetime" plans from a company two years old. Reads that a product is "GDPR-compliant" and asks who holds the keys, whether ten years of folders, versions and shares can be exported in a form another provider imports — and what leaving would cost.
Sync, clients & file access · How files reach the people who work with them: desktop clients for Windows, macOS and Linux, files on demand (virtual drive) and selective sync, offline access, mobile apps with camera upload and offline folders, a web interface, block-level or delta sync for large files, sync of folders outside the main folder, file size limits, preview of common formats, full-text search, and access through open protocols (WebDAV, SFTP, S3) or a mounted network drive.
Sharing & external collaboration · How files are shared inside the team and with people outside it: shared team folders or spaces, share links with password, expiry, download limits and view-only or no-download mode, upload links (file requests) for customers, guest or external user accounts, link and access reports, notifications, watermarking, comments and file locking, editing of office documents in the browser together, large-file transfer, and an Outlook or Teams add-in for sending links instead of attachments.
Encryption, key custody & recovery · How the files are protected and restored: encryption in transit and at rest, client-side or end-to-end encryption and whether it covers all folders, sharing and office editing, who holds the keys and what happens when a user loses theirs, customer-managed keys, two-factor authentication and single sign-on, version history and its length, a recycle bin, restore of a whole folder or account to a point in time after ransomware, ransomware detection, malware scanning, an independent security audit or penetration test, a bug bounty, and certifications (ISO 27001, SOC 2, BSI C5) with their scope. Where the data is stored is scored under sovereignty.
Administration, audit & governance · What an administrator controls: an admin console with users, groups and roles, provisioning through Entra ID, Google or LDAP with SCIM, quotas per user or team, an audit log of logins, shares and file actions with export, retention policies and legal hold, data loss prevention or classification, device management with remote wipe and unlinking, policies for external sharing, account transfer when someone leaves, team folders that belong to the company rather than to a user, and reports on storage and sharing.
Export, API & self-hosting · Whether the files and their structure can leave and connect: a bulk export or download of all data with folders and versions, open protocols (WebDAV, S3, SFTP) usable for migration, a documented REST API and SDKs, webhooks, migration tools from Dropbox, Google Drive, OneDrive or a file server, integrations with office suites, Microsoft 365 and Teams, Slack, CRM and project tools, an app marketplace, open-source code, a self-hosted or on-premise edition, and deletion of data on termination.
European sovereignty · Who the contracting entity and the parent company are, where files, metadata and backups are stored and processed, and who the subprocessors are (data centres, CDN, email that carries share notifications, support desk, payment, office editing). Independently sourced by the sovereignty pipeline; files hold the company's documents and personal data, so the whole chain counts, not only the storage. End-to-end encryption with keys only the customer holds reduces what a foreign provider could hand over but does not change who the provider is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user or per plan, storage included per user or pooled, the minimum number of users, what extra storage costs, which features (end-to-end encryption, SSO, audit log, longer version history, data residency, advanced admin) need a higher tier or an add-on, the free tier and its limits, lifetime offers and their terms, the self-hosted edition's licence and support, minimum term and VAT.
Cloud Telephony (VoIP & Cloud PBX) rubric v1
| Criterion | The Office Manager v1.0 | The IT Administrator v1.0 | The Contact Centre Lead v1.0 | The Inside Sales Lead v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Calling, numbers & call routing | 3.0 | 2.5 | 2.0 | 1.5 | 1.5 | 2.0 |
| Apps, desk phones & Microsoft Teams | 2.0 | 3.0 | 1.0 | 2.0 | 1.0 | 1.5 |
| Call centre, analytics & AI | 0.5 | 1.0 | 3.0 | 2.5 | 1.0 | 1.0 |
| CRM integration, API & administration | 1.0 | 3.0 | 2.0 | 3.0 | 1.5 | 1.5 |
| Reliability, call security & telecoms compliance | 2.0 | 2.5 | 1.5 | 1.0 | 3.0 | 2.5 |
| European sovereignty | 2.0 | 1.5 | 1.5 | 1.0 | 3.0 | 2.5 |
| Pricing transparency | 2.0 | 1.0 | 1.0 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The Office Manager · Runs the office of a tax advisory firm with twenty-five staff in Hanover, where the old phone box in the server cupboard is being switched off by the carrier. The firm's number has been on every letterhead for thirty years and must not change. Wants the number ported without a gap, a greeting and a queue during the tax deadline weeks, voicemail by email, the desk phones kept, and a monthly bill the partners can read without calling anyone.
The IT Administrator · IT administrator at a machine builder with 280 staff on three sites in Baden-Württemberg, with production halls on DECT handsets, the office on Microsoft Teams and a service team abroad. Wants desk and DECT phones provisioned without touching each one, Teams calling with the company numbers, users created from Entra ID with single sign-on, an API for the number plan, and an emergency call from a home office that reaches the right control centre.
The Contact Centre Lead · Leads customer support for an online shop for bicycle parts, with eighteen agents in Leipzig and a hotline in German and English. On Mondays after a sale the queue reaches forty callers. Wants skills-based queues, a wallboard, callbacks instead of hold music, listen and whisper for training new agents, reports per agent and hour, and call summaries in the helpdesk without anyone typing them.
The Inside Sales Lead · Leads twelve inside sales reps at a B2B software company in Munich who call prospects in Germany, Austria and Switzerland from HubSpot. Wants click-to-call and a power dialer in the CRM, every call and its recording logged on the contact, local numbers in each country, the mobile app showing the company number at trade fairs, and AI notes that a rep can trust before the follow-up email.
The Data Protection Officer · External data protection officer for a group of six medical practices whose patients call about appointments, results and prescriptions. Knows that call records fall under the secrecy of telecommunications and that a recorded or transcribed call can hold health data. Reads the subprocessor list, asks which AI model writes the transcripts and where, wants encryption on by default, and needs a DPA and a retention period before any call is recorded.
The Skeptic · Has seen "all calls included" that excluded mobile numbers abroad, a "five-minute setup" followed by six weeks of porting, and an "AI assistant" that sent every recorded call to a model in the US. Asks what porting the numbers back out costs and how long it takes, whether the desk phones still work after leaving, who carries the calls, what the SLA pays when the platform is down — and what the second year costs.
Calling, numbers & call routing · What the phone system does with a call: local geographic numbers in the customer's own area code and in other countries, number blocks and porting of existing numbers, extensions, IVR menus, queues, ring groups and hunt groups, time-based and holiday routing, call forwarding and transfer, voicemail to email, fax to email, conference calls, call recording, call park and pickup, busy lamp fields, caller ID per user or team, and emergency calls (110 and 112) with the caller's location.
Apps, desk phones & Microsoft Teams · Where the calls are made and taken: desktop and mobile softphone apps, a browser client, presence, desk phones and DECT handsets from named makers (Yealink, Snom, Gigaset, Poly, Cisco) provisioned automatically, devices for sale or rent, the mobile phone as an extension with the company number shown, fixed-mobile convergence, Microsoft Teams calling through Direct Routing or Operator Connect, headset support, and the apps' ratings and update notes.
Call centre, analytics & AI · How a team that lives on the phone is run: ACD queues with skills and priorities, agent states and wrap-up time, a wallboard, live monitoring with listen, whisper and barge, callbacks instead of waiting, outbound and power dialers, call statistics and reports per agent and queue, missed-call handling, AI transcription, summaries and sentiment, an AI receptionist or voicebot, and SMS or WhatsApp beside calls.
CRM integration, API & administration · How the phone system fits the company: integrations with CRM and helpdesk tools (Salesforce, HubSpot, Pipedrive, Zendesk, Microsoft Dynamics) with click-to-call, caller pop-ups and automatic call logging, a documented REST API and webhooks for call events, SIP trunks for an existing PBX and bring-your-own-carrier, an admin portal with roles, single sign-on (SAML) and SCIM, two-factor authentication, multi-site and multi-company set-up, bulk user import, audit logs, and partner or reseller accounts.
Reliability, call security & telecoms compliance · Whether the service holds on a bad day and in an audit: redundant data centres and carrier connections, a stated availability or SLA with credits, the vendor's own public status page and incident history, call quality measures (codecs, quality monitoring), encryption of signalling and media (TLS and SRTP), registration as a telecoms provider with the national regulator (Bundesnetzagentur or its EU equivalent), the secrecy of telecommunications, recording consent and retention, emergency call handling for remote users, fraud protection against toll fraud, and security certifications such as ISO 27001.
European sovereignty · Who the contracting entity and the parent company are, where call records, voicemails, recordings, transcripts, contacts and account data are stored and processed, which carriers carry the calls, and who the subprocessors are (hosting, carriers and number providers, SMS gateways, AI transcription and summary models, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. International numbers and carriers needed to reach other countries are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted phone system the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user or extension and per plan, what numbers, number blocks and porting cost, which calls are included in a flat rate (landline, mobile, international) and what the rest cost per minute, which features (call centre, recording, AI, CRM integrations, Teams calling) cost extra, device prices or rent, set-up fees, minimum term and notice period, and VAT.
Code Security & Quality (SAST/SCA) rubric v1
| Criterion | The Lead Developer v1.0 | The Application Security Engineer v1.0 | The Engineering Manager v1.0 | The Platform Engineer v1.0 | The Product Security Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Code analysis (SAST & code quality) | 3.0 | 3.0 | 3.0 | 2.0 | 2.0 | 2.5 |
| Dependencies (SCA), licences & secrets | 2.0 | 3.0 | 1.5 | 2.0 | 3.0 | 2.0 |
| Developer workflow, quality gates & fixes | 3.0 | 2.0 | 2.5 | 2.0 | 1.0 | 1.5 |
| Platforms, deployment & administration | 1.5 | 1.5 | 2.5 | 3.0 | 1.5 | 1.0 |
| Source-code handling, security & compliance | 1.0 | 2.5 | 1.5 | 2.5 | 3.0 | 2.5 |
| European sovereignty | 1.0 | 1.5 | 1.0 | 2.5 | 3.0 | 2.5 |
| Pricing transparency | 2.0 | 0.5 | 1.0 | 1.0 | 0.5 | 2.0 |
The judges and the criteria
The Lead Developer · Lead developer at a web agency in Cologne with fourteen developers building Laravel, TypeScript and React Native projects for clients on GitHub and GitLab. Wants every merge request checked for bugs, injection flaws and vulnerable packages before review, comments in the merge request rather than a separate dashboard, the same rules in VS Code and PhpStorm, few false positives, and a bill that does not jump each time a freelancer pushes a commit.
The Application Security Engineer · Application security engineer at a payments company in Frankfurt with 120 developers, two of them security champions per team, under PCI DSS and DORA. Wants taint analysis that follows user input across files, reachability so the backlog holds only vulnerable code that is actually called, secrets checked for validity across the whole git history, push protection, custom rules for in-house frameworks, and reports an auditor accepts.
The Engineering Manager · Head of engineering at a B2B SaaS company in Munich with six teams and a ten-year-old Java and Kotlin codebase. Wants technical debt and code health shown per team and hotspot, a quality gate on new code that every team keeps, trends to show the board that the rewrite budget worked, findings routed to Jira, single sign-on and roles per team, and to know what the AI-written code the teams now merge does to the numbers.
The Platform Engineer · Platform engineer at an insurer in Hanover who runs a self-managed GitLab and Jenkins for 300 developers inside the company network; source code may not leave it. Wants a self-hosted edition or a scanner that runs in the pipeline and sends only results, SAML and SCIM from Entra ID, an API to roll scan settings out to 900 repositories, SARIF output, audit logs, and upgrades that do not break the pipelines.
The Product Security Officer · Product security officer at a machine builder in Baden-Württemberg whose controllers and service apps fall under the EU Cyber Resilience Act. Needs an SBOM per release in a standard format, every component's vulnerabilities and licences tracked after shipping, evidence of secure development an auditor can file, and to know where the firmware source code is stored, for how long, and whether any AI model is trained on it.
The Skeptic · Has seen "zero false positives" bury a team under four thousand findings on day one, a "free for open source" plan that counted every bot as a contributor, and an "AI autofix" that shipped the repository to a model in the US. Asks how contributors are counted, which languages get real data-flow analysis rather than regular expressions, what happens to the code after a scan, whether the findings export when the contract ends — and what the second year costs.
Code analysis (SAST & code quality) · What the tool finds in the company's own code: static application security testing with data-flow and taint analysis across functions and files, the languages and frameworks covered and at what depth, the rule sets (OWASP Top 10, CWE, custom rules), bugs and code smells, duplication, cyclomatic and cognitive complexity, maintainability and technical-debt measures, test coverage import, infrastructure-as-code checks, and how false positives are measured and kept down.
Dependencies (SCA), licences & secrets · What comes from outside or should never be committed: software composition analysis of direct and transitive dependencies with the ecosystems and lockfiles supported, the vulnerability database and how quickly it is updated, reachability analysis, licence detection and policies, SBOM export (CycloneDX, SPDX), malicious and typosquatted package detection, end-of-life components, automatic upgrade pull requests, container image scanning, and secret detection in code and git history with the number of detectors, validity checks and revocation guidance.
Developer workflow, quality gates & fixes · Whether developers see and act on the findings where they work: pull and merge request comments and status checks, quality gates that block a merge on new issues, a focus on new code against a baseline, IDE plugins with the same rules as the server, CLI and CI integrations (GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, Bitbucket Pipelines), pre-commit hooks, triage, suppression and ignore rules with reasons, deduplication, fix suggestions and AI autofix with the model behind it, and scan times.
Platforms, deployment & administration · How the tool fits the company: the code hosts supported (GitHub, GitLab, Bitbucket, Azure DevOps) cloud and self-managed, a self-hosted or on-premise edition or a scanner that runs inside the customer's network, a documented REST API and webhooks, issue tracker integrations (Jira), single sign-on (SAML or OIDC) and SCIM, roles and permissions per project and team, portfolio reports across repositories, audit logs, export of findings (SARIF, CSV), and partner or multi-organisation accounts.
Source-code handling, security & compliance · What the vendor does with the customer's source code and how it holds up in an audit: whether code leaves the customer's network or only results do, where and how long code and findings are stored, whether code or findings are used to train AI models and how to opt out, encryption, the vendor's own certifications (ISO 27001, SOC 2) with their scope, a stated availability or SLA and a public status page, audit logs, and reports mapped to OWASP, CWE, PCI DSS, ISO 27001 or the EU Cyber Resilience Act.
European sovereignty · Who the contracting entity and the parent company are, where source code, findings, SBOMs, account and usage data are stored and processed, and who the subprocessors are (hosting, AI models used for autofix and triage, vulnerability data sources, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Public vulnerability databases and package registries the scanner queries are part of what the product does and are not counted against it; where the customer's code and findings are stored and who processes them is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per developer, contributor, committer or line of code and per plan, how contributors are counted, what the free tier and open-source plan include, which scanners (SAST, SCA, secrets, containers) and features (SSO, self-hosting, AI autofix, compliance reports) cost extra, limits on repositories, scans or lines of code, minimum seats, monthly versus annual terms, and VAT.
Consent Management (CMP) rubric v1
| Criterion | The Data Protection Officer v1.0 | The Agency Developer v1.0 | The Publisher Marketing Lead v1.0 | The In-House Lawyer v1.0 | The WordPress Webmaster v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Banner & choice architecture | 2.5 | 1.5 | 2.5 | 3.0 | 2.0 | 2.0 |
| Prior blocking & script control | 3.0 | 3.0 | 1.5 | 2.5 | 2.5 | 3.0 |
| Scanning & cookie classification | 2.0 | 2.5 | 1.0 | 1.5 | 2.5 | 2.0 |
| Consent records & proof | 3.0 | 1.5 | 1.5 | 3.0 | 1.5 | 2.5 |
| Frameworks, signals & platforms | 1.0 | 2.5 | 3.0 | 1.5 | 1.5 | 1.0 |
| European sovereignty | 2.5 | 1.0 | 1.0 | 2.0 | 1.5 | 2.5 |
| Pricing transparency | 0.5 | 1.5 | 1.5 | 1.0 | 2.0 | 2.0 |
The judges and the criteria
The Data Protection Officer · External DPO for a dozen mid-sized companies, two of which received a letter from a state supervisory authority about their cookie banner last year. Wants reject on the first layer, nothing loaded before the click, a consent log that shows which banner version each visitor saw, a cookie list that matches the site, and a DPA and subprocessor list that keep visitor data in the EU.
The Agency Developer · Lead developer at a web agency that maintains forty client sites on WordPress, TYPO3 and Shopify. Wants one account for every client, blocking that works without rewriting each theme, content blockers for YouTube and Maps, a Tag Manager template, a scanner that flags the tracker a client added on Friday, and a JavaScript API documented well enough that forms and plugins can ask for consent.
The Publisher Marketing Lead · Runs marketing for an ad-funded news site and an online shop in the same group, where every point of consent rate shows up in ad revenue and in Google Ads conversions. Wants a registered IAB TCF CMP, Google Consent Mode v2 in advanced mode, banner tests within what the law allows, consent shared between the site and the app, and a dashboard that shows where visitors drop off.
The In-House Lawyer · In-house counsel at a retailer with shops in Germany, France and Austria, who has read the court decisions on missing reject buttons and the regulators' banner guidance. Wants § 25 TDDDG and the GDPR mapped to concrete settings, equal-weight choices as the default, consent that can be withdrawn as easily as it was given, and records that would hold up if a competitor or a consumer group sued.
The WordPress Webmaster · Looks after the WordPress site of a mid-sized engineering company on top of the actual job, with Google Analytics, a YouTube channel, a Maps embed and a contact form with reCAPTCHA. Wants a plugin that finds these by itself, blocks them until the visitor agrees, survives the next plugin update and caching, and costs a known amount per site per year without a call to sales.
The Skeptic · Has opened the browser's network tab on sites with a "certified" banner and watched the ad pixels fire before anything was clicked. Reads "consent rate optimisation" as a hint that reject will be grey and small, "auto-blocking" as a claim until the test steps are published, and "EU hosting" next to a US script CDN — and asks what leaving would cost: the consent logs, and every visitor asked again.
Banner & choice architecture · What the visitor is asked and how: a reject option on the first layer with the same prominence as accept, consent by category and by vendor, withdrawal and changed choices as easy as the first consent (a persistent button or link), banner texts and layouts the site owner controls, languages, rules per country or regulation (GDPR, Swiss FADP, US state laws), accessibility of the banner itself, and consent-rate analytics or A/B tests that stay within the rules.
Prior blocking & script control · What happens before the visitor decides: automatic blocking of scripts, pixels, cookies and embedded content until consent is given, content blockers with placeholders for videos, maps and social embeds, integration with tag managers (Google Tag Manager, Matomo Tag Manager) and server-side tagging, consent passed to forms and plugins, and a documented way for the site owner to check that nothing loads too early.
Scanning & cookie classification · How the product knows what the site sets: a scanner that crawls the site for cookies, local storage, pixels and third-party requests, scheduled rescans, a maintained database that classifies cookies and services by purpose, provider and lifetime, alerts on new or changed trackers, and a cookie declaration or policy section that updates itself from the scan.
Consent records & proof · What the site owner can show afterwards: a record per consent with time, pseudonymous ID, the choices made and the banner version shown, how long records are kept and where, export of the consent log, re-consent when the services or texts change, consent expiry, records available to the visitor (a consent ID), and proof that withdrawal took effect.
Frameworks, signals & platforms · Where the consent goes and where the product runs: the IAB Transparency and Consent Framework (TCF, current version) with a registered CMP ID, Google Consent Mode v2 and Google's CMP certification, Microsoft UET consent mode and other ad-platform signals, the Global Privacy Platform and Global Privacy Control for US laws, plugins and apps for WordPress, Shopify, TYPO3 and other systems, iOS and Android SDKs, connected TV, multi-domain and agency accounts, and an API.
European sovereignty · Who the contracting entity and the parent company are, where the banner script is served from, where consent logs and scan results are stored, and who the subprocessors are (hosting, CDN, geolocation, scanner infrastructure, app SDK telemetry, email and support). Independently sourced by the sovereignty pipeline; a CMP runs on every page of the customer's site and sees every visitor, so the whole chain counts, not only the database. For a plugin that runs on the customer's own server, the vendor's licence, update and scanner services are the chain.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per domain or site licence, the page-view, session or consent limits of each tier and what happens above them, the free tier's limits, which features (TCF, app SDKs, A/B testing, multi-domain, white label) cost extra, agency or reseller terms, minimum term, and setup.
Content Marketing rubric v2
| Criterion | The Head of Content v1.0 | The SME Marketer v1.0 | The Localisation Lead v1.0 | The Web Engineer v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Planning, editorial calendar & briefs | 3.0 | 2.0 | 1.0 | 0.5 | 0.5 | 1.0 |
| Creation, review & approval | 3.0 | 1.0 | 1.5 | 1.0 | 1.5 | 1.5 |
| Structured content, localisation & export | 1.5 | 1.0 | 3.0 | 2.5 | 1.0 | 2.5 |
| Publishing, distribution & integrations | 1.5 | 2.0 | 2.0 | 3.0 | 1.0 | 1.5 |
| AI assistance & content rights | 1.5 | 3.0 | 1.5 | 0.5 | 2.5 | 2.5 |
| European sovereignty | 1.0 | 1.0 | 1.0 | 1.5 | 3.0 | 1.5 |
| Pricing transparency | 1.0 | 2.0 | 1.0 | 1.0 | 0.5 | 2.0 |
The judges and the criteria
The Head of Content · Runs an editorial team of six plus freelancers and answers for what goes live. Wants briefs that carry the goal to the writer, a calendar that shows what is late, and an approval trail that says which version legal released — not a status anyone can flip to "approved".
The SME Marketer · Is the marketing department of a 120-person Mittelstand company and writes half the content with an AI assistant. Wants to know who owns what the model wrote, whether her drafts train it, and what the plan costs once she adds a second language and the agency as guests.
The Localisation Lead · Ships every piece in German, English and French for the DACH region and beyond. Wants locales on the field, not copies of the entry, translation status per language, and a documented export of content, model and locales — because a repository that cannot leave is a hostage, not an asset.
The Web Engineer · Builds the website and the integrations the content flows through. Wants a versioned API with published rate limits, webhooks on publish, preview environments, and a migration CLI that works in both directions — and reads "headless" as a promise about the API, not a logo.
The Data Protection Officer · Signs off every tool that stores the company's drafts, author profiles and campaign data. Wants the contracting entity and hosting region named, the subprocessor list with the AI providers on it, prompt retention in days, and training on customer content excluded in the terms rather than in a blog post.
The Skeptic · Has read "AI-powered content at scale", "one source of truth for every channel" and "no lock-in, it's headless" on every page in this category. Reads instead for the export that includes locales and history, the clause on training with customer content, and what the invoice does when the third locale and the API overage arrive.
Planning, editorial calendar & briefs · Turning a content strategy into scheduled work: topics and campaigns, an editorial calendar across channels, briefs that carry the goal, audience and keywords to the writer, and a view of what is due, late or missing.
Creation, review & approval · Writing and reviewing content together: editing with comments and suggestions, roles and permissions for internal and external contributors, and an approval trail that records who released which version — published content is a legal statement (UWG, Heilmittelwerbegesetz, the imprint duty).
Structured content, localisation & export · Whether content is stored as reusable structure rather than pages: a content model, components shared across channels, German and other locales managed side by side, and the whole repository exportable in a documented format.
Publishing, distribution & integrations · Getting approved content to where it is read: publishing to websites and channels, a documented API and webhooks, and named connections to the CMS, CRM, analytics, SEO and translation tools a marketing stack already runs.
AI assistance & content rights · What the platform's AI does with the customer's content and what the customer may do with the AI's: the models and where they run, whether content trains them, opt-out, labelling of generated text under the EU AI Act, and who holds the rights to output.
European sovereignty · Who the contracting entity is, where content, assets and AI prompts are stored and processed, and which subprocessors touch them. Independently sourced by the sovereignty pipeline; dimensions the evidence does not establish are unknown, not non-European.
Pricing transparency · Whether a buyer can compute the annual cost for their team, locales and traffic from public pages alone — seats and contributor roles, locales, content records, API calls and bandwidth, AI credits, and the plan where approval workflows or SSO begin.
Contract Management (CLM) rubric v2
| Criterion | The General Counsel v1.0 | The Procurement Analyst v1.0 | The Sales Ops Owner v1.0 | The IT Integrator v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Drafting, templates & clause library | 2.5 | 1.0 | 3.0 | 1.0 | 0.5 | 1.0 |
| Negotiation, redlining & approval | 3.0 | 1.5 | 2.5 | 1.0 | 1.0 | 1.5 |
| Repository, deadlines & obligations | 2.0 | 3.0 | 1.0 | 1.5 | 1.5 | 2.5 |
| AI extraction & review transparency | 2.0 | 2.0 | 1.0 | 1.5 | 3.0 | 3.0 |
| Integrations, signature & exit | 1.0 | 1.5 | 2.0 | 3.0 | 1.5 | 2.5 |
| European sovereignty | 1.5 | 1.0 | 0.5 | 2.0 | 3.0 | 1.5 |
| Pricing transparency | 0.5 | 1.0 | 2.0 | 0.5 | 0.5 | 2.0 |
The judges and the criteria
The General Counsel · Runs a three-lawyer legal team that negotiates every supplier and customer contract in Word with the other side's counsel. Wants approved clauses with fallbacks, redlines that survive the round-trip, and an approval on record for every deviation — not a sign-off by email.
The Procurement Analyst · Holds four hundred supplier contracts and the Kündigungsfristen nobody else remembers. Wants notice periods and auto-renewals modelled rather than typed into a note, reminders that escalate to a named owner, and a portfolio report that shows what can be cancelled this quarter.
The Sales Ops Owner · Owns the quote-to-signature path for a sales team that closes standard deals without legal. Wants contracts generated from the CRM record, approvals that route by discount and value, signature in the same flow, and a price she can put in next year's budget.
The IT Integrator · Connects the CLM to SAP, Microsoft 365 and the CRM, and will be the one migrating out of it. Wants a versioned API, SSO and SCIM, qualified signature where the law asks for it, and an export that brings back metadata, versions and audit trail — not a ZIP of PDFs.
The Data Protection Officer · Reads the subprocessor list before the feature page. Asks which model provider receives contract text, whether it is retained or used for training, where OCR runs, and whether the counterparties' personal data in every contract is covered by the DPA.
The Skeptic · Has seen "AI that reads your contracts" miss a notice period buried in an amendment. Reads for an extraction accuracy nobody states, "Word integration" that loses tracked changes, "never miss a renewal" with reminders to one inbox, and an export that leaves the metadata behind.
Drafting, templates & clause library · Creating a contract without starting from an old one: templates with variables and conditional clauses, an approved clause library, self-service generation for business teams, and support for German-language and German-law templates.
Negotiation, redlining & approval · Getting from draft to agreed text with a counterparty and through internal sign-off: redlining in Word and in the browser, external collaboration, version comparison, approval workflows, and a record of who approved which version.
Repository, deadlines & obligations · Knowing what has been signed and what it requires: a searchable repository with metadata, notice periods (Kündigungsfristen) and renewal dates captured and reminded, obligations tracked to an owner, access rights by department, and reporting on the portfolio.
AI extraction & review transparency · Whether the AI that extracts dates and clauses or reviews a draft is disclosed, verifiable and controllable: named model provider and processing location, no training on customer contracts, extracted values shown with their source passage, and features the customer can switch off. A product without AI features is judged on stating so.
Integrations, signature & exit · How contracts connect to the rest of the company and leave it again: CRM, procurement and ERP integration, e-signature (and which eIDAS level: simple, advanced or qualified), SSO, an API, and a documented export of documents together with their metadata, versions and audit trail.
European sovereignty · Who the contracting entity is, where contracts and their extracted data are hosted, and who the subprocessors are — including the AI and OCR providers the text is passed to. Independently sourced by the sovereignty pipeline; weighted with care here because a contract repository holds a company's most confidential commitments and those of its counterparties. Dimensions the evidence does not establish are unknown, not non-European.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: the pricing basis (per user, per contract, per module), which features sit in which tier, add-ons for AI, e-signature volume or integrations, onboarding and migration fees, and the minimum term.
Conversion Optimization rubric v2
| Criterion | The Growth Lead v1.0 | The E-Commerce Manager v1.0 | The Product Engineer v1.0 | The CRO Consultant v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Experiment types & delivery | 3.0 | 2.5 | 2.5 | 2.0 | 0.5 | 1.0 |
| Statistical method & guardrails | 2.0 | 1.5 | 2.0 | 2.0 | 0.5 | 3.0 |
| Consent & visitor tracking | 1.5 | 1.5 | 1.0 | 2.0 | 3.0 | 1.0 |
| Snippet performance & flicker | 1.5 | 3.0 | 2.5 | 1.5 | 0.5 | 1.5 |
| Analytics, data export & integrations | 2.0 | 1.5 | 3.0 | 2.0 | 1.0 | 2.5 |
| European sovereignty | 1.0 | 1.0 | 1.0 | 1.5 | 3.0 | 1.0 |
| Pricing transparency | 1.0 | 1.5 | 0.5 | 2.0 | 0.5 | 1.0 |
The judges and the criteria
The Growth Lead · Runs the testing programme for a German marketing team and reports uplift to the board. Wants a visual editor the team can use without a developer, targeting that goes beyond the URL, and results she can defend when finance asks where the promised revenue went.
The E-Commerce Manager · Owns a shop where a tenth of a second of load time shows up in the conversion rate. Wants personalisation that can be tested against a control, a snippet that does not flicker the product page, and a traffic-based price that does not jump a tier every December.
The Product Engineer · Ships experiments behind feature flags and would rather not ship a third-party script at all. Wants server-side SDKs for the stack in use, edge delivery, metrics computed in the warehouse the team already trusts, and an API good enough to build internal tooling on.
The CRO Consultant · Sets up testing programmes for several clients and has to recommend a platform each can afford and defend. Reads for multi-project management, clean analytics integration, a consent setup a client's DPO will sign off, and a traffic metric she can estimate before the contract.
The Data Protection Officer · Has to answer whether the test script may run before the consent banner is answered, and usually finds the vendor has not said. Wants the storage keys listed, a documented consent-pending mode, visitor data processed in the EU, and a published subprocessor list that includes the CDN.
The Skeptic · A statistician who has watched too many "winners" regress to zero. Reads for the method by name, what stops a team from peeking, sample ratio mismatch checks and multiple-comparison corrections — and treats a "probability to beat" without documented assumptions as marketing.
Experiment types & delivery · What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.
Statistical method & guardrails · Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.
Consent & visitor tracking · Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.
Snippet performance & flicker · The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".
Analytics, data export & integrations · Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.
European sovereignty · Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
Pricing transparency · A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
CRM rubric v2
| Criterion | The Solo Seller v1.2 | The Data Protection Officer v1.0 | The Sales Ops Lead v1.0 | The RevOps Integrator v1.0 | The Migrator v1.1 | The Skeptic v1.2 |
|---|---|---|---|---|---|---|
| Contact & data model | 2.0 | 1.5 | 1.5 | 1.0 | 1.0 | 1.0 |
| Pipeline & forecasting | 2.0 | 0.5 | 3.0 | 1.0 | 0.5 | 1.0 |
| Automation & workflows | 0.5 | 0.5 | 2.0 | 1.5 | 0.5 | 1.0 |
| Integrations & API | 1.0 | 1.0 | 1.5 | 3.0 | 1.5 | 1.0 |
| European sovereignty | 0.5 | 3.0 | 0.5 | 0.5 | 1.0 | 1.0 |
| Import, export & exit | 1.0 | 3.0 | 0.5 | 1.5 | 3.0 | 1.5 |
| Pricing transparency | 1.0 | 0.5 | 1.0 | 0.5 | 1.0 | 1.0 |
The judges and the criteria
The Solo Seller · Runs their pipeline between customer calls and pays with their own card. Optimizes for a CRM that is set up in an afternoon, priced honestly at 1-5 seats, and never asks them to configure an object model. Rejects seat minimums and features held hostage in enterprise tiers.
The Data Protection Officer · Knows a CRM is a database of other people's personal data before it is a sales tool. Optimizes for GDPR posture: EU hosting, DPA, subprocessor hygiene, consent fields, retention and deletion that actually delete. Rejects US-default hosting and enrichment features that scrape contacts from the open web.
The Sales Ops Lead · Owns the forecast a 40-seat team lives by. Optimizes for pipeline discipline: stage hygiene, required fields, routing, quota and forecast reporting the CFO will accept. Rejects freeform pipelines that cannot enforce a process and reporting that stops at a dashboard screenshot.
The RevOps Integrator · Treats the CRM as one system in a revenue stack. Optimizes for two-way email and calendar sync, a real API with webhooks, and native connections to the tools money already flows through. Rejects closed ecosystems and integrations that are one-way imports in disguise.
The Migrator · Has moved a company off a CRM twice and remembers every scar. Optimizes for clean import with dedupe, full export of every object including notes and activity history, and contract terms that permit leaving. Rejects export behind support tickets and per-record API metering that makes exit a project.
The Skeptic · Assumes the pricing page is the nicest thing the vendor will ever say. Hunts per-seat maths that explode at renewal, "unlimited" with footnotes, AI features priced by credits, dead changelogs and acquisition rumours. Exists to keep the rest of the bench honest.
Contact & data model · Depth and hygiene of the core records: contacts, companies and deals linked to each other, custom fields, activity history on the record, import hygiene and deduplication.
Pipeline & forecasting · How deals move through a sales process and what the pipeline reports: pipelines and stages, probabilities, forecasts, goals or quotas, win/loss analysis and sales reporting.
Automation & workflows · Triggers, sequences and routing that remove manual work without a consultant: workflow rules, email sequences, task creation and lead assignment.
Integrations & API · Email and calendar sync, native connections, an integration marketplace, and an API that treats external systems as first-class.
European sovereignty · Where other people's personal data actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, email and calendar sync, telephony, enrichment, AI features), and the data processing agreement. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.
Import, export & exit · Getting in with history intact, and out with everything: self-service import with field mapping, migration from other CRMs, export of records, activities and files, and API access for the rest. The anti-lock-in criterion.
Pricing transparency · Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone: tier prices, billing periods, seat minimums, add-ons, usage meters and onboarding fees.
Customer Service & Helpdesk rubric v2
| Criterion | The Support Lead v1.0 | The Agent Advocate v1.0 | The Data Protection Officer v1.0 | The Shop Operator v1.0 | The Integrator v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Ticketing, queues & SLA | 3.0 | 3.0 | 1.0 | 2.0 | 1.5 | 1.5 |
| Channels in one queue | 2.0 | 2.5 | 0.5 | 3.0 | 1.5 | 2.0 |
| Knowledge base & deflection | 2.0 | 2.0 | 0.5 | 2.5 | 0.5 | 1.0 |
| Customer data protection | 1.0 | 1.0 | 3.0 | 1.0 | 1.5 | 1.5 |
| Integrations & API | 1.5 | 1.0 | 0.5 | 2.5 | 3.0 | 1.0 |
| European sovereignty | 0.5 | 0.5 | 3.0 | 0.5 | 1.0 | 1.5 |
| Pricing transparency | 1.0 | 1.0 | 0.5 | 1.5 | 1.0 | 2.0 |
The judges and the criteria
The Support Lead · Runs a team of twelve against an SLA the sales team promised. Wants routing that reflects skill, timers that warn before they breach, and reporting she can take to a quarterly review. Reads "AI-powered" as a claim to be checked against the queue on a Monday morning.
The Agent Advocate · Has answered tickets for six years and judges every tool by the hundredth reply, not the first. Wants search that finds the old thread, macros that save real keystrokes, and one screen rather than four tabs. Treats agent-activity dashboards as a smell.
The Data Protection Officer · Sees a ticket archive for what it is: years of personal data customers typed themselves, including the things they should not have. Wants retention that executes, redaction, an audit of who read what, and an answer on whether vendor support can open a ticket.
The Shop Operator · Handles "where is my parcel" at volume and needs the order in front of the agent without a second login. Judges omnichannel by whether WhatsApp and the shop actually land in one queue, and deflection by whether the ticket count falls in December.
The Integrator · Has to wire the helpdesk into a CRM, a shop and an identity provider that all predate it. Wants a documented API with rate limits, webhooks that retry, SCIM, and a sandbox. Reads a partner-contact form on an integrations page as a missing API.
The Skeptic · Counts the channel logos on the marketing page, then asks which of them share one queue and one history. Reads for the tier where SLA policies begin, what a "light agent" may actually do, and whether the AI summariser is included or metered.
Ticketing, queues & SLA · The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.
Channels in one queue · Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.
Knowledge base & deflection · Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.
Customer data protection · A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.
Integrations & API · The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.
European sovereignty · Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.
Pricing transparency · Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.
Data Protection rubric v3
| Criterion | The External DPO v2.0 | The In-House Counsel v2.0 | The Drafted Generalist v2.1 | The Lead Auditor v2.0 | The IT Integrator v2.0 | The Skeptic v2.1 |
|---|---|---|---|---|---|---|
| Records & DPIA depth | 3.0 | 2.0 | 1.5 | 1.5 | 1.5 | 1.0 |
| Data subject rights & incidents | 2.0 | 2.5 | 2.0 | 1.0 | 1.0 | 1.5 |
| Privacy regime coverage | 1.0 | 2.0 | 0.5 | 1.5 | 0.5 | 1.0 |
| Audit readiness & evidence | 1.0 | 1.0 | 1.0 | 3.0 | 0.5 | 1.5 |
| Integrations & automation | 1.0 | 0.5 | 0.5 | 0.5 | 3.0 | 0.5 |
| European sovereignty | 1.5 | 1.5 | 1.0 | 1.0 | 1.0 | 1.5 |
| Pricing transparency | 1.0 | 0.5 | 1.0 | 0.5 | 0.5 | 1.0 |
The judges and the criteria
The External DPO · Carries thirty client mandates and bills by the hour they save. Optimizes for multi-client capability, reusable templates, a RoPA that drives the rest, and client-ready reports. Rejects single-tenant tools that treat the consultancy as thirty separate customers.
The In-House Counsel · Answers personally when the authority writes. Optimizes for defensibility: request clocks that never slip, a breach workflow that produces the Art. 33 notification, regime coverage that matches where the company actually operates. Rejects tools whose legal content nobody maintains.
The Drafted Generalist · Office manager at an 80-employee firm who got compliance added to her job title, not her calendar. Optimizes for guided workflows in plain language and software that knows the law so she does not have to. Rejects consultant-shaped platforms that assume a compliance department.
The Lead Auditor · Audits management systems for a living and has seen every folder of screenshots. Optimizes for revision-safe history, evidence packs on demand, and a defensible answer to "show me the state on date X". Rejects systems where the audit trail is assembled the week before the audit.
The IT Integrator · Has to feed the compliance platform from the estate that already exists: Entra ID, Jira, the CMDB. Optimizes for directory import, a real API, webhooks and SSO — compliance data that stays current because it syncs, not because someone retypes it. Rejects data islands with a CSV drawbridge.
The Skeptic · Hunts certification logos that link nowhere, "AI-powered" features with no substance behind them, consulting bundled as software, legal-update promises with no named lawyer, and customer counts that disagree between pages. Exists to keep the rest of the bench honest.
Records & DPIA depth · The DSMS core: records of processing activities (RoPA/VVT, Art. 30 DSGVO), data protection impact assessments (DSFA, Art. 35), processor and DPA management (AVV), and technical and organisational measures (TOMs) — how deeply the legal artefacts are modelled and connected.
Data subject rights & incidents · The operational half of the DSMS: handling data subject requests within the Art. 12 deadline, a breach register with the 72-hour notification of Art. 33, and deletion concepts that are carried out.
Privacy regime coverage · Which privacy regimes the product operationalises — DSGVO/GDPR, BDSG, TTDSG/ePrivacy, Swiss nDSG, UK GDPR, EU AI Act privacy duties — and whether one record maps across them or each regime is a fresh island.
Audit readiness & evidence · Whether the system produces defensible proof: change history, evidence collection, and reports for auditors, authorities and management.
Integrations & automation · Whether the platform feeds from the real IT estate — directory import, ticketing, SSO, API — and automates the recurring privacy work instead of re-typing it.
European sovereignty · Where the compliance record of the whole company actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, AI features, email, support tooling), DPA. A platform that maps your processing is itself your most concentrated processing. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.
Pricing transparency · Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.
Design rubric v2
| Criterion | The Product Designer v1.0 | The Frontend Engineer v1.0 | The Brand Marketer v1.0 | The Agency Owner v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Design, prototyping & design systems | 3.0 | 2.0 | 1.5 | 2.0 | 0.5 | 1.0 |
| Collaboration, review & developer handoff | 2.5 | 3.0 | 1.5 | 2.0 | 1.5 | 1.5 |
| Brand assets & governance | 1.0 | 0.5 | 3.0 | 1.0 | 1.0 | 1.0 |
| Files, formats & portability | 2.0 | 2.5 | 1.0 | 3.0 | 1.5 | 2.5 |
| AI features & rights to the work | 1.0 | 0.5 | 2.5 | 1.5 | 2.5 | 2.5 |
| European sovereignty | 0.5 | 1.0 | 1.0 | 1.0 | 3.0 | 1.5 |
| Pricing transparency | 1.0 | 0.5 | 1.0 | 2.0 | 0.5 | 2.0 |
The judges and the criteria
The Product Designer · Owns the design system of a B2B software product. Wants components with variants, tokens with modes, prototypes that test a real flow, and library releases that are versioned and reviewable — a design system is a product, not a page of nicely arranged buttons.
The Frontend Engineer · Turns the designs into code and gets the ticket when they disagree. Wants an inspect mode without a paid seat, tokens exported in a documented format, components mapped to the code ones, and an API that reads the whole file rather than a screenshot of it.
The Brand Marketer · Keeps the brand consistent across twelve sales offices that make their own flyers. Wants locked templates non-designers can use, guidelines inside the tool, licence and expiry dates on every stock image, and a clear answer on whether a generated image may go on a trade-fair stand.
The Agency Owner · Runs a design agency of fifteen and hands every project over to the client at the end. Wants files that export with layers and components intact, guests who are not billed as editors, and terms that say the client owns the work — and what happens to it after a cancellation.
The Data Protection Officer · Reviews every tool where unreleased products, customer screenshots and employee photos end up. Wants the contracting entity and hosting region named, the AI providers on the subprocessor list, and training on customer files excluded for the whole organisation in the terms — not behind a toggle each user has to find.
The Skeptic · Has read "free for viewers", "commercially safe AI" and "export anytime" on every page in this category. Reads instead for the click that turns a reviewer into a billed editor, the plan the IP indemnity actually covers, and whether the export keeps a single component.
Design, prototyping & design systems · The making itself: vector and layout tools, interactive prototypes, and the shared components, styles and tokens that keep a company's products and materials consistent — judged on what the feature and help pages document, not on showcase images.
Collaboration, review & developer handoff · Working on the same files with colleagues, clients and developers: comments and review, permissions for internal and external people, and the handoff that gives engineering measurements, assets and code rather than screenshots.
Brand assets & governance · Keeping a brand usable and correct across a company: a central library for logos, images and templates, brand guidelines people can find, locked templates that let non-designers produce material, and rights and expiry metadata on every licensed asset.
Files, formats & portability · Whether the work can leave: open or documented file formats, export that keeps layers, vectors and components, offline or self-hosted options, and what happens to files after a downgrade, a removed seat or a cancelled contract.
AI features & rights to the work · What the vendor's AI does with the customer's files and what the customer may do with the AI's output: training on customer content and the opt-out, the models and where they run, commercial use of generated images, stock licences and indemnity.
European sovereignty · Who the contracting entity is, where design files, brand assets and AI prompts are stored and processed, and which subprocessors touch them. Independently sourced by the sovereignty pipeline.
Pricing transparency · Whether a buyer can compute the annual cost for their team from public pages alone — which seat types exist and what each may do, how viewers and guests are billed, how seats are added and trued up, AI credits, and the plan where SSO, admin controls and brand features begin.
Desk Booking & Hybrid Workplace rubric v1
| Criterion | The Workplace Manager v1.0 | The People Lead v1.0 | The Microsoft 365 Administrator v1.0 | The Works Council Member v1.0 | The Office Manager v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Desk, room & parking booking | 2.5 | 2.0 | 1.5 | 1.0 | 3.0 | 1.5 |
| Check-in, auto-release & booking rules | 2.5 | 1.0 | 1.5 | 1.5 | 2.0 | 2.5 |
| Hybrid work coordination | 1.5 | 3.0 | 1.0 | 1.5 | 2.0 | 1.0 |
| Occupancy analytics & employee privacy | 3.0 | 1.5 | 1.0 | 2.5 | 1.0 | 2.5 |
| Integrations, identity & administration | 2.0 | 1.5 | 3.0 | 1.0 | 1.5 | 2.0 |
| European sovereignty | 1.5 | 1.5 | 2.0 | 3.0 | 1.0 | 2.5 |
| Pricing transparency | 1.0 | 1.0 | 1.0 | 0.5 | 2.0 | 2.0 |
The judges and the criteria
The Workplace Manager · Runs workplace and facilities for a 900-person insurer with offices in Cologne, Munich and Vienna and 0.6 desks per employee since the move to hybrid work. Tuesdays are full, Fridays are empty, and the Munich lease is up in eighteen months. Wants desks, rooms and parking on real floor plans, no-shows released automatically, neighbourhoods per team, and occupancy figures built from check-ins rather than bookings, good enough to take to the board.
The People Lead · Head of People at a 250-person software company in Hamburg that asks for two office days a week and gets complaints that nobody else is there on them. Wants everyone to see who is coming in before they commute, team and anchor days, desks next to the colleagues they plan with, all of it inside Microsoft Teams where people already are, and nudges rather than a control system the works council would never sign.
The Microsoft 365 Administrator · Runs Microsoft 365, Entra ID and Intune for a 1,200-person manufacturer with six sites and forty room mailboxes nobody keeps tidy. Will not create accounts by hand: wants single sign-on and SCIM provisioning from Entra ID, room bookings synced both ways with Exchange, a Teams app and an Outlook add-in deployed centrally, room displays that are not a closed box, an API, audit logs, and a subprocessor list the security team can review.
The Works Council Member · Sits on the works council of a 2,000-person utility and chairs its IT committee. Under § 87(1) no. 6 BetrVG a desk booking system is a technical device that can monitor employees, so nothing goes live without a works agreement. Wants to know who sees who sat where, how long booking and check-in records are kept, whether reports stay anonymous below a minimum group size, whether presence can be hidden, and where the data is hosted and by whom.
The Office Manager · Office manager at a 70-person design and marketing agency in Leipzig with 40 desks, three meeting rooms and twelve parking spaces, and does it next to reception, purchasing and onboarding. The parking spreadsheet causes an argument every Monday. Wants a floor plan set up in an afternoon, booking from Slack and the phone, a fair rule for the parking spaces, desks released when someone does not show, and a monthly price read off the website.
The Skeptic · Has seen "real-time occupancy" that counted bookings and never a person, an auto-release nobody switched on because check-in annoyed the board, and a per-user price that doubled once rooms, parking and SSO were added. Asks how a no-show is detected, what the occupancy figures are built from, which room displays and sensors work without the vendor's own hardware, where the booking history is stored — and how it would leave.
Desk, room & parking booking · What can be booked and how easily: desks, meeting rooms, parking spaces and other resources (lockers, equipment, EV chargers), interactive floor plans per site and floor, desk attributes (monitor, standing desk, accessibility), neighbourhoods and zones, hot and assigned desks, recurring and multi-day bookings, booking for colleagues and guests, room booking synced both ways with Microsoft 365 or Google calendars, room displays, booking from the web, mobile apps, Outlook, Microsoft Teams and Slack, and several languages.
Check-in, auto-release & booking rules · How the booking is kept honest and fair: check-in by app, QR code, NFC, room display, Wi-Fi or sensor, auto-release of desks and rooms nobody checked in to, booking rules per site, area or group (how far ahead, how many days a week, maximum duration), approvals for restricted areas, assigned and permanent desks with release when the owner is away, fair allocation of scarce parking (lottery, rotation, priority for disabled or EV drivers), capacity limits per floor, and notifications and reminders.
Hybrid work coordination · How people plan office days together: a weekly view of who will be in the office, home office and absence, favourite colleagues and teams, team days and anchor days, booking next to colleagues, office events, attendance planning and office policies (for example two office days a week) with nudges rather than enforcement, the planner inside Microsoft Teams, Outlook or Slack, sync with absence and HR systems, and visibility settings so employees decide who sees their plans.
Occupancy analytics & employee privacy · What the data is worth for a real estate decision and how it treats the people it measures: utilisation per desk, room, zone, floor and site, booked against checked-in or measured use, peak days and times, no-show rates, room size against meeting size, occupancy sensors, badge, Wi-Fi or people counting data, scenario planning for consolidation, scheduled reports and export to Excel or BI tools, and on the other side aggregation, anonymisation and minimum group sizes, configurable retention and deletion of booking records, role-based access to personal data, and documentation a works council or data protection officer can work with.
Integrations, identity & administration · How the tool fits the company's systems and is run: Microsoft 365 and Exchange room mailboxes, Google Workspace, Microsoft Teams and Slack apps, single sign-on with Entra ID, Okta or Google (SAML or OIDC), SCIM user provisioning, HR system sync (Personio, SAP SuccessFactors, Workday), access control and badge systems, room displays and sensor hardware, a documented REST API and webhooks, several sites, countries and companies in one account, roles and delegated administration per site, audit logs, bulk import of users and resources, and implementation and support.
European sovereignty · Who the contracting entity and the parent company are, where employee profiles, bookings (who sat where on which day), presence and absence plans, parking licence plates and sensor data are stored and processed, and who the subprocessors are (hosting, email and push notifications, maps, analytics, support and payment tools, hardware and sensor clouds). Independently sourced by the sovereignty pipeline. A calendar integration with Microsoft 365 or Google that the customer already runs is part of the customer's chain; the vendor's own hosting and subprocessors are what is judged.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per tier by user, desk, bookable resource, site or device, what rooms, parking and analytics cost on top, which features (SSO, SCIM, HR sync, sensors, room displays, visitor management, API) need a higher tier or an add-on, hardware prices and their licences, platform or setup fees, minimum users or minimum spend, the free tier and its limits, minimum term and VAT.
Document Management (DMS) rubric v2
| Criterion | The GoBD Auditor v1.0 | The Records Manager v1.0 | The IT Integrator v1.0 | The Mittelstand Owner v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Capture, OCR & indexing | 1.0 | 2.5 | 2.0 | 3.0 | 1.0 | 1.0 |
| Versioning, permissions & audit trail | 2.0 | 2.5 | 1.5 | 1.0 | 2.5 | 1.0 |
| Audit-proof archiving & retention | 3.0 | 2.0 | 1.0 | 2.0 | 2.0 | 3.0 |
| Document workflows & integrations | 1.0 | 1.0 | 3.0 | 2.5 | 0.5 | 1.0 |
| Search, retrieval & exit | 1.5 | 3.0 | 2.5 | 1.0 | 1.0 | 2.5 |
| European sovereignty | 1.0 | 0.5 | 1.0 | 1.0 | 3.0 | 1.5 |
| Pricing transparency | 0.5 | 0.5 | 0.5 | 2.0 | 0.5 | 2.0 |
The judges and the criteria
The GoBD Auditor · Has sat through tax audits on the company side and knows that "GoBD-konform" on a homepage proves nothing. Wants the auditor's Testat with its scope and date, archived documents that cannot change, retention per document type, and a Z3 export the tax office can read.
The Records Manager · Owns the filing plan and gets the call when a contract from 2019 cannot be found. Wants metadata that is set at capture rather than typed later, version history with restore, search that respects permissions, and a bulk export that keeps metadata and versions together.
The IT Integrator · Connects the DMS to the ERP, DATEV and Microsoft 365 and maintains it afterwards. Wants connectors with a stated scope rather than a logo wall, a documented API with webhooks, single sign-on, and a migration path in and out that does not depend on the vendor's services team.
The Mittelstand Owner · Runs a forty-person company and wants the paper out of the office and the invoices approved without chasing anyone. Reads for e-invoice intake, an approval workflow that works without a consultant, and a price for users, storage and modules before the partner visit, not after.
The Data Protection Officer · Knows the DMS ends up holding personnel files, health certificates and customer contracts in one place. Asks where the cloud edition stores them, which AI provider reads them during capture, who the subprocessors are, and how GDPR deletion is reconciled with retention duties.
The Skeptic · Has read "revisionssicher" on every DMS homepage and a Testat on almost none. Distrusts "AI-powered capture" without a validation step, "seamless SAP integration" without a scope, and "no vendor lock-in" from a vendor that documents no export — and treats "price on request from your partner" as an answer.
Capture, OCR & indexing · How documents get in and become findable: scanning and email intake, OCR, classification and metadata extraction, and whether incoming e-invoices (XRechnung, ZUGFeRD) are read as structured data rather than as pictures.
Versioning, permissions & audit trail · Who may see and change which document, what happened to it, and whether earlier states can be recovered: version history, check-in and check-out, role- and attribute-based rights, and an audit trail of reads and changes.
Audit-proof archiving & retention · GoBD-compliant, revisionssicher archiving: immutability of archived documents, retention schedules and deletion, tax-audit data access, and the independent evidence behind the claim — scored on what is certified and documented, not on the word "GoBD-konform".
Document workflows & integrations · What happens to a document after it arrives: approval and invoice workflows, tasks and deadlines, and the connectors that tie the DMS to ERP, accounting, DATEV, Microsoft 365 and the rest of the stack.
Search, retrieval & exit · Finding documents again and taking them with you: full-text and metadata search, saved searches and mobile access, and whether documents, metadata, versions and audit trail can be exported in documented formats when the contract ends.
European sovereignty · Who the contracting entity and its owner are, where documents and their metadata are stored and processed in the cloud edition, and who the subprocessors are — including any AI provider that reads document content. Independently sourced by the sovereignty pipeline.
Pricing transparency · Whether a buyer can compute the cost of a given number of users, storage and modules — including cloud versus on-premises licensing, maintenance, implementation partner fees and price increases — from public pages alone.
E-Commerce Platforms & Shop Systems rubric v2
| Criterion | The Merchant v1.0 | The B2B Seller v1.0 | The Developer v1.0 | The Operations Lead v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Catalogue & checkout | 3.0 | 2.5 | 1.5 | 1.5 | 0.5 | 1.5 |
| Tax & German legal correctness | 1.5 | 3.0 | 1.0 | 1.5 | 1.5 | 1.5 |
| Extensibility & developer surface | 1.5 | 1.0 | 3.0 | 1.0 | 0.5 | 1.5 |
| Order operations & back office | 2.0 | 2.0 | 1.0 | 3.0 | 0.5 | 1.0 |
| Data ownership & exit | 1.0 | 1.0 | 2.5 | 1.5 | 2.5 | 2.0 |
| European sovereignty | 0.5 | 1.0 | 1.0 | 0.5 | 3.0 | 1.5 |
| Pricing transparency | 2.0 | 1.5 | 1.0 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The Merchant · Sells to consumers and lives on conversion. Wants a checkout that can be changed without a rebuild, the payment methods German shoppers expect including invoice, and promotions with rules. Judges price against contribution, not against a competitor's tier.
The B2B Seller · Sells to businesses across the EU: net prices, VAT-ID validation, reverse charge, customer-specific price lists and payment on account. Reads a shop that shows gross prices to a trade customer as one that has not met a trade customer.
The Developer · Will maintain this for five years. Wants local development, version control for themes, a plugin architecture with a dependency model, and upgrades that do not orphan the customisations. Reads a closed template editor as a future migration.
The Operations Lead · Ships the orders and handles the returns. Wants stock that is true across channels, partial shipments, carrier integrations with labels, and an ERP link the vendor maintains. A shop that cannot do a partial refund is a shop that has never had December.
The Data Protection Officer · The shop holds customers, addresses and buying histories, and the checkout is full of third parties. Wants the subprocessor list, consent handling that survives a complaint, deletion that executes against order history, and an answer on where the CDN and analytics sit.
The Skeptic · Knows the headline price is never the invoice here. Reads for the transaction fee, the apps that turn out to be mandatory, the hosting nobody mentioned, and what the platform charges to let a merchant leave with their own order history.
Catalogue & checkout · Products, variants, pricing rules and the path to payment — the part that either converts or does not.
Tax & German legal correctness · VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
Extensibility & developer surface · Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.
Order operations & back office · What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.
Data ownership & exit · Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.
European sovereignty · Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline. Dimensions the evidence does not establish are unknown, not non-EU.
Pricing transparency · Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.
E-Signature rubric v2
| Criterion | The Legal Counsel v1.0 | The HR Operations Lead v1.0 | The Revenue Operations Lead v1.0 | The Integration Engineer v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| eIDAS levels & trust services | 3.0 | 2.5 | 1.0 | 1.5 | 1.0 | 3.0 |
| Signer identification | 2.0 | 3.0 | 1.0 | 1.0 | 2.5 | 1.5 |
| Signing workflow & signer experience | 0.5 | 2.5 | 3.0 | 1.5 | 0.5 | 1.0 |
| Evidence, validation & retention | 3.0 | 1.5 | 1.0 | 2.0 | 2.0 | 2.0 |
| Integrations & API | 0.5 | 1.0 | 2.5 | 3.0 | 0.5 | 1.0 |
| European sovereignty | 1.5 | 1.0 | 0.5 | 1.0 | 3.0 | 1.5 |
| Pricing transparency | 0.5 | 2.0 | 1.5 | 0.5 | 0.5 | 2.0 |
The judges and the criteria
The Legal Counsel · Decides which contracts may be signed electronically and at which level. Wants SES, AdES and QES named per plan and country, the qualified trust service provider linked to the EU Trust List, and an audit trail with timestamps that still validates when the contract is disputed in eight years.
The HR Operations Lead · Sends two hundred employment contracts a year, many of them fixed-term and so under written form. Wants QES that a new hire can complete on a phone in ten minutes, identification that accepts the IDs applicants actually hold, bulk sending from templates, and a price per qualified signature known before the contract is signed.
The Revenue Operations Lead · Measures how long a quote takes to come back signed and where it stalls. Wants signing from inside the CRM, templates sales cannot break, reminders and signing order that run themselves, and a signer experience that needs no account, no app and no explanation.
The Integration Engineer · Embeds signing into the company's own portal and archives the result in the DMS. Wants a versioned API with webhooks and a sandbox, every signature level reachable through the API rather than only in the web app, and signed documents exported with their evidence intact.
The Data Protection Officer · Knows every signer who holds an ID card up to a camera hands biometric and identity data to a provider they never chose. Asks who performs the identification, where documents and ID data are stored, how long the audit trail keeps IP addresses, and who the subprocessors in the trust service chain are.
The Skeptic · Knows "legally binding" usually means a simple signature. Reads for the level the default plan actually signs at, the QTSP the provider does not operate itself, the per-QES and ident fees on top of the plan, the envelope limit, and "eIDAS-compliant" from a provider that names no trust service at all.
eIDAS levels & trust services · Which signature levels the platform offers — simple, advanced, qualified, and qualified seals — through which qualified trust service provider on the EU Trust List, for which countries and legal regimes (eIDAS, ZertES), and on which plans.
Signer identification · How the signer is identified for each level: email and SMS codes, video ident, eID card (Online-Ausweis), bank ident or EUDI wallet — who performs it, in which countries it works, and what happens to the ID data afterwards.
Signing workflow & signer experience · Getting a document out and back signed: templates and form fields, signing order and roles, bulk sending, reminders and delegation, signing without an account or app, mobile signing, and accessibility for signers.
Evidence, validation & retention · What proves a signature years later: the audit trail and certificate of completion, qualified timestamps, long-term validation (PAdES-LTV), validation reports, and how long signed documents and evidence are kept — and whether they can leave the platform.
Integrations & API · Signing from inside the systems where contracts are made: a documented API with webhooks and a sandbox, embedded signing, and connectors for Microsoft 365, CRM, HR, DMS and ERP systems.
European sovereignty · Who the contracting entity, the trust service provider and their owners are, where documents, audit trails and ID data are stored and processed, and who the subprocessors are. Independently sourced by the sovereignty pipeline.
Pricing transparency · Whether a buyer can compute the cost of their signing volume from public pages alone — plan prices, envelope or document limits, the per-signature price of AdES and QES, identification fees, API pricing and overage.
Email Marketing & Newsletter rubric v2
| Criterion | The CRM Manager v1.0 | The Deliverability Engineer v1.0 | The Data Protection Officer v1.0 | The Shop Owner v1.0 | The Integrator v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Campaigns & automation | 3.0 | 1.0 | 0.5 | 2.5 | 1.5 | 1.0 |
| Deliverability infrastructure | 2.0 | 3.0 | 1.0 | 2.0 | 1.5 | 1.5 |
| Consent, proof & tracking limits | 1.0 | 2.0 | 3.0 | 1.0 | 1.0 | 1.5 |
| List ownership, import & exit | 1.0 | 1.0 | 2.0 | 1.0 | 2.0 | 1.5 |
| Integrations & API | 2.0 | 1.0 | 0.5 | 3.0 | 3.0 | 1.0 |
| European sovereignty | 0.5 | 1.0 | 3.0 | 0.5 | 1.0 | 1.5 |
| Pricing transparency | 1.0 | 1.0 | 0.5 | 1.5 | 1.0 | 2.0 |
The judges and the criteria
The CRM Manager · Owns the lifecycle programme and measures it. Wants segmentation on real behaviour, journeys that branch, and testing that reports significance rather than a bigger number. Treats a tool that can only broadcast as a mailing list with invoicing.
The Deliverability Engineer · Cares about one number nobody publishes honestly: what reaches the inbox. Reads for authentication, IP and domain reputation, bounce discipline and sunsetting. Ignores every advertised delivery rate on principle — the infrastructure either is documented or it is not.
The Data Protection Officer · Signs off the tool that holds named people and records what each of them opened. Wants double opt-in with a proof that survives a complaint, tracking that can be switched off, and an answer to where the behavioural data lives that does not require a Schrems II argument.
The Shop Owner · Runs a shop where the newsletter is a revenue channel. Wants the shop connected properly — orders, carts, products flowing in, abandoned-cart and post-purchase flows out — and revenue attributed per campaign. Judges price against contribution, not against a competitor's tier.
The Integrator · Has to wire this into a stack that already exists. Wants a documented API with rate limits, webhooks that retry, a sandbox and a deprecation policy. Treats a partner-form integration page as a missing API, and reads "Zapier supported" as an outsourced one.
The Skeptic · Has seen every vendor claim 99% deliverability and GDPR compliance on the same page. Reads for the contact-tier staircase, the overage rate, the feature that begins two tiers up, and whether "EU hosting" covers the sending infrastructure or only the database.
Campaigns & automation · Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.
Deliverability infrastructure · Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.
Consent, proof & tracking limits · How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.
List ownership, import & exit · Whether the list and its history remain the sender's: import with attributes intact, full export including engagement history, deletion that executes, and no metering that prices leaving out of reach.
Integrations & API · The connection surface a newsletter lives on: shop and CRM systems, events in and out, webhooks, and an API somebody can build against without a partner agreement.
European sovereignty · Where subscriber data and behavioural tracking live, who the contracting entity is, and which subprocessors touch the send. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily. Dimensions not proven either way are unknown, not non-European.
Pricing transparency · Whether a sender can compute the real invoice for their list size and send volume — including overage, extra domains and automation limits — from public pages alone.
Employee Communication & Intranet rubric v1
| Criterion | The Internal Communications Lead v1.0 | The Frontline Operations Lead v1.0 | The Microsoft 365 Administrator v1.0 | The Works Council Member v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Reach & targeted announcements | 3.0 | 3.0 | 1.5 | 1.5 | 1.0 | 2.0 |
| Pages, documents & knowledge | 2.0 | 1.5 | 2.0 | 1.0 | 1.0 | 1.5 |
| Engagement, surveys & onboarding | 2.5 | 2.5 | 1.0 | 2.0 | 1.0 | 1.0 |
| Works council, private phones & privacy by design | 1.5 | 2.0 | 1.5 | 3.0 | 3.0 | 2.0 |
| Integration, identity & administration | 1.5 | 1.5 | 3.0 | 0.5 | 1.5 | 2.5 |
| European sovereignty | 1.5 | 1.0 | 2.0 | 2.0 | 3.0 | 2.5 |
| Pricing transparency | 1.0 | 2.0 | 1.0 | 0.5 | 0.5 | 2.0 |
The judges and the criteria
The Internal Communications Lead · Heads internal communications at a 3,000-person manufacturer with eleven sites in four countries, a third of the staff at desks and the rest on the shop floor. Sends the CEO letter, the site news and the safety notice, and wants each to reach the right people in their language, a read confirmation where the law asks for one, and figures that show the board who actually saw it — not an email open rate.
The Frontline Operations Lead · Runs HR and operations for a logistics company with 1,800 drivers, pickers and store staff, most of them without a company email address and many on temporary contracts. The notice board and the WhatsApp group are what works today. Wants a login a new picker manages on day one, onboarding before the first shift, content in six languages, and a per-user price that still makes sense for seasonal staff.
The Microsoft 365 Administrator · Looks after Entra ID, SharePoint and Teams for a company of 4,000, of whom 2,500 have no Microsoft licence. Has seen an intranet project end as a second SharePoint nobody maintains. Wants provisioning from the HR system including staff without email, SSO and SCIM, the app inside Teams rather than beside it, delegated admin rights per site, a real API, and an export when the contract ends.
The Works Council Member · Sits on the works council of a retail chain and negotiates the Betriebsvereinbarung for every new system under § 87 BetrVG. Will not sign off an app that tells a store manager who read a post at eleven at night, or that colleagues must install on their private phones to get their shift news. Reads the analytics pages first and asks what a manager can see about one person.
The Data Protection Officer · External data protection officer for several mid-sized employers. Reads the DPA and the subprocessor list before the feature pages: where push notifications, translation and the AI assistant send employee data, how long messages and read receipts are kept, how voluntary use on a private phone stays voluntary, and whether the parent company sits under a non-EU law that reaches the whole workforce's data.
The Skeptic · Has seen an "employee super app" that was a news feed with a chat bolted on, "reach every employee" that needed a company email to log in, and "95 percent adoption" that counted downloads. Reads "GDPR compliant" next to a push provider and a translation API that sit outside the EU, and per-user prices that apply only above a thousand seats — and asks what leaving would cost.
Reach & targeted announcements · How a message reaches every employee: a news feed and announcements on phone, browser and shared devices, targeting by site, department, role and language, access for staff without a company email address (invite codes, phone number, personnel number, QR codes, kiosk or shared devices), push notifications, mandatory reading with read confirmation, urgent alerts, scheduled posts, and reach analytics per message and audience.
Pages, documents & knowledge · What employees can look up: intranet pages and a content management system, documents and policies with versions and owners, search across content and connected systems, a people directory and org chart, multilingual content with machine translation of posts and pages, content review and expiry, and access from the app as well as the browser.
Engagement, surveys & onboarding · How the workforce answers back and gets started: comments, reactions and moderation, employee surveys and pulse checks with anonymity rules, recognition, user-generated posts and communities, onboarding journeys for new starters including those without a desk, event and campaign pages, and the measures the vendor offers to report engagement.
Works council, private phones & privacy by design · Whether the product can be rolled out under German co-determination and data protection: guidance or a template for a works agreement (Betriebsvereinbarung, § 87 BetrVG), no individual performance or behaviour monitoring by default, read and usage analytics aggregated or configurable, use on private phones without a company device (BYOD) with work and private data separated, quiet hours and availability settings, voluntary use without an employee email address, data minimisation and deletion, and accessibility.
Integration, identity & administration · How the product fits the company's systems and is run: Microsoft 365, SharePoint, Teams and Google Workspace integration, user provisioning from the HR system or directory (Entra ID, SAP SuccessFactors, Personio, Workday), single sign-on and SCIM, roles and admin rights by site or department, an API and webhooks, integrations with shift planning and payroll for frontline links, white-label apps, and an export of content and users when leaving.
European sovereignty · Who the contracting entity and the parent company are, where employee profiles, messages, files and usage data are hosted, and who the subprocessors are (hosting, push notifications, email and SMS delivery, video, translation, AI models, analytics, support). Independently sourced by the sovereignty pipeline; an employee app holds data on the whole workforce, often on private phones, so the whole chain counts, not only the database.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user or per employee, whether frontline and desk staff are priced differently, platform or base fee, which modules (intranet, employee email, surveys, translation, AI, a white-label app) cost extra, minimum seats and term, and setup and onboarding fees.
Employee Scheduling rubric v2
| Criterion | The Shift Manager v1.0 | The Operations Director v1.0 | The Payroll Officer v1.0 | The Works Council Advocate v1.0 | The Frontline Employee v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Roster building & demand planning | 3.0 | 3.0 | 1.0 | 1.0 | 1.0 | 1.5 |
| Working-time law & collective agreements | 2.0 | 2.0 | 2.5 | 2.5 | 1.5 | 2.5 |
| Mobile self-service for deskless staff | 2.5 | 1.5 | 0.5 | 1.5 | 3.0 | 1.0 |
| Works council & employee data | 1.0 | 1.0 | 1.0 | 3.0 | 2.0 | 1.5 |
| Payroll handoff & integrations | 1.0 | 2.0 | 3.0 | 0.5 | 0.5 | 1.5 |
| European sovereignty | 0.5 | 1.0 | 1.0 | 2.5 | 1.0 | 1.5 |
| Pricing transparency | 1.0 | 1.0 | 1.0 | 0.5 | 0.5 | 2.0 |
The judges and the criteria
The Shift Manager · Builds next week's roster for a restaurant or store on Thursday night and fields the sick calls on Saturday morning. Wants templates, qualifications that stop the wrong person landing on the till, open shifts staff can claim, and a rest period warning before publication rather than after the inspection.
The Operations Director · Answers for labour cost across thirty locations in retail, hospitality or care. Wants demand-based planning from real POS or occupancy data, labour cost against budget while the plan is still editable, and staff shared across sites. Reads "AI-powered scheduling" as a request to see the method.
The Payroll Officer · Turns the worked month into DATEV and answers for every surcharge. Cares about night, Sunday and holiday supplements from the Tarifvertrag, Minijob limits caught before the month closes, and corrections after the close. Treats "CSV export" as an admission that the handoff was never designed.
The Works Council Advocate · Co-determines how hours and overtime are distributed and how staff are monitored (BetrVG §87), and will not sign a works agreement for a system that watches more than it plans. Asks who sees absence reasons, what the app stores about location, what is logged and when it is deleted. Reads "performance insights" as a warning.
The Frontline Employee · Works part-time shifts next to a second job or a degree and never opens a laptop at work. Judges the product by its phone app: can she mark availability, swap a shift without three calls, see her hours, and read it in her own language. A roster she learns about from a photo in a group chat has failed.
The Skeptic · Has read a great many pages saying the product "supports" the Arbeitszeitgesetz and wants to know whether it blocks a violation, warns about it, or merely exports it. Reads for which tier the time clock and the DATEV export sit in, how seasonal staff are counted per employee, and what the forecasting "AI" actually uses as input.
Roster building & demand planning · How a plan gets built across locations, roles and qualifications — templates, staffing requirements, forecasting from sales or occupancy, and whether the product proposes a roster or only draws one.
Working-time law & collective agreements · Whether the roster knows the rules it is subject to — ArbZG rest periods and maximum hours, youth and maternity protection, Minijob earnings limits, Tarifvertrag and works-agreement rules, surcharges — and whether it enforces them, warns, or leaves them to the export.
Mobile self-service for deskless staff · What the employee on the shop floor actually gets: a mobile app to read the roster, enter availability, request and accept swaps, claim open shifts and clock in — in their language, on their own device or a shared one.
Works council & employee data · Whether the product can be introduced under co-determination (BetrVG § 87) — role-based visibility, what is logged, which monitoring can be switched off, retention of availability, absence and location data — and whether the vendor supplies what a works agreement needs.
Payroll handoff & integrations · How planned and worked hours, surcharges and absences reach payroll — DATEV, Lohn und Gehalt, the tax adviser — and how the roster connects to the POS, HR and time systems a shift business already runs.
European sovereignty · Where the employee data lives, who the contracting entity is, who the subprocessors are, and whether that is documented rather than assumed. Independently sourced by the sovereignty pipeline; weighted seriously here, because a scheduling tool holds availability, absence and often location data about employees who had no say in the vendor.
Pricing transparency · Whether a buyer can compute the real annual invoice for their headcount and locations — including the time clock, payroll export, forecasting and other modules sold as add-ons — from public pages alone.
ERP rubric v1
| Criterion | The Managing Director v1.0 | The Head of Finance v1.0 | The Operations Lead v1.0 | The Online Retailer v1.0 | The IT Integrator v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Finance, tax & compliance | 2.0 | 3.0 | 1.0 | 2.0 | 1.0 | 2.5 |
| Purchasing, inventory & order processing | 2.5 | 1.5 | 3.0 | 3.0 | 1.5 | 2.0 |
| Manufacturing, services & projects | 2.0 | 1.5 | 3.0 | 0.5 | 1.0 | 1.5 |
| Integration, API & data portability | 1.5 | 2.0 | 1.5 | 3.0 | 3.0 | 2.5 |
| Rollout, roles & operations | 3.0 | 1.5 | 2.0 | 1.5 | 2.5 | 2.0 |
| European sovereignty | 1.5 | 2.0 | 1.0 | 1.0 | 2.5 | 2.0 |
| Pricing transparency | 2.0 | 1.0 | 0.5 | 2.0 | 1.0 | 2.0 |
The judges and the criteria
The Managing Director · Runs a sixty-person wholesaler that outgrew an invoicing tool, two Excel stock lists and a shop backend nobody reconciles. Wants one system that goes live without stopping the business for a quarter, an implementation path and cost they can plan before signing, and a vendor that will still be there when the contract renews.
The Head of Finance · Closes the books for three companies every month and has retyped one supplier invoice too many. Wants incoming e-invoices read and matched to the purchase order, GoBD stated with a procedure documentation, DATEV for the tax adviser, intercompany postings that balance, and every figure traceable to the order and the person behind it.
The Operations Lead · Runs purchasing, two warehouses and a small assembly line, and is the one called when a delivery is promised from stock that is not there. Wants goods receipt booked on a scanner, stock per bin and batch, purchase proposals from real demand, and bills of materials that plan next week's production instead of a whiteboard.
The Online Retailer · Sells on a Shopware shop, Amazon and eBay from one warehouse with eight staff, and oversold a bestseller twice last Christmas. Wants stock synchronised across every channel, orders, labels and returns handled in one place, OSS VAT done right, and a price that does not jump with every thousand orders.
The IT Integrator · Looks after IT for a mid-sized manufacturer and has to connect the ERP to the shop, the bank, payroll, the BI tool and a supplier's EDI. Wants a public, versioned API with webhooks and a sandbox, roles and an audit log, hosting and subprocessors named, and a full export the day the company leaves.
The Skeptic · Has watched ERP projects run a year late and twice over budget, the partner's day rate the real price. Reads "ERP" that is an invoicing tool with a stock column, "GoBD-ready" with no procedure documentation, "open API" without a public reference, and a module price list that stops where implementation starts, and asks how the data gets out again.
Finance, tax & compliance · Whether the ERP keeps books a tax adviser and an auditor accept: general and subledgers, VAT per country, GoBD-compliant posting and archiving, e-invoices sent and received (XRechnung, ZUGFeRD), payments and dunning, and a DATEV export or a documented hand-over to the accountant.
Purchasing, inventory & order processing · The goods chain from supplier to customer: quotes, orders and order confirmations, purchasing and goods receipt, stock per warehouse and bin, batch and serial numbers, picking and shipping, returns — and whether each step posts through to the next document and to the ledger instead of being retyped.
Manufacturing, services & projects · The depth for the buyer's own business model: bills of materials, work orders and capacity planning for manufacturers; projects, time, resources and milestone billing for service firms; contracts, subscriptions and field service. A product is judged on the models it says it serves.
Integration, API & data portability · How the ERP connects and how the data gets in and out: a public API reference, webhooks, standard connectors for shops, marketplaces, banks, payroll, DATEV and BI, data import from the previous system, and a documented full export when the company leaves.
Rollout, roles & operations · What it takes to go live and run the system: implementation path (self-service, vendor, partner network), onboarding and training, roles and permissions, audit log, updates and customisation that survive them, support channels and service levels, and availability.
European sovereignty · Who the contracting entity and the parent company are, where the ERP data — customers, suppliers, prices, postings, employees — is hosted, and who the subprocessors are (cloud infrastructure, email, support tooling, AI features). Independently sourced by the sovereignty pipeline; an ERP holds a company's entire commercial record, so the ownership chain counts, not only the server location.
Pricing transparency · Whether a company can compute the real annual cost from public pages alone: price per user, module, company or transaction volume, which modules (accounting, warehouse, production, POS) cost extra, implementation and onboarding fees, minimum term, and what happens to the data on cancellation.
Error Tracking & APM rubric v1
| Criterion | The Agency Tech Lead v1.0 | The SaaS CTO v1.0 | The Mobile Team Lead v1.0 | The Site Reliability Engineer v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Error capture, grouping & triage | 3.0 | 2.5 | 3.0 | 2.0 | 1.0 | 2.0 |
| APM, tracing & profiling | 2.0 | 3.0 | 1.5 | 2.5 | 0.5 | 1.5 |
| Alerting, integrations & developer workflow | 2.0 | 2.5 | 2.0 | 3.0 | 1.0 | 1.5 |
| Data scrubbing, retention & volume control | 2.5 | 1.5 | 2.0 | 2.0 | 3.0 | 2.5 |
| Access control, security & the vendor's reliability | 1.0 | 2.0 | 1.0 | 3.0 | 2.5 | 2.0 |
| European sovereignty | 2.0 | 1.5 | 1.5 | 1.0 | 3.0 | 2.5 |
| Pricing transparency | 2.0 | 1.0 | 1.5 | 1.0 | 0.5 | 2.0 |
The judges and the criteria
The Agency Tech Lead · Technical lead at a web agency in Cologne with fourteen developers and forty client sites on Laravel, Shopware and WordPress, most on maintenance contracts. Wants every client in its own project with its own alert channel, PHP stack traces that show the query and the queued job, slow pages found before the client calls, request data scrubbed because the shops hold customer addresses, and a monthly bill that does not jump when one client's cron job throws the same exception a million times.
The SaaS CTO · CTO of a B2B SaaS company in Berlin with thirty-five engineers, twelve services in Go, Python and TypeScript on Kubernetes and a React frontend. Wants one trace from the click in the browser to the slow database call three services down, OpenTelemetry so the instrumentation is not locked to one vendor, errors routed to the team that owns the service, releases linked to the commits that broke them, and an EU region because the enterprise customers ask where their data goes.
The Mobile Team Lead · Leads the six-person app team of a fashion retailer in Hamburg, with an iOS and an Android app and a Flutter rewrite under way, released every two weeks. Wants native crashes symbolicated without a manual upload, crash-free users per release so a bad version is stopped in the store rollout, the device, OS and the last screens before the crash, logs from a customer's phone when support asks, and alerts when a new release crashes more than the last.
The Site Reliability Engineer · Site reliability engineer on the on-call rota of a payments platform in Amsterdam, woken at night when checkout latency climbs. Wants alerts on error rates and latency percentiles, not on every single exception, routed to PagerDuty with the trace attached, spike protection so an incident does not also blow the quota, SSO and audit logs for the auditors, and a vendor whose own status page and SLA say what happens when the monitoring is the thing that is down.
The Data Protection Officer · Data protection officer of a statutory health insurer whose member portal and app are built by an in-house team and two agencies. Knows that a stack trace or a request body can carry a member number, a diagnosis code or an IBAN. Reads the subprocessor list, asks where events are stored and for how long, wants scrubbing on the server and not only in the SDK, asks which AI model explains the errors and where, and needs a DPA before the first SDK goes into production.
The Skeptic · Has seen a "free tier" that ran out on the first busy Monday, an overage bill larger than the plan after one deploy looped on an exception, "EU hosting" with the support desk and the AI assistant in the US, and an SDK that slowed the app it was meant to watch. Asks what happens at the quota, how long events are really kept, whether the instrumentation works with another vendor after leaving, what the self-hosted edition leaves out — and what the second year costs.
Error capture, grouping & triage · What happens to an exception or crash: SDKs for the languages, frameworks and platforms a team runs (PHP and Laravel, JavaScript in the browser and Node, Python, Ruby, Java, .NET, Go, iOS, Android, Flutter, React Native), stack traces with source maps and symbolication, context (request, user, breadcrumbs, environment, local variables), grouping and custom fingerprints, deduplication, issue states (resolved, ignored, regressed), releases and deploy tracking, suspect commits, crash-free sessions and users for mobile apps, and search and filters over issues.
APM, tracing & profiling · How the product shows where time goes: transaction and endpoint timings with percentiles, slow database queries and N+1 detection, background jobs and queues, external HTTP calls, distributed tracing across services, OpenTelemetry ingestion, code-level profiling, frontend performance and Core Web Vitals (real user monitoring), host or container metrics beside the traces, anomaly detection on throughput and latency, and the link from a slow trace to the error it caused.
Alerting, integrations & developer workflow · How an error reaches the person who fixes it: alert rules on new issues, regressions, frequency and performance thresholds, notifications to email, Slack, Microsoft Teams, PagerDuty or Opsgenie, issue tracker integrations (Jira, GitHub, GitLab, Linear) that create and sync issues, source code links to the repository, deploy and release hooks from CI, a documented REST API and webhooks, a CLI, AI features that explain an error or suggest a fix (and which model runs them), and digest or weekly reports.
Data scrubbing, retention & volume control · What the product does with the personal and secret data an error carries and how volume is kept in check: scrubbing of passwords, tokens, card numbers and personal data in the SDK and on the server with configurable rules, IP address anonymisation, opting out of request bodies and user data, data retention per plan and deletion on request, sampling of errors and traces, rate limits, spike protection and quota caps per project, filters that drop events before they count, data export, and a self-hosted edition that keeps every event on the customer's own servers.
Access control, security & the vendor's reliability · Whether the service holds up in an audit and on the vendor's own bad day: organisations, teams and projects with roles, single sign-on (SAML or OIDC) and SCIM, two-factor authentication, audit logs, encryption in transit and at rest, security certifications and reports (ISO 27001, SOC 2), a security page and a vulnerability disclosure policy, the vendor's own public status page and incident history, a stated availability or SLA, and how ingestion behaves when the vendor is down (SDK buffering, no impact on the app).
European sovereignty · Who the contracting entity and the parent company are, where error events, stack traces, request data, traces, profiles, session data and account data are stored and processed, and who the subprocessors are (hosting, email and chat delivery, AI models that explain errors, support and payment tools). Independently sourced by the sovereignty pipeline. An EU data region the customer can choose counts for the product; a US default without a stated EU option does not. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per plan, what is included (errors or events, spans or transactions, replays, profiles, logs, seats, projects, retention), what overage costs per unit and whether it is capped, which features (SSO, audit logs, longer retention, EU region, AI) need a higher plan, host or seat based pricing for suites, the price of the self-hosted edition, annual versus monthly terms, and VAT.
Event Registration & Ticketing rubric v1
| Criterion | The Conference Organiser v1.0 | The Venue Promoter v1.0 | The Course Provider v1.0 | The Revenue Accountant v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Ticket shop, checkout & registration | 3.0 | 2.0 | 3.0 | 1.0 | 1.0 | 1.0 |
| Payments, payouts, fees & refunds | 1.5 | 3.0 | 2.0 | 2.5 | 0.5 | 2.5 |
| VAT, invoices & accounting handoff | 2.5 | 1.0 | 2.5 | 3.0 | 0.5 | 1.5 |
| Check-in, badges & on-site sales | 2.5 | 2.5 | 1.0 | 0.5 | 1.0 | 1.0 |
| Attendee data & the customer relationship | 1.5 | 2.0 | 1.5 | 1.0 | 3.0 | 3.0 |
| European sovereignty | 1.0 | 0.5 | 1.0 | 1.0 | 3.0 | 2.5 |
| Pricing transparency | 1.0 | 2.0 | 1.5 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The Conference Organiser · Runs the annual congress of a trade association: 900 attendees over two days, member and non-member prices, workshops with twenty seats each, and half the bookings made by an assistant for three colleagues at once. Wants the shop on the association's own site, invoices that a company's accounts payable accepts without a phone call, badges printed at the door from the same data, and session check-in that counts towards continuing-education points.
The Venue Promoter · Books bands and DJs into a 250-capacity club, four nights a week, and pays the artists their guarantee before the show. Needs the ticket money before the event rather than three weeks after, a fee that buyers pay on top of a twelve-euro ticket, a door app two volunteers can run on their phones without signal in the basement, and the buyers of last month's show on a list the club can mail, not the platform.
The Course Provider · Runs a small adult education business: evening courses over eight weeks, weekend workshops for coaches, and a few seminars that employers pay for. Wants registrations with the questions each course needs, a waiting list that fills a cancelled seat by itself, VAT that is right for exempt teaching and taxable workshops in one shop, invoices to employers in her own name, and cancellation rules her terms can point to.
The Revenue Accountant · Keeps the books for a concert promoter and two conference organisers and gets a payout statement each month that nets ticket sales, refunds and platform fees into one number. Wants to know who sold the ticket in whose name, which VAT rate applied to each ticket, a fee invoice kept apart from the revenue, credit notes for every refund, and an export that reaches DATEV without a spreadsheet in between.
The Data Protection Officer · Advises a federation of sports clubs whose events collect names, employers, dietary needs and the odd wheelchair note. Reads the ticket buyer terms before the feature list, because they say whether the platform is a processor or a controller with its own newsletter. Wants a DPA that names the organiser as controller, subprocessors with their countries, and attendee lists that are deleted after the event instead of kept for marketing.
The Skeptic · Has seen "free for free events" turn into a fee on every paid ticket that buyers blame the organiser for, payouts held until a week after the show, and a platform that emails the organiser's audience about a rival's concert. Reads "your data belongs to you" next to buyer accounts on the platform's own app, and an export that stops at names and emails — and asks what leaving would cost.
Ticket shop, checkout & registration · How a ticket or a registration is sold: ticket types and categories, member and early-bird prices, discount codes, bundles and add-ons, a shop embeddable on the organiser's own website or under its own domain, custom questions per ticket and per attendee, group and company bookings, capacity limits and waiting lists, reserved seating with a seating plan, recurring dates and course series, several languages, and an accessible mobile checkout.
Payments, payouts, fees & refunds · How the money moves: payment methods offered to buyers (cards, PayPal, SEPA direct debit, invoice, local methods), whether the organiser connects its own payment account or the platform collects as merchant of record, when the revenue is paid out (continuously, before the event, or after it), the per-ticket and payment fees and whether they can be passed on to the buyer, refunds of single tickets and of a cancelled event, ticket transfer and resale, and chargebacks.
VAT, invoices & accounting handoff · How ticket revenue reaches the books correctly: the VAT rate set per ticket or product (reduced rates for concerts and culture, exemptions for education and seminars), gross and net prices shown, invoices to buyers in the organiser's name with consecutive numbers, business buyers with company name and VAT ID, reverse charge for cross-border events, cancellation invoices and credit notes, the platform's own fee invoice, e-invoicing, and exports to DATEV or named accounting systems.
Check-in, badges & on-site sales · What happens at the door: a check-in app that scans tickets on phones or scanners, offline scanning and several devices at once, entrances and time slots, check-in lists by name, badge printing with attendee data and QR code, box office and on-site sales with card terminals, walk-in registration, session and room check-in at conferences, attendance certificates, and live attendance figures.
Attendee data & the customer relationship · Who the ticket buyer belongs to: whether the organiser is the controller of attendee data and the platform its processor, or the platform a controller in its own right; whether buyers must create an account on the platform; whether the platform markets other events to the organiser's buyers or lists the event on its own marketplace; consent for the organiser's newsletter collected in the checkout; messages to attendees; attendee data exportable at any time; and deletion and anonymisation after the event.
European sovereignty · Who the contracting entity and the parent company are, where attendee, order and payment data are hosted, and who the subprocessors are (hosting, payment providers, email delivery, analytics, support). Independently sourced by the sovereignty pipeline; attendee lists show who goes where and when, and a conference list holds names, employers and dietary or accessibility answers, so the whole chain counts, not only the database.
Pricing transparency · Whether an organiser can compute the real cost of an event from public pages alone: the fee per ticket or per registration (fixed, percentage or both), payment processing fees, whether fees are charged to the organiser or added to the buyer's price, free events, subscriptions or credit packs, payout and refund fees, add-ons (seating, white label, badges, box office), hardware rental, minimums and term, and VAT on the fees.
Expense Management rubric v1
| Criterion | The Travelling Employee v1.0 | The Office Manager v1.0 | The Controller v1.0 | The Finance Lead v1.0 | The Tax Adviser v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Receipt capture & expense claims | 3.0 | 2.5 | 1.5 | 2.0 | 2.5 | 2.0 |
| Company cards & spend control | 2.5 | 3.0 | 2.5 | 2.0 | 0.5 | 2.0 |
| Approval workflows & expense policy | 1.5 | 1.5 | 3.0 | 2.0 | 1.0 | 2.0 |
| Reimbursement, travel allowances & VAT | 3.0 | 1.5 | 2.0 | 2.0 | 3.0 | 2.0 |
| Accounting handoff & DATEV | 1.0 | 2.0 | 2.5 | 3.0 | 3.0 | 2.0 |
| European sovereignty | 1.0 | 1.0 | 1.5 | 1.5 | 2.0 | 2.5 |
| Pricing transparency | 1.0 | 2.0 | 0.5 | 1.0 | 1.0 | 2.0 |
The judges and the criteria
The Travelling Employee · A sales engineer on the road three days a week, with hotel bills in three currencies and a glovebox full of parking tickets. Wants to photograph a receipt and be done, mileage and per diems worked out without a spreadsheet, a company card so private money is never spent, and the money back on the account within days rather than at the end of the quarter.
The Office Manager · Runs the office of a thirty-person agency and is the one who chases missing receipts every month. Wants a card for each project lead with a limit she sets, software subscriptions on their own virtual cards, receipts that arrive without reminders, an export the tax adviser accepts, and a monthly price she can work out before the trial ends.
The Controller · Owns the travel and expense policy of a manufacturer with four legal entities and twelve hundred staff. Wants approval chains by cost centre and amount, limits checked before a claim is submitted rather than after it is paid, duplicates and private spending caught, budgets that cards draw from, and an audit trail that shows who approved and changed what.
The Finance Lead · Closes the month for a hundred-and-fifty-person Mittelstand company and books card spend from three banks. Wants card statements that reconcile by themselves, booking proposals with account, tax key and cost centre, receipts that reach DATEV with the booking, reimbursements paid in one SEPA run, and nothing that has to be retyped.
The Tax Adviser · A Steuerberaterin whose clients send their expenses from five different tools. Wants per diems and mileage at the statutory rates, the input VAT read from a receipt that actually qualifies for the deduction, substitute receipts only where the law allows them, scanned originals archived GoBD-compliant, and bookings that arrive in DATEV with the receipt image attached.
The Skeptic · Has seen "no more expense reports" turn into a card programme with a currency fee on every hotel abroad and a per-user price that counts everyone who ever logged in. Reads "DATEV integration" that means a CSV, "AI receipt scanning" with no word on where the receipts are read, card terms that leave the issuer unnamed, and subprocessor lists that stop at the hosting provider — and asks what leaving would cost.
Receipt capture & expense claims · How an expense gets into the system: a mobile app that photographs receipts, text recognition (OCR) that reads amount, date, merchant and VAT, receipts forwarded by email or pulled from suppliers, claims for out-of-pocket spending in any currency, mileage and trip entries, a substitute receipt (Eigenbeleg) when the original is lost, and duplicate detection.
Company cards & spend control · How spending is controlled before it happens: physical and virtual company cards with limits, single-use and subscription cards, limits by amount, merchant category and time, budgets per team or project, real-time notifications and receipt reminders — or, for a product that issues no cards of its own, live feeds from the company's existing cards with automatic receipt matching. The issuing institution and its licence count where cards are issued.
Approval workflows & expense policy · How the company's rules are applied: approval chains by amount, team, cost centre or project, delegation and deputies, an expense policy with limits per category and per country that the product checks, pre-approval of trips and purchases, roles and permissions, multi-entity set-ups, and an audit trail of who approved and changed what.
Reimbursement, travel allowances & VAT · How the employee gets money back and the company gets the tax right: reimbursement of approved claims by bank transfer or a SEPA payment file, mileage allowances and per diems at statutory rates per country (Verpflegungspauschalen, Kilometerpauschale, meal deductions), taxable and tax-free reimbursements separated for payroll, the input VAT captured per receipt for the deduction, and foreign VAT reclaimed.
Accounting handoff & DATEV · What reaches the books: export or sync to DATEV (DATEV format, DATEV Unternehmen online, Belegbilderservice) and to named accounting and ERP systems, booking proposals with account, tax key and cost centre, receipts that travel with the booking, card statements reconciled, a GoBD-compliant archive, an API and webhooks, and a complete export of claims, receipts and booking data.
European sovereignty · Who the contracting entity and the parent company are, where receipt, card and employee data are hosted, and who the subprocessors are (hosting, card issuer and processor, text recognition, open banking, email delivery). Independently sourced by the sovereignty pipeline; expense data is personal and financial at once and shows where employees travel, so the whole chain counts, not only the database.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user or per active user, platform or base fee, which modules (travel, reimbursements, DATEV or ERP connectors, extra entities) cost extra, card fees (physical cards, foreign transactions, currency conversion, top-ups), minimum seats and term, and setup.
Forms & Surveys rubric v1
| Criterion | The Market Researcher v1.0 | The Operations Manager v1.0 | The HR Lead v1.0 | The Academic Researcher v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Form & survey building | 2.5 | 2.5 | 1.5 | 3.0 | 1.0 | 1.5 |
| Distribution, response collection & workflows | 2.0 | 3.0 | 2.0 | 1.5 | 1.5 | 2.0 |
| Survey analysis & reporting | 3.0 | 1.0 | 2.5 | 3.0 | 1.0 | 1.5 |
| Consent, GDPR & respondent data | 1.5 | 2.0 | 3.0 | 2.0 | 3.0 | 2.5 |
| Hosting choice, teams & portability | 1.0 | 2.0 | 1.5 | 1.5 | 2.5 | 2.5 |
| European sovereignty | 1.5 | 1.0 | 2.0 | 1.0 | 3.0 | 2.5 |
| Pricing transparency | 1.5 | 2.0 | 1.0 | 0.5 | 0.5 | 2.0 |
The judges and the criteria
The Market Researcher · Runs customer and brand studies for a mid-sized consumer-goods company, three waves a year in four languages. Wants logic and quotas that keep the sample clean, invitations with reminders, cross-tabs and NPS without exporting to a spreadsheet first, and open answers grouped into themes before the board meeting.
The Operations Manager · Replaces paper and PDF forms at a service company: event registrations, supplier onboarding, damage reports with photos, order requests with a payment. Wants forms a colleague can build without IT, file uploads, a submission that lands in the right inbox and the CRM or spreadsheet without copy and paste, and a price that does not jump when the response count does.
The HR Lead · Runs the yearly engagement survey and pulse checks for a German company of six hundred, with the works council reading every question. Wants anonymity that is real and stated, results hidden below a minimum group size, reports per department that managers can read, and answers that are deleted when the agreement with the works council says so.
The Academic Researcher · Runs questionnaire studies at a European university and has to satisfy the ethics board before the first respondent sees a question. Wants complex branching, randomisation and validated scales, an informed-consent page that is part of the instrument, exports to SPSS and R with labels intact, and a licence the faculty can host or at least keep in the EU.
The Data Protection Officer · Signs off every form tool a department wants to use and has found health data in a feedback form before. Wants a data processing agreement and a subprocessor list on the vendor's own pages, consent fields and an anonymous mode that drops IP addresses, retention periods that delete on their own, EU hosting the customer can choose, and roles that keep responses away from people who do not need them.
The Skeptic · Has seen a "free form builder" put its logo on every customer survey and charge per response the month the campaign worked. Reads "GDPR compliant" with no data processing agreement behind it, "anonymous" surveys that still log IP addresses, "EU hosting" on the enterprise plan only, and AI analysis features with no word on where the answers go — and asks whether the responses can leave with the customer.
Form & survey building · What can be built without code: question and field types, conditional logic and branching, piping and hidden fields, calculations, multi-page forms and progress, templates, design and branding, multiple languages, and accessible output for respondents.
Distribution, response collection & workflows · How forms reach people and what happens to an answer: share links, embedding, QR codes, email invitations with reminders, contact lists and panels, offline or kiosk collection, file uploads, payments and signatures inside the form, notifications, approval or assignment of submissions, and automations that pass a response on to other tools.
Survey analysis & reporting · What the product does with the answers: live results and charts, filters and segments, cross-tabulation, NPS, CSAT and other standard scores, open-text and sentiment analysis, shareable dashboards and reports, and exports to the formats analysts use (CSV, Excel, SPSS, R).
Consent, GDPR & respondent data · What the product gives the customer to collect personal data lawfully: consent and privacy-notice fields, anonymous surveys that really drop IP addresses and identifiers, retention periods and automatic deletion, handling of access and erasure requests, encryption of responses, a data processing agreement, and controls over cookies and tracking on the form itself.
Hosting choice, teams & portability · What the customer may choose about where and how the product runs and who uses it: a selectable data region or EU-only hosting, self-hosting or an on-premise edition, team workspaces with roles and permissions, single sign-on, an audit log, custom domains and white-labelling, and a complete export of forms and responses that another tool can import.
European sovereignty · Who the contracting entity and the parent company are, where forms and responses are hosted, and who the subprocessors are (hosting, email delivery, payment providers, analytics, AI features). Independently sourced by the sovereignty pipeline; responses often carry personal and sometimes special-category data, so the whole chain counts, not only the database.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per plan and per user, response or submission limits and what happens above them, which features (logic, branding removal, SSO, EU hosting, analysis modules) need a higher plan, add-ons, minimum term and the free tier's limits.
HR Management rubric v2
| Criterion | The People Lead v1.0 | The Payroll Officer v1.0 | The Works Council Advocate v1.0 | The Data Protection Officer v1.0 | The IT Integrator v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Digital personnel file & data model | 3.0 | 1.5 | 1.0 | 1.0 | 2.0 | 1.5 |
| Payroll handoff | 2.0 | 3.0 | 0.5 | 0.5 | 1.5 | 1.5 |
| Absence & working-time | 2.5 | 2.5 | 2.5 | 1.0 | 1.0 | 1.0 |
| Recruiting & onboarding | 1.5 | 0.5 | 1.0 | 1.5 | 2.0 | 1.0 |
| Employee data protection & co-determination | 1.0 | 1.0 | 3.0 | 3.0 | 1.5 | 1.5 |
| European sovereignty | 0.5 | 0.5 | 1.5 | 2.5 | 1.0 | 1.5 |
| Pricing transparency | 1.0 | 1.0 | 0.5 | 0.5 | 1.0 | 2.0 |
The judges and the criteria
The People Lead · Runs HR for 400 people with two colleagues and is replacing a shared drive and eleven spreadsheets. Optimizes for the record being true and the month closing without chasing anyone. Buys breadth that actually connects, and is unmoved by a beautiful org chart sitting next to a manual vacation calculation.
The Payroll Officer · Closes payroll every month and answers to the tax adviser when it is wrong. Cares about one thing above all: whether the month leaves this system clean, with backdated changes, mid-month leavers and variable pay handled. Treats "CSV export" as a confession, not a feature.
The Works Council Advocate · Sits on the Betriebsrat and has to approve this rollout under BetrVG §87. Reads every feature for whether it can monitor behaviour, and asks what is logged, who can read it and what can be switched off. A tool that cannot answer those questions does not get installed, however good it is.
The Data Protection Officer · Answers for the most sensitive personal data the company holds, about people who cannot decline the processing. Wants retention that executes rather than promises, a published subprocessor list, and applicant data that deletes itself on the stated date. Treats an unpublished DPA as a finding.
The IT Integrator · Owns identity and has to make the HR system the source of truth for accounts. Wants SCIM provisioning, SSO that is not an enterprise upsell, and an API with documentation rather than a partner form. Judges onboarding by whether it can create the account, not by whether it has a checklist.
The Skeptic · Has watched three HR suites promise one system and deliver five modules with a shared logo. Reads every claim for what it does not say: which module the feature lives in, what it costs on top, and whether "integration" means a maintained connector or a documented endpoint someone could build against.
Digital personnel file & data model · The system of record: employee master data, the digital personnel file, org structure, custom fields, and whether history is kept rather than overwritten.
Payroll handoff · Whether the month closes cleanly into payroll — DATEV, Lohn und Gehalt, an in-house system or an external tax adviser — and how much of that is automated rather than re-typed.
Absence & working-time · Vacation, sickness and working-time recording — including whether the product meets the German recording duty (BAG 2022, ArbZG) rather than merely offering a timer.
Recruiting & onboarding · The join path — vacancy to signed contract to a person who has an account, equipment and a plan on day one.
Employee data protection & co-determination · How the product handles the most sensitive personal data a company holds — retention, deletion, role separation, subject rights — and whether it can pass a works council (BetrVG §87) rather than merely a procurement checklist.
European sovereignty · Where the data lives, who the contracting entity is, who the subprocessors are, and whether the answer is documented rather than assumed. Independently sourced by the sovereignty pipeline; scored here as the buyer would weigh it. Dimensions not proven either way are unknown, not non-European.
Pricing transparency · Whether an HR lead can compute the real annual invoice for their headcount — including the modules they actually need — from public pages alone.
Information Security rubric v2
| Criterion | The CISO v1.0 | The GRC Consultant v1.0 | The Drafted IT Officer v1.1 | The Lead Auditor v1.0 | The Evidence Integrator v1.0 | The Skeptic v1.1 |
|---|---|---|---|---|---|---|
| Asset & risk management depth | 3.0 | 2.0 | 1.5 | 1.5 | 1.0 | 1.0 |
| Controls, SoA & measures | 2.0 | 2.5 | 1.5 | 2.0 | 0.5 | 1.0 |
| Framework & standard coverage | 1.5 | 2.0 | 0.5 | 1.5 | 0.5 | 1.5 |
| Audit readiness & evidence | 1.0 | 1.5 | 1.0 | 3.0 | 1.0 | 1.5 |
| Integrations & automation | 1.0 | 0.5 | 1.5 | 0.5 | 3.0 | 0.5 |
| European sovereignty | 1.0 | 0.5 | 1.0 | 0.5 | 1.0 | 1.5 |
| Pricing transparency | 0.5 | 1.0 | 1.0 | 0.5 | 0.5 | 1.0 |
The judges and the criteria
The CISO · Owns the ISO 27001 certificate and the NIS2 exposure of a 400-employee company. Optimizes for a real risk backbone: methodology, inheritance, incident clocks, a statement of applicability that is never stale. Rejects checklist theater and risk registers that cannot answer who accepted what.
The GRC Consultant · Builds and runs ISMSs for a dozen clients at once. Optimizes for reusable control catalogs, multi-framework mapping that answers a control once, and templates that make client twelve cheaper than client one. Rejects single-tenant tools and frameworks bolted on as checklists.
The Drafted IT Officer · SME IT admin who became the information security officer by an email from management. Optimizes for guided setup, sane defaults, plain-language controls and a tool that runs alongside the day job. Rejects platforms that assume a security team and a consultant on retainer.
The Lead Auditor · Certifies ISMSs for a living and has seen every folder of screenshots. Optimizes for revision-safe history, an SoA generated from live control status, and a defensible answer to "show me the state on date X". Rejects audit trails assembled the week before the audit.
The Evidence Integrator · Believes evidence that is typed is evidence that is stale. Optimizes for connectors to the live estate — directory, CMDB, ticketing, cloud — continuous control checks, and an API with parity to the UI. Rejects data islands with a CSV drawbridge.
The Skeptic · Hunts "100% audit success" claims, framework logos that link nowhere, "coming soon" integrations sold as shipped, consulting bundled as software, and customer counts that disagree between pages. Exists to keep the rest of the bench honest.
Asset & risk management depth · The ISMS core: asset inventory, risk methodology (identification, assessment, treatment), inheritance of protection needs (Schutzbedarf) across assets, and security incident handling with its reporting deadlines.
Controls, SoA & measures · Control catalogues, the statement of applicability, measure tracking and internal audit — whether the control side of the ISMS is operable or a checklist.
Framework & standard coverage · Which regimes the product operationalises — ISO 27001, NIS2, TISAX/VDA ISA, DORA, BSI IT-Grundschutz, SOC 2 — and whether one control maps across them or each framework is a fresh island.
Audit readiness & evidence · Whether the system produces defensible proof: change history, evidence collection, and reports for auditors, authorities and management.
Integrations & automation · Whether the platform feeds from the real IT estate — directory import, CMDB, ticketing, scanners, SSO, API — and automates evidence collection instead of re-typing it.
European sovereignty · Where the security posture of the whole company actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, AI features, email, support tooling), DPA. The risk register is itself a target. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.
Pricing transparency · Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.
IT Service Management rubric v1
| Criterion | The Service Desk Lead v1.0 | The MSP Owner v1.0 | The Change & Configuration Manager v1.0 | The Municipal IT Lead v1.0 | The Solo IT Admin v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Service desk, incidents & requests | 3.0 | 2.5 | 1.5 | 2.0 | 2.5 | 1.5 |
| Change, problem & release management | 1.5 | 1.0 | 3.0 | 1.0 | 0.5 | 2.0 |
| Assets, CMDB & discovery | 2.0 | 2.0 | 3.0 | 1.5 | 2.0 | 2.0 |
| Self-service portal & service catalog | 2.5 | 1.5 | 1.0 | 2.0 | 2.5 | 1.0 |
| Deployment, integrations & multi-client operation | 1.5 | 3.0 | 1.5 | 2.5 | 2.0 | 2.5 |
| European sovereignty | 1.5 | 1.5 | 2.0 | 3.0 | 1.5 | 2.5 |
| Pricing transparency | 1.5 | 2.0 | 0.5 | 1.5 | 2.0 | 2.0 |
The judges and the criteria
The Service Desk Lead · Leads a team of eight agents at a machine builder with 1,400 employees across three plants in Germany and one in Poland. Most tickets still arrive by email, and the same printer and VPN questions come in every Monday. Wants incidents and requests told apart, SLAs that escalate on their own, a portal with a catalog people actually use, answers that deflect the Monday tickets, and reports the IT director reads without a spreadsheet.
The MSP Owner · Owns a managed service provider with twenty-two technicians and sixty client companies, from dental practices to a logistics firm with nine sites. Every client has its own contract, its own SLA and its own devices, and every hour has to end up on an invoice. Wants one desk with client data kept apart, the RMM and remote support tool connected, time and contracts billed, a portal per client, and a price per technician that still works when the team doubles.
The Change & Configuration Manager · Change and configuration manager at a regional bank that answers to BaFin and, since January 2025, to DORA. Chairs the weekly change advisory board and has to show an auditor who approved which change, which services it touched and which incident it caused. Wants change types with real approvals, risk read from a CMDB that knows how systems depend on each other, problem records tied to incidents, and an audit trail that can be exported.
The Municipal IT Lead · Runs IT for a district administration with 900 staff, schools included, on servers in the municipal data centre. Follows BSI IT-Grundschutz and buys through public tenders, and the data protection officer will not sign off staff and device data on a US cloud. Wants an on-premise or open-source edition that is documented and maintained, a portal for teachers and clerks, assets linked to tickets, and a contract and price list the procurement office can put into a tender.
The Solo IT Admin · The whole IT department of a 160-person engineering firm, with a part-time trainee on Thursdays. Requests come in by email, Teams and in the corridor, and the asset list is a spreadsheet nobody trusts. Has no time for an ITIL project: wants email and Teams turned into tickets, a simple portal with answers to the common questions, laptops and licences found automatically, a setup that takes days rather than months, and a price they can read off the website.
The Skeptic · Has seen "ITIL-certified" on a tool whose change management is a status field, a "CMDB" that is a list of devices without a single relationship, and an "AI agent" that searches the knowledge base. Reads that a product runs on premise and asks whether that edition gets the same features, which of the asset packs are extra, where the tickets and attachments are stored — and how ten years of ticket history would leave.
Service desk, incidents & requests · How tickets come in and get resolved: intake by email, portal, chat, phone and Microsoft Teams or Slack, incidents and service requests told apart, categories, priorities and an impact-urgency matrix, assignment rules and queues, SLAs with escalation and business hours, major incidents, templates and canned responses, a knowledge base for agents, automations and workflows, time tracking on tickets, and reports and dashboards on volume, resolution time and SLA compliance.
Change, problem & release management · The ITIL processes behind the ticket: problem records linked to incidents with root cause and known errors, change requests with standard, normal and emergency types, risk and impact assessment, approvals and a change advisory board, a change calendar with blackout periods, release and deployment records, links between changes, problems, incidents and configuration items, process certifications (PinkVERIFY, PeopleCert/AXELOS) named with their scope, and audit trails that a regulated buyer can show an auditor.
Assets, CMDB & discovery · What the product knows about the things tickets are about: an asset inventory of hardware, software and licences, a CMDB with configuration item types, attributes and relationships, a service map or dependency view, agent-based or agentless discovery, imports and synchronisation from Active Directory, Entra ID, Intune, SCCM, JAMF or a discovery tool, software licence compliance, contracts, warranties and the asset life cycle, and assets linked to users, tickets and changes.
Self-service portal & service catalog · What employees or clients see: a self-service portal with the service catalog, request forms with fields and approvals per service, ticket status and history for the requester, a searchable knowledge base for end users, announcements and outage notices, a virtual agent or chatbot, password reset or other automated fulfilment, branding and languages, single sign-on for the portal, access from Teams or a mobile app, and satisfaction surveys.
Deployment, integrations & multi-client operation · How the product is run and connected: a cloud edition and an on-premise or open-source edition with feature parity stated, system requirements and update cadence, a documented REST API and webhooks, integrations with Microsoft 365, Teams, Entra ID, Slack, monitoring tools, RMM and remote support tools, single sign-on (SAML, OIDC) and SCIM, roles and permissions, multi-client or multi-tenant operation with separated data for MSPs, time and contract billing for MSPs, a migration path from other tools, and a public status page.
European sovereignty · Who the contracting entity and the parent company are, where tickets, attachments, user directories and CMDB data are stored and processed, and who the subprocessors are (hosting, email delivery, AI features, support and payment tools). Independently sourced by the sovereignty pipeline; a service desk holds personal data about every employee and often credentials and network details, so the whole chain counts, not only the database. An on-premise or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per agent, technician or analyst and tier, whether requesters and portal users are free, what counts as an asset or node and how it is priced, which modules (CMDB, change, asset discovery, AI, ESM) cost extra, the on-premise licence or subscription and its maintenance, the free or open-source edition and paid support, minimum term, onboarding and setup.
Knowledge Base & Wiki rubric v1
| Criterion | The Operations Lead v1.0 | The IT Administrator v1.0 | The Support Knowledge Manager v1.0 | The Engineering Lead v1.0 | The Quality Manager v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Editor, structure & search | 3.0 | 1.5 | 2.0 | 3.0 | 1.5 | 1.0 |
| Verification, ownership & freshness | 2.5 | 1.5 | 3.0 | 1.5 | 3.0 | 1.5 |
| Permissions, SSO & administration | 2.0 | 3.0 | 1.0 | 1.5 | 2.5 | 1.5 |
| Help-center publishing & integrations | 1.5 | 1.0 | 3.0 | 2.5 | 0.5 | 1.0 |
| Import, export & self-hosting | 1.5 | 3.0 | 1.5 | 2.5 | 1.5 | 3.0 |
| European sovereignty | 2.0 | 2.5 | 1.5 | 1.5 | 2.0 | 2.5 |
| Pricing transparency | 2.0 | 1.5 | 1.5 | 1.0 | 1.0 | 2.0 |
The judges and the criteria
The Operations Lead · Head of operations at a 180-person machine builder in Baden-Württemberg, where onboarding, travel rules and the service hotline's answers live in a shared drive, three OneNote books and two colleagues' heads. Wants one place the whole company actually uses: an editor office staff manage without training, a search that finds the answer rather than the file, pages that name who keeps them current, and a price that does not double when the workshop gets read access.
The IT Administrator · Runs IT for a public utility with 900 staff whose Confluence Server held twelve years of pages until Atlassian ended its support. Was offered the cloud, read the subprocessor list and went looking instead. Needs a migration that keeps page trees, permissions and attachments, single sign-on against Entra ID with groups synced, an audit log the auditor accepts, and an edition they can run in the utility's own data centre if the works council or the regulator asks.
The Support Knowledge Manager · Owns the knowledge base of a Dutch SaaS company with customers in six languages and a support team of twenty-five. Writes once for agents and customers, publishes the public part as a help center on the company's own domain, and watches which searches find nothing. Wants review dates that nag the right expert, translations kept in step with the source, a widget inside the product, and articles that show up in the help desk next to the ticket.
The Engineering Lead · Leads a forty-person engineering team at a Berlin fintech that writes runbooks, architecture decisions and on-call guides. Writes in Markdown, links pages to Jira tickets and Slack threads, and has moved the team's docs twice. Wants fast search, code blocks and diagrams that render, an API and webhooks to generate pages from the pipeline, AI answers that cite their pages, and a full export the next tool can read.
The Quality Manager · Quality manager at a medical device supplier certified to ISO 9001 and ISO 13485, where every work instruction must be approved, versioned and read by the people it applies to. Today that means Word files, a sign-off sheet and an audit every spring. Wants approval workflows with named reviewers, read confirmations, review dates that expire pages, an audit trail they can export for the certifier, and permissions that keep drafts out of sight.
The Skeptic · Has migrated a wiki whose "export" turned out to be one PDF per page, watched a self-hosted edition announced as retired with two years' notice, and read "your data is never used for training" above a subprocessor list naming two AI providers. Asks what a full export contains, which model reads the pages and where, whether readers are billed like editors — and what leaving would cost.
Editor, structure & search · How knowledge is written, organised and found again: the editor (rich text, Markdown, tables, embeds, diagrams, code blocks), templates, spaces or collections and a page tree, linking and backlinks, real-time co-editing, comments and mentions, page history with restore, full-text search across pages and attachments with filters, search inside the chat tool, and AI answers that cite the pages they draw on.
Verification, ownership & freshness · Whether the content stays true: page owners or experts named per page, verification with a review date and a reminder when it lapses, approval or publishing workflows with drafts and reviewers, read confirmations for mandatory pages, analytics on views, searches without a result and stale pages, duplicate detection, archiving rules, and an audit trail of who changed and approved what.
Permissions, SSO & administration · Who may see and edit what, and how the administrator keeps control: roles and permissions per space and per page, restricted or private pages, guest and external access, groups synced from Azure AD/Entra ID, Google Workspace or LDAP, single sign-on (SAML, OIDC), SCIM provisioning, two-factor authentication enforced, an audit log of access and permission changes, and admin controls over sharing and public links. Where the data is hosted and certifications are scored under sovereignty.
Help-center publishing & integrations · How knowledge reaches people outside the editor: public or password-protected sites and help centers with a custom domain, branding and SEO controls, an in-app widget or contextual help, ticket deflection in a help desk, multilingual publishing, integrations with Slack, Microsoft Teams, Jira, Google Drive, help desks and CRMs, a browser extension, a documented REST or GraphQL API, webhooks, and an MCP server or connector for AI assistants.
Import, export & self-hosting · What arriving and leaving would cost: import from Confluence, Notion, Google Docs, Word and Markdown with structure, attachments and links kept, a full export of every space in an open format (Markdown, HTML, XML, PDF) with attachments and history, an API that reaches all content, a stated migration path from Confluence Server or Data Center, open-source code under a named licence, and a self-hosted or on-premise edition with its own documentation.
European sovereignty · Who the contracting entity and the parent company are, where pages, attachments and search indexes are stored and processed, and who the subprocessors are (hosting, CDN, search, email, support, payment, and the AI model provider that reads pages for answers and summaries, with whether content is used for training). Independently sourced by the sovereignty pipeline; a wiki holds internal processes, customer data and trade secrets, so the whole chain counts, not only the database. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user and tier, readers or guests free or charged, minimum seats, which features (SSO, SCIM, audit log, verification, help-center publishing, custom domain, AI answers, EU data residency) cost extra, the free tier and its limits, storage limits, the self-hosted edition's licence and support price, minimum term and setup or migration fees.
Lead Generation rubric v2
| Criterion | The SDR Team Lead v1.0 | The RevOps Manager v1.0 | The Data Protection Officer v1.0 | The ABM Marketer v1.0 | The DACH Sales Director v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Coverage, accuracy & freshness | 3.0 | 2.0 | 0.5 | 2.0 | 3.0 | 2.0 |
| Data sources & lawful basis | 1.0 | 1.5 | 3.0 | 1.0 | 2.0 | 2.0 |
| Visitor identification & intent signals | 1.5 | 1.0 | 2.0 | 3.0 | 1.5 | 1.0 |
| Prospecting workflow & outreach rules | 2.5 | 1.5 | 2.0 | 1.0 | 2.5 | 1.5 |
| CRM sync, enrichment & export | 2.0 | 3.0 | 1.0 | 2.0 | 1.0 | 1.0 |
| European sovereignty | 0.5 | 1.0 | 3.0 | 1.0 | 2.0 | 1.5 |
| Pricing transparency | 1.0 | 1.0 | 0.5 | 1.0 | 1.0 | 2.0 |
The judges and the criteria
The SDR Team Lead · Runs eight SDRs against a monthly meeting target. Wants filters that find the right buyer at the right company, emails that do not bounce, and direct dials that reach a person. Measures a database by connect rate, not by the record count on the homepage.
The RevOps Manager · Owns the CRM and cleans up after every tool sales buys. Wants sync with field mapping and deduplication, re-enrichment that updates rather than duplicates, objections that propagate into synced records, and exit terms that say what the company may keep.
The Data Protection Officer · Knows the company becomes controller the moment a list is exported. Wants the source and legal basis of every record stated, the Art. 14 notice actually sent, a removal route for the people in the database, and a visitor script that does not fire before consent.
The ABM Marketer · Works a list of three hundred target accounts and wants to know which of them are in market. Cares about company-level visitor identification, intent data with a named source, and alerts that reach the account owner while the signal is still warm.
The DACH Sales Director · Sells into German Mittelstand companies that are barely visible in US-built databases. Wants register-based company data, coverage stated for Germany, Austria and Switzerland rather than for "Europe", and a tool that knows a cold call under UWG §7 is not a growth hack.
The Skeptic · Has read "98% accuracy" and "GDPR-compliant data" on every homepage in the category. Reads instead for the refresh cadence, the credit-back rule for a bounced email, what a mobile number costs in credits, and the source the privacy notice admits to.
Coverage, accuracy & freshness · How much of the target market the database actually covers — judged on DACH and EU coverage as much as North American — and what the vendor documents about verification and refresh, because accuracy claims cannot be checked from outside.
Data sources & lawful basis · Where the personal data in the database comes from and on what legal basis it is processed — as evidenced on the vendor's own pages. Covers Art. 6(1)(f) legitimate interest, the Art. 14 notice to the people in the database, and whether they can find, object to and remove their record.
Visitor identification & intent signals · Identifying companies behind website visits and surfacing buying intent — scored on what is identified (company or person), how the tracking works, and whether the vendor states that its script needs consent under §25 TDDDG and how it behaves without it.
Prospecting workflow & outreach rules · Search, list building and outreach — and whether the product helps the buyer stay within UWG §7 and the GDPR once the list exists, rather than leaving the legal risk entirely with the customer.
CRM sync, enrichment & export · Getting the data into the systems where sales works — CRM sync, enrichment of existing records, API — and what happens to exported data, and to the buyer's access to it, when the subscription ends.
European sovereignty · Where a database of EU residents' personal data is held, who the contracting entity and controller are, and which subprocessors see it. Independently sourced by the sovereignty pipeline; weighted heavily here, because the product itself is personal data about people who never chose the vendor.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone — including credits per email, phone number and mobile, credit expiry, seat pricing, visitor-identification tiers and the API — in a category where the unit of billing is often invented by the vendor.
Learning Management (LMS) rubric v1
| Criterion | The Onboarding Lead v1.0 | The Compliance Officer v1.0 | The Customer Education Lead v1.0 | The Works Council Member v1.0 | The IT & HR Systems Admin v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Courses, learning paths & content standards | 2.5 | 1.5 | 2.5 | 1.0 | 1.5 | 1.5 |
| Compliance training, recertification & audit trail | 2.0 | 3.0 | 1.0 | 1.5 | 1.5 | 2.0 |
| Onboarding, extended enterprise & academies | 3.0 | 1.0 | 3.0 | 1.0 | 1.5 | 1.0 |
| Reporting, learner data & works council | 2.0 | 2.5 | 1.5 | 3.0 | 1.5 | 2.0 |
| Integrations, administration & portability | 2.0 | 1.5 | 2.5 | 1.0 | 3.0 | 2.5 |
| European sovereignty | 1.5 | 2.0 | 1.0 | 2.5 | 2.0 | 2.5 |
| Pricing transparency | 1.5 | 0.5 | 2.0 | 0.5 | 1.5 | 2.0 |
The judges and the criteria
The Onboarding Lead · Head of people development at a manufacturer with 1,400 employees across three plants in Germany and the Czech Republic, a third of them on shifts and without a company email address. Hires around 200 people a year, apprentices included. Wants new starters enrolled the day HR creates them, a path that works on a phone in German, Czech and English, tasks for the manager and the buddy, and to stop chasing completions by spreadsheet.
The Compliance Officer · Compliance officer at a regional bank supervised by BaFin, with 900 staff who complete anti-money-laundering, data protection, information security and code of conduct training every year. The last audit asked for proof of which version of a course each person had completed, and it took them a week to assemble. Wants assignments by role and entity, reminders that escalate to the manager, recertification that runs on its own, and an audit trail they can hand over as it is.
The Customer Education Lead · Runs customer education at a software company in Amsterdam that sells to 3,000 business customers and trains 120 implementation partners. Built the first academy on a course shop and outgrew it when partners needed their own portal and certifications that expire. Wants branded portals per audience, single sign-on from the product, paid courses with invoices, completions in the CRM, and a price that does not double when the academy finally works.
The Works Council Member · Member of the works council at a logistics company with 2,000 employees, responsible for IT systems and the works agreements that govern them. Knows that a system which logs who learned what, when and with which score can monitor performance, and that it needs their consent under §87(1) no. 6 BetrVG before it goes live. Reads which data is recorded, who sees individual results, whether time tracking can be switched off, and when records are deleted, before reading a single feature page.
The IT & HR Systems Admin · Runs identity and HR systems for a 600-person engineering services firm on Microsoft 365, Entra ID and Personio. Every new tool means another set of user accounts unless it supports SAML and SCIM. Wants users and departments synced from the HR system, learning inside Teams, a documented API, completions exportable for payroll and audits, and courses that leave as SCORM packages if the contract ends.
The Skeptic · Has seen "AI-powered learning" that meant a chatbot on top of a course list, "compliance-ready" that meant a completion checkbox, and "unlimited users" that ended at the first price review. Reads that a product is "GDPR-compliant" and asks where the learner records are stored, who can see each score, whether five years of completion history can be exported in a format the next system imports — and what leaving would cost.
Courses, learning paths & content standards · How learning is built and delivered: a course builder with video, documents, quizzes and assignments, import of SCORM 1.2 and 2004, xAPI, cmi5 and LTI packages, learning paths with prerequisites, assessments and question pools, certificates, blended learning with classroom or virtual sessions, a mobile app with offline access, multilingual courses and interface, accessibility (WCAG), AI-assisted authoring, and an off-the-shelf content library.
Compliance training, recertification & audit trail · Whether mandatory training can be run and proven: automatic assignment by role, department, location or legal entity, due dates with reminders and escalation to the manager, recurring recertification (annual data protection, IT security, anti-money-laundering, occupational safety instruction), attestations and acknowledgements of policies, attendance records for classroom sessions, course versioning with who completed which version, expiry of certificates, and audit-ready reports and exports for regulators or auditors.
Onboarding, extended enterprise & academies · Which audiences the product serves and how much runs without an administrator: onboarding journeys enrolled automatically from the HR system on the start date, manager and buddy tasks, frontline staff without a company email, multiple branded portals or tenants for customers, partners, franchisees or members, self-registration and SSO for external users, selling courses with checkout, subscriptions and coupons, partner certification programmes, and groups, branches and delegated administration.
Reporting, learner data & works council · What the system shows about learning and about each learner, and how far the customer can limit it: dashboards and reports for L&D, managers and auditors, custom and scheduled reports, which learner data is recorded (completions, scores, time spent, logins), role-based visibility so managers see only their team, aggregated or pseudonymised reports, the option to switch off time tracking or scoring, retention and deletion rules, learner access to their own data, and material for a works agreement under §87(1) no. 6 BetrVG or the vendor's description of codetermination. Where the data is processed is scored under sovereignty.
Integrations, administration & portability · How the system fits the company and what leaving would cost: single sign-on (SAML, OpenID Connect) and user provisioning (SCIM) from Entra ID, Google or Okta, sync with HR systems (Personio, SAP SuccessFactors, Workday), Microsoft Teams, Slack and video conferencing integrations, a documented REST API and webhooks, CRM and e-commerce connectors for academies, export of users, completions and certificates, export of courses as SCORM, open-source code, and a self-hosted or on-premise edition.
European sovereignty · Who the contracting entity and the parent company are, where learner data (names, completions, scores, certificates) is stored and processed, and who the subprocessors are (hosting, video streaming, email, AI features, support and payment tools). Independently sourced by the sovereignty pipeline; learner records are employee data, so the whole chain counts, not only the database. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per tier by active or registered users, what counts as an active user, what happens above the tier, which features (SSO, API, HR connectors, extra portals, e-commerce, custom domain, content library) cost extra, the free tier or trial and its limits, implementation and support fees, the self-hosted edition and its licence, minimum term and VAT treatment.
Marketing Automation rubric v2
| Criterion | The Demand Gen Lead v1.0 | The Sales Ops Manager v1.0 | The Data Protection Officer v1.0 | The Lifecycle Marketer v1.0 | The Solution Architect v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Journeys & orchestration | 3.0 | 1.0 | 0.5 | 3.0 | 2.0 | 1.5 |
| Lead scoring, routing & lifecycle | 2.5 | 3.0 | 1.5 | 1.0 | 1.5 | 1.5 |
| Channels & personalisation | 2.0 | 0.5 | 0.5 | 3.0 | 1.5 | 1.0 |
| Consent, tracking & profiling | 1.0 | 1.0 | 3.0 | 1.5 | 1.5 | 1.5 |
| CRM integration & data model | 2.0 | 3.0 | 1.0 | 1.5 | 3.0 | 1.5 |
| European sovereignty | 0.5 | 0.5 | 3.0 | 0.5 | 1.0 | 1.5 |
| Pricing transparency | 1.0 | 1.5 | 0.5 | 1.0 | 1.0 | 2.0 |
The judges and the criteria
The Demand Gen Lead · Owns pipeline contribution and is measured on it. Wants journeys that branch on real behaviour, scoring that sales trusts, and attribution that survives a quarterly review. Unmoved by a builder that demos beautifully and cannot say which journey sent yesterday's email.
The Sales Ops Manager · Owns the CRM and inherits every duplicate the platform creates. Wants field-level ownership defined, conflict rules that are configurable rather than folklore, and a sync error log somebody can act on before the pipeline report is wrong.
The Data Protection Officer · Sees a profiling system, not a mailing tool. Wants consent reproducible per person, tracking that can be switched off for someone who never agreed to it, deletion that removes derived scores as well as raw events, and scoring documented well enough to assess under Art. 22.
The Lifecycle Marketer · Thinks in cohorts and retention rather than in campaigns. Wants frequency capping across every journey, holdout groups so the effect is measurable, and personalisation drawn from the behavioural record rather than assembled by hand.
The Solution Architect · Has implemented three of these and knows where they fail: identity resolution, custom objects, and the API limit nobody mentioned. Wants a data model extensible without vendor services and a documented path from anonymous visitor to known contact.
The Skeptic · Reads for the contact-tier staircase, the tier where journeys actually begin, and the mandatory onboarding fee that never appears on the pricing page. Has watched "unlimited emails" mean unlimited within a sending limit described elsewhere.
Journeys & orchestration · Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
Lead scoring, routing & lifecycle · Scoring, qualification and handover to sales — including whether the customer can explain to a lead why the system decided what it decided.
Channels & personalisation · What the platform can send and personalise — email, SMS, push, on-site content, ad audiences — judged on what shares one profile and one suppression list.
Consent, tracking & profiling · The platform builds behavioural profiles of named people. Consent capture and proof, tracking that can be limited, retention, and whether automated decisions about individuals are documented and contestable.
CRM integration & data model · The join that decides the implementation: how the platform and the CRM stay in agreement about who a person is, and what happens when they disagree.
European sovereignty · Where behavioural profiles of named EU residents are processed, who the contracting entity is, and which subprocessors see them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which given the profiling is heavily. Dimensions the sources do not establish are unknown, not non-EU.
Pricing transparency · Whether a buyer can compute the real annual invoice for their contact base and send volume — including the tier where automation actually begins, overage, and mandatory onboarding — from public pages alone.
Mobile Device Management (MDM/UEM) rubric v1
| Criterion | The Solo IT Administrator v1.0 | The Mac Fleet Administrator v1.0 | The Field Operations Lead v1.0 | The MSP Technician v1.0 | The Information Security Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Enrolment & platform coverage | 3.0 | 2.0 | 3.0 | 2.0 | 1.5 | 2.0 |
| Configuration, apps & updates | 2.5 | 3.0 | 3.0 | 2.0 | 1.5 | 1.5 |
| Device security & compliance | 2.0 | 2.5 | 1.5 | 1.5 | 3.0 | 2.0 |
| Directory, API & administration | 1.5 | 2.0 | 1.5 | 3.0 | 1.5 | 1.0 |
| Hosting options, reliability & assurance | 1.0 | 2.0 | 1.5 | 1.5 | 2.5 | 2.5 |
| European sovereignty | 1.5 | 1.0 | 1.0 | 1.5 | 3.0 | 2.5 |
| Pricing transparency | 1.5 | 1.0 | 1.0 | 2.0 | 0.5 | 2.0 |
The judges and the criteria
The Solo IT Administrator · Is the whole IT department of an engineering consultancy with 120 staff in Bremen: iPhones for the project leads, Android phones for the site engineers, Windows laptops for everyone and a handful of Macs in marketing. Wants a new phone to set itself up out of the box, mail, Wi-Fi and VPN pushed without a desk visit, updates that install on time, a lost phone wiped from the browser, and one console he can learn in an afternoon rather than four.
The Mac Fleet Administrator · Runs 350 MacBooks and 200 iPhones at a software company in Hamburg whose new hires get a sealed box from the reseller and work by lunch. Lives in Apple Business Manager and Automated Device Enrollment, wants FileVault keys escrowed, Platform SSO with Entra ID, apps and patches from a maintained catalogue, and support for a new macOS on the day Apple releases it, not three weeks later. Reads release notes before the homepage.
The Field Operations Lead · Leads operations at a facility services company with 600 cleaners and technicians across North Rhine-Westphalia, who share rugged Android handsets and tablets per shift. Needs devices locked to the time-recording and work-order apps, zero-touch enrolment with Knox or Android Enterprise, apps updated overnight, a dropped device replaced in a day without IT on site, and remote view when a foreman calls in because a screen shows something nobody understands.
The MSP Technician · Works for an IT service provider in Nuremberg that looks after the devices of forty small firms, from a dental practice with six iPads to an architect with eighty laptops. Wants one partner console with a tenant per customer, roles so an apprentice can reset a passcode but not wipe a fleet, policy templates copied between tenants, an API and webhooks for the ticket system, and a price per device he can put on a monthly invoice.
The Information Security Officer · Information security officer of a municipal utility that counts as critical infrastructure, with staff who want their own phones for mail and the on-call app. Needs encryption and compliance proven per device for the auditor, BYOD with a work profile the works council can sign off because the admin cannot see private apps or the location, a data processing agreement and subprocessor list, and an on-premise or German-hosted option if the cloud one stores the inventory abroad.
The Skeptic · Has seen "manage every device" that meant iPhones fully and Windows through a script, "zero-touch" that needed a reseller the company did not use, a BYOD profile that showed the admin every installed app, and a per-device price that doubled once the security add-on was required. Asks what leaving costs — whether devices must be wiped to move to another MDM — how long a new iOS took to be supported last year, where the inventory lives, and what the second year costs.
Enrolment & platform coverage · How devices get under management and which ones: the operating systems managed (iOS and iPadOS, macOS, Android, Windows, ChromeOS, Linux, tvOS) and to what depth, zero-touch enrolment through Apple Business Manager (Automated Device Enrollment), Android Enterprise zero-touch and Samsung Knox Mobile Enrollment and Windows Autopilot, QR code and email enrolment, BYOD user enrolment and the Android work profile, supervised and corporate-owned modes, shared devices, rugged and dedicated devices, and migration from another MDM.
Configuration, apps & updates · What the administrator can push and keep current: configuration profiles and policies (Wi-Fi, VPN, email, certificates through SCEP or ACME, restrictions), scripts and custom settings, an app catalogue with Apple Volume Purchase and managed Google Play, in-house app distribution and a self-service portal, OS update enforcement with deadlines, third-party app patching, kiosk and single-app mode, content and document distribution, remote control or remote view for support, and inventory with custom attributes.
Device security & compliance · Whether a lost or non-compliant device stays harmless: passcode and encryption enforcement (FileVault, BitLocker, Android encryption) with escrowed recovery keys, remote lock, lost mode and full or selective wipe, compliance rules with automatic actions, conditional access to mail and cloud apps, security baselines such as CIS, jailbreak and root detection, mobile threat defence integration, separation of work and private data on BYOD with what the admin can and cannot see, location tracking that can be switched off, and compliance reports for audits.
Directory, API & administration · How the MDM fits the company and the people who run it: directory integration with Microsoft Entra ID, Google Workspace, Okta or LDAP and Active Directory, single sign-on (SAML or OIDC) for admins and SCIM provisioning, roles and permissions per site or department, audit logs, multi-tenancy for service providers with sub-accounts, a documented REST API and webhooks, integrations with helpdesk, ITSM and SIEM tools, reports and dashboards, and admin notifications.
Hosting options, reliability & assurance · Whether the service holds on a bad day and in an audit: cloud, private cloud and on-premise or self-hosted editions, data centre regions named by country, a public status page and incident history, a stated availability or SLA, backup and recovery of the management server, release notes and the record of support for new OS versions, support channels and hours, security certifications (ISO 27001, SOC 2, BSI C5) with their scope, penetration tests, and a vulnerability disclosure process.
European sovereignty · Who the contracting entity and the parent company are, where the device inventory, location data, user accounts, app lists, logs and support data are stored and processed, and who the subprocessors are (hosting, push and email delivery, analytics, AI assistants, support and payment tools). Independently sourced by the sovereignty pipeline. Apple's, Google's and Microsoft's push and enrolment services are part of what managing their devices means and are not counted against a product; where the MDM's own data is stored and who processes it is. An on-premise or self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per device or per user and per plan, what a user with three devices pays, which features (security, patching, remote control, identity, kiosk) are in which plan or cost extra, minimum device counts, monthly or annual billing, on-premise licence and maintenance prices, education, non-profit and MSP pricing, onboarding fees, minimum term and VAT.
On-Call & Incident Management rubric v1
| Criterion | The SRE Lead v1.0 | The IT Operations Manager v1.0 | The MSP NOC Lead v1.0 | The ICT Risk Officer v1.0 | The Engineering Manager v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| On-call schedules, rotations & escalation | 2.5 | 3.0 | 2.5 | 1.5 | 3.0 | 2.0 |
| Alert delivery, routing & noise reduction | 2.5 | 3.0 | 3.0 | 1.5 | 2.0 | 2.5 |
| Incident response, status pages & post-incident review | 3.0 | 1.5 | 1.5 | 2.5 | 2.0 | 1.5 |
| Integrations, API & administration | 2.5 | 2.0 | 3.0 | 1.5 | 1.5 | 1.5 |
| Platform reliability, security & compliance | 2.0 | 2.5 | 2.0 | 3.0 | 1.5 | 2.5 |
| European sovereignty | 1.5 | 2.0 | 1.5 | 3.0 | 1.5 | 2.5 |
| Pricing transparency | 1.0 | 1.5 | 1.5 | 0.5 | 2.0 | 2.0 |
The judges and the criteria
The SRE Lead · Leads site reliability at a Berlin SaaS company with sixty engineers in eight product teams, Prometheus and Grafana for metrics, Sentry for errors and everything discussed in Slack. Wants an incident declared with one command, a channel with roles and a timeline, the status page updated from the same place, alerts grouped so one database outage does not page five teams, schedules kept in Terraform, and a postmortem that writes its first draft.
The IT Operations Manager · Runs IT operations for a packaging manufacturer with 900 staff and three plants running around the clock, with Checkmk and PRTG watching servers, networks and the production line. Five administrators share a weekly standby. Wants a Checkmk alert to become a phone call that the right person acknowledges by keypad, the deputy called after ten minutes, no pages during planned maintenance, and an alerting service that still works when the plant's own network is the thing that is down.
The MSP NOC Lead · Leads the network operations centre of a managed service provider in Nuremberg that looks after sixty mid-sized customers, with Zabbix, Microsoft Sentinel and Autotask in the stack. Wants alerts routed by customer and contract hours, tickets opened and closed in the PSA without anyone copying text, a separate on-call rota for the night shift and for each key account, one customer never seeing another's data, and a monthly report per customer on response times.
The ICT Risk Officer · ICT risk officer at a Frankfurt payments company supervised by BaFin, where DORA requires major ICT incidents to be classified and reported within hours. The incident tool is itself an ICT third-party service in the register. Reads the subprocessor list, asks where incident timelines and the AI summaries of the response channel are processed, wants an SLA, audit logs and a DORA addendum in the contract, and needs the timeline to hold up as evidence for the regulator.
The Engineering Manager · Engineering manager at a logistics software company in Hamburg with developers in Germany, Portugal and Poland, where the works council has agreed an on-call policy with paid standby hours and rest periods after a night call. Wants a follow-the-sun rota across three time zones, swaps from the phone, on-call hours exported to payroll each month, a warning when the same person is paged three nights running, and a price per responder that does not charge for the managers who only read along.
The Skeptic · Has seen "never miss an alert" from a pager that was down in the same cloud region as the outage it should have reported, "unlimited notifications" that meant twenty SMS a month outside the US, and an "AI incident assistant" that sent the whole response channel to a model nobody named. Asks which carriers deliver the calls, what the SLA pays, whether schedules and history can be exported when leaving — and what the plan costs once the stakeholders need seats.
On-call schedules, rotations & escalation · Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.
Alert delivery, routing & noise reduction · Whether the alert reaches a human and only the right one: notification by push, SMS, voice call, email and chat, critical alerts that override do-not-disturb on iOS and Android, personal notification rules with retries and fallbacks, acknowledgement by app, SMS reply or keypad, delivery receipts, live call routing for a hotline, routing rules by service, severity, payload and time, deduplication, grouping and correlation of related alerts, suppression and maintenance windows, heartbeats for silent failures, and inbound email and webhook endpoints.
Incident response, status pages & post-incident review · What happens once the alert is a real incident: declaring an incident from Slack, Microsoft Teams or the app, a dedicated channel and video bridge, incident roles and commander, severities and incident types, runbooks, tasks and automated workflows, stakeholder updates, public and internal status pages with subscribers, a timeline, post-incident reviews and postmortem templates with follow-up actions, analytics such as MTTA and MTTR, and AI features that summarise, suggest causes or draft the review.
Integrations, API & administration · How the tool fits the stack and the organisation: inbound integrations with monitoring and observability tools (Prometheus, Grafana, Datadog, Zabbix, Checkmk, PRTG, Azure Monitor, CloudWatch, Sentry), outbound integrations with chat, ticketing and ITSM tools (Slack, Microsoft Teams, Jira, ServiceNow, ConnectWise, Autotask), bidirectional sync, a documented REST API, webhooks and a Terraform provider, teams and services, roles and permissions, single sign-on (SAML or OIDC) and SCIM, audit logs, multi-tenant or customer separation for service providers, and migration help from other tools.
Platform reliability, security & compliance · Whether the pager works on the day everything else is down and holds up in an audit: an architecture independent of the customer's own cloud, multi-region or multi-zone hosting with failover, a stated availability or SLA with credits, the vendor's own public status page and incident history, delivery via redundant carriers, encryption in transit and at rest, security certifications (ISO 27001, SOC 2, BSI C5), penetration tests, data retention and deletion, audit trails, and what the vendor documents for DORA, NIS2, HIPAA or other regulated customers.
European sovereignty · Who the contracting entity and the parent company are, where alerts, incident timelines, chat transcripts, contact data, phone numbers and account data are stored and processed, and who the subprocessors are (hosting, SMS and voice carriers, push services, email delivery, AI summary and transcription models, analytics, support and payment tools). Independently sourced by the sovereignty pipeline. Telephony and push providers needed to reach a responder in another country are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user or responder and per plan, whether stakeholders and viewers are free, how many SMS and voice notifications are included and what the rest cost per country, which features (incident response, status pages, AI, live call routing, SSO, audit logs) are add-ons or in higher plans, platform fees, minimum seats, annual versus monthly billing, and the currency and VAT treatment.
Online Whiteboard rubric v1
| Criterion | The Workshop Facilitator v1.0 | The Product Team Lead v1.0 | The Microsoft 365 Admin v1.0 | The Works Council Member v1.0 | The Public-Sector Project Lead v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Canvas, templates & content | 2.5 | 2.5 | 1.0 | 0.5 | 1.5 | 1.0 |
| Workshop facilitation & participation | 3.0 | 2.0 | 1.0 | 1.0 | 2.0 | 1.0 |
| Integrations, import & export | 1.5 | 3.0 | 2.5 | 1.0 | 1.0 | 2.5 |
| Sharing, permissions & administration | 1.5 | 1.5 | 3.0 | 2.5 | 2.0 | 2.0 |
| Security, AI controls & deployment | 1.0 | 1.0 | 2.5 | 3.0 | 2.5 | 2.5 |
| European sovereignty | 1.5 | 1.0 | 2.0 | 3.0 | 3.0 | 2.5 |
| Pricing transparency | 2.0 | 1.5 | 1.0 | 0.5 | 1.5 | 2.0 |
The judges and the criteria
The Workshop Facilitator · Freelance facilitator and agile coach who runs three to four remote workshops a week for clients from car suppliers to city utilities, most of them with participants who have never used the tool and will not create an account. Builds the board the evening before from their own templates. Needs guests in by link, a timer, anonymous brainstorming, dot voting and a way to pull twenty people to the same frame, and a client who asks where the board is stored before the session starts.
The Product Team Lead · Leads three product teams at a logistics software company in Hamburg, with developers in Poland and Portugal. The board is where story maps, quarterly planning, architecture sketches and retrospectives happen, and the outcome has to land in Jira without anyone retyping it. Wants diagrams and sticky notes on one board, a two-way sync with the tickets, an API for the team's own automation, and an export that still makes sense when the company switches tools.
The Microsoft 365 Admin · Runs Microsoft 365 and Teams for a machine builder with 2,400 staff and found 600 free whiteboard accounts on company addresses, boards shared publicly by link among them. Has to decide between the whiteboard that comes with Teams and a licensed one. Wants single sign-on, SCIM, domain capture of the existing accounts, sharing rules set once for everyone, audit logs in the SIEM, retention rules, and an AI that can be switched off until legal has read the terms.
The Works Council Member · Sits on the works council of an insurance company and leads its IT committee, which has to agree before any tool that could show who did what goes live (§87(1) no. 6 BetrVG). Reads the admin documentation before the feature page: whether contributions and time on board are tracked per person, what a manager can see, how long logs are kept, what the AI does with retrospective notes, and where the boards are stored and by whom.
The Public-Sector Project Lead · Leads the digitalisation programme of a state ministry and runs workshops with municipalities, agencies and external consultants. The data protection officer has ruled out US-hosted boards, and procurement asks for BSI C5 or an on-premises installation in the state data centre. Needs guests from other authorities without accounts, a board that works in the browser on locked-down machines, an accessibility statement, and a contract the procurement office can sign.
The Skeptic · Has seen a free plan with "unlimited members" that locks every board after the third, "EU data residency" that covers the database but not the AI, and an export that turns two years of workshops into a stack of PNGs. Reads that a product is "enterprise-grade" and asks who can open a board shared by link, whether the boards train anyone's model, what the export keeps — and what leaving would cost.
Canvas, templates & content · What can be put on the board and how fast: an infinite canvas, sticky notes, text, shapes and connectors, freehand drawing and pen input, frames and sections, images, files, documents and video embedded on the board, tables, mind maps, diagrams and flowcharts, a template library for workshops, retrospectives and planning, own templates for the organisation, search across boards, performance on large boards, and AI that clusters, summarises or generates content.
Workshop facilitation & participation · What it takes to run a session on the board: guests who join without an account, a timer, voting and dot voting, a private or anonymous mode for notes, bringing everyone to the facilitator's view (summon, follow), a presentation or frame mode, locking objects, reactions, breakout areas, an agenda or session plan, built-in audio or video or the call apps the board runs inside, participant limits, and accessibility for participants (keyboard, screen reader, contrast).
Integrations, import & export · How the board connects to the work around it and whether the content can leave: apps for Teams, Zoom, Webex, Slack and Google or Microsoft files, a two-way sync with Jira, Azure DevOps or other work tools, embedding boards in Confluence, SharePoint or intranets, a documented REST API and webhooks, import from Miro, Mural or other boards and from CSV or images, and export as PDF, image, CSV of the notes or an editable file another tool can open.
Sharing, permissions & administration · Who can see and change a board and how the organisation controls it: sharing by link with expiry and password, guest and external-user rules, roles per board, project and team, default sharing settings set by the admin, single sign-on (SAML, OpenID Connect), user provisioning (SCIM), domain capture and control of shadow accounts, audit logs, content retention and legal hold, transfer of boards when a person leaves, and admin reports.
Security, AI controls & deployment · How the content of the boards is protected and where the product can run: encryption in transit and at rest, customer-managed encryption keys, a dedicated or private-cloud tenant and an on-premises edition, AI features that the admin can switch off and that do not train on customer boards, which AI providers process board content, data loss prevention, deletion of boards and accounts with stated periods, and whether individual activity (logins, contributions, time on board) is tracked and shown to managers, with a statement for works councils. Who processes the data and where, and the certifications, are scored under sovereignty.
European sovereignty · Who the contracting entity and the parent company are, where boards, files and user data are stored and processed, and who the subprocessors are (hosting, CDN, real-time collaboration servers, AI providers, email, support and payment tools). Independently sourced by the sovereignty pipeline; boards hold personal data of participants and often of customers, so the whole chain counts, not only the database. An on-premises or self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user and tier, how guests, viewers and external participants are counted, limits of the free plan (number of boards, objects, members), which features (SSO, SCIM, audit logs, EU data residency, AI credits, on-premises) cost extra, the enterprise tier's price or minimum, annual versus monthly billing, minimum seats and term.
Password Management rubric v2
| Criterion | The CISO v1.0 | The Identity Engineer v1.0 | The Compliance Auditor v1.0 | The SME Owner v1.0 | The DevOps Engineer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Encryption model & independent audits | 3.0 | 2.0 | 1.5 | 1.5 | 2.0 | 3.0 |
| Sharing, roles & recovery | 2.0 | 2.0 | 2.0 | 3.0 | 1.0 | 1.5 |
| SSO, directory sync & provisioning | 2.0 | 3.0 | 1.0 | 1.0 | 1.5 | 2.5 |
| Audit logs, policies & reporting | 2.0 | 1.5 | 3.0 | 1.0 | 1.0 | 1.5 |
| Hosting choice, offline access & export | 1.5 | 1.0 | 1.0 | 1.5 | 3.0 | 1.5 |
| European sovereignty | 1.5 | 1.0 | 3.0 | 1.0 | 2.0 | 1.5 |
| Pricing transparency | 0.5 | 0.5 | 0.5 | 2.0 | 0.5 | 2.0 |
The judges and the criteria
The CISO · Answers to the board for the day the vault vendor is breached. Wants a whitepaper that says which fields are encrypted and which are not, audits by named firms with dates, a bug bounty, and an incident history written down rather than discovered in the press.
The Identity Engineer · Runs Entra ID for two thousand staff and owns the joiner-mover-leaver process. Wants SCIM that suspends a leaver's vault the moment the account is disabled, an SSO unlock whose key model is documented, and FIDO2 keys and passkeys supported for the vault itself.
The Compliance Auditor · Prepares the ISO 27001 and NIS2 evidence and has to show who could see the firewall admin password last March. Wants event logs that cover views and copies, export to the SIEM, enforceable policies, and the contracting entity, hosting and subprocessors named.
The SME Owner · Runs a forty-person company where the shared passwords currently live in an Excel file. Wants shared vaults the team actually uses, a way back in when someone forgets the master password, credentials handed over when someone leaves, and a per-user price with SSO not hidden two tiers up.
The DevOps Engineer · Would rather run the vault in the company's own data centre than trust another SaaS with root credentials. Wants a documented self-hosted deployment with backup and high availability, open-source code to read, a CLI and API for pipelines, and an export that loses nothing.
The Skeptic · Has read the breach post-mortems. Reads "zero knowledge" next to unencrypted URLs and item names, "independently audited" with no report, "SSO unlock" where the vendor holds half the key, and "admin recovery" that means the vendor can decrypt — and treats a missing incident history as an answer.
Encryption model & independent audits · What the vendor can prove about its security design: end-to-end encryption with named algorithms and key derivation, which fields are encrypted on the device and which are not, independent audits and penetration tests with published results, a bug bounty, and incident history disclosed.
Sharing, roles & recovery · How credentials are shared and governed across a company: shared vaults or collections, role-based permissions, view-only and time-limited access, admin account recovery, emergency access, and what happens to shared items when an employee leaves.
SSO, directory sync & provisioning · How the vault fits into the company's identity stack: SSO with Entra ID, Okta or Google, and the key model behind an SSO unlock; SCIM or directory sync for joiners and leavers; MFA options including hardware keys; and passkey support for users and the vault itself.
Audit logs, policies & reporting · What an administrator and an auditor can see and enforce: event logs of access and changes, password health and breach reports, enforceable policies (master password, MFA, sharing, export), SIEM integration, and reports an ISO 27001 or NIS2 audit can use.
Hosting choice, offline access & export · Where and how the vault runs and how the data leaves it: cloud region choice, a self-hosted or on-premises option, offline access during a vendor outage, client coverage across operating systems and browsers, and a complete, documented export and import path.
European sovereignty · Who the contracting entity and the parent company are, where vault data and metadata are hosted, and who the subprocessors are. Independently sourced by the sovereignty pipeline; end-to-end encryption narrows what a foreign authority could compel, but metadata, logs and the update channel for the client software remain in the vendor's hands, so the chain still counts.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per user and tier, which features (SSO, SCIM, SIEM, self-hosting) sit in which tier, minimum seats, add-ons, and the minimum term.
Payment rubric v2
| Criterion | The Finance Lead v1.0 | The E-Commerce Lead v1.0 | The SaaS Founder v1.0 | The Payments Engineer v1.0 | The Compliance Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Payment methods & local coverage | 1.0 | 3.0 | 1.5 | 1.5 | 0.5 | 1.0 |
| Checkout, SCA & fraud | 0.5 | 3.0 | 1.0 | 2.5 | 1.5 | 1.0 |
| Subscriptions & recurring payments | 1.0 | 1.0 | 3.0 | 2.0 | 0.5 | 1.0 |
| Settlement, reconciliation & API | 3.0 | 1.5 | 2.0 | 3.0 | 1.0 | 2.0 |
| Licence, risk & account terms | 2.5 | 1.0 | 2.0 | 1.0 | 3.0 | 3.0 |
| European sovereignty | 1.0 | 0.5 | 1.0 | 1.0 | 3.0 | 1.5 |
| Pricing transparency | 1.5 | 1.0 | 1.0 | 0.5 | 0.5 | 2.0 |
The judges and the criteria
The Finance Lead · Closes the month and owns the cash position. Wants payouts on a stated schedule, fees itemised per transaction rather than netted into a lump, reports that match the bank statement, and a rolling reserve written into the contract with a limit rather than discovered on a Tuesday.
The E-Commerce Lead · Sells to customers in eight EU countries and is measured on conversion. Wants the local methods each market actually uses named per country, a checkout that stays on her domain, and 3-D Secure that challenges only when it must. Reads "100+ payment methods" as a count, not a list.
The SaaS Founder · Runs a B2B subscription business where every failed renewal is churn nobody chose. Wants SEPA mandates as well as cards, dunning that recovers, proration that is correct, and the payment tokens exportable — because a provider that keeps the tokens keeps the customer base hostage.
The Payments Engineer · Integrates the provider and gets paged when webhooks stop arriving. Wants a versioned API with idempotency keys, a test mode that behaves like production, the PCI scope of each integration stated, and a status page that admits incidents rather than a green dot.
The Compliance Officer · Handles data protection and outsourcing risk, and wants the regulated entity named with its supervisor and register number, not "licensed in Europe". Asks where transaction and cardholder data are processed, who the subprocessors are, and where the provider acts as controller rather than processor.
The Skeptic · Knows the headline rate covers the cheapest card in the cheapest country. Reads for the currency conversion markup, the chargeback fee, the payout delay and the clause that lets the provider freeze funds without a reason — and treats a missing licence number as an answer.
Payment methods & local coverage · Which methods a European customer can actually pay with — cards and wallets, SEPA Direct Debit, and the local methods that decide conversion per country — judged on the named list per market rather than on a method count.
Checkout, SCA & fraud · The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.
Subscriptions & recurring payments · Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.
Settlement, reconciliation & API · Getting the money and knowing what it was: payout cadence and currencies, fee itemisation per transaction, reports that match a bank statement, and an API and webhooks a team can build finance processes on.
Licence, risk & account terms · Who holds the merchant's money under which licence, and what the contract lets the provider do on a bad day: freezes, reserves, termination, chargebacks. Scored on what the terms and the imprint state, not on reputation.
European sovereignty · Who the contracting and regulated entity is, and where transaction and cardholder data are processed and stored. Independently sourced by the sovereignty pipeline. The card schemes are US-based for every provider, so the scheme layer is not held against any one vendor; the part the vendor controls is.
Pricing transparency · Whether a merchant can compute the effective fee for their own mix of cards, countries and methods — including cross-border and currency conversion markups, chargebacks, refunds, payouts and monthly fees — from public pages alone.
POS & Checkout Systems rubric v1
| Criterion | The Café Owner v1.0 | The Retail Shop Owner v1.0 | The Tax Adviser v1.0 | The Hospitality Operations Manager v1.0 | The Fee-Conscious Merchant v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Checkout, receipts & hardware | 2.5 | 2.0 | 1.0 | 1.5 | 2.5 | 1.5 |
| Card payments & fees | 2.0 | 1.5 | 1.5 | 1.5 | 3.0 | 2.5 |
| Fiscal compliance (TSE, DSFinV-K, RKSV) | 2.5 | 2.0 | 3.0 | 2.0 | 1.5 | 2.5 |
| Inventory, tables, staff & locations | 2.0 | 3.0 | 0.5 | 3.0 | 1.0 | 1.0 |
| Accounting handoff, DATEV & data export | 1.5 | 2.0 | 3.0 | 2.0 | 1.0 | 2.5 |
| European sovereignty | 1.0 | 1.0 | 2.0 | 2.5 | 1.0 | 2.5 |
| Pricing transparency | 2.0 | 1.5 | 0.5 | 1.0 | 2.0 | 2.0 |
The judges and the criteria
The Café Owner · Runs a café with twelve tables, a counter and a terrace in summer, and closes the till herself at eleven at night. Wants an iPad till the student staff learn in one shift, orders that reach the kitchen printer, split bills and tips without arithmetic, a till that keeps selling when the Wi-Fi drops, a TSE she does not have to think about, and a monthly cost she can still read in the second year.
The Retail Shop Owner · Owns a stationery and gift shop with a second branch across town and about four thousand articles, many in several colours. Wants barcodes scanned at the till, stock that shows what the other branch still has, transfers between the two shops, suppliers and reorders in the same back office, vouchers that work in both branches, and the month's sales handed to the tax adviser without a USB stick.
The Tax Adviser · Looks after the books of sixty restaurants, bakeries and shops and has sat in on more than one unannounced Kassennachschau. Wants the TSE named with its certificate, a DSFinV-K export that opens in the auditor's software, the § 146a registration done, a procedure documentation that exists before it is asked for, a DATEV export with the right revenue accounts, and ten years of records still readable after the client changes tills.
The Hospitality Operations Manager · Runs operations for a group of eight restaurants in three cities with two hundred staff. Wants one menu and price list pushed to every site with local exceptions, staff rights that stop a waiter voiding his own bills, reports that compare sites by the hour, and a works council and data protection officer who can sign off what the till records about employees and loyalty guests, and where it is hosted.
The Fee-Conscious Merchant · Sells ice cream from a shop in spring and summer and from a market stall at Christmas, mostly in amounts under five euros, and more of them by card every year. Wants the fee per girocard and credit card payment on the price page, a terminal he can choose rather than the one the till insists on, hardware that runs off a battery, no monthly fee in the closed months, and the real cost of "free".
The Skeptic · Has seen a "free" till paid for twice over in card fees, printers that work with one vendor's software only, a TSE charged by the year on top of the licence, and a cancelled contract that left ten years of fiscal journals behind a login. Reads "100 % finanzamtkonform" with no TSE provider named and "DATEV-ready" with no export format — and asks what leaving would cost.
Checkout, receipts & hardware · How a sale is rung up and what it runs on: a fast till on tablet, phone or dedicated terminal, articles, modifiers and discounts, split bills and tips, receipts printed or sent digitally (QR code, email, a digital Bon), returns and cancellations, a customer display, which hardware is supported or sold (receipt printers, cash drawers, scanners, scales), and whether the till keeps selling when the internet is down.
Card payments & fees · How the till takes card and mobile payments and what that costs: an integrated terminal and the acquirer behind it named, girocard, credit cards, Apple Pay and Google Pay, tap to pay on a phone, the fee per transaction by card type, monthly terminal fees, payout timing, and whether the merchant may use a terminal or acquirer of their own choice instead. A "free" till paid for by card fees counts here.
Fiscal compliance (TSE, DSFinV-K, RKSV) · Whether the till survives a cash audit: for Germany a certified technical security device (TSE) with its provider and BSI certificate named, hardware or cloud, the DSFinV-K export for the Kassennachschau and the tax audit, the receipt obligation (Belegausgabepflicht), the Kassenbuch and daily closing (Z-Bericht), GoBD-compliant storage for ten years, and help with the § 146a AO registration; for Austria the RKSV signature and FinanzOnline registration; for other countries their named fiscal rules (NF525, Fiskaltrust and similar).
Inventory, tables, staff & locations · What the till runs beside the sale: stock and articles with variants, suppliers and purchase orders, recipes or ingredients for hospitality, tables, courses and a kitchen display or kitchen printer, self-order and QR ordering, staff logins with roles and rights, cash differences per employee, reports by product, staff and hour, and several branches or sites managed from one back office.
Accounting handoff, DATEV & data export · What reaches the books and what leaves with the merchant: an export to DATEV (DATEV format, DATEV Kassenarchiv online, DATEV Unternehmen online) and to named accounting tools, booking with revenue accounts and tax rates, card payouts and fees reconciled, an API and webhooks, integrations with shop, booking or staff tools, and a complete export of articles, customers, sales and fiscal journals when the contract ends.
European sovereignty · Who the contracting entity and the parent company are, where sales, customer and employee data are hosted, and who the subprocessors are (hosting, cloud TSE, payment processing, receipt delivery, email, analytics). Independently sourced by the sovereignty pipeline; POS data is financial and fiscal at once, holds staff logins and customer cards, and has to stay readable for the tax office for ten years, so the whole chain counts, not only the database.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: licence per till or per location, which modules (tables, kitchen display, stock, extra tills, DATEV export) cost extra, the TSE and its yearly fee, hardware to buy or rent, card terminal fees and transaction fees, setup and installation, support plans, minimum term and notice period.
Project Management & Collaboration rubric v1
| Criterion | The Data Protection Officer v1.0 | The Bootstrapper v1.2 | The Enterprise Architect v1.0 | The UX Purist v1.0 | The Integrator v1.0 | The Skeptic v1.2 |
|---|---|---|---|---|---|---|
| Collaboration depth | 0.5 | 1.5 | 1.0 | 1.5 | 1.0 | 1.0 |
| Reporting | 0.5 | 1.0 | 1.5 | 0.5 | 1.0 | 1.0 |
| Integrations | 1.0 | 1.0 | 2.0 | 0.5 | 3.0 | 1.0 |
| Onboarding effort | 0.5 | 2.0 | 0.5 | 3.0 | 0.5 | 1.0 |
| European sovereignty | 3.0 | 0.5 | 2.0 | 0.5 | 0.5 | 1.5 |
| Support & documentation | 1.5 | 0.5 | 1.5 | 1.0 | 1.0 | 1.0 |
| Pricing transparency | 0.5 | 1.0 | 1.0 | 0.5 | 0.5 | 1.0 |
The judges and the criteria
The Data Protection Officer · Reads the DPA before the feature list. Optimizes for GDPR posture: EU hosting, subprocessor exposure, deletion guarantees. Rejects anything that cannot answer where the data lives.
The Bootstrapper · Pays with their own card. Optimizes for price/value at 3 seats and at 30, a usable free tier, and a price page that answers instead of qualifying. Rejects hidden seat minimums and "contact sales".
The Enterprise Architect · Buys for two hundred seats and answers for it later. Optimizes for SSO/SCIM, permissions, audit trails, certifications and a clean exit. Rejects anything that cannot survive procurement.
The UX Purist · Measures time-to-first-value with a stopwatch. Optimizes for clarity, density and software that teaches itself. Rejects fourteen-step setups and empty screens that offer no way forward.
The Integrator · Lives in the API docs before the product tour. Optimizes for webhooks, import/export and a tool that plays well in a stack. Rejects closed ecosystems and CSV-only exits.
The Skeptic · Assumes the marketing is lying until the evidence says otherwise. Hunts lock-in, dark patterns, hidden cost and dead changelogs. Exists to keep the rest of the panel honest.
Collaboration depth · How much real multi-person project work the tool carries: shared planning, assignments, dependencies, workload, comments, guest access.
Reporting · Whether the tool can answer questions about the work: progress, time, budgets, utilization — and export the answer.
Integrations · How well the tool connects to the rest of the stack: native integrations, calendar/comms hooks, API and webhooks, import/export paths.
Onboarding effort · Time and friction from signup to first real value for a small team, without paid services.
European sovereignty · Where the company and the data actually sit: legal entity, ownership control, data residency, and subprocessor exposure to non-EU jurisdictions.
Support & documentation · Whether a stuck user gets unstuck: docs quality, support channels and their availability per plan, and the health of the learning surface.
Pricing transparency · Can a buyer determine the real, payable cost of the tool for their team before talking to anyone?
Property & WEG Management rubric v2
| Criterion | The WEG Administrator v1.0 | The Advisory Board Member v1.0 | The Accountant v1.0 | The Portfolio Manager v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Wirtschaftsplan, Jahresabrechnung & Rücklage | 3.0 | 2.5 | 3.0 | 2.0 | 1.0 | 2.0 |
| Eigentümerversammlung & Beschluss-Sammlung | 2.5 | 2.5 | 1.0 | 1.5 | 1.0 | 2.0 |
| Owner & tenant self-service | 1.5 | 3.0 | 1.0 | 2.0 | 2.0 | 1.0 |
| Maintenance, defects & contractors | 2.0 | 1.5 | 1.0 | 3.0 | 0.5 | 1.0 |
| Documents, retention & handover | 1.5 | 2.0 | 2.0 | 2.0 | 2.5 | 2.0 |
| European sovereignty | 0.5 | 1.0 | 1.0 | 0.5 | 3.0 | 1.5 |
| Pricing transparency | 1.0 | 1.0 | 1.0 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The WEG Administrator · Manages forty communities and personally carries the duties the WEG places on the Verwalter. Wants the statutory year — Wirtschaftsplan, Jahresabrechnung, Versammlung, Beschluss-Sammlung — discharged inside one system. Judges a product by the March settlement run, not the demo.
The Advisory Board Member · An owner, elected and unpaid, who checks the administrator's settlement before recommending it to the assembly — and is answerable to the neighbours if it is wrong. Wants to see the underlying records without asking, the resolution register current, and arithmetic that can be followed back to an invoice.
The Accountant · Prepares the settlement and answers for its form. Cares that the Abrechnungsspitze is shown separately, that the Rücklage is genuinely segregated trust money rather than a labelled balance, and that heating costs apportion per HeizkostenV without a spreadsheet.
The Portfolio Manager · Runs a firm managing several thousand units and lives on throughput. Wants statutory inspections scheduled with proof stored, defects that route to the right trade, multi-community reporting, and onboarding a new WEG that takes days rather than a quarter.
The Data Protection Officer · The system holds names, addresses, bank details and arrears for people who never chose the vendor. Wants owner and tenant visibility strictly separated, an access log over the archive, retention that executes, and an answer on where the AI invoice reader sends a document.
The Skeptic · Has read many pages claiming "WEG-konform" and wants the feature that makes it true — the post-2021 settlement form, the maintained Beschluss-Sammlung, the majority arithmetic. Also reads for the per-unit minimum, the setup fee, and what it costs a community to leave with its own records.
Wirtschaftsplan, Jahresabrechnung & Rücklage · The statutory financial cycle: business plan, annual settlement in the form the law and the BGH require, distribution keys, and the separate handling of reserve funds held in trust for the community.
Eigentümerversammlung & Beschluss-Sammlung · Convening, running and recording the owners' meeting — including the resolution register the law requires the administrator to maintain, and the majority arithmetic that decides whether a resolution stands.
Owner & tenant self-service · How an owner exercises their right to see the records, and how much routine correspondence the portal removes: statements, documents, meeting papers, defect reporting.
Maintenance, defects & contractors · The building side: defect intake and tracking, recurring maintenance obligations, contractor assignment, and the evidence trail when something goes wrong.
Documents, retention & handover · The archive and the exit. A Verwalter's appointment is finite by law, and the records belong to the community — so handover is a statutory event, not a support ticket.
European sovereignty · Where the community's financial and personal records live, who the contracting entity is, and which subprocessors touch them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the sources do not establish are unknown, not non-EU.
Pricing transparency · Whether an administrator can compute the real annual cost for the units under management — including modules, per-community fees and setup — from public pages alone.
Recruiting rubric v2
| Criterion | The Talent Acquisition Lead v1.0 | The Employer Branding Manager v1.0 | The Data Protection Officer v1.0 | The Works Council Advocate v1.0 | The HR IT Integrator v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Applicant management & hiring workflow | 3.0 | 1.5 | 1.0 | 1.5 | 1.5 | 2.0 |
| Multiposting, career page & candidate experience | 2.5 | 3.0 | 0.5 | 0.5 | 1.0 | 1.5 |
| Retention, deletion & talent-pool consent | 1.5 | 1.0 | 3.0 | 2.5 | 1.5 | 2.0 |
| AI screening transparency & control | 1.5 | 1.0 | 2.5 | 3.0 | 1.0 | 2.5 |
| HR handover, integrations & API | 1.5 | 1.0 | 1.0 | 0.5 | 3.0 | 1.5 |
| European sovereignty | 1.0 | 0.5 | 3.0 | 1.5 | 1.5 | 1.5 |
| Pricing transparency | 1.0 | 1.5 | 0.5 | 0.5 | 1.0 | 2.0 |
The judges and the criteria
The Talent Acquisition Lead · Fills sixty roles a year across three locations with a team of two. Wants pipelines hiring managers actually use, scorecards that make a decision defensible, and multiposting that reaches the German boards without a separate login. Unmoved by a match score she cannot explain to a candidate.
The Employer Branding Manager · Owns the career page and the job-ad budget. Wants a career site that works on a phone, applications without an account, and cost per applicant per channel rather than a logo wall of job boards. Reads a pricing page for what a posting on StepStone actually adds to the bill.
The Data Protection Officer · Answers for thousands of CVs from people who never chose the vendor. Wants deletion that runs on the stated date after rejection, talent-pool consent that expires, a subprocessor list that names the CV parser and the AI provider, and an access log over every applicant file.
The Works Council Advocate · Sits on the Betriebsrat, which co-determines selection guidelines and questionnaires. Asks what any ranking evaluates, whether it can be switched off, who sees which applicant, and whether an internal candidate's file leaks into their personnel record. No answer, no agreement.
The HR IT Integrator · Has to connect the ATS to the HR system, the calendar and identity. Wants a documented API, SSO that is not an enterprise upsell, and a hire that arrives in Personio or SAP with its documents rather than as a PDF someone retypes. Judges integrations by who maintains them.
The Skeptic · Has read "DSGVO-konform" and "AI-powered matching" on every page in this category. Reads instead for the deletion deadline that is actually configured, the AI feature that can actually be turned off, and what the invoice does when a job goes out to three paid boards.
Applicant management & hiring workflow · The daily work of hiring: pipeline stages per job, collaboration with hiring managers, structured evaluation, interview scheduling and candidate communication — judged on whether a decision is documented rather than merely made.
Multiposting, career page & candidate experience · Getting a vacancy in front of the right people and letting them apply: job-board distribution for the German market, the career page, and an application process that does not lose candidates on a phone.
Retention, deletion & talent-pool consent · What happens to the data of people who were not hired: automatic deletion on a configurable deadline, talent-pool consent that expires, data-subject requests, and access logging — the criterion the employer is actually liable for.
AI screening transparency & control · Whether any automated ranking, matching, parsing or rejection is disclosed, explained and switchable — recruitment is a high-risk use under the EU AI Act, and an undisclosed score next to a candidate's name is a co-determination matter (BetrVG §§ 94, 95). A product without AI features is judged on stating so.
HR handover, integrations & API · The hire does not end in the ATS: handover to the HR system and payroll, identity and calendar integration, e-signature for contracts, and an API a team can build on.
European sovereignty · Where applicant data lives, who the contracting entity is, who the subprocessors are — including the job boards, CV parsers and AI providers the system passes CVs to. Independently sourced by the sovereignty pipeline; weighted higher here than in categories holding the customer's own data, because every record belongs to a third party who never chose the vendor. Dimensions the evidence does not establish are unknown, not non-European.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: the pricing model (per employee, per open job, per recruiter seat), job-board posting costs, add-ons for AI, career page or integrations, and the minimum term.
Remote Desktop & Remote Support rubric v1
| Criterion | The IT Support Lead v1.0 | The MSP Technician v1.0 | The Software Support Lead v1.0 | The Small Office Owner v1.0 | The Information Security Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Remote control & attended support sessions | 3.0 | 2.5 | 3.0 | 2.0 | 1.0 | 2.0 |
| Unattended access & device deployment | 3.0 | 3.0 | 1.0 | 2.5 | 1.5 | 1.5 |
| Support desk workflow, branding & reporting | 2.0 | 2.0 | 3.0 | 0.5 | 1.0 | 1.0 |
| Administration, identity & API | 2.5 | 3.0 | 1.5 | 1.0 | 2.5 | 1.5 |
| Session security, audit & reliability | 2.5 | 2.0 | 2.0 | 2.0 | 3.0 | 2.5 |
| European sovereignty | 1.5 | 1.0 | 1.5 | 2.0 | 3.0 | 2.5 |
| Pricing transparency | 1.0 | 1.5 | 1.5 | 2.0 | 0.5 | 2.0 |
The judges and the criteria
The IT Support Lead · Leads the six-person service desk of a pump manufacturer with four hundred workstations on three sites in North Rhine-Westphalia, mostly Windows, some Macs in marketing and a few Linux machines on the test benches. Wants a user to join a session from a link, sessions across UAC prompts and reboots, agents rolled out through Intune to every device group, sessions started from the ticket in the service desk tool, and technicians signing in with their Entra ID accounts.
The MSP Technician · Senior technician at an IT service provider in Freiburg that looks after sixty small businesses — law firms, dental practices, a bakery chain — with about 1,800 endpoints and servers between them. Wants each client's devices kept apart with their own technicians, unattended access to servers at night with wake-on-LAN, the remote tool linked to the RMM and the PSA so that every session lands on the right ticket and invoice, and a licence that does not double when the client list grows.
The Software Support Lead · Runs first- and second-level support for a vendor of practice software for physiotherapists, with fourteen agents in Kassel and four thousand customer practices that are not IT people. Wants a small support client in the company's own branding that runs without admin rights, a support button on the website that puts the caller in a queue, the session written back to the helpdesk ticket, and reports per agent that show how long a fix takes.
The Small Office Owner · Owns an accounting firm with eleven staff in Lübeck and is its IT department in the evenings. Wants to reach the office PCs from home and from a tablet, to help a colleague whose scanner stopped working without driving in, the client data never leaving a European provider, and a plan that is clearly licensed for commercial use, with the price of the second year shown before the first is paid.
The Information Security Officer · Information security officer at a municipal utility that runs power and water networks and falls under the critical infrastructure rules. Treats every remote access tool as a way in for attackers and support scammers. Wants enforced two-factor authentication and single sign-on, access limited by device group and time, every session logged and recorded, published security advisories with fixed versions, and the option to run the relay on the utility's own servers.
The Skeptic · Has seen a "free" remote tool flag a company for commercial use and lock it out mid-session, "bank-grade encryption" with no word on who runs the relay, and a licence that counted technicians, then sessions, then endpoints at each renewal. Asks what the audit log really records, how fast the last vulnerability was fixed and disclosed, whether the agents can be removed cleanly from four hundred machines — and what the second year costs.
Remote control & attended support sessions · What a technician can do in a session with a user who is present: starting a session from a code, link or small support client without admin rights, viewing and controlling the screen with good image quality at low bandwidth, multi-monitor switching, file transfer, clipboard, chat and voice, remote reboot with automatic reconnect, running as administrator and crossing UAC or elevation prompts, session handover to a colleague, whiteboard or annotation, screen sharing in the other direction, and which operating systems can be supported (Windows, macOS, Linux, iOS and Android, including control rather than only viewing of mobile devices).
Unattended access & device deployment · How machines are reached when nobody sits at them: unattended agents for workstations and servers, mass deployment through MSI packages, group policy, Intune or other management tools, device lists and groups with search, tagging and an address book, wake-on-LAN, access to the login screen and after reboot, access to headless or terminal-only machines, remote command line and file manager without taking over the screen, connecting through proxies and restrictive firewalls, and a desktop or browser client for the person connecting, including remote work access to one's own office PC.
Support desk workflow, branding & reporting · How a support team runs remote sessions as a service: session queues and routing to technicians or groups, a support request button or chat on the vendor's website, a support client and portal in the customer's own branding with its own domain, post-session surveys, session notes and summaries, integrations with helpdesk and ITSM tools (ServiceNow, Jira Service Management, Zendesk, Freshservice, HubSpot) that start sessions from a ticket and write the session back, reports per technician and customer, session duration for billing, and any AI assistance in sessions with its provider named.
Administration, identity & API · How the tool fits the company or the MSP: user and technician management with roles and granular permissions per device group, single sign-on (SAML or OpenID Connect) with Entra ID or Google, SCIM or directory sync, enforced two-factor authentication, central policies for agents (who may connect, when, with which features), multi-tenant customer separation for MSPs, a documented REST API and webhooks for users, devices and sessions, integrations with RMM, PSA and endpoint management tools, and licence management across seats, endpoints and concurrent sessions.
Session security, audit & reliability · Whether remote access is a door only the right people can open: end-to-end or transport encryption with the protocol and key length named, two-factor authentication, the user's consent prompt and the option to block input or blank the screen, device and IP allow-lists, trusted-device approval, brute-force protection, session recording and an audit log of who connected to what and when, protection against support scams and misuse of free accounts, a published vulnerability disclosure process and security advisories, independent certifications (ISO 27001, SOC 2), the location and redundancy of relay servers, a public status page, an SLA, and an on-premise or self-hosted server for organisations that keep the relay in their own network.
European sovereignty · Who the contracting entity and the parent company are, where account data, device lists, session logs, recordings, chat transcripts and file transfers are stored and processed, where the relay and brokering servers that carry session traffic stand, and who the subprocessors are (hosting, relay networks, email delivery, support and payment tools, AI models). Independently sourced by the sovereignty pipeline. A self-hosted or on-premise server the customer runs on its own European infrastructure counts as the customer's chain, whatever the vendor's seat, as long as it does not call home for more than licensing.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per plan and what the licence counts (technicians or seats, concurrent sessions, managed or unattended endpoints), what extra technicians, endpoints and sessions cost, which features (mobile device support, branding, SSO, session recording, integrations, on-premise server) cost extra, monthly versus annual billing, renewal prices, the terms for commercial use of a free version, minimum term, and VAT.
Sales Enablement rubric v2
| Criterion | The Head of Sales v1.0 | The Enablement Manager v1.0 | The Product Marketer v1.0 | The CRM Integrator v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Sales content management | 2.0 | 2.0 | 3.0 | 1.5 | 0.5 | 1.0 |
| Buyer engagement & digital sales rooms | 3.0 | 1.0 | 2.0 | 1.5 | 2.5 | 2.5 |
| Onboarding, training & coaching | 1.5 | 3.0 | 1.0 | 0.5 | 2.5 | 2.0 |
| Analytics, AI & seller monitoring | 1.5 | 2.0 | 2.0 | 1.5 | 3.0 | 2.5 |
| CRM, workplace integrations & exit | 2.0 | 1.5 | 1.0 | 3.0 | 1.0 | 1.5 |
| European sovereignty | 0.5 | 1.0 | 0.5 | 1.5 | 3.0 | 1.5 |
| Pricing transparency | 1.5 | 1.0 | 1.0 | 1.0 | 0.5 | 2.0 |
The judges and the criteria
The Head of Sales · Runs twenty account executives across DACH and is measured on win rate and cycle length. Wants a sales room the buyer's committee actually opens, a mutual action plan that keeps the deal moving after the demo, and content sellers find from the opportunity rather than in last year's email.
The Enablement Manager · Owns onboarding and wants a new hire selling in weeks, not quarters. Wants onboarding paths with certifications, practice with feedback a manager can actually give, and call recording that starts with the consent of everyone on the line, because a German customer has to agree before anything is recorded.
The Product Marketer · Writes the decks and wants the old ones gone. Wants versioning that replaces a superseded slide everywhere it was shared, approval before a claim goes out, brand-locked templates sellers can personalise within limits, and usage per asset so content nobody sends can be retired.
The CRM Integrator · Runs the Salesforce or Dynamics org and the Microsoft 365 tenant. Wants engagement data written back to the opportunity rather than kept in one more dashboard, SSO and SCIM, an API with webhooks, and a documented export of the content library for the day the contract ends.
The Data Protection Officer · Sees two groups being measured who never signed the vendor's terms: the buyer's employees in every tracked room and the company's own sellers in every scored call. Wants the tracking documented and switchable, recordings with a consent step and a retention period, transcription and AI providers named, and seller analytics a works council can agree to.
The Skeptic · Knows that "buyer intent" means tracking named people at the customer, that "AI coaching" means scoring employees, and that "reps find content 50% faster" rests on a vendor survey. Reads for what a room records about its visitors, what a readiness score is built from, whether call recording asks everyone on the line, and how many seats the minimum contract really buys.
Sales content management · 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.
Buyer engagement & digital sales rooms · 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.
Onboarding, training & coaching · 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.
Analytics, AI & seller monitoring · 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 (BetrVG § 87 (1) 6).
CRM, workplace integrations & exit · 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.
European sovereignty · 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.
Pricing transparency · 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.
SEO rubric v2
| Criterion | The In-House SEO Lead v1.0 | The Agency Owner v1.0 | The Technical SEO v1.0 | The Content Strategist v1.0 | The Data Analyst v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Crawling & technical audit | 2.5 | 2.0 | 3.0 | 1.0 | 1.5 | 1.5 |
| Keyword research & content guidance | 3.0 | 2.0 | 1.0 | 3.0 | 1.0 | 1.5 |
| Rank tracking & index quality | 2.5 | 2.0 | 1.5 | 2.0 | 2.5 | 2.5 |
| Reporting, integrations & API | 1.5 | 3.0 | 2.0 | 1.5 | 3.0 | 1.0 |
| Data portability & exit | 1.0 | 1.5 | 1.5 | 1.0 | 3.0 | 2.0 |
| European sovereignty | 0.5 | 0.5 | 0.5 | 0.5 | 1.0 | 1.0 |
| Pricing transparency | 1.0 | 2.0 | 1.0 | 1.5 | 1.0 | 2.0 |
The judges and the criteria
The In-House SEO Lead · Owns organic traffic for one large German site and reports on it monthly. Wants German-language keyword data that is not an afterthought, rankings she can defend when they disagree with Search Console, and audit findings specific enough to become a developer ticket.
The Agency Owner · Runs forty client sites and rebills the licence. Wants multi-client management, white-label reports a client can receive unedited, and per-seat costs that do not punish a growing team. Reads "contact us" on a pricing page as a margin problem.
The Technical SEO · Lives in crawl data and log files. Wants JavaScript rendering, crawl budget analysed, indexation diagnosed rather than listed, and regressions caught between crawls. Treats an issue list sorted by count rather than by traffic impact as busywork.
The Content Strategist · Decides what gets written and can only commission so much. Wants topic clusters, honest opportunity sizing, cannibalisation caught before it happens, and briefs scored against what actually ranks rather than against keyword density.
The Data Analyst · Wants the numbers in the warehouse, not in a PDF. Cares about a documented API with published credit costs, bulk historical export, and whether three years of ranking history leaves with the customer or dies with the subscription.
The Skeptic · Knows every vendor claims the largest index and the most accurate rankings, and that no buyer can check either. Reads instead for what can be held to: refresh frequency, stated limits, credit costs per endpoint, and what the invoice does when the team adds a seat.
Crawling & technical audit · Site crawling at real scale: what the crawler finds, how deeply it checks, whether Core Web Vitals and indexation problems are diagnosed rather than merely listed.
Keyword research & content guidance · Keyword discovery, intent classification, SERP feature analysis and on-page guidance — judged on the depth of the German-language data as much as the English.
Rank tracking & index quality · The proprietary data: ranking accuracy and frequency, backlink index size and freshness. Scored on what the vendor documents about their own data, because nothing here can be verified from outside.
Reporting, integrations & API · Getting the data out and in front of someone: dashboards, white-label reporting for agencies, Search Console and analytics integration, and an API a team can build on.
Data portability & exit · Whether the ranking and crawl history — the only thing a multi-year subscription actually accumulates — remains the customer's when they leave.
European sovereignty · Where the account and crawl data live and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted lower here than in categories holding personal data, because an SEO tool mostly holds the customer's own strategy rather than their customers' identities. Dimensions the sources do not establish are unknown, not non-EU.
Pricing transparency · The category where the headline price is least often the invoice. Whether a buyer can compute the real annual cost including keyword limits, crawl credits, API units, extra users and client seats — from public pages alone.
Social Media Marketing rubric v2
| Criterion | The Community Manager v1.0 | The Agency Lead v1.0 | The Brand Governance Officer v1.0 | The Analyst v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Publishing & calendar | 2.5 | 2.5 | 1.0 | 1.0 | 0.5 | 1.5 |
| Engagement & community inbox | 3.0 | 1.5 | 1.0 | 1.0 | 1.5 | 1.0 |
| Analytics & reporting | 1.0 | 2.5 | 1.0 | 3.0 | 1.0 | 1.5 |
| Approvals, roles & brand safety | 1.5 | 3.0 | 3.0 | 1.0 | 2.0 | 1.5 |
| Network coverage & API resilience | 2.0 | 1.5 | 1.5 | 2.5 | 1.0 | 2.5 |
| European sovereignty | 0.5 | 0.5 | 2.5 | 1.0 | 3.0 | 1.5 |
| Pricing transparency | 1.0 | 2.0 | 0.5 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The Community Manager · Answers the comments, including the angry ones, and lives in the inbox. Wants every mention and message in one queue with ownership and history, saved replies that save real time, and a failed 3am post that tells her rather than silently not existing.
The Agency Lead · Runs twelve client brands from one tool and must keep them strictly apart. Wants client workspaces, approval chains that include the client, white-label reporting, and per-account pricing that does not make a small client unprofitable.
The Brand Governance Officer · Answers to the board for what appears on the corporate account. Wants enforced approval before anything publishes, an audit trail of who wrote and released it, granular permissions, and no shared credentials anywhere in the design.
The Analyst · Has to compare metrics the networks define differently and report a number the board believes. Wants history retained past the platforms' own windows, normalisation documented rather than hidden, and UTM attribution that reaches web analytics.
The Data Protection Officer · Notes that every comment and message arriving from a network is personal data the company now processes. Wants a DPA that addresses that squarely, retention on the conversation archive, and an answer on where the sentiment analysis sends the text.
The Skeptic · Counts the network logos, then asks which are official API integrations and what each one cannot do. Has watched a platform change break a feature overnight, and wants to know what the vendor did last time and whether the archive survived it.
Publishing & calendar · Scheduling across networks: per-network formatting, the calendar as a working surface, bulk operations, and what happens when a post fails.
Engagement & community inbox · Comments, mentions and messages in one queue — the half of the job that is customer service wearing a marketing badge.
Analytics & reporting · Measurement across networks with different metrics and retention windows, plus the reporting an agency hands a client.
Approvals, roles & brand safety · How a team of several people and an agency publish to a brand account without an accident — and who can be shown to have approved what.
Network coverage & API resilience · Which networks are supported through official APIs, how quickly the vendor follows platform changes, and what the customer keeps when a network breaks or leaves.
European sovereignty · Where the archive and the community conversations are processed, who the contracting entity is, which subprocessors touch them. Independently sourced by the sovereignty pipeline. Note that the networks themselves are non-EU by definition — this criterion judges the tool, not the platforms it talks to. Dimensions the sources do not establish are unknown, not non-EU.
Pricing transparency · Whether a team can compute the real annual invoice for their account and user count — including the tier where approvals and the inbox begin — from public pages alone.
Stable & Equestrian Management rubric v2
| Criterion | The Boarding-Stable Owner v1.0 | The Stable Manager v1.0 | The Boarder v1.0 | The Riding-School Lead v1.0 | The Tax Adviser v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Board contracts, extra services & billing | 3.0 | 1.0 | 2.0 | 2.0 | 3.0 | 2.5 |
| Horse records, feeding & health | 1.5 | 3.0 | 2.5 | 1.5 | 1.0 | 2.0 |
| Staff, rotas & daily operations | 2.0 | 3.0 | 0.5 | 1.5 | 2.5 | 2.0 |
| Boarder portal & communication | 2.0 | 1.5 | 3.0 | 1.5 | 0.5 | 1.5 |
| Facilities, lessons & events | 1.0 | 1.5 | 1.5 | 3.0 | 1.0 | 1.0 |
| European sovereignty | 1.0 | 1.0 | 2.0 | 1.0 | 2.0 | 2.0 |
| Pricing transparency | 2.0 | 0.5 | 0.5 | 1.5 | 1.0 | 2.0 |
The judges and the criteria
The Boarding-Stable Owner · Runs a forty-box Pensionsstall and loses a few hundred euros a month to blanket changes and leg wraps nobody wrote down. Wants extra services logged where they happen and billed without retyping, direct debit that collects on time, and one system instead of a spreadsheet and three WhatsApp groups.
The Stable Manager · Runs the morning round with two grooms, a trainee and a mini-jobber, and is the one the vet calls. Wants feeding plans the night shift can read on a phone, medication logged with who gave what, rotas and time records that hold up, and an app that still works at the far end of the barn.
The Boarder · Pays five hundred euros a month for her mare and works full time. Wants to see what the farrier did, why the bill has three extra wraps, and whether her turnout instruction was read — and does not want the other boarders, or an analytics company, seeing her horse's file.
The Riding-School Lead · Runs lessons six days a week on twelve school horses, plus weekend clinics with guest riders. Wants lessons and arena slots booked without double bookings, school horses not over-worked, ten-lesson cards that count themselves, and course payments that land in the same books as board.
The Tax Adviser · Does the books for a dozen equestrian businesses and knows that board, lessons and sold hay are not taxed alike. Wants invoices with GoBD-compliant numbering, VAT per service, a DATEV export instead of a shoebox of PDFs, and time records for the staff that would survive a customs minimum-wage check.
The Skeptic · Has seen stable apps arrive with a launch post and vanish two seasons later with the horse records inside. Reads "billing" that is a price list, "staff management" that is a chat, geofencing with no word on staff consent, and an imprint that names a riding stable rather than a software company — and asks what happens to the data then.
Board contracts, extra services & billing · How the stable gets paid: board contracts per box and horse, extra services logged at the moment they are done, prepaid credit, recurring invoices, SEPA direct debit, VAT treatment that a tax adviser accepts, and an export to the accountant.
Horse records, feeding & health · The record per horse: master data and passport details, feeding and supplement plans, vaccinations, worming, farrier and vet appointments, medication given, turnout and blanket instructions — kept so that a vet, an inspector or the owner can rely on it, and exportable when the horse leaves.
Staff, rotas & daily operations · The daily running of the yard: tasks and feeding rounds, shift and holiday planning, time recording for employees and mini-jobbers, help from boarders (Stalldienst), and reminders — and, where staff are clocked in by location, how that is done and documented.
Boarder portal & communication · What the horse owner sees and does: their horse's records and the services billed to them, instructions to the stable, bookings, news from the yard — and how their personal data and their horse's data are scoped, so each owner sees their own horse and nothing else.
Facilities, lessons & events · The yard's shared resources and teaching business: arena and indoor school bookings, horse walker, treadmill and solarium use, lessons and school horses, courses and clinics with registration and payment, guest boxes.
European sovereignty · Who the contracting entity and the parent company are, where boarder, staff and horse data are hosted, and who the subprocessors are (hosting, push notifications, payments, email). Independently sourced by the sovereignty pipeline; a phone app also sends data through the app-store and push providers, so the chain counts, not only the server.
Pricing transparency · Whether a stable owner can compute the real annual cost from public pages alone: price per stable, box, horse or module, which modules (billing, staff, portal, devices) cost extra, setup fees, minimum term, and what happens to the data on cancellation.
Supply Chain & Logistics rubric v1
| Criterion | The E-Commerce Operations Lead v1.0 | The Warehouse Manager v1.0 | The Transport Planner v1.0 | The Fulfilment Provider v1.0 | The IT & Integration Lead v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Inventory & stock control | 2.5 | 2.5 | 1.0 | 2.5 | 1.5 | 2.0 |
| Warehouse operations: receiving, picking & packing | 2.0 | 3.0 | 1.0 | 3.0 | 1.0 | 2.0 |
| Multi-carrier shipping & returns | 3.0 | 2.0 | 1.5 | 2.5 | 1.0 | 2.0 |
| Freight & transport management | 0.5 | 1.0 | 3.0 | 1.0 | 1.0 | 1.5 |
| Integrations, automation & exit | 2.5 | 1.5 | 2.0 | 2.5 | 3.0 | 2.5 |
| European sovereignty | 1.0 | 0.5 | 1.0 | 1.0 | 2.5 | 2.0 |
| Pricing transparency | 2.0 | 0.5 | 1.5 | 1.5 | 1.0 | 2.0 |
The judges and the criteria
The E-Commerce Operations Lead · Ships three hundred parcels a day from a shop, two marketplaces and a wholesale channel. Wants stock that is right on every channel so nothing is oversold, labels for four carriers printed in one batch, customs papers for Switzerland without retyping, and a returns portal that stops the support inbox filling up every January.
The Warehouse Manager · Runs two shifts in a four-thousand-square-metre warehouse with temps who start on Monday. Wants goods receipt against the purchase order, bin locations and scanner-guided picks a new hire gets right on day one, batch and best-before dates that are actually tracked, and pick and error rates per shift instead of a feeling.
The Transport Planner · Books forty pallets and three part loads a week for a machinery wholesaler, mostly by e-mail and phone. Wants quotes from several forwarders compared in one place, the agreed rates stored so invoices can be checked against them, eCMR instead of paper, and a CO2 figure per shipment the sustainability report can cite.
The Fulfilment Provider · Runs a 3PL warehouse with twenty-two client brands, each on a different shop system. Wants one WMS that keeps every client's stock and orders apart, connects to whatever shop the next client brings, ships on the client's own carrier contracts or the house rates, and turns picks, storage and packaging into a client invoice.
The IT & Integration Lead · Owns the ERP, the shop and the DATEV export for a mid-sized manufacturer, and gets the call when an order does not arrive in the warehouse. Wants a documented API and webhooks, EDI for the two retail chains, connectors the vendor actually maintains, a processor list for the recipient addresses, and a full export the day the contract ends.
The Skeptic · Has seen a "WMS" that was a stock column in a shop plugin and a "free" shipping tool that made its money on every label. Reads "integrates with everything" as a logo wall, asks whether own carrier contracts are allowed on the cheap tier, what the per-order fee is past the allowance, and how the order history leaves with you.
Inventory & stock control · Whether the stock figure can be trusted: every goods receipt, sale, transfer, return and correction booked as a movement, stock per location and channel, batches, serial numbers and best-before dates where the goods need them, reorder points and purchase orders, and stock synchronised to every sales channel so nothing is oversold.
Warehouse operations: receiving, picking & packing · The physical work in the warehouse: goods receipt against a purchase order, putaway to bin locations, picking strategies (single order, batch, wave, zone), scanner and mobile app guidance, packing with checks, and the performance figures a warehouse lead runs the shift by.
Multi-carrier shipping & returns · Getting parcels out and back: carriers connected, label creation in bulk, rules that pick the carrier and service, customs documents for non-EU destinations, tracking and the notifications the recipient sees, a returns portal, and whether the customer uses its own carrier contracts or buys labels through the vendor.
Freight & transport management · Moving goods beyond parcels: pallet, groupage, full and part truckload, sea and air freight booked with carriers or forwarders, quotes and tenders compared, transport orders and documents (CMR, eCMR, delivery notes), shipment tracking across modes, freight cost audit, and CO2 emissions reported per shipment.
Integrations, automation & exit · How the tool fits the business around it: maintained connectors to shop systems, marketplaces, ERP and accounting (DATEV and the like), a documented API and webhooks, EDI for retail and logistics partners, rules that automate order routing and status updates, and a documented export of orders, stock and shipment history when the customer leaves.
European sovereignty · Who the contracting entity and the parent company are, where order, customer and shipment data are hosted, and who the subprocessors are (hosting, carriers' label APIs, payment, e-mail, analytics). Independently sourced by the sovereignty pipeline; recipient addresses flow to every connected carrier, so the processing chain counts, not only the server.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: subscription per tier, user, warehouse or module, the per-order, per-label or per-shipment fees, label rates and surcharges when shipping through the vendor's contracts, connector and setup fees, hardware, minimum term, and what happens to the data on cancellation.
Talent Management rubric v2
| Criterion | The Head of HR v1.0 | The Managing Director v1.0 | The People Analyst v1.0 | The Works Council Member v1.0 | The HR IT Integrator v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Performance reviews & calibration | 3.0 | 2.0 | 2.0 | 2.0 | 1.0 | 2.0 |
| Goals, OKRs & continuous feedback | 2.5 | 3.0 | 1.5 | 1.0 | 1.0 | 1.0 |
| Learning, skills & succession | 2.0 | 1.0 | 3.0 | 1.0 | 1.0 | 1.5 |
| Works council, visibility & AI disclosure | 2.0 | 1.5 | 1.0 | 3.0 | 1.5 | 3.0 |
| HRIS sync, integrations & data portability | 1.5 | 1.0 | 2.0 | 0.5 | 3.0 | 2.0 |
| European sovereignty | 1.0 | 1.0 | 0.5 | 2.5 | 2.0 | 1.5 |
| Pricing transparency | 1.0 | 2.0 | 0.5 | 0.5 | 0.5 | 2.0 |
The judges and the criteria
The Head of HR · Runs the annual review cycle for four hundred people and has to defend every rating in it. Wants criteria fixed before the cycle starts, calibration across departments, reminders that chase managers so HR does not have to, and a review history the employee can see and sign.
The Managing Director · Runs a sixty-person company without a talent team and wants goals everyone can see, regular one-to-ones that actually happen, and a yearly conversation that is prepared rather than improvised. Has no patience for a suite that needs a consultant before the first review goes out.
The People Analyst · Owns the skills model, the succession bench and the training budget. Wants skills profiles with gaps against role requirements, learning tied to those gaps rather than to a course catalogue, talent reviews per key role, and data that can be exported and analysed outside the tool.
The Works Council Member · Has to sign the works agreement before any of this goes live. Asks who can read a manager's private note, how small a team may be before survey results stop being anonymous, how long ratings are kept, and whether any AI feature summarises or scores colleagues without a human deciding.
The HR IT Integrator · Connects the tool to the HR system and the identity provider and will be asked for the data when the contract ends. Wants org chart and manager relations synced from the HRIS, SSO and SCIM, a documented API, and a full export of reviews and goals rather than one PDF per person.
The Skeptic · Has heard "high-performance culture", "bias-free reviews" and "AI-powered growth" from every vendor. Reads for the anonymity threshold behind the anonymous survey, what the AI review summary was built from, whether the "skills engine" is more than a tag list, and whether five years of reviews leave with the customer.
Performance reviews & calibration · The review cycle itself: configurable templates and rating scales, self, manager and 360° input, calibration across teams, and whether each rating can be traced back to criteria fixed before the cycle began.
Goals, OKRs & continuous feedback · The work between review cycles: individual and team goals or OKRs with alignment, progress check-ins, 1:1 meetings with shared agendas, and feedback and recognition — judged on whether the year-end review can draw on it rather than starting from memory.
Learning, skills & succession · Growing people rather than only rating them: learning paths or course delivery, a skills or competency framework, career paths and development plans, and talent reviews and succession planning for key roles.
Works council, visibility & AI disclosure · What the employer can put in a works agreement (BetrVG § 87 (1) no. 6, § 94): visibility and access rules per role, anonymity thresholds for surveys and upward feedback, retention and deletion of review data, access logging, and disclosure and control of every AI feature that summarises, scores or suggests ratings.
HRIS sync, integrations & data portability · How the tool fits next to the system of record and what leaves with the customer: employee and org-chart sync from the HR system, SSO and SCIM, collaboration-tool integrations, an API, and export of the full review, goal and feedback history.
European sovereignty · Where performance, feedback and survey data lives, who the contracting entity is, and who the subprocessors are — including the AI providers that summarise reviews and feedback. Independently sourced by the sovereignty pipeline. Weighted with the employment relationship in mind: these are judgements about people who did not choose the vendor.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: the pricing basis (per employee, per active user, per module), which of reviews, goals, engagement surveys and learning sit in which tier, add-ons for AI or analytics, and the minimum term.
Time Tracking & Attendance rubric v2
| Criterion | The Operations Lead v1.0 | The Payroll Officer v1.0 | The Works Council Advocate v1.0 | The Agency Owner v1.0 | The Field Supervisor v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Capture in the real workplace | 3.0 | 1.5 | 1.5 | 1.5 | 3.0 | 1.5 |
| Working-time law & audit record | 2.0 | 2.0 | 3.0 | 1.0 | 1.5 | 2.0 |
| Absence & shift planning | 2.5 | 1.5 | 1.5 | 1.0 | 2.0 | 1.0 |
| Project, cost-centre & billing | 1.0 | 0.5 | 0.5 | 3.0 | 1.5 | 1.0 |
| Payroll handoff | 1.5 | 3.0 | 1.0 | 1.0 | 1.0 | 1.5 |
| European sovereignty | 0.5 | 0.5 | 2.0 | 0.5 | 0.5 | 1.5 |
| Pricing transparency | 1.0 | 1.0 | 0.5 | 1.5 | 1.0 | 2.0 |
The judges and the criteria
The Operations Lead · Runs a 200-person operation with office, workshop and field staff, and has to record all of them since the BAG ruling. Wants capture that fits each of those groups and a roster that reflects reality. Unmoved by a beautiful desktop timer that half the workforce cannot use.
The Payroll Officer · Turns the recorded month into an payroll run and answers for it. Cares about surcharges for night, Sunday and holiday work, time accounts that reconcile, and corrections that arrive after the close. Treats "export to CSV" as an admission that the handoff was never designed.
The Works Council Advocate · Has co-determination over how working time is recorded (BetrVG §87 (1) 6) and will not approve a system that watches more than it measures. Asks what GPS actually stores, who can read an individual's day, what is logged and what can be switched off. Reads "productivity insights" as a warning.
The Agency Owner · Bills forty people's hours to clients and lives on the gap between recorded and billable. Wants project structure, rate cards that survive a mid-project change, budget warnings before the overrun, and an export the invoicing system takes. Attendance compliance is the floor, not the product.
The Field Supervisor · Supervises crews on sites with no reliable signal and no desks. Judges everything by whether it works in a basement at 6am: offline capture, a shared terminal, corrections a foreman can make without a support ticket. A cloud-only app is a tool that will be filled in from memory on Friday.
The Skeptic · Has read a great many pages claiming to be "BAG-konform" and wants to know which feature makes that true. Reads compliance claims for what they do not say: which module, at which tier, and whether the terminal in the photograph costs extra.
Capture in the real workplace · How time actually gets recorded across the workforces a buyer has — desk staff, field and site crews, shift and deskless workers — and what happens when the network is not there.
Working-time law & audit record · Whether the record satisfies the German recording duty (BAG 2022, § 3 ArbSchG) and the ArbZG rules around it — breaks, maximum hours, rest periods, retention — and whether it survives being inspected.
Absence & shift planning · Vacation, sickness and the shift or duty roster — the half of attendance that decides whether the time data means anything.
Project, cost-centre & billing · Whether recorded time can carry the allocation an agency, workshop or professional-services firm needs — project, task, cost centre, billable status — through to an invoice or a client report.
Payroll handoff · How the recorded month reaches payroll — DATEV, Lohn und Gehalt, an in-house system or the tax adviser — and how much of it is automated rather than retyped.
European sovereignty · Where the data lives, who the contracting entity is, who the subprocessors are, and whether that is documented rather than assumed. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions not proven either way are unknown, not non-European.
Pricing transparency · Whether a buyer can compute the real annual invoice for their headcount — including terminals, modules and minimums — from public pages alone.
Transactional Email rubric v1
| Criterion | The SaaS Developer v1.0 | The Platform Engineer v1.0 | The Shop Operator v1.0 | The Data Protection Officer v1.0 | The Agency Lead v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Sending API, SMTP & developer experience | 3.0 | 2.0 | 1.5 | 1.0 | 2.0 | 1.5 |
| Deliverability & sender reputation | 2.5 | 2.5 | 3.0 | 1.0 | 2.0 | 2.5 |
| Message logs, events & webhooks | 2.5 | 3.0 | 2.0 | 1.5 | 2.0 | 2.0 |
| Message data, retention & security | 1.5 | 2.0 | 1.5 | 3.0 | 1.5 | 2.5 |
| Reliability, accounts & support | 1.5 | 3.0 | 2.5 | 1.0 | 3.0 | 2.0 |
| European sovereignty | 1.5 | 1.5 | 2.0 | 3.0 | 1.5 | 2.5 |
| Pricing transparency | 1.5 | 1.0 | 2.0 | 0.5 | 2.0 | 2.0 |
The judges and the criteria
The SaaS Developer · Backend developer at a twelve-person B2B SaaS in Hamburg, built on Laravel, that sends sign-up confirmations, password resets, invoices and weekly digests to 40,000 users. Has replaced the mail driver once already and does not want to again. Wants an official driver for the framework, templates with variables, a test mode that never reaches a real inbox, signed webhooks for bounces, and a log that answers "did this user get the reset mail?" without opening a ticket.
The Platform Engineer · Platform engineer at a fintech in Frankfurt whose customers sign in with a one-time code sent by email, so a delay of three minutes is an outage. Is on call for it. Reads the status page history before the feature list, wants the SLA in writing with credits, mail queued and retried during an incident, delivery latency per mailbox provider, alerts on bounce spikes, and scoped API keys that can be rotated without a deploy.
The Shop Operator · Runs a Shopware shop for kitchen equipment in Germany and Austria with 900 orders a week. Order confirmations, invoices and shipping notices went out through the hosting provider's mail server until a customer found theirs in spam and the support inbox filled up. Wants guided SPF and DKIM set-up a non-specialist can follow, a plugin for the shop, order mail kept apart from the newsletter, and someone to ask when Gmail starts refusing.
The Data Protection Officer · In-house data protection officer at a health software company whose appointment reminders and lab-result notices carry patients' names. Treats the sending service as a processor like any other. Reads the DPA, the subprocessor list and the retention section first: whether message bodies are stored and for how long, whether open tracking can be turned off, which entity signs, and whether the EU region covers the logs as well as the mail.
The Agency Lead · Technical lead at a web agency in Cologne that builds and runs thirty client applications, from a booking portal to a membership site, each sending its own mail from the client's domain. Wants one account with a sub-account, keys and limits per client, domains verified by API, roles so a client can see their own logs and nothing else, and a price per client that can be written into a maintenance contract.
The Skeptic · Has seen "99% deliverability" with no method behind it, "dedicated IPs" that shared a pool with bulk senders, "EU hosting" that covered the API endpoint but not the logs, and seven days of log retention discovered during an incident on day eight. Reads that a vendor is "trusted by thousands of developers" and asks how bounces are suppressed, what is stored per message, which entity signs the DPA — and what moving away would cost.
Sending API, SMTP & developer experience · How an application sends mail: a REST API and an SMTP relay with their limits stated, official SDKs and drivers for named languages and frameworks (PHP and Laravel, Node, Python, Ruby and Rails, Java, Go, .NET), stored templates with variables and versions, batch sending, attachments, idempotency keys, scheduled sending, a test or sandbox mode that does not deliver, inbound email parsed into a webhook, and the quality of the API reference and guides.
Deliverability & sender reputation · What the vendor does so the mail reaches the inbox: guided SPF, DKIM and DMARC set-up with a custom return path and tracking domain, shared IP pools and how senders on them are vetted and policed, dedicated IPs with automatic warm-up, transactional and bulk mail kept on separate streams or IP pools, bounces, complaints and unsubscribes turned into suppressions automatically, feedback loops with mailbox providers, blocklist and DMARC monitoring, compliance with the Gmail and Yahoo bulk-sender rules, and published delivery times or inbox placement with their method.
Message logs, events & webhooks · What the team can see about each message once the application has handed it over: a message log searchable by recipient, subject, tag or message ID, the full event history (processed, delivered, deferred, bounced with the remote server's answer, opened, clicked, complained), how long logs and message content are kept, event webhooks with retries and a signature, an events API, dashboards and statistics per stream, tag or domain, alerts on bounce or complaint spikes, and access for a support team without developer rights.
Message data, retention & security · What is stored about each message and what the customer controls: whether message bodies are stored or only metadata, retention periods and the setting to shorten them, deletion of a recipient's data on request, open and click tracking that can be switched off per stream or message, TLS for delivery with an option to require it, encryption at rest, API keys with scopes and per-domain restrictions, IP allow-listing, two-factor authentication and SSO for the dashboard, an audit log, a vulnerability disclosure programme, and security certifications or audits with their scope. Where the data is processed and by whom is scored under sovereignty.
Reliability, accounts & support · Whether the platform can be relied on and run by a team: a public status page with incident history, uptime SLA and service credits published, redundancy or failover across data centres described, queueing and retry of mail during outages, sub-accounts or servers per application, client or tenant, team members with roles, separate environments, support channels and response times per plan, named migration help, and integrations with platforms that send mail on the customer's behalf (WordPress, Shopify, Shopware, Supabase, Vercel and similar).
European sovereignty · Who the contracting entity and the parent company are, where messages, logs and recipient data are processed and stored, whether an EU region can be chosen and what it covers, and who the subprocessors are (cloud hosting, sending infrastructure, logging, support and payment tools). Independently sourced by the sovereignty pipeline; every message carries personal data, so the whole sending chain counts, not only the dashboard.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per tier by monthly message volume, the price per additional thousand messages, the free tier and its limits, what dedicated IPs, extra log retention, sub-accounts, SSO and support plans cost, minimum term, and whether unused volume carries over.
Translation & Localization rubric v1
| Criterion | The Localization Manager v1.0 | The App Developer v1.0 | The In-House Document Translator v1.0 | The Data Protection Officer v1.0 | The E-Commerce Marketer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Machine translation & AI quality | 2.0 | 1.5 | 3.0 | 1.0 | 2.5 | 1.5 |
| Translation memory, terminology & review workflow | 3.0 | 1.5 | 0.5 | 1.0 | 1.5 | 1.0 |
| Integrations, file formats & developer tools | 2.0 | 3.0 | 1.5 | 0.5 | 2.5 | 1.0 |
| Confidentiality of translated content | 1.5 | 1.0 | 3.0 | 3.0 | 1.0 | 2.5 |
| Data export, portability & self-hosting | 2.0 | 2.5 | 1.0 | 1.5 | 1.5 | 3.0 |
| European sovereignty | 1.5 | 1.0 | 2.0 | 3.0 | 1.0 | 2.5 |
| Pricing transparency | 1.0 | 1.5 | 1.5 | 0.5 | 2.0 | 2.0 |
The judges and the criteria
The Localization Manager · Runs localization for a Hamburg software company whose product, help centre and marketing site ship in fourteen languages, with two agencies and a pool of freelancers. Every release brings a few thousand new strings and a deadline. Wants one translation memory and termbase across all content, machine translation that respects the glossary, review steps per language, QA checks that stop a broken placeholder before it ships, and cost and progress per vendor in one view.
The App Developer · Lead developer of a web app and two mobile apps at a Vienna start-up, with strings in JSON, xcstrings and Android XML. Has hand-merged translation files once and will not do it again. Wants a CLI and a GitHub sync that opens pull requests, over-the-air updates so a typo fix does not need an app store release, an API that does everything the interface does, and ideally an open-source edition they could run themselves if the vendor changes course.
The In-House Document Translator · Works in the legal and export team of a machine builder in Baden-Württemberg with customers in France, Italy, Poland and China. Translates contracts, operating manuals and supplier correspondence every day, with no translation management system and no wish for one. Needs translations that read like the company wrote them, the company's terms kept through a glossary, Word and PDF files back with their layout intact, and a written promise that a draft contract is not kept or used to train anything.
The Data Protection Officer · Data protection officer of a health insurer whose staff translate letters to members, HR documents and internal guidelines. Found a free translator in the proxy logs and had to explain to the board what had been pasted into it. Reads the terms before the feature page: how long texts are kept, whether they train a model, which engines and LLM providers a platform passes them to, who the subprocessors are and where, and whether the contract names a European entity.
The E-Commerce Marketer · Runs marketing for a Shopify shop selling cycling apparel from Munich, live in German and English and due in French, Italian, Dutch and Spanish before the spring season. Has no developer and no translator on staff. Wants product pages, checkout and emails translated in days, a way to fix a bad product name by hand, multilingual SEO that search engines index, and a monthly price that does not double when the catalogue grows.
The Skeptic · Has seen "human quality" on an engine nobody has evaluated in public, "we never store your data" next to a TMS that forwards every segment to three LLM providers, and a translation memory built over six years that could only leave as a spreadsheet. Reads that a product is "enterprise-grade secure" and asks how long the text is kept, which models it reaches, and whether the memory and termbase export as TMX and TBX — and what leaving would cost.
Machine translation & AI quality · What the machine translation does and how well it is controlled: the languages and language pairs covered, the engine (own neural or LLM model, or a choice of third-party engines such as DeepL, Google, Microsoft or an LLM), glossaries and formality applied during translation, document translation that keeps the layout (Word, PowerPoint, PDF, InDesign), custom or adaptive models trained on the customer's own translations, automatic quality estimation or scoring, and published evaluations of translation quality.
Translation memory, terminology & review workflow · How translation is managed as an ongoing process: translation memory with fuzzy matches, a termbase or glossary managed centrally, style guides, review and approval stages, automated QA checks (placeholders, tags, length, terminology, punctuation), an in-context or visual editor, screenshots and context for translators, tasks and deadlines, roles per language, and ordering or inviting human translators and agencies inside the product.
Integrations, file formats & developer tools · How content gets in and out: the file formats supported (XLIFF, PO, JSON, YAML, Android XML, iOS strings and xcstrings, Office documents, InDesign), a REST API and CLI, SDKs and over-the-air updates for apps, Git repository sync (GitHub, GitLab, Bitbucket) and CI pipelines, connectors for CMS, shop and design tools (WordPress, Contentful, Shopify, Figma), browser and office add-ins, webhooks, and a JavaScript snippet or proxy for website translation.
Confidentiality of translated content · What happens to the text a customer translates: whether source and target texts are stored and for how long, deletion after translation, whether customer content is used to train the vendor's or a third party's models, which machine translation and LLM providers a TMS sends text to and whether that can be restricted or switched off, encryption in transit and at rest, single sign-on, roles and audit logs, and certifications (ISO 27001, SOC 2) with their scope. Where the text is processed is scored under sovereignty.
Data export, portability & self-hosting · Whether translation assets stay the customer's and can leave with them: export of translation memory and termbase in open formats (TMX, TBX, XLIFF, CSV), export of all projects and files, import from another TMS, an API that can read every asset, the return or deletion of data on termination, open-source code and a self-hosted or on-premise edition.
European sovereignty · Who the contracting entity and the parent company are, where texts are translated, stored and processed, and who the subprocessors are (hosting, machine translation engines, LLM providers, CDN for over-the-air delivery, support and payment tools). Independently sourced by the sovereignty pipeline; translated texts often hold personal data and trade secrets, so the whole chain counts, including the engines a TMS calls. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per tier by characters, words, keys, hosted words or seats, what happens when the volume exceeds the tier, the number of users, projects and languages included, which features (machine translation volume, AI credits, SSO, integrations, API access) cost extra, the free tier and its limits, the self-hosted edition and its support, minimum term and setup.
Uptime Monitoring & Status Pages rubric v1
| Criterion | The Agency Developer v1.0 | The SaaS Platform Engineer v1.0 | The Customer Support Lead v1.0 | The E-Commerce Operations Manager v1.0 | The Information Security Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Checks, locations & failure confirmation | 3.0 | 3.0 | 1.5 | 2.5 | 1.5 | 2.0 |
| Alerting, escalation & on-call | 2.0 | 3.0 | 1.5 | 2.5 | 2.0 | 1.5 |
| Status pages & incident communication | 1.5 | 2.0 | 3.0 | 1.0 | 1.5 | 1.5 |
| API, monitoring as code & team administration | 2.5 | 2.5 | 1.0 | 1.0 | 2.5 | 1.5 |
| Uptime reports, data & the vendor's own reliability | 2.0 | 1.5 | 2.0 | 2.0 | 2.5 | 3.0 |
| European sovereignty | 1.5 | 1.0 | 1.5 | 1.5 | 3.0 | 2.5 |
| Pricing transparency | 2.0 | 1.0 | 1.0 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The Agency Developer · Runs hosting and maintenance at a fifteen-person web agency with sixty client sites on WordPress, TYPO3 and Shopware. Has learned about an expired certificate from a client's angry phone call once and does not want a second time. Wants HTTP, keyword, SSL and domain expiry checks set up in bulk, client groups with their own status pages and monthly uptime reports, and a price per monitor that still works at two hundred monitors.
The SaaS Platform Engineer · Platform engineer at a forty-person B2B SaaS in Berlin, one of four people on the on-call rotation. Wants multi-step API checks with assertions, kept in Terraform next to the services they test, failures confirmed from a second location before anyone is woken, phone calls and escalation when an alert is not acknowledged, and a status page that updates without someone logging in at 3 a.m.
The Customer Support Lead · Leads a support team of nine at a software company whose customers are tax advisers and payroll offices. During the last outage the team answered three hundred tickets that all asked the same question. Wants a status page on the company's own domain with components customers recognise, incident templates, subscribers notified by email, a private page for the largest accounts, and an uptime history they can point to in a contract renewal.
The E-Commerce Operations Manager · Runs operations for an online shop selling garden furniture in Germany, Austria and Switzerland, with half the year's revenue between March and June. The homepage once answered 200 while the checkout threw an error for six hours. Wants the checkout and the payment page checked, not only the homepage, an SMS or call to whoever is on duty that night, and a report that shows the agency what the downtime cost.
The Information Security Officer · Information security officer at a mid-sized logistics company that falls under NIS2 and is working towards ISO 27001. Needs every outage recorded with detection time, response and resolution, in a form an auditor accepts. Reads the subprocessor list before the feature page, because the on-call staff's mobile numbers and the status page subscribers are personal data, and wants single sign-on and an audit log before anyone gets a login.
The Skeptic · Has seen "30-second checks from 20 locations" that paged the whole team for a single probe's network glitch, a status page that went down with the product it reported on, and "unlimited SMS" with a fair-use clause on page nine. Asks how a failure is confirmed, how long the history is kept and whether it can be exported, where the monitor itself publishes its own outages — and what leaving would cost.
Checks, locations & failure confirmation · What can be monitored and how reliably a failure is detected: HTTP(S) with status code and keyword checks, TCP and port, ping, DNS records, SSL certificate and domain expiry, cron jobs and heartbeats, multi-step API checks with assertions, browser or transaction checks of a login or checkout, the shortest check interval, the number and regions of probe locations, the re-check from a second location before an alert, timeouts and response time thresholds, and private locations inside the customer's own network.
Alerting, escalation & on-call · How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.
Status pages & incident communication · How customers and colleagues are told: public status pages on a custom domain with SSL, components and component groups fed automatically by monitors or set by hand, incident updates and scheduled maintenance announcements, subscribers notified by email, SMS, RSS or webhook, uptime history shown per component, private or password-protected pages for internal teams or single customers, branding and custom CSS, several languages, page templates, and how the status page itself stays online when the main product is down.
API, monitoring as code & team administration · How the tool fits a team and a deployment pipeline: a documented REST API to create and read monitors, status pages and incidents, a Terraform provider, CLI or monitoring-as-code workflow, checks run from CI/CD before a deploy, bulk import of monitors, integrations with ticketing and chat tools, team members with roles, single sign-on (SAML) and SCIM, audit logs, several teams or client accounts in one organisation, white-label or client reporting for agencies, and two-factor authentication.
Uptime reports, data & the vendor's own reliability · What the record is worth and whether the monitor itself can be trusted: uptime and SLA reports per monitor and period, response time charts and percentiles, scheduled reports by email, client-facing reports, how long check results and incident history are kept, export of results by CSV or API, the vendor's own public status page and incident history, its SLA, the probe IP addresses and user agent published for allow-listing, and an open-source or self-hosted edition.
European sovereignty · Who the contracting entity and the parent company are, where account data, alert contacts (names and phone numbers of the people on call), status page subscribers and check results are stored and processed, and who the subprocessors are (hosting, SMS and phone gateways, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Probe locations outside Europe are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per tier by number of monitors, check interval and status pages, team seats and on-call responders, what SMS and phone alerts cost, which features (multi-step or browser checks, SSO, longer retention, private locations, white-label) cost extra, the free tier and its limits, overage handling, minimum term and VAT.
Video Conferencing rubric v2
| Criterion | The IT Administrator v1.0 | The Security Officer v1.0 | The Works Council Advocate v1.0 | The Educator v1.0 | The Accessibility Advocate v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| The meeting itself | 3.0 | 1.0 | 1.0 | 2.5 | 1.5 | 1.5 |
| Encryption & meeting access | 1.5 | 3.0 | 1.5 | 1.0 | 0.5 | 2.0 |
| Reach & accessibility | 2.0 | 0.5 | 1.0 | 3.0 | 3.0 | 1.0 |
| Recordings, retention & admin control | 1.0 | 2.0 | 3.0 | 1.5 | 1.0 | 1.5 |
| Integrations & deployment | 2.5 | 1.0 | 0.5 | 1.0 | 0.5 | 1.0 |
| European sovereignty | 1.0 | 3.0 | 2.5 | 1.5 | 1.0 | 1.5 |
| Pricing transparency | 1.0 | 0.5 | 0.5 | 1.5 | 1.0 | 2.0 |
The judges and the criteria
The IT Administrator · Gets the call when the board meeting will not start. Wants capacity published rather than promised, room systems that work, SSO, and diagnostics after a bad call. Judges a product by its worst meeting, not its demo.
The Security Officer · Wants to know what the vendor can see, and reads "encrypted" as a question rather than an answer. Asks which meetings get end-to-end encryption, what stops working when they do, who holds the keys, and who can walk into a meeting with a link.
The Works Council Advocate · A recorded meeting is personal data about everyone in it. Wants to know who may record, who is told, how long it is kept, and whether attention tracking or attendance analytics can be switched off outright. Reads engagement scoring as surveillance with a chart.
The Educator · Teaches thirty people who join from whatever they have, half of them on a phone in a dead spot. Cares that the browser works without an install, that guests need no account, that breakout rooms are usable, and that nobody is excluded by bandwidth or by a missing caption.
The Accessibility Advocate · Judges the product by whether a deaf colleague and a screen-reader user can run the meeting, not merely attend it. Wants live captions, keyboard operation, a published conformance report, and dial-in for people with no usable connection. Treats an accessibility page with no report as a marketing page.
The Skeptic · Has read many pages claiming end-to-end encryption and wants the sentence that says which meetings, on which plan, with what turned off. Also reads for the participant cap, the dial-in minutes, and where recording storage stops being free.
The meeting itself · Whether the call works: participant capacity, video and audio quality under load, screen sharing, breakout rooms, moderation, and what happens on a bad connection.
Encryption & meeting access · What is actually encrypted and against whom, plus who can get into a meeting. Judged on documented mechanism rather than on the word "encrypted".
Reach & accessibility · Whether everyone who needs to join can: browser without an install, dial-in, low bandwidth, guests without accounts, captions and keyboard operation.
Recordings, retention & admin control · A recording is personal data about everyone in the room. Who may record, who is told, where it is stored, how long it lives, and what the works council can switch off under BetrVG §87(1) no. 6.
Integrations & deployment · Calendar, identity and the wider stack — plus, in this category, whether the product can be run on the customer's own infrastructure at all.
European sovereignty · Where media and metadata are processed, who the contracting entity is, which subprocessors carry the traffic. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily. Dimensions the evidence does not establish are unknown, not non-EU.
Pricing transparency · Whether a buyer can compute the annual invoice for their host count — including the capacity, dial-in and recording storage they actually need — from public pages alone.
Web Analytics rubric v1
| Criterion | The E-Commerce Marketing Lead v1.0 | The Data Protection Officer v1.0 | The Agency Developer v1.0 | The Growth Analyst v1.0 | The Public-Sector Site Owner v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Traffic, sources & campaign reports | 2.5 | 1.0 | 1.5 | 2.0 | 2.0 | 1.0 |
| Goals, events, funnels & e-commerce | 3.0 | 1.0 | 1.5 | 3.0 | 0.5 | 1.0 |
| Consent-free operation & data minimisation | 2.0 | 3.0 | 2.0 | 1.5 | 3.0 | 2.5 |
| Data access, export & self-hosting | 1.5 | 2.0 | 2.0 | 2.5 | 2.0 | 3.0 |
| Installation, integrations & performance | 2.0 | 1.0 | 3.0 | 1.5 | 1.5 | 1.5 |
| European sovereignty | 1.5 | 2.5 | 1.5 | 1.0 | 2.5 | 2.5 |
| Pricing transparency | 1.5 | 0.5 | 2.0 | 1.0 | 1.5 | 2.0 |
The judges and the criteria
The E-Commerce Marketing Lead · Runs marketing for a Shopware shop selling outdoor gear in Germany and Austria, with a monthly ad budget split between Google, Meta and two price comparison sites. Since the consent banner went live, a third of the orders no longer show a source. Wants revenue per campaign that matches the shop backend, a checkout funnel that shows where carts are left, conversions sent back to the ad platforms, and numbers that hold without a click on "accept".
The Data Protection Officer · External data protection officer for eleven mid-sized companies, three of which still ran Universal Analytics when the Austrian authority ruled on it. Reads the data policy before the feature page: which fields are stored, how a visitor is counted without a cookie, whether the IP address is cut before it is written, who the subprocessors are and where. Signs off a site without a banner only when the vendor states its reading of §25 TDDDG in writing.
The Agency Developer · Lead developer at a twelve-person web agency that runs forty client sites on WordPress and TYPO3 and a few Shopify shops. Installs the analytics once per site and answers for it for years. Wants a small script or server-side collection, a plugin per CMS, an own tracking domain so ad blockers do not cut the numbers in half, client accounts with their own logins, and a price that does not jump when one client goes viral.
The Growth Analyst · Product and growth analyst at a B2B SaaS in Munich with a marketing site, a web app and a mobile app. Needs signups traced from the first campaign click to the first paid invoice, funnels and cohorts on custom events, and the raw events in the company's warehouse every night. Has moved tracking twice and knows that a tool without a raw export means starting the history again from zero.
The Public-Sector Site Owner · Web editor for a district administration whose site serves 400,000 residents, from vehicle registration to daycare places. The state data protection authority publishes guidance on analytics, and the council will not show a cookie banner on a public service. Needs to know which pages people search for and where forms are abandoned, with data that stays in Germany or on the municipal data centre's own servers, and a contract the procurement office can sign.
The Skeptic · Has seen "no cookie banner needed" on a tool that fingerprints every visitor, "EU-hosted" on a proxy in front of a US data store, and "unlimited" data history that ends with the subscription. Reads that a product is "GDPR-compliant" and asks which ruling the vendor means, what is stored per visit, whether the history can be exported in a format another tool imports — and what leaving would cost.
Traffic, sources & campaign reports · What the standard reports show: page views, visits and visitors, entry and exit pages, referrers, search engines and social networks as sources, campaigns tagged with UTM parameters, countries, devices and browsers, a real-time view, date comparisons, segments and filters, custom dashboards, scheduled email reports, shared or public dashboards, and whether reports are sampled or complete.
Goals, events, funnels & e-commerce · How the product measures what visitors do: goals for pages and events, custom events with properties, outbound links, downloads, form submissions and scroll depth tracked without code, funnels with drop-off, e-commerce tracking of orders, revenue and products, attribution of conversions to channels and campaigns, cohorts and retention, and conversion data passed back to ad platforms.
Consent-free operation & data minimisation · What is collected and whether a consent banner is needed: a cookieless mode with how visitors are counted (daily hash, server-side fingerprint, no identifier), IP addresses truncated or not stored, no cross-site or cross-device profile and no use of data for the vendor's own purposes, data retention settings, opt-out and Do Not Track, a consent mode for features that do need consent, the vendor's stated reading of §25 TDDDG, the CNIL consent exemption and the authorities' rulings on Google Analytics, and guidance for the site's privacy policy. Where the data is processed is scored under sovereignty.
Data access, export & self-hosting · Whether the data stays the customer's and can leave with them: a reporting API and a raw event export, CSV export of every report, a scheduled export or sync to a data warehouse or BI tool (BigQuery, Snowflake, Looker Studio), no data sampling or limits on history, import of historical data from Google Analytics or another tool, open-source code, and a self-hosted or on-premise edition the customer runs on its own servers.
Installation, integrations & performance · What it takes to install and run: the size and loading of the tracking script, plugins and documented set-ups for named CMS and shop systems (WordPress, TYPO3, Shopify, Shopware, WooCommerce), single-page apps and mobile SDKs, a tag manager or Google Tag Manager template, server-side tracking and first-party proxying to avoid ad blockers, team roles and permissions, client and agency accounts, single sign-on, and an uptime or status page.
European sovereignty · Who the contracting entity and the parent company are, where visitor data is collected, stored and processed, and who the subprocessors are (script CDN, collection endpoint, hosting, email reports, support and payment tools). Independently sourced by the sovereignty pipeline; visitor data is personal data under European rulings, so the whole chain counts, not only the database. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
Pricing transparency · Whether a buyer can compute the real annual cost from public pages alone: price per tier by monthly page views or events, what happens when traffic exceeds the tier, the number of sites and users included, which features (e-commerce, funnels, raw export, API, SSO, longer retention) cost extra, the free tier and its limits, the self-hosted edition and its support, minimum term and setup.
Web Hosting rubric v1
| Criterion | The Agency Lead v1.0 | The Small-Business Owner v1.0 | The Shop Operator v1.0 | The Freelance App Developer v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Performance, uptime & infrastructure | 2.0 | 1.5 | 3.0 | 2.0 | 1.0 | 2.0 |
| Control panel, WordPress & developer tooling | 3.0 | 1.0 | 1.5 | 3.0 | 0.5 | 1.0 |
| Security, backups & recovery | 2.5 | 2.5 | 2.5 | 1.5 | 2.5 | 2.0 |
| Scaling, migration & exit | 2.0 | 1.0 | 2.5 | 2.5 | 1.5 | 3.0 |
| Support, domains & email | 2.0 | 3.0 | 2.0 | 1.0 | 1.0 | 1.5 |
| European sovereignty | 1.5 | 1.5 | 1.5 | 1.5 | 3.0 | 2.5 |
| Pricing transparency | 2.0 | 2.0 | 1.5 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The Agency Lead · Runs a fifteen-person web agency that hosts sixty client sites, most on WordPress, some on TYPO3 and two WooCommerce shops. Every site is one more login, one more update window and one more call when it breaks. Wants one panel with client projects, staging and push to live, backups they can restore without opening a ticket, roles for freelancers, a way to hand a project and its invoice to the client, and a price per site that does not double after the first year.
The Small-Business Owner · Owns a heating and plumbing firm with twelve staff, a WordPress site a nephew built and twelve mailboxes on the same contract. Does not know what PHP is and does not want to learn it. When the site shows a warning or the mail stops, they need someone on the phone in German the same day, backups that the support can restore, and an invoice that matches the price on the website, year after year.
The Shop Operator · Runs a Shopware shop for coffee equipment with 4,000 orders a month and a Black Friday that brings ten times the usual traffic in one weekend. Every minute offline is lost revenue and a lost ad budget. Reads the resources per tariff, the caching and the SLA before the price, wants to scale for one weekend without moving the shop, and wants yesterday's database back within the hour if an update goes wrong.
The Freelance App Developer · Freelance developer who builds Laravel and Node apps for small clients and runs them for years afterwards. Deploys from Git, needs SSH, Composer, cron, queues and a current PHP version, and sets servers up from scripts rather than by clicking. Wants an API and a CLI that cover servers, snapshots, firewalls and DNS, resource limits stated in numbers, and a stack that runs anywhere else if the client ever moves.
The Data Protection Officer · External data protection officer for a group of medical practices and two law firms whose sites take appointment requests and contact forms. Reads the DPA, the subprocessor list and the certifications before anything else: where the servers and the backups are, which group company outside the EU can reach them, how customers are isolated from each other, and when data is deleted after the contract ends.
The Skeptic · Has seen "unlimited" storage end at an inode limit in the small print, "99.9 % uptime" with no credit when it was missed, "free daily backups" that only the support could restore for a fee, and a tariff from 1 € that cost eight times as much in the second year. Asks what the limits are in numbers, what the SLA pays, who can reach the data, and what it costs to take everything and leave.
Performance, uptime & infrastructure · What runs the sites and how reliably: CPU, RAM and storage per tariff stated, SSD or NVMe storage, current PHP versions and how long old ones are kept, HTTP/2 or HTTP/3, server-side caching (OPcache, Redis, a page cache), a CDN, databases and their limits, resources that are guaranteed rather than shared without a stated limit, an uptime SLA with a service credit, a public status page with incident history, and redundancy of the platform. Where the data centre is located is scored under sovereignty.
Control panel, WordPress & developer tooling · How sites are set up and run day to day: the control panel or console, one-click installers for named CMS and shop systems, managed WordPress features (automatic core and plugin updates, staging, cloning, a search-and-replace), SSH, SFTP, Git deployment, Composer, cron jobs, a PHP version and settings per site, databases and phpMyAdmin or an equivalent, log access, a public API and command-line tool, infrastructure-as-code support, team members and roles, and client or project management for agencies. On a cloud server: images, snapshots, firewalls, private networks and the API that manages them.
Security, backups & recovery · How the sites are protected and how fast they come back: isolation between customers (containers, separate PHP processes, chroot), free SSL with automatic renewal, a web application firewall, malware scanning and cleanup, DDoS protection, two-factor login to the panel, brute-force protection, backup frequency and retention, off-site or geo-redundant backup copies, self-service restore of files and databases from a point in time, restore of single sites or tables, security updates handled by the vendor on managed tariffs, and security certifications (ISO 27001, BSI C5, SOC 2) with their scope.
Scaling, migration & exit · What it takes to grow and what it takes to leave: tariff changes up and down without a migration, resource limits stated rather than "unlimited" with a fair-use clause, add-on resources, the path from shared hosting to a server or cluster within the same vendor, a free or paid migration service from another host, standard tooling that runs elsewhere (no proprietary stack lock-in), full export of files, databases and mailboxes, domain transfer out without a fee, cancellation periods and minimum terms, and the deletion of data after the contract ends.
Support, domains & email · Who helps and what comes with the hosting: support channels (phone, chat, ticket, email), hours and languages, response times stated or guaranteed, technical depth (WordPress or server experts, help with a hacked site), a help centre and documentation, a premium or managed support option, an agency or partner programme, and the domains, SSL certificates and mailboxes included or bookable in the same account, with their DNS management and mail features (IMAP, webmail, spam filter, mailbox size).
European sovereignty · Who the contracting entity and the parent company are, where the servers, backups and support sit, and who the subprocessors are (data centre operator, CDN, DNS, mail filtering, support and payment tools). Independently sourced by the sovereignty pipeline; a host stores everything the customer's sites collect, so the whole chain counts, including where backups are kept and which non-EU group company can reach the data.
Pricing transparency · Whether a buyer can compute the real cost over the contract from public pages alone: the price per tariff for the first term and on renewal, minimum term and how the price depends on it, setup fees, what is included (domains, mailboxes, SSL, backups, restores, migration), what costs extra (additional PHP versions or extended support, more backups, a restore, premium support, staging, CDN), traffic or resource overage, VAT treatment, and the cancellation terms.
Website Builders rubric v1
| Criterion | The Small-Business Owner v1.0 | The Freelance Web Designer v1.0 | The Marketing Lead v1.0 | The Practice Owner v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Editor, templates & design control | 2.0 | 3.0 | 2.0 | 1.5 | 0.5 | 1.5 |
| Hosting, domains & portability | 1.5 | 2.5 | 1.5 | 1.5 | 2.0 | 2.5 |
| SEO, analytics & visibility | 2.5 | 2.0 | 3.0 | 2.0 | 1.0 | 1.5 |
| Forms, bookings & business features | 2.0 | 1.5 | 2.5 | 3.0 | 2.0 | 1.5 |
| Imprint, privacy & cookie compliance | 2.5 | 1.5 | 1.5 | 2.5 | 3.0 | 2.5 |
| European sovereignty | 1.0 | 1.0 | 1.5 | 2.0 | 3.0 | 2.5 |
| Pricing transparency | 2.0 | 1.5 | 1.0 | 1.5 | 0.5 | 2.0 |
The judges and the criteria
The Small-Business Owner · Runs a joinery with six staff and builds the company website on a Sunday afternoon. Wants a template that looks like a craftsman and not like a start-up, to be found when someone nearby searches for a carpenter, an enquiry form that lands in the inbox, the imprint and cookie banner handled without a lawyer, and a price that is still clear in the second year.
The Freelance Web Designer · Builds about twenty sites a year for doctors, restaurants and consultants, and looks after them afterwards. Wants real control over layout, mobile breakpoints and type, reusable sections across client sites, a client login that cannot break the design, backups that restore in one click, and a way to take the site and its content elsewhere if the client or the tool changes.
The Marketing Lead · Owns the website of a forty-person engineering firm and is measured on enquiries, not on page views. Wants landing pages built without waiting for the agency, clean URLs, redirects and structured data, analytics that work without a consent wall in front of every visit, and form entries that reach the CRM instead of a shared mailbox.
The Practice Owner · Runs a physiotherapy practice with four therapists and a waiting list. Wants patients to book and cancel appointments online, a contact form that does not send health details around in plain email, a site an older patient can read and use, a cookie banner that holds up if the regulator asks, and the data kept in Europe.
The Data Protection Officer · Serves as external data protection officer for thirty small companies and reviews their websites once a year. Wants a consent banner that blocks scripts and embeds until the visitor agrees, fonts and maps that do not leave for the US on page load, a data processing agreement and subprocessor list that can be filed, form entries with a retention period, and hosting that is named rather than implied.
The Skeptic · Has seen "your website for 1 euro" renew at thirty, templates that only exist inside the builder, an export that turns out to be the blog posts alone, and a domain that costs a fee to move. Reads "GDPR compliant" next to a cookie banner that loads trackers before anyone clicks, and a subprocessor list that stops at the CDN — and asks what leaving would cost.
Editor, templates & design control · How a site gets built and how far the owner can shape it: the editor (drag and drop, sections, AI drafts), the template range, responsive and mobile editing, fonts and brand styles, multilingual pages, custom code, and roles for collaborators or clients.
Hosting, domains & portability · What runs the site once it is built: included hosting, custom domains and domain registration, SSL, email mailboxes, speed (CDN, image optimisation), backups and restore, availability commitments — and whether pages, content and media can be exported when the owner moves on.
SEO, analytics & visibility · How the site is found and measured: page titles and descriptions, clean URLs and redirects, sitemaps and indexing, structured data, local SEO, page speed for search, built-in or connectable analytics, newsletter or social sharing, and guidance for the owner who is not an SEO.
Forms, bookings & business features · What the site does for the business beyond showing pages: contact and custom forms with spam protection and notifications, where form entries are stored, appointment bookings, member areas, events, integrations with CRM or calendar, payments and a small shop as an add-on — judged as features of a website, not as a shop system.
Imprint, privacy & cookie compliance · What the product does so that the owner's site is legal in Germany and the EU: an imprint page, privacy-policy and legal-text generators or partners, a cookie consent banner that blocks scripts until consent, GDPR-compliant forms, a data processing agreement for visitor data, fonts and media served without third-country transfers, and accessibility under the European Accessibility Act.
European sovereignty · Who the contracting entity and the parent company are, where the sites, the form entries and the visitor data are hosted, and who the subprocessors are (hosting, CDN, email delivery, analytics, payments, AI features). Independently sourced by the sovereignty pipeline; the data subjects here are the owner's own visitors and customers, so the whole chain counts, not only the editor.
Pricing transparency · Whether a buyer can compute the real cost over two or three years from public pages alone: the monthly price per plan, the introductory price and how long it lasts, the renewal price after it, setup fees, minimum term and notice, domain and mailbox renewals, transaction fees on sales, and which features (ad removal, extra languages, bookings, more storage) cost extra.
Whistleblowing Portals rubric v2
| Criterion | The Compliance Officer v1.0 | The Reporter's Advocate v1.0 | The SME Operator v1.2 | The Group Counsel v1.0 | The Security Auditor v1.0 | The Skeptic v1.2 |
|---|---|---|---|---|---|---|
| Reporting channels & reporter experience | 1.0 | 3.0 | 1.5 | 1.0 | 1.0 | 1.0 |
| Case management & deadline discipline | 3.0 | 1.0 | 1.0 | 1.5 | 1.0 | 1.0 |
| Legal compliance alignment | 2.5 | 1.0 | 2.0 | 2.0 | 0.5 | 1.0 |
| Security & anonymity assurance | 1.0 | 2.5 | 0.5 | 1.0 | 3.0 | 1.5 |
| Group & multi-entity capability | 0.5 | 0.5 | 0.5 | 3.0 | 0.5 | 0.5 |
| European sovereignty | 1.0 | 1.0 | 1.0 | 1.0 | 2.5 | 1.5 |
| Pricing transparency | 0.5 | 0.5 | 1.0 | 0.5 | 0.5 | 1.0 |
The judges and the criteria
The Compliance Officer · Runs the internal reporting office of a 600-employee company and answers for every missed statutory clock. Optimizes for case discipline: automated acknowledgment and feedback deadlines, role separation, documentation that survives a regulator. Rejects inbox-with-a-form products that make the deadlines her problem.
The Reporter's Advocate · Judges from the frightened side of the form. Optimizes for anonymity that survives contact, a two-way dialog without an account, languages the workforce actually speaks, and channels that work on a night-shift phone. Rejects login walls, app installs and anything that makes reporting feel like a deposition.
The SME Operator · Runs a 60-employee company that the law obligated, not convinced. Optimizes for compliance set up in an afternoon at a price the year-end review will not question, with the legal duties handled by the product. Rejects per-report fees, setup charges and anything that needs a compliance department to operate.
The Group Counsel · Rolls one system out to 25 subsidiaries in a dozen countries. Optimizes for per-entity channels with real access separation, per-country legal rule sets, external ombudsman roles and group reporting that respects entity boundaries. Rejects one-channel products multiplied by twenty-five contracts.
The Security Auditor · Pentests the anonymity promise for a living. Optimizes for evidenced security: current certificates with visible scope, published pentests, documented end-to-end encryption, metadata minimization, and hosting outside hostile jurisdictional reach. Rejects adjective security and "military-grade" anything.
The Skeptic · Assumes "audit-proof" and "100% anonymous" are marketing until the evidence says otherwise. Hunts certification claims without certificates, anonymity claims next to analytics scripts, per-report pricing traps and legal-update promises with no named lawyer. Exists to keep the rest of the bench honest.
Reporting channels & reporter experience · The intake side: how a reporter actually submits — web form, anonymous dialogue, phone or voice message, languages, accessibility — and whether anonymity survives first contact.
Case management & deadline discipline · The case worker's side: triage, the statutory deadlines (7-day acknowledgement, 3-month feedback), roles for case handlers, documentation of each case, and retention and deletion.
Legal compliance alignment · How specifically the product implements EU Directive 2019/1937 and its national transpositions (HinSchG et al.): which statutory duties it maps to features, which countries it names, and how it keeps up when the law changes.
Security & anonymity assurance · Whether the confidentiality promise is engineered and evidenced: encryption, IP and metadata handling, penetration tests, certifications of the vendor and its hosting.
Group & multi-entity capability · Whether one contract can serve a corporate group: separate channels per legal entity, central oversight, ombudsman access, white-labelling.
European sovereignty · Where reports about people actually live and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, phone or voice provider, translation, email), and the data processing agreement. In this category the data is by definition the most sensitive a company holds. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.
Pricing transparency · Whether an obligated company can compute the real invoice — per entity, per employee band, per year — from public pages alone: tier prices, billing period, employee bands, add-ons (phone intake, languages, entities) and setup fees.
Workflow Management rubric v2
| Criterion | The Process Owner v1.0 | The Integration Engineer v1.0 | The Operations Analyst v1.0 | The Head of IT v1.0 | The Data Protection Officer v1.0 | The Skeptic v1.0 |
|---|---|---|---|---|---|---|
| Process design, forms & approvals | 3.0 | 1.0 | 2.0 | 1.0 | 0.5 | 1.0 |
| Connectors, API & on-premise reach | 1.5 | 3.0 | 1.0 | 1.5 | 1.0 | 2.0 |
| Execution, error handling & monitoring | 1.5 | 2.5 | 3.0 | 1.5 | 1.0 | 2.0 |
| Governance, credentials & audit trail | 2.0 | 1.5 | 1.5 | 2.5 | 3.0 | 1.5 |
| Hosting options & portability | 1.0 | 2.0 | 1.0 | 3.0 | 2.0 | 2.5 |
| European sovereignty | 1.0 | 1.0 | 0.5 | 2.0 | 3.0 | 1.5 |
| Pricing transparency | 1.5 | 1.0 | 2.0 | 1.0 | 0.5 | 2.0 |
The judges and the criteria
The Process Owner · Runs purchase approvals and invoice release for a 400-person Mittelstand company. Wants approvers set by role rather than by name, a substitute when someone is on holiday, deadlines that escalate, and a process change that does not break the forty requests already in flight.
The Integration Engineer · Wires the ERP to the shop, the shop to DATEV and the CRM to everything else. Wants connectors documented by action rather than counted in logos, a generic HTTP step for the rest, an on-premise agent that reaches the SQL server without a hole in the firewall, and a failed run replayable from the step that failed.
The Operations Analyst · Is asked every Monday why invoices took eleven days. Wants a searchable execution history, cycle times per step, alerts that reach a channel rather than an unread mailbox, runtime and throughput limits published before the month-end run hits them — and to know what a loop over 5,000 rows costs in tasks.
The Head of IT · Answers for every automation a department builds without asking. Wants SSO, separate test and production, an inventory of workflows with their owners — and an exit: definitions exportable as BPMN or documented JSON, a self-hosted edition, and an engine licence that will still apply in five years.
The Data Protection Officer · Reads every workflow as a chain of transfers. Asks where the execution log keeps its copy of the payload and for how long, which subprocessors and AI model providers a step sends data to, whether payloads can be masked, and what the approval trail records about employees before the works council asks.
The Skeptic · Knows that "7,000 integrations" counts connectors nobody maintains, that "unlimited workflows" says nothing about the tasks each run consumes, and that "no-code" ends at the first API without a connector. Reads for what counts as a task, how long failed runs are kept, which model an "AI agent" step sends data to, and whether the workflows can leave the platform at all.
Process design, forms & approvals · Modelling the process people take part in: a visual designer or BPMN, forms, approval steps with roles and substitutes, deadlines and escalation, and versioning of a process that is already running — judged on whether a business owner can change a process without breaking the instances in flight.
Connectors, API & on-premise reach · Reaching the systems a European company actually runs: maintained connectors judged by name rather than count, a generic HTTP and webhook step, custom connectors, and a way to reach systems behind the firewall without opening it.
Execution, error handling & monitoring · What happens when a step fails at 3 a.m.: retries, error paths, alerting, an execution history someone can search, limits on runtime and throughput, and a status page that admits incidents.
Governance, credentials & audit trail · Keeping automation from becoming shadow IT: roles and permissions, SSO, where connection credentials are stored, separate environments with controlled publishing, an audit trail of changes and approvals, and what the execution log retains of the payload. An approval record is also a record of employees' behaviour (BetrVG § 87 (1) 6), so what the trail captures matters to a works council.
Hosting options & portability · Where the engine runs and whether the workflows can leave: cloud regions, self-hosted or on-premise editions, the licence of the engine, and export of workflow definitions in a format another tool or a later version can read.
European sovereignty · Who the contracting entity is, where workflows execute and where execution logs with their payload copies are stored, and who the subprocessors are — including the AI model providers behind any AI steps. Independently sourced by the sovereignty pipeline. A self-hosted edition counts only for the data that actually stays on the customer's servers.
Pricing transparency · Whether a buyer can compute the monthly cost of their own processes from public pages alone: what the billing unit is (task, operation, execution, run, user or flow) and what counts as one, the allowance per tier, overage prices, and the cost of premium connectors, self-hosting, environments and AI steps.
How lists are ordered
- Category pages are alphabetical by default. They are an index, not a ranking: no product is first because of its vendor or anything paid. You can choose to sort a category by panel rating or by sovereignty, or to filter it by provenance; that choice is yours and follows the rules on this page — products without a rating, or with sovereignty not fully proven, sort last.
- Search results are ordered by relevance to what you typed.
- Autosuggest puts name matches first: a product whose name is exactly what you typed, then names that start with it, then names that contain it, then other matches. Within each of those groups, the higher panel rating comes first.
- Comparisons are curated pairs, chosen by us, and a comparison refuses to render when the two were judged under unequal conditions — a different rubric or a different bench.
Published pages are re-checked. A page whose price evidence is older than 30 days is re-captured weekly; a page that cannot be refreshed stays up and shows the date its evidence was captured. A daily check applies the same freshness rules to every published product.
Conflicts of interest
whats-best.ai is operated by nelo digitalagentur GmbH & Co. KG. Companies connected to the operator develop software for data protection, whistleblowing, information security and property management, and those products are listed here like every other product in their category.
They get no special treatment, and we say so where it matters rather than only here: the same rubric, the same bench of judges, the same publish gate and the same evidence rules apply to them, nobody at those companies can see or influence the panel’s work before it is published, and no score, rank or placement is for sale. Their product pages, the four category pages concerned and every comparison one of them appears in carry this note.
The judges themselves are AI models. In AI Agents & Assistants, where the products are models and assistants of the same kind, the products of the company whose models power the panel are not listed, and that category page says so.
If you think one of those pages reads too kindly, report it like any other error — it is read against the same sources, by the same check, as a report about anyone else’s product.
What money can and cannot do
There is nothing to buy. No paid tier, no booking, no invoice: vendors cannot pay for a score, a rank, a placement or a listing, and nothing on this site is an advertisement. The order form and the paid options this page once described were removed rather than switched off.
What a vendor can do, free: claim the listing, correct any fact, publish a reply, add screenshots and evidence links, fill in what our checks left out, and ask once a month for their pages to be read again. Everything a vendor supplies is labelled vendor-supplied, rendered outside the panel’s text and structurally excluded from the scoring.
A re-reading is the only thing a vendor can set in motion, and it buys a reading, not an outcome: the panel scores what it finds, and the score can go down.
Corrections and suspensions
Anyone can report an error, without an account. Every element of a product page — a fact, a score, a criterion, a verdict, a sovereignty dimension, a vendor reply — carries a “Report an error” link. Say what is wrong and, if you can, what the right value is and where it is published.
A report changes nothing by itself. Filing one does not take anything off this site: the reported fact, score or passage stands as it is while the report is read. That is deliberate — a form anyone can fill in must not be a way to edit the site — and it is why there are no limits on how many reports a product or a sender may file.
A model reads it, and the reading is the decision. A model checks your report against the source we cited and, where you named one, against that page too. What it finds decides the report, by rules we publish rather than by anyone’s mood on the day:
- a source bears you out — the claim is replaced by what the source states, or removed where we have nothing to put in its place;
- nothing we can read settles it — a disputed fact still comes off the page, because a claim we can no longer confirm is not one we print;
- the source contradicts you — the page stays as it is;
- a report about a score, a criterion or a verdict is different: it moves the panel only when a source bears it out, because a disagreement about judgement is not an error of fact.
The decision is usually made within minutes and always within 5 business days. If you left an address you get it in writing, with the reasons, the fact that it was automated, and how to object. The operator can overrule any of it, and may suspend a reported element while a report is open; they are not asked to approve one.
What an accepted correction does. A wrong fact is replaced by a new one, cited to the source that supports it, and the product is re-queued for scoring. Where the report concerns an opinion — a score, a rationale, a verdict — we add a dated editorial note to the page and, where warranted, have the panel re-evaluate. Opinions are never edited by hand.
AI disclosure
Every score, rationale and verdict on this site is generated by AI models, and every fact is read from its source by AI models. The label appears on every page, at the top, as Art. 50 of the AI Act asks.
Humans do not write the verdicts, and no person approves a fact before it is shown: a fact appears only when it is proven as described above. The weekly sample is read by a third model rather than by a person. Since 20 September 2026 the same is true of the decisions around the edges — a correction, a notice of unlawful content, a vendor’s listing, claim or reply are all decided automatically, by models reading them against these published rules. Every such decision says so in writing and can be objected to, and the operator can overrule any of them.
Versions
Judges and rubric are versioned, and the versions in force are printed on every product page under “Method and versions”. A changed anchor is a new rubric version; scores from different versions are never compared.