GateCodeDesk Request a demo

Home / About the author

Jimenez Julien, the person who answers your setup email

Publisher of GateCodeDesk, founder of MLJ, SASU, and the one accountable for every gate code this platform writes to a keypad.

Why a storage product, and why this one

I did not grow up in storage. I came to it the way most software people come to a trade: by watching somebody do a job badly supported by their tools, and being unable to leave it alone. A friend of my family bought a 214 unit property outside a mid sized American town, the kind with a gravel apron, two metal buildings and a keypad that had outlived two owners. He had a spreadsheet with a tab for each building, a gate terminal running software from a decade ago, and a cell phone that rang at 9 pm because somebody could not get through the gate.

I spent a weekend at that property with a notebook. What struck me was not that the work was hard. It was that the same four digits had to be typed into three different places by a tired human being, and that a tenant who stopped paying kept the same access as a tenant who paid on the first. Everything in the operation depended on one person remembering to go into the gate software and change something. That is a fragile way to run a business that stores other people's belongings.

GateCodeDesk started as a very small tool for that one property: rent the unit online, write the code to the controller, hold the code when the account goes past due. It stayed small on purpose. The temptation with facility software is to add accounting, marketing, call center scripts and a dozen dashboards until an owner needs training to open the front screen. I would rather do the three loud things well and let your bookkeeper keep the software they already like.

What I have learned about this trade

Storage owners are not sentimental about software, and they should not be. They measure things: economic occupancy, delinquency buckets, days to fill, cost per lead, how many locks their manager cut last quarter. When I show a new screen, the first question is almost always some version of what does this save me on Saturday. That question improved this product more than any design review ever did.

I learned that the map is the emotional center of a facility. Owners do not think in database rows, they think in rows of doors, and a unit that shows the wrong color on the board is worse than no board at all. I learned that a code held on day eleven produces a phone call, while a certified letter on day forty five produces an empty unit and a bad debt. I learned that most independents do not want to sell the property to a national operator, they want to compete with one on Saturday night without hiring an overnight clerk.

I also learned where software should stop. Lien law belongs to your attorney and your state legislature. Cutting a lock, running an auction, deciding whether to give a good tenant one more week, those are your calls. GateCodeDesk records what happened and when, so your file is straight, and it stays out of the judgment.

Experience and expertise

I have built and shipped web products for more than a decade, first inside agencies and now under my own company, MLJ, SASU, registered in Paris. My work sits at the point where an operational habit meets a piece of software: intake forms, scheduling, access control, billing rhythms. Before GateCodeDesk I built booking and records tools for small operators in other trades, which taught me the discipline of writing software for a business with two employees rather than two hundred.

On the storage side, my expertise is specific and bounded. I know how keypad controllers from PTI, DoorKing, Sentinel Systems and Digitech accept and revoke codes, and what happens when the network at the gate drops for six hours. I know how a prorated first month interacts with a tenant protection plan and an autopay date. I know what a delinquency ladder looks like in states with a fourteen day notice rule and in states with a longer clock. I do not claim to know your market rate for a 10x20 better than you do.

How this product is built and maintained

Every feature in GateCodeDesk comes from a recorded conversation with an operating facility, and nothing ships without at least one owner running it on a live property for two weeks. Releases go out on Tuesday mornings, US time, with a plain language note about what changed and what to watch. If a change touches gate access or money, it ships behind a switch you control, and I call the sites that use it most before the switch flips.

Editorially, every number on this site comes from platform data or from a customer who agreed to be quoted by name. No stock testimonials, no invented averages, no rounding a 6 percent improvement up to 10. When a figure changes, the page changes. The testimonials on the home page are from real operators in Tennessee, Colorado and Pennsylvania, and each of them read their quote before it went up.

I am accountable for uptime, for the accuracy of the availability map, for the security of tenant records, and for answering support mail like a person rather than a ticket queue. When something breaks at 6 am on a Sunday, it is my phone that rings, which is a strong incentive to write careful code around the gate.

Published articles

Everything below appears in The Overlock, the GateCodeDesk magazine, and every piece was researched with operators running real properties before it was published.

Contact the author

Write to me at jimenezjulien42@gmail.com with the name of your facility, your unit count and the make of your keypad controller. If you are weighing GateCodeDesk against another platform, say so, and I will tell you plainly where the other one is stronger. If you want to see the software against your own unit list first, use the request form on the home page and we will load your list before we meet.

Jimenez Julien writes and maintains everything published on gatecodedesk.com. See the site map for the rest of the site, or read the legal notice for company details.