One asset class. One site. One month. A working certified-equipment register at the end of it.

The problem

Most equipment registers are a spreadsheet, a certificate tab, and a shared drive of scanned PDFs that one person understands.

It works until a client’s auditor finds an expired certificate on live equipment. Or a package is turned away at the gate. Or that person goes on leave.

What we need from you

1. Your equipment register for one asset class, in Excel, in whatever state it is in. We are not asking for a clean one. A messy register is a better input than a tidy one.
2. The certificates for those items. A folder, a zip, or a shared-drive link. Scans are fine.
3. One named pilot owner with authority over the register. Usually the QHSE, integrity or compliance manager.
4. Up to ten named people for seats, with email addresses.
5. A 90-minute kickoff, then about two hours a week of the pilot owner’s time.

That is the whole ask. If you cannot send the first item, we are not the right conversation yet, and we would rather say so now.

The success measure

One measure. Yours. Pass or fail.

At the end of week four, every item in the scoped asset class has a known, current certificate status in RelyentX, and your pilot owner produces the 90-day expiry list from the system in under two minutes, without us in the room.

Agreed in writing in week one. Assessed at week four. Measured by you, not by us.

We are not going to promise you a downtime reduction, a cost saving or a payback period. A month is too short to attribute any of them and we have no customer data to base a figure on. This pilot measures whether your register is complete and answerable. Nothing beyond that.

At the end of the month, three doors, and you pick in that meeting

• Continue.

  It becomes a subscription: the modules you turn on and the named people who sign in. No per-site charge, no per-asset charge. The term and how seats and modules adjust are in the quote, which you will have had since week three.

• Stop.

  You owe nothing. No auto-renewal, no notice period, no termination fee. Your data exports to Excel (equipment, certificates, maintenance history, mobilisation) and your workspace is suspended, and can be reactivated later without starting over.

• Keep going.

  If the measure was not met in week four, the pilot does not close there. See the guarantee below.

What we do not guarantee

We would rather you read this now than find it in week three.

• It needs a connection. There is no offline mode that caches records on the device or queues job closures for later upload. If your crews record where there is no coverage, factor that in.
• No predictive maintenance. No failure prediction, no condition monitoring, no sensor, SCADA or IoT integration. If that is what you need, we are not it.
• No ERP integration today. No SAP, no Epicor, no Maximo.
• Where your data is hosted: In a hosting location the infrastructure code restricts: it accepts only an approved set of locations and refuses any other value. We name the location, and every third party that processes your data, in writing before a pilot.
• Three AI features run at third-party providers, and each receives your data. To make records searchable, the text of every record and document is sent as it is written. To read documents, the page images and extracted text of a certificate imported from a chat, and the page images of a chat file our own text extraction could not read, are sent, up to a daily limit per workspace. The page images and extracted text of other scans our own extraction is not confident about, such as a file saved to a record, are sent only in a workspace where reading has been switched on, and it is off by default. To answer a question to Root, the question, the records retrieved for it and the text of any file attached to the chat are sent. Root answers and document reading are routed only to providers whose published policy is not to train on the request; the search-indexing provider states it never trains on API data. How long each provider keeps a request follows its own terms. This processing is not limited to where the platform is hosted. We name each provider in writing in the security review.
• We hold no ISO 27001 certification and no SOC 2 report.
• We do not do rental billing. The system records the time equipment was in use. It does not invoice it.
• We will not clean your register. We load what you have and tell you where it disagrees with itself.
• No claim about your downtime, your costs or your savings. We have no customer baseline and we will not construct one.

References

We have no customer we can name yet, so you would be early, and the terms reflect that.

What we can put in front of you instead of a logo is the product against your own data, a security page that says plainly what is and is not covered, and a fixed-scope pilot with a success measure you define and no fee attached.