About
Asset management software, built for how self-storage runs.
Every month, someone in your office opens a property management report, retypes its numbers into a spreadsheet, formats a workbook, writes an email to an owner, and starts again at the next store. The numbers are right. The process is the problem.
LumaIQ closes that month once, then spends the same numbers on the decisions that follow: what to budget, which units to raise, which store needs a visit, and what the owner should hear.
I was an area manager in self-storage, closing that month store by store. LumaIQ is the tool I wanted then.
How it is built
Six rules the product is held to.
Each one closed off a shortcut that would have made the product worse. All six are checkable in the product itself.
No scraping.
Competitor rates are typed or pasted by a manager who visited the page themselves, and each survey records which. There is no fetcher, no per-site extractor, no browser extension, and nothing that goes and collects a rate on a schedule.
Square feet is the headline.
Occupancy is reported on square feet everywhere it is surfaced: the owner workbook, the owner email, the home page, and the default goal. Unit and economic occupancy stay visible as supporting detail.
A saved scenario reproduces exactly.
The pro forma model is pure. Scenarios persist the baseline and the assumptions, never the projection, and a version marker guards the contract if the math changes.
A number with no destination is a dead end.
Every count on the home page and the field roster is a route to the screen that resolves it. When nothing is outstanding, the tile says so.
One isolated workspace per operator.
Access level decides the actions and property scope decides the stores. Both are enforced in Postgres rather than in the interface, so a screen that should not load does not load, whatever the URL says.
A recommendation must survive being questioned.
Anything the product suggests, whether a rate increase, a ranking, or a budget, has to be defensible to the person whose store it is. If the inputs cannot support the claim, the product says so instead of guessing.
Leadership
Caleb Pham
Founder
I was an area manager in self-storage before I wrote a line of this, and I am back in school in finance and computer science to formalize what I had been building on the side. The questions came from the job. The software came from needing answers to them, for owners, for operators, and for the people on the floor.
Spreadsheets stop scaling long before anyone admits it, and the tool that would fix it does not exist. So I started building it, one line at a time. What interests me is where operations meets software: how the messy reality of running a business becomes a system that actually reflects it.
I am always glad to hear from operators who build, software people curious about overlooked industries, and anyone working in real estate technology or applied AI.
We are hiring.
Open roles across engineering, product, and customer success.