What it is
A rental goes out. Weeks later it comes back damaged, or it does not come back at all. The details often end up scattered across email, paper notes, and individual memory. When that renter calls again, the next person at the counter needs the history in seconds.
VeriGuard Pro brings phone-based identity checks, background reports, and renter incident history into one shared operational record. Teams can document an issue once, retrieve it across shifts, and optionally share relevant incident information with other verified rental businesses.
The product is aimed at independent yards and growing multi-location operations. Its workflows, pricing, and permissions are designed around real counter decisions rather than the assumptions of a large enterprise fleet system.
How the partnership worked
VeriGuard Pro began with an insurance agent who knew the equipment-rental market and the people in it. They brought the problem, the distribution channel, and the relationships. I brought the product workflow, the application and data architecture, the external verification services, subscriptions, and production operation.
When that partner had to step away, I took responsibility for product development and carried the work forward with a group of co-founders. The software kept running through the change because it was built to run without any one person at the counter.
What had to be right
This is trust software used while a customer is waiting at the counter. The system has to return useful information quickly, but the information it handles is sensitive, arrives from more than one source, and may be incomplete. Identity checks, background reports, internal incident records, and shared reports each have different meanings. The interface has to preserve those distinctions instead of flattening them into a single risk score.
Organization boundaries make that problem more demanding. A yard needs one durable record across shifts and locations, while each employee should see only what their role permits. Cross-yard reporting creates a second boundary: an incident can help another verified business avoid a repeat loss, but sharing must be deliberate, attributable, and revocable.
Decisions that shaped the product
A background check scoped to the decision. A report needs enough information to support a responsible review, but including every available data point raises the price without improving the rental decision. VeriGuard Pro uses a deliberately scoped check that balances useful information with a very low per-check cost, which is what makes it practical for routine use at an independent yard.
AI that advises and never decides. VeriGuard Pro uses AI to turn dense background reports into practical guidance: it highlights relevant patterns, explains why a detail may matter, and suggests questions worth asking. It does not approve or deny a rental. The underlying report remains the source, yard policy remains the standard, and the user remains responsible for the decision. AI output is always presented as analysis, never as fact or authority.
Honest about uncertainty. External verification services fail differently from ordinary application requests. A check may be pending, partially complete, unavailable, or superseded by a newer result. The application represents those states as they are and gives counter staff enough context to decide what to do next. When software informs a consequential decision, simplicity cannot come from hiding uncertainty.
Sharing that is opt-in and reversible. Cross-yard reporting is a choice a yard makes, incident by incident, and can withdraw. Useful collaboration never comes at the cost of indiscriminate access.
What shipped
- Phone-based identity verification and background-report workflows
- AI-assisted analysis that advises without making the rental decision
- Shared renter and incident history across a yard’s team
- Role-aware organization access
- Optional, revocable cross-yard reporting
- Subscription plans for independent and multi-location operations
What this taught the studio
The partner model works on the software side: someone who knew the market shaped a product no developer would have designed alone. Life also happens, and when it did, the product kept running because the engineering was built for continuity. Now the agreements are too. Every partnership plans, from the start and in both directions, for what happens if either side has to step away, so that nobody’s circumstances put the product at risk.