Corporate Real Estate Portfolio Software: Configure CoStar and Tango, or Build the Decision Layer?
Location count and what is actually constraining you decide this. Under roughly 150 leased locations, or where your driving requirement is lease accounting compliance, buy: CoStar Real Estate Manager, Lucernex, Tango or IBM TRIRIGA will beat a build comfortably and the arithmetic is not close.
On this page
Location count and what is actually constraining you decide this. Under roughly 150 leased locations, or where your driving requirement is lease accounting compliance, buy: CoStar Real Estate Manager, Lucernex, Tango or IBM TRIRIGA will beat a build comfortably and the arithmetic is not close. Above roughly 400 locations, where site decisions each take a week of analyst work and option windows have already been missed, a build of the decision layer runs $100,000 to $220,000 for a first release. Note the shape of that answer: almost nobody should rebuild lease accounting. The question is whether to build what sits above it.
When is off the shelf genuinely the right call here?
Buy if you occupy fewer than roughly 150 locations. At that scale a configured tenancy plus a competent lease administrator beats anything custom, and a build would be automating judgement that has not yet become a bottleneck. Buy if your driving requirement is accounting compliance, because that capability is mature, your auditor already knows it, and recreating it is expensive in exactly the way that produces no operational benefit.
These products are capable and the reasons to pick each are clear enough to state. CoStar Real Estate Manager and Lucernex handle abstraction and lease accounting properly, with auditor familiarity that has real value at year end. Tango was designed for retail occupiers and understands site decisions better than most, so if you run stores you should evaluate it seriously before commissioning anything. IBM TRIRIGA is a genuine integrated workplace management system, and if you are a large owner occupier whose actual problem is facilities, space planning and work orders across corporate buildings, rebuilding that is a poor use of capital.
Buy also if the constraint is record keeping rather than decision throughput. Holding a lease, producing an accounting entry and printing a report of upcoming dates is a solved problem. If nobody in your team is stuck for want of a decision, and the complaint is that the data is messy, that is an abstraction project rather than a software one.
The honest test is how a renew or exit decision gets made today. If your head of real estate can answer for a specific location inside an hour, with the trading numbers and the restoration liability in front of them, you have not outgrown what you can buy.
When does a custom build actually pay off?
The structural reason occupiers break these tools 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 and the restoration obligation. The lease is one input among six. When the primary object is wrong, every report is subtly answering a question nobody asked.
That shows up in a specific failure. A regional director asks in March what the plan is for a store whose lease expires in October. The abstract shows one option remaining, 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 starts from a position the company gave away by being busy. The alert existed. It fired on the date rather than when the decision process had to begin, went to a mailbox rather than a named person, and arrived without the information needed to decide, which turned a decision into a research task.
Build when several of these hold. You have missed option or kick out windows and the cost was material. Site decisions each require a week of analyst work, so most of them do not get made properly. Landlord charges are paid without validation and you have never audited a reconciliation. Your decisions depend on modelling transfer between locations, which no packaged occupier tool does with your own closure history. Or the real estate system needs to be the operational spine linking finance, operations and construction, and no vendor will integrate on your terms.
Build, in short, when the constraint is decision throughput rather than record keeping.
How do they compare on the things that matter in this industry?
The differences are narrow and specific, and each is testable against your own portfolio in a demonstration.
- The primary object. Ask any vendor or developer whether the location or the lease sits at the centre. If the answer is lease, you will get another lease register, which is what you already have and what already failed.
- Backward scheduled dates. A report of upcoming deadlines is not a control. What matters is whether a case opens when the decision process must start, which for a site needing a market test and committee approval is often twelve to eighteen months before the notice date.
- Decision pack population. Does the alert arrive with trailing twelve month sales, four wall contribution, occupancy cost ratio against a portfolio benchmark, remaining fit out life, capital spent in five years, market comparables and the restoration liability. If not, it is a research task and research tasks slip.
- Landlord charge validation. Encoding each lease's recovery caps, exclusions and share definition once, then testing every incoming statement against them, is the clearest configuration ceiling in the category. Ask whether it exists or whether a person reads statements.
- Transfer modelling. Closing a location rarely loses all its revenue. A model that ignores transfer to nearby sites systematically recommends keeping locations you should exit, and calibrating transfer needs your own closure history rather than a flat assumption.
- Obligation coverage. Restoration accrued during occupancy rather than discovered at exit, co-tenancy rights that expire unexercised, percentage rent reporting on landlord specific schedules, and annual certificate delivery to hundreds of landlords.
- Data portability. Lease documents and decision records outlive most software, because a commitment signed today may be litigated in fifteen years. Ask what leaves as data.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience, a location centric record with a backward scheduled critical date engine, named owners and escalation runs $100,000 to $150,000. Adding site decision packs joining lease economics to trading performance and automated landlord charge validation takes a first release to $150,000 to $220,000 across fourteen to twenty weeks. A full platform with transaction and approval workflow, capital project tracking, sublease and disposal, obligation management, portfolio analytics and lease accounting output runs $250,000 to $650,000 over eight to fourteen months.
Country count is the largest multiplier at $25,000 to $60,000 each, because lease structures, indexation mechanics, tax treatment and statutory renewal rights differ enough that a second country touches the lease model rather than sitting on top of it. Location count matters far less than people expect: a nine hundred store single country portfolio can be cheaper to model than a two hundred site European one. Lease accounting in scope adds $60,000 to $140,000. A mixed property type portfolio adds $30,000 to $70,000, because offices bring space planning and stores bring trading analysis and they share the lease and almost nothing else. Abstraction backlog is $20,000 to $120,000 and is usually the pacing item above a thousand leases.
Running costs are 14 to 18 percent of build a year for support, because critical dates are unforgiving and a missed notice is not recoverable by a fix. Add $5,000 to $12,000 for hosting and document retention, $6,000 to $15,000 for integration maintenance and $10,000 to $30,000 a year for country and rule updates. Your retained accounting platform continues. The cost most often left out of the business case is abstraction of new and renewed leases, which at any real transaction volume is a standing internal role or an outsourced line rather than a project cost.
What does the hybrid look like, and when is it the honest answer?
The hybrid is the recommendation for almost every occupier large enough to be reading this. Keep your incumbent for abstraction and lease accounting, where it is genuinely strong and where your auditor is already comfortable. Build the decision layer above it: the location record, backward scheduled critical dates with named owners, decision packs and landlord charge validation. That is a $100,000 to $220,000 piece rather than a $650,000 programme, and it is the part that changes outcomes.
The split works because the boundary is clean. Accounting needs remeasurement on modification, discount rate policy, transition treatment and evidence an auditor will accept. Decisions need trading performance, sunk capital, remaining fit out life and a restoration estimate. Those are different disciplines with different quality bars, and forcing them into one system is how these programmes drift. Decide the boundary explicitly at kickoff, because retrofitting accounting into a decision system costs more than planning for it, and many occupiers never bring it across at all.
The scoping rules that keep a hybrid honest are worth stating. One country and one property type first, so every later region inherits a working model rather than a design argument. Import your existing lease abstracts rather than re-abstracting from source documents, flag the fields you distrust, and correct them as each location comes up for decision. Start charge validation on your largest landlords, because encoding caps for the leases carrying most of your operating expense recovers most of the exposure for a fraction of the abstraction effort. And skip the broker facing portal, which adds external user management without addressing the constraint.
Which should you choose, by operator size and stage?
Under 150 locations, one country: buy. A configured tenancy and a good lease administrator.
One hundred and fifty to 400 locations, accounting driven: buy, and fix the process rather than the software. Route critical dates to named people rather than a mailbox, and start each renewal case a year before the notice date rather than at it. Both are free, and together they remove a large share of the exposure that funds these builds.
Four hundred or more locations, one country, one property type: build the decision layer and keep accounting where it is. Roughly $150,000 to $220,000 over fourteen to twenty weeks. This is the population where the analyst week per decision has quietly become the reason most decisions are not made.
Retail and branch networks of any size above the threshold: evaluate Tango properly first, because it was built for this workflow. Then build only if transfer modelling against your own closure history, or a specific decision pack your operators need, is what the evaluation exposes as missing.
Multi country occupiers, or mixed office and store portfolios: build, and budget honestly for country count and property type mix rather than treating them as configuration. A programme scoped as one build and delivered as two is the most common failure mode here.
Any occupier who has never audited a landlord reconciliation: build the charge validation piece first, whatever else you decide. It typically recovers a meaningful part of the build within two reconciliation cycles, and it is the line item a finance director understands without explanation.
If you want that decision made properly rather than quickly, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- McKinsey estimates that digitizing the supply chain (Supply Chain 4.0) can cut lost sales by up to 75%, reduce inventories by up to 75%, and lower supply chain operational costs by up to 30%, with up to 30% lower transport and warehousing costs. Source: McKinsey & Company (2016) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
Frequently asked questions
Is Tango or CoStar Real Estate Manager enough, or should we build?
For portfolios under roughly 150 locations, or where the driving requirement is accounting compliance, clearly enough, and a build is hard to defend. Tango in particular was designed around retail occupier site decisions and deserves a serious evaluation before anything is commissioned.
The build case appears when decisions depend on joining lease economics to trading performance and to transfer between locations using your own closure history. That is the join packaged occupier tools leave to an analyst, and it is why site decisions cost a week each.
What does it cost to switch occupier platforms later?
The subscription is the small part. The expensive part is re-validating abstraction, because lease data extracted under one vendor's field model rarely maps cleanly to another's, and every field you decide on has to be trusted.
Ask now how abstracts, critical dates, documents and accounting history export as data rather than as reports. Occupiers who built the decision layer themselves switch far more cheaply, because the location record, decision history and encoded recovery caps never lived in the vendor.
What happens if the vendor changes its per location pricing?
Pricing in this category typically follows location or lease count, so it grows precisely as your estate does. Model it against your expansion plan over three years rather than today's portfolio, since that projection changes the answer more than any single increase.
The practical protection is owning the decision layer. A repricing then becomes a procurement negotiation about record keeping and accounting, which is replaceable, rather than about the system your regional directors use to make decisions.
How long does a corporate real estate build take?
Fourteen to twenty weeks for a first release covering one country and one property type. A full programme runs eight to fourteen months.
For portfolios above a thousand leases the pacing item is abstraction rather than engineering, so importing an existing professional abstraction instead of re-abstracting from source documents is the most reliable way to protect the schedule. Re-abstracting first is how a twenty week project becomes a fifty week one.
Should lease accounting sit inside the build?
Usually not, and many occupiers deliberately keep it in CoStar Real Estate Manager or Lucernex. It adds $60,000 to $140,000 and brings remeasurement on modification, discount rate policy, transition treatment and an evidence standard an auditor will accept.
Decide it explicitly at kickoff either way. Retrofitting accounting into a system designed for decisions costs more than planning for it, and the reverse is also true: a decision layer bolted onto an accounting build tends to inherit the wrong primary object.
Can software really catch landlord overcharges?
Yes, and it is usually the fastest payback at roughly $24,000 to implement. Encode each lease's recovery caps, exclusions and share definition once during abstraction, then validate every incoming statement automatically and rank a review queue by exposure so a stretched team spends its hours on the statements worth challenging.
Track the audit right window per lease as well, because an expired right is worth nothing regardless of the merits. Most findings need a letter citing a clause rather than litigation.
Why does country count matter more than location count?
Because a thousand similar retail units cost little more to model than four hundred, while a second country brings different lease structures, indexation mechanics, tax treatment and statutory renewal rights, all of which touch the lease model itself.
Budget $25,000 to $60,000 per country. This is the largest multiplier in the category and the one most often missed at scoping, which is why quoting this work on location count produces the wrong number in both directions.
Should the primary object be the lease or the location?
The location, with leases, trading performance, capital, obligations and transactions attached to it. It sounds like a modelling detail and it decides everything downstream.
Ask any prospective developer or vendor directly. If the answer is lease, you will get another lease register, which is what you already have and what already failed to stop the option window passing. If the answer is location, ask next how a critical date becomes a populated decision rather than a notification.
Can I start with one ERP module instead of the full system?
Yes, and it is how most successful custom ERP projects at Digital Heroes begin. We build the single module causing the worst pain first, typically inventory or order management, get it live in 10 to 14 weeks, and let it prove ROI before the next phase gets funded. Starting with one module also derisks data migration because you move one dataset at a time.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
Can a custom ERP meet compliance requirements like SOC 2 or GDPR?
Yes, and often more cleanly than a shared SaaS platform because you control exactly where data lives and who touches it. The build includes role-based access control, full audit logs, encryption at rest and in transit, and data residency in whatever region your regulator requires. If you need SOC 2 attestation, tell the agency before development starts, since audit logging is far cheaper to design in than to bolt on.
How do I calculate the ROI on a custom ERP?
Add up three lines: hours of manual work removed at loaded labor cost, subscription licenses you cancel, and error costs like mispicks and double entry that disappear. In Digital Heroes delivery experience, mid-market ERP builds typically reach payback in 18 to 30 months, faster when they replace a per-seat platform at 30 or more users. Run the math over five years, because that is where a one-time build beats recurring licenses decisively.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
What tech stack should a custom ERP be built on?
A boring, hireable one: Digital Heroes most often ships ERPs on PostgreSQL with a Node.js or Python backend and a React frontend, hosted on AWS or Azure. The stack matters far less than the database design, because your ERP schema will outlive every framework choice. Be skeptical of any agency proposing a niche or proprietary framework, since your ability to hire maintainers later is part of the total cost.
What mistakes kill ERP projects most often?
The three we see most in rescue work at Digital Heroes: recreating the old system's broken process in new software, launching everything at once instead of module by module, and having no single internal owner with authority to decide. A fourth is skipping the parallel run on data migration to save two weeks, which trades a short delay for months of distrust in the numbers. None of these are technical failures, which is why vendor selection should weigh process discipline over demo polish.
Can a freelancer build an ERP, or do I need an agency?
An ERP is too wide for one person: it needs backend, frontend, database design, integrations, QA, and someone mapping your business processes. A solo freelancer can extend an existing ERP or ship one small internal tool, but full ERP builds by single developers are the most common rescue scenario Digital Heroes takes on. If budget is tight, shrink the scope to one module rather than shrinking the team below three or four people.
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Pick Business Central if you already live in the Microsoft stack, your processes are close to standard, and around $80 per user per month for Business Central Essentials stays affordable at your headcount. Build custom when your revenue-driving workflow, such as custom manufacturing steps or unusual pricing logic, would need heavy extension work anyway. In our experience, once Dynamics customization quotes pass about $100,000 the custom option deserves a serious side-by-side.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other ERP software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Maya.
Senior QA Engineer · Delhi · 1 post on the site
Published · Last updated .
