How I built an end-to-end rental agreement pipeline for a mobility rental business — eliminating wrong contracts, missed follow-ups, and the manual effort of keeping a solo operator's process from falling apart.
When I came in, the client was running a mobility rental business on his own. He was the operator, the follow-up person, the closer. Every order that came in meant he had to manually pull the right rental agreement, fill in the client's details, attach the right addendum depending on the item rented, and send it out himself.
It sounds manageable until it isn't. Wrong agreements were going out with some regularity — wrong client name, wrong rental item, wrong dates, wrong delivery location. Not because he was careless, but because he was doing too many things at once and the process had no guard rails.
"Beyond the wrong contracts, the follow-up problem was just as bad. Keeping track of who had signed, who hadn't responded, who was about to show up for a rental without a signed agreement — it was all manual. All in his head. All on him."
Clients were moving through the pipeline inconsistently. Some would get chased for a signature. Others would slip through. And when the rental date was close and the agreement still wasn't signed, there was no system telling anyone to act — just the hope that he'd remember to check.
He hired me specifically to fix this. And what he needed wasn't a patch. He needed the whole thing automated so that once an order came in, the process ran itself.
The build itself took about a week. But the real work happened in the two weeks after — going back and forth with the client on edge cases, preferences, and the small quirks that only surface once a system starts running against real orders. That back-and-forth is where the difference between a workflow that technically works and one that actually fits how someone operates gets sorted out.
The goal was simple in concept: every rental agreement touchpoint — sending it, following up, notifying the right person, confirming when it's signed — had to happen without him manually initiating anything. He places the order in GoHighLevel, and from that point forward, the system handles it.
The system is built across four distinct workflow stages, each one picking up where the last left off. Together they cover the full lifecycle of a rental agreement from the moment an order is placed to the moment it's confirmed signed.
Before this system, the rental agreement process was entirely manual — sending agreements, tracking who signed, following up, updating the pipeline, notifying the right person. All of it depended on the owner remembering to do each step and doing it correctly every time.
After the system went live, his involvement in that side of the process dropped to zero. Not reduced — eliminated. The agreements go out correctly every time. The follow-ups happen on their own schedule. When something needs his attention, he gets a notification. That's it. He doesn't chase signatures anymore. He receives confirmations.
| Before | After | |
|---|---|---|
| Contract selection | Owner manually picks the right agreement | System reads the item and sends automatically |
| Wrong contracts | Sent with some regularity | Zero after go-live |
| Follow-up timing | Whenever the owner remembered | 12 business hours, automatic, business days only |
| Internal alerts | None — owner had to track it himself | Proximity-aware alerts to assigned user |
| Signing confirmation | Manual check of pipeline status | Auto SMS, email, CRM note, pipeline update |
| Owner involvement | Every step | Receives notifications only |
There's something particular about building a system for someone who is running a whole business by themselves. Every hour you give back to them isn't just saved time — it's breathing room. It's the difference between a founder who's constantly reacting and one who actually has space to think.
When the rental agreement pipeline was fully operational, he stopped being the person who chased signatures. The system did that. He stopped being the one who had to remember to move a contact from one stage to the next. The workflow did that too. By the time he heard from the process again, it was to confirm something was done — not to ask him to do it.
That shift — from doing to receiving — is what the system was built for.