Corporate Real Estate Portfolio Software: Why the Option Date Passes While Everyone Is Busy

Why occupiers break the tools sold to them

A regional director calls in March to say the lease on store 4127 expires in October and asks what the plan is. The head of corporate real estate pulls the abstract. It shows one five year option remaining at market rent with notice due nine months prior, which was June of last year. Nobody served it. The store trades well, the landlord knows it trades well, and the negotiation that follows starts from a position the company gave away for free by being busy.

The tools are Tango, Accruent Lucernex, CoStar Real Estate Manager or IBM TRIRIGA, usually one of them, plus a finance system that owns the payments, plus store operations reporting that owns the sales, plus a construction tracker in Excel. Each of these products is capable. CoStar Real Estate Manager and Lucernex handle abstraction and accounting well. Tango is built for retail occupiers and understands site decisions better than most. TRIRIGA is a genuine integrated workplace management system for large owner-occupiers with facilities complexity.

The structural problem is the same across all of them. They model the lease as the primary object. An occupier does not make lease decisions, it makes location decisions, and a location decision needs the lease, the trading performance, the capital already sunk, the remaining useful life of the fit-out, the market alternatives, the restoration obligation, and the cost of being wrong. The lease is one input among six. When the primary object is wrong, every report is subtly answering a question nobody asked.

Problem 1: critical dates fail for a management reason, not a data reason

Three specific mechanics cause the misses. First, the alert fires on the date rather than on the point at which the decision process must start, which for a site needing a market test and an internal approval is often twelve to eighteen months earlier. Second, the alert goes to a mailbox rather than to an accountable person with an escalation path. Third, and most damaging, the alert arrives without the information needed to decide, so it becomes a task to gather information rather than a decision, and it moves to next week.

What a custom build does: work backwards from the notice deadline through the actual decision process. If a renewal decision needs site performance analysis, a market rent opinion, a capital assessment and committee approval, the system knows those durations from your own history and opens the case at the right time. The case arrives populated: trailing twelve month sales, four-wall contribution, occupancy cost ratio against your portfolio benchmark, remaining fit-out life, capital spent in the last five years, comparable market rents, and the restoration liability if you exit. The named owner has a decision in front of them, not a research task. Escalation runs to their manager on a schedule and to the head of real estate if nothing happens. Sites where no decision is recorded at the point of no return should be a board-visible number.

Problem 2: a location decision needs the P&L, and the P&L lives somewhere else

Renew or exit is an economics question. What does this site contribute, what does it cost fully loaded, what happens to those sales if we close, what does relocation cost including capital and lost trade, and how does the answer change under the rent the landlord is asking?

What a custom build does: make the location the primary object and hang everything from it, including the lease. Sales feed in from your point of sale (POS) or branch reporting weekly. Occupancy cost as a share of sales gets computed for every site continuously, which by itself surfaces the outliers nobody had time to find. The renewal case then models scenarios: renew at the asking rent, renew at target, relocate within the trade area with capital and transfer assumptions, or close with restoration and transfer of sales to nearby sites. For retail and branch networks the transfer assumption is the crux, since closing a site does not lose all its revenue, and a portfolio tool that ignores transfer will systematically recommend keeping sites it should exit.

Problem 3: you are almost certainly overpaying landlord charges

Occupiers receive operating expense reconciliations, tax recoveries, insurance charges and percentage rent calculations from hundreds of landlords, each computed by the landlord under clauses the landlord drafted. Most are paid on receipt because checking one takes a half day and the property team does not have four hundred half days.

The recurring findings in this work are consistent: charges that exceed a negotiated cap, capital items pushed into an operating pool, a pro rata share computed on the wrong denominator, a management fee above the permitted percentage, and charges for a period before the lease commenced. None of these require litigation. Most require a letter citing the clause.

What a custom build does: encode each lease's recovery limits, exclusions and cap structure once at abstraction, then validate every incoming landlord statement against them automatically. The output is a review queue ranked by exposure rather than by arrival date, so the team spends its limited hours on the twelve statements worth challenging. Track the audit right window per lease, because the right to audit expires and expired rights are worth nothing. This feature usually pays for a meaningful part of the build within two reconciliation cycles, and it is the one an occupier's finance director understands immediately.

Problem 4: the transaction pipeline and the approval trail are fragmented

Between deciding to renew and signing sit a broker, a negotiation, a letter of intent, legal review, an internal approval that may require capital committee sign-off, and execution. Between deciding to open sit site search, committee approval, lease negotiation, design, permitting, construction and opening. Both are multi-month processes with dependencies and both are usually run in a spreadsheet plus email.

What a custom build does: run transactions as cases against the location with stages, owners, dates and documents, and make the approval an artefact with a locked version showing what the approver saw. When the negotiated outcome differs from the approved parameters, that difference is visible rather than buried in an email thread. Delegated authority rules mean a renewal within approved parameters can proceed without a committee, which is where the speed comes from. For openings, the construction and permitting path shares the same case so the opening date has one owner and one source.

Problem 5: the obligations you forget until they cost money

Restoration and make-good clauses require the tenant to return the premises to a defined condition, and the liability is frequently discovered at exit rather than accrued during occupancy. Co-tenancy clauses give rights when an anchor leaves, and those rights expire if not exercised. Percentage rent obligations require sales reporting to landlords on schedules that vary. Assignment and sublease rights carry consent processes with response deadlines. Continuous operation clauses can be breached by a temporary closure. Insurance certificates must be delivered annually to hundreds of landlords.

What a custom build does: model obligations as recurring or triggered items with owners and evidence, not as notes in an abstract. Restoration liability gets estimated per site and carried forward so exit decisions include it rather than discovering it. Co-tenancy triggers get monitored against actual centre occupancy where you can obtain it. Certificate delivery gets automated because it is pure administration and should never consume a person.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this is the honest shape. A first release covering the location-centric data model, lease abstraction structures, the critical date engine with decision-ready cases and escalation, landlord charge validation, and a site decision pack joining lease economics to trading performance runs $100,000 to $220,000 and ships in 14 to 20 weeks. A full platform adding transaction and approval workflow with delegated authority, capital project tracking, sublease and disposal, obligation management, portfolio analytics and lease accounting output runs $250,000 to $650,000 phased over 8 to 14 months.

What drives price up in this category: the number of countries, since lease structures, indexation, tax treatment and statutory renewal rights differ enough that each region is real scope. Whether lease accounting under the current standards is in scope, which brings remeasurement on modification, discount rate policy and auditor evidence with it, and is a genuine work package rather than a report. Integration count, because this system is only as good as its feeds from finance, point of sale or branch reporting, and construction. Property type mix, since offices bring space and occupancy planning and stores bring trading analysis and they share almost no logic. And your abstraction backlog, which for portfolios above a thousand leases is usually the pacing item.

Build versus buy, and when buying is right

Buy if you occupy fewer than about 150 locations, or if your driving requirement is accounting compliance rather than portfolio decisions. CoStar Real Estate Manager and Lucernex do lease accounting properly, come with auditor familiarity, and cost far less than building that capability. Buy if you are a large owner-occupier whose real problem is facilities, space planning and work orders across corporate buildings, because that is what TRIRIGA exists for and rebuilding an integrated workplace management system is a poor use of capital. And look hard at Tango before building if you are a retailer, since it was designed around exactly the site decision workflow described here.

Build when several of these are true. You have missed option or kick-out windows and the cost was material. Your site decisions require a week of analyst work each, so most of them do not get made properly. Your landlord charges are paid without validation and you have never audited a reconciliation. Your portfolio decisions depend on transfer between locations, which no packaged occupier tool models with your data. You operate across property types or countries in ways that force the packaged product into a shape it resists. Or the real estate system needs to be the operational spine linking finance, operations and construction, and no vendor will integrate on your terms.

Our position: build when the constraint is decision throughput rather than record keeping. Packaged systems are good at holding a lease and producing an accounting entry. They are not built to hand an accountable manager a decision that is ready to make, and that gap is where occupiers lose the most money, quietly, every year.

How to choose a developer for corporate real estate software

Ask them what the primary object is. If they say lease, they will build another lease register. The answer you want is location, with leases, trading performance, capital, obligations and transactions attached to it, because that is the shape of every decision your team makes.

Ask how a critical date becomes a decision. You want backward scheduling from the notice deadline through your real decision process, a populated case, a named owner and an escalation path. A report of upcoming dates is what you already have and it is what failed.

Ask how they would validate a landlord's operating expense statement against the lease. If they cannot describe encoding caps, exclusions and share definitions once and testing every statement against them, they have not worked on the occupier side of this problem.

Ask who owns the code and get it in writing before kickoff. You should own the repository, the infrastructure accounts and the right to hire anyone else to continue. At Digital Heroes that is the default from the first commit. A portfolio system holds commitments that run for decades, and it should never depend on a vendor relationship that will not.