Lentra vs. building it yourself
Buy the lockers, stock them, run it in-house. Entirely possible, occasionally the right call, and almost always underestimated in the second year.
The case for building it yourself
You keep all the revenue, you own the hardware, you choose every item, and you are not paying anyone's margin. For an operator with a large portfolio, existing service infrastructure and the appetite to run a small retail and rental operation, this can be the better economics. Some do it well.
Where they actually differ
| Lentra | The alternative | |
|---|---|---|
| Capital | None under Fixed Rent; one-time under Self-Owned | All of it, up front |
| Software | Access, payments, inventory, app, reporting included | Build, buy or do without |
| Restocking | Contracted, driven by actual consumption | Somebody on your team, weekly, forever |
| Item selection | Reviewed against real usage | Whoever has time to think about it |
| When it breaks | Monitored and dispatched | Your maintenance queue |
| Resident support | 24/7 routing | Your on-site team, in person |
We wrote this table, so read it accordingly. Nothing in it is ranked: the right answer depends entirely on which job your building needs doing.
Choose building it yourself
A large portfolio, an existing service operation that can absorb restocking routes, and someone internally who owns it as a real job rather than an addition to one. The economics genuinely improve at scale.
Choose a convenience hub
One building or a few, no appetite to run a retail operation, and no wish to discover in month eight that restocking has quietly become a two-hour weekly job for your building manager. Also when the software is the part you do not want to build.
The money, honestly
In-house looks cheaper because the visible line is hardware. The line that surprises operators in year two is labour: restocking, chasing damaged items, reconciling payments, answering residents at hours nobody is rostered for. None of that appears in a capital comparison and all of it recurs. If your team already drives between buildings every week, that labour may genuinely be close to free, and the arithmetic changes in your favour.
How each one goes wrong
Every option on this page fails in a particular way. Knowing which failure you are signing up for is more useful than a list of benefits.
The software is the part that does not get built
Access control, payments, inventory, a resident app and reporting are each individually simple and collectively a product. Most in-house builds arrive at a keypad and a spreadsheet, which holds up until the first dispute about who had the item last.
Ownership drifts
It is somebody's project until they leave. The failure is rarely dramatic: restocking slips from weekly to fortnightly, then to whenever somebody complains, and the thing is half empty by month nine.
A provider fails differently
We fail by being slow to site, by getting the selection wrong, or by pricing a small building badly. Those are contractual failures with a named counterparty, which is most of the reason to buy rather than build.
Questions worth asking before you decide
Ask these of us and of anyone else in the running. The answers separate the options faster than a feature table does.
- Who owns this in month eighteen, by name and in a job description rather than as a favour?
- What happens to a compartment that jams at eleven on a Sunday night?
- How will residents pay, and who handles the chargeback when one is disputed?
- What will you do with the usage data, and who is going to read it?
Asked about this comparison
Does Lentra sell the hardware outright?
What is the real weekly time commitment if we run it ourselves?
Can we start with a provider and bring it in-house later?
Still weighing it up for your building
Tell us the property. If something else suits it better, that is what the proposal will say.