Editorial Policy
How we research, write and check this blog
This page explains how the articles on retorio.com are produced, who stands behind them, where the numbers come from, and what we do when we get something wrong. It is written for the people who read us most: sales enablement leads, commercial excellence teams, service owners and the managers who have to defend a decision internally.
The short version
We use AI to help draft and translate articles. A person decides what gets written and what ships. Every figure we publish about our own results traces back to a maintained internal record. Every claim we make about another vendor comes from that vendor's own public pages, and where their pages do not answer a question we say so rather than guessing.
Who stands behind the articles
Two people run the blog day to day, and each subject area has a named owner who reviews what we publish in it. These are Retorio employees, not pen names.
Editorial direction and final check
Oender MutluerWebsite Manager and Marketing StrategistSets the content strategy for retorio.com, decides what gets written and edits every article before it ships. Digital marketing and SEO expert, working daily with the search, analytics and CRM data that decides what we publish and how we measure it.
Dr. Patrick OehlerCo-founder and Co-CEOBehavioral scientist by training, with a TUM doctorate in behavioral research that laid the scientific foundation for the platform. Brings that science, and what he hears in enterprise client conversations across insurance, pharma and automotive, into what we publish. Signs off on what we claim about the product and our results.
Who reviews which topic
Elena ZieglerCustomer SuccessCustomer service and support coaching, day-to-day practice in live accounts.
Dr. Florian AbichtChief AI OfficerAnything we write about how the AI works, what it measures and what it cannot do.
Jan BeuthHead of Customer SuccessCustomer service and support coaching, rollout and adoption.
Jan-Henrik SchwarzEnterprise Account ExecutiveInsurance: agent and broker coaching, regulated selling.
Martin WeberGlobal Pharma ExpertPharma and healthcare: field force, HCP engagement, compliance-bound conversations.
Peter HoldenriedHead of SalesSales methodology, pipeline and enablement articles.
How a post is produced
1. We decide whether the post should exist. Before anything is written we define who the reader is, what they are trying to do, and what this page gives them that they cannot get from the pages already ranking. If we cannot answer that, the post is not written. Rewriting what is already published elsewhere does not pass this step.
2. We research. What people are actually searching for and reading comes from Google Analytics and Google Search Console. How those readers behave once they talk to us comes from our own HubSpot CRM analytics. On top of that sit two sources no tool provides: sector insight into how selling and service actually work in insurance, pharma, automotive and telecommunications, and the direct experience of our clients and our own sales, customer success and AI teams. Product facts come from our own documentation. Customer outcomes come from our own deployments, named where the customer has approved it. Third-party claims come from the original source, not from a summary of it.
3. We draft with AI assistance. Drafting and German translation are AI-assisted. This is a tool, in the same way a spellchecker or an analytics dashboard is a tool. It does not decide what we publish, what we claim, or which numbers we use.
4. We run checks before publishing. Automated checks look for unsourced figures, banned or misleading phrasing, broken and redirected links, missing alt text, schema errors and structural defects. A post that fails them does not ship until it is fixed.
5. Subject review. Articles that fall into one of the areas above are read before publication by the person who owns that area, and that person is named at the foot of the article with their role. Where no reviewer is named, no subject review took place, and you should read the article as the work of our editorial team rather than as an expert opinion.
Where our numbers come from
Figures about Retorio's own results, such as ramp-time reduction or quota attainment, come from measured enterprise deployments and are held in one internal record that has a named owner and a refresh date. A number that has no record does not get published, and when we cannot substantiate a figure we remove it rather than soften it.
Where a figure belongs to a specific customer, we name that customer only with their approval, and we link to the case study that carries the number so you can check it. Charts that illustrate a shape rather than report a measurement are labelled as illustrative in their own caption.
How we write about other vendors
We publish comparisons that name competitors, and we are one of the vendors in them. Three rules keep those pages usable:
We only state what the vendor publishes. Every competitor claim comes from that vendor's own public website. We do not cite a competitor's internal data or their own case studies as evidence.
We do not infer absence. If a vendor's public pages do not state a capability, we write that it is not stated publicly and suggest you ask them. We do not write that they lack it.
We say which entries are ours. The Retorio entries in a comparison come from our own documentation and pricing page, and we label them that way on the page.
Updates and corrections
Articles carry the date they were last updated. We revisit posts when the underlying facts change, when a linked source moves or disappears, or when a reader tells us something is wrong. A correction that changes the substance of a claim is made in the text itself rather than quietly removed.
If you find an error, a stale figure, or a statement about your own product that you believe is inaccurate, write to contact@retorio.com and we will check it against the source and correct the page if you are right.
What we do not do
We do not publish pages whose purpose is to rank rather than to answer. We do not generate large volumes of near-identical pages. We do not present a vendor comparison as neutral when we are in it. And we do not put a name on a review that did not happen.