Oxaron
A product I am building myself, live at oxaron.com and in active development ahead of general availability. Most organisations cannot answer a simple question about their own software: what are we actually paying for, who is actually using it, and what would one more tool really cost us? Oxaron connects read-only to the identity system staff already sign in with, Microsoft 365 or Google Workspace, and turns that into one view of the whole estate, priced.
What it does: an audit that puts a figure on unused accounts, wasted licences, and overlapping tools; a stack map that shows every tool grouped by the job it does, sized by how many people it covers and shaded by what it costs a year; and a simulation that tests a tool you are considering against everything you already run, before anyone signs for it.
Concepts explored: read-only integration with enterprise identity providers, multi-tenant isolation enforced at the database level and covered by tests, deriving cost signals from directory and usage metadata rather than from content, and treating every figure as something the customer must be able to check, with the rule and the arithmetic shown alongside it.
Why these decisions: the product asks a finance or IT lead to act on a number, which means the number has to survive being questioned. Read-only access with a names-and-numbers scope, never files or messages, keeps the blast radius small and the security review short. Showing the working behind each euro turns a disputed figure into something that can be checked rather than argued about. EU hosting is a procurement requirement in the market it serves, not a detail to retrofit later. And deciding where intelligence genuinely improves a decision, rather than where it would simply be expected, is part of the engineering.