xOpsentia

I'm currently building an early-stage SaaS product focused on helping MRO and maintenance teams identify parts, diagnose problems, and resolve equipment issues faster--especially in environments where downtime, part ambiguity, and tribal knowledge create daily friction. Before building anything at scale, I'm intentionally spending time learning directly from MRO leaders, maintenance managers, reliability engineers, and technicians who work on the ground every day. My goal is not to pitch--but to understand: * Where part identification breaks down today (especially for legacy equipment) * How technicians currently diagnose issues and decide on corrective actions * What tools, manuals, systems, or workarounds are actually used vs officially adopted * Where knowledge lives (people, PDFs, OEM docs, ERP, CMMS) and where it gets lost * What truly causes downtime delays--parts, data, access, approvals, or context The product I'm exploring aims to support technicians and MRO teams by: * Helping identify parts more accurately * Providing relevant specifications and context * Assisting with troubleshooting and potential resolution paths * Reducing dependency on tribal knowledge and manual searches This is a learning-led, practitioner-driven effort. Every conversation directly shapes what gets built--and what doesn't. If you work in maintenance, reliability, asset management, operations, or MRO, I'd genuinely value: * Your perspective * Your lived challenges * Your advice on what would actually help (and what wouldn't) Even a short conversation or a few pointers over chat would be incredibly helpful. Happy to share back insights I'm gathering across the industry as well.