About Mulemark

Built around the moment
someone needs an answer.

The machine is right there. The instructions, support contact or condition photo should not be somewhere else.

The problem behind the product

A great explanation only helps if it is still there when you need it.

A walkthrough happens once. A rental can last for days or weeks. The operator may change, the details may be forgotten, and the question may not arise until the equipment reaches the jobsite.

Mulemark is built around a simple idea: keep the useful guidance, support path and reporting tools with the equipment. Give the renter a clear way forward, and give the rental company a more useful record of what happens.

The QR code is the access point. The value is what the person can do after the scan.

Why fairness matters

Neither side should have to rely on memory.

During an RV rental, Josh saw the owner help push a binding slide outward during the initial walkthrough. When the RV came back, the fault was attributed to the renters. There was no clear, shared record of the condition at handoff.

That experience illustrates why a simple way to document a concern matters to both parties. A record should help establish the facts, whether those facts support the rental company or the customer.

Mulemark gives renters a way to report what they notice and helps staff connect those reports with the equipment and rental session. It supports a fair review; it does not automatically determine responsibility.

An operations perspective

Useful to the renter.
Workable for the yard.

Josh's background is in industrial operations, manufacturing leadership, process improvement and quality systems. That perspective shapes Mulemark: the front-line workflow has to be practical, and the record has to be useful when someone needs to act on it.

Mulemark is being developed as a focused addition to the rental business, not a replacement for reservations, contracts or billing. Early deployments are founder-led, with a defined asset group and a clear implementation scope.

Make the first scan useful.

Start with guidance people can understand. Keep help and reporting easy to find.

Preserve the context.

Connect observations to the asset and rental, rather than creating another pile of disconnected information.

Earn the next rollout.

Use real deployments to learn what customers use, what creates work and what they value enough to keep.

Talk to the person building it.

Bring a real handoff, support or return problem from your operation.

Talk about your fleet

Tag placement

Proposed tag placement on a real photograph. The larger tag detail is provided separately for scanning.