Customers
Customers
There is no logo wall here yet. Instead: who Rydya is built for, what a rollout involves, and how to price the case with your own numbers.
- Hospital operations
- Executive and finance
- Biomedical engineering
What is Rydya built for?
Definition
The Rydya customer
Rydya is built for organisations that own medical equipment and are accountable for keeping it working and provable: hospital groups, diagnostic and imaging centres, laboratory networks, dialysis chains, specialist clinics, biomedical maintenance companies, equipment vendors and leasing businesses, and NGO or donor-funded facilities.
They share three recurring questions: what do we own, is it working, and what is it costing us. If you can answer those today, you probably do not need this.
Each segment has its own page, which names its load-bearing problem.
Why there is no case study here yet
Because we have no customers to write one about.
Publishing one needs a customer who has run Rydya long enough for the numbers to be theirs, permission to name them, and figures they would defend at their own board. That bar takes a year.
If your evaluation requires reference customers, Rydya does not meet that bar today.
How a rollout runs
Import, label, configure, hand technicians the mobile surface, then widen. Weeks, not quarters.
- 1
Import the register you have, imperfections included
An afternoon, not a data-cleansing project, which is how this work usually stalls. The register becomes accurate through use.
- 2
Put codes on the equipment where failure hurts
Only the devices where an unreported fault is expensive or unsafe. Every scan afterwards confirms the register.
- 3
Configure your rules
Intervals, procedures, limits, approval thresholds. This step takes real thought: it states policies often never written down. We supply none of these values.
- 4
Give technicians the mobile surface in the same week
The technician at a real device is your best data source; their scans make the register true.
- 5
Let the first month correct the plan
It will find devices nobody knew about and locations that were fiction. That is the system working; warn your sponsor.
- 6
Widen on readiness rather than on schedule
The second site is much faster: the configuration is mostly reusable and your people know what good looks like.
How to build an ROI case
From your downtime, your rates and your estate. We supply no numbers.
Establish what an hour of unavailability is worth for the devices where failure costs something, then measure for a quarter how many such hours you have. That figure is your ceiling. The saving is never the whole of it: preventive work, faster reporting and better parts availability each remove some losses, and the platform makes each measurable.
The second case is often larger: the cost of not being able to answer. The pre-inspection fortnight, the lost renegotiation and the replacement decided on a hunch belong in the case even without a number.
What a case study will contain
The framework we will hold ourselves to, published in advance.
A named organisation, with permission
Not "a leading hospital group in the region". Anonymity does the work the evidence should be doing.
The starting position, honestly described
Including how bad the register was on day one, or the study describes a competent organisation rather than a product.
Figures from their system, not our model
Measured downtime hours against their own configured rates, over a period long enough to mean something.
What did not work
Every real implementation has a part that went badly; its absence is visible to anyone who has run a project.
The counterfactual, acknowledged
Improvement that would have happened anyway, because somebody was finally paying attention, is not attributable to us.
What to ask us instead of references
Ask us to break the safety gate in a live demo, what a device with no data shows in a compliance report, where the downtime clock starts and whether it runs while a part is on order, and what we have not built. The buyer's guide lists these in full, including the four we currently lose on.
Who should not buy this yet
Organisations that need certifications, enterprise single sign-on, committed data residency, or reference customers. None of the four is close.
If your procurement requires SOC 2 or ISO 27001, we hold neither and have not been penetration tested. If your identity team requires SAML, it is not built. If your risk assessment requires committed data residency, the hosting region is an open decision. If your process requires reference customers, this page is the answer.
Test them in week one, not month four. What remains is a product whose architecture is decided, whose safety gates do not bend, and whose gaps are published.
Questions
Who is using Rydya today?
Nobody we can point you at. If your evaluation requires reference customers, Rydya does not meet that bar today, and we would rather say so than imply a roster.
Why are there no case studies or customer logos?
Because we do not yet have a customer who has run Rydya long enough for the numbers to be theirs, permission to name them, and figures they would defend at their own board.
What return on investment should we expect?
We will not give a number; any figure we supplied would describe a hospital we have never seen. Build it from your inputs: the worth of an hour of unavailability on the devices that matter, times the hours you lose in a quarter.
How long does a rollout take?
Weeks rather than quarters: import the register, label the equipment where failure hurts, configure your rules, and give technicians the mobile surface the same week. Cleaning the data first is how it takes a year.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us