The Net Lease Tech Stack: Every Tool a Firm Runs On, and What to Consolidate

Most net lease firms do not have a technology stack so much as a sediment of tools. An inbox rule was set up when deal flow picked up. An underwriting model was inherited from a former analyst. A shared drive grew a folder for every property. A calendar holds the option dates someone remembered to enter. Each tool was a reasonable choice when it arrived. Together they form a system nobody designed, and the cost of that system shows up in the hand-offs between tools rather than inside any one of them.

This guide walks the net lease lifecycle stage by stage, from the broker email to the investor report. For each stage it describes the category of tool firms typically use today, where data is re-keyed on its way to the next stage, and what can go wrong. It closes with a framework for deciding what to consolidate and what to keep. It names no products. The categories matter more than the brands, and the same failure modes appear regardless of vendor.

Why net lease stacks fragment differently

A net lease firm’s work is unusually document-driven and unusually long-lived. A single-tenant property may be bought on the strength of one lease, and that lease may govern the asset for fifteen or twenty years. The facts that matter at acquisition, such as the rent schedule, the renewal options, the landlord’s repair obligations and the guarantor, are the same facts that matter on the day a notice window opens a decade later.

That continuity is what fragmentation breaks. Acquisitions teams read the lease to price the deal. Asset managers read it again to administer it. Accounting reads it a third time to bill rent. When each group keeps its own copy of the facts in its own tool, the firm ends up with three versions of the same lease, and no reliable way to tell which one is right.

Stage by stage: the typical stack

1. Deal intake

What firms use: a shared inbox or individual inboxes, folders and forwarding rules, and sometimes a pipeline spreadsheet or a CRM. Offering memorandums arrive as attachments, as links to marketing sites that require a sign-in, or as a confidentiality agreement that must be signed before the OM is released.

The hand-off: someone opens the email, downloads the OM, saves it to a drive and types the headline figures (tenant, price, cap rate, lease term remaining, location) into a tracker. Duplicates are common: the same property comes from two brokers, or the same broker sends it twice with a revised price.

The risk: deals that are never logged. An offering that arrives during a busy week can sit unread until it is under contract with someone else. The tracker reflects what the team had time to enter, not what the market sent.

2. Screening against the buy box

What firms use: a written buy box, often a one-page document or a slide, applied by judgment. Some firms encode it as filters in a spreadsheet.

The hand-off: the analyst compares the tracker row to the criteria from memory. Reasons for passing are rarely recorded in a structured way.

The risk: inconsistency. Two analysts apply the same criteria differently, and the firm cannot later answer basic questions, such as how many offerings it saw from a tenant it now wants to own, or why it passed on them.

3. Underwriting

What firms use: spreadsheet models, usually a firm template that each analyst copies and modifies per deal. For single-tenant net lease, the model is often simple in structure: a rent schedule with escalations, a purchase price, a debt assumption and a return calculation.

The hand-off: figures are typed from the OM into the model. Later, when the lease itself arrives in diligence, figures may or may not be re-checked against it. The model’s inputs carry no link back to the page they came from.

The risk: version drift and unsourced numbers. By the time a deal reaches committee there may be several copies of the model in circulation, and the escalation rate in the model may be the broker’s summary rather than the lease’s actual language. Spreadsheet errors are well documented in academic literature; the problem is not that analysts are careless, it is that a model with no source links cannot be audited quickly.

4. Comps

What firms use: paid market data subscriptions, broker-provided comp sheets, and an internal spreadsheet of past offerings and closed trades.

The hand-off: comps are pulled into the memo by hand. The firm’s own history, every OM it has ever received, is usually the richest dataset it owns and the least searchable.

The risk: stale or unverifiable comps, and an internal record that exists only in old email.

5. Investment committee memo and LOI

What firms use: word processing templates for the memo and the letter of intent, with figures pasted from the model.

The hand-off: every number in the memo is a copy of a number in the model, which is a copy of a number in the OM. If the model changes after the memo is drafted, the memo does not update. LOI negotiation runs through emailed drafts with tracked changes and file names that end in “v4 final revised.”

The risk: a committee approving figures that no longer match the model, and an executed LOI whose terms differ from what the team believes it agreed.

6. Diligence tracking

What firms use: a spreadsheet checklist, sometimes a task tool, keyed to the purchase and sale agreement. Third-party reports (title, survey, environmental, property condition) arrive by email.

The hand-off: PSA deadlines, such as the end of the inspection period, deposit hardening and title objection dates, are calculated by hand and entered into the checklist and someone’s calendar. Each received document is checked off manually.

The risk: a missed contractual deadline. In a PSA, dates carry money: an earnest money deposit that goes hard while an issue is unresolved changes the firm’s negotiating position.

7. Data rooms and file storage

What firms use: the seller’s virtual data room on the way in, and a shared drive or document management system internally.

The hand-off: documents are downloaded from the seller’s room and re-filed into the firm’s own folder structure, often inconsistently. The lease that was reviewed in diligence and the lease that is filed after closing are not always the same copy, and amendments may be missing.

The risk: an incomplete lease file. Lease abstraction tends to fail not on the base lease but on the amendment nobody filed.

8. Estoppels and closing

What firms use: word processing for the estoppel form, email for collection, and a side-by-side manual comparison of the signed estoppel against the lease.

The hand-off: the estoppel review happens under deadline pressure, close to closing. The comparison lives in an email or a redline and is rarely carried forward into the asset’s records.

The risk: a discrepancy between what the tenant certifies and what the lease says, such as a different rent amount, an undisclosed amendment or a claimed default, that is noticed late or not at all.

9. Lease abstraction and administration

What firms use: an outsourced abstraction vendor, an in-house analyst, or both, feeding a lease administration system or a spreadsheet of abstracts.

The hand-off: this is the largest re-keying event in the lifecycle. The lease was read in diligence by the acquisitions team; it is now read again from scratch by someone who was not there. The abstract is a summary, often without page references, and it is entered into a separate system.

The risk: an abstract that disagrees with the underwriting, with no way to tell which is correct without rereading the lease.

10. Critical dates

What firms use: calendars, the lease administration system’s reminders, or a spreadsheet of expirations and option windows.

The hand-off: dates are derived from the abstract, which was derived from the lease. Notice windows (for example, “no earlier than twelve months and no later than six months before expiration”) are converted into calendar entries by hand.

The risk: a missed renewal, termination, purchase option or right of first refusal window. These are low-frequency, high-cost events, and calendar entries are only as good as the person who created them and whether that person still works at the firm.

11. Rent, debt and property accounting

What firms use: a property accounting or general ledger system, bank portals, and spreadsheets for loan covenants, maturities and rate resets.

The hand-off: rent schedules are entered into accounting from the abstract. Loan terms are entered into a debt tracker from the loan documents. Rent receipts are reconciled against the schedule, often in a spreadsheet.

The risk: a scheduled escalation that never makes it into billing, a late payment that goes unnoticed, or a covenant test or maturity that surfaces too late to refinance on good terms.

12. Investor reporting

What firms use: spreadsheets and presentation templates assembled from the accounting system, the debt tracker and the asset managers’ notes. Funds reporting to institutional limited partners may align to industry templates; the Institutional Limited Partners Association, for example, published an updated Reporting Template and a new Performance Template in January 2025.

The hand-off: every quarter, figures are pulled from several systems and reconciled by hand.

The risk: a report that is internally inconsistent, or that takes so long to assemble that it is stale on delivery.

13. General AI chat tools

What firms use: increasingly, general-purpose AI chat assistants, used by individuals to summarize an OM, draft an email or answer a question about a lease.

The hand-off: the analyst uploads a document, gets an answer and copies it somewhere else. The answer has no persistent link to the firm’s records, and the next person to ask the same question starts over.

The risk: confidential documents leaving the firm’s controls, answers that cannot be traced to a page, and a policy question many firms have not yet answered: whether the tool’s provider may use uploaded content to improve its models under the plan the analyst happens to be on.

The pattern: one set of facts, typed many times

Laid end to end, the stages above show the same handful of facts, namely tenant, rent, escalations, term, options, obligations and debt, being transcribed from the OM to a tracker, to a model, to a memo, to an abstract, to a calendar, to the ledger and to an investor report. The table below summarizes where the re-keying happens.

Each transcription is a chance to introduce an error, and each copy is a chance for versions to diverge. The firm does not usually lack data. It lacks a single place where each fact lives, with a link back to the document it came from.

A framework for what to consolidate and what to keep

Consolidation is not the goal in itself. Replacing ten tools with one can simply move the problem if the new system is weaker at a job the old tool did well. A more useful question is: for each fact, where should it be created, and who should read it from there? The following principles help answer that.

Keep the systems of record that carry legal or financial authority

The general ledger and property accounting system should remain the system of record for the books. It is what the auditors test, what the tax preparers use and what the fund administrator reconciles to. The right move is to feed it accurate lease and rent data, not to replace it. The same applies to the firm’s executed documents: the signed lease and the recorded deed are the authority, and every abstract or figure should point back to them.

Consolidate wherever the same fact is typed twice

If the rent schedule is entered in the model, the abstract and the ledger, those three entries should come from one extraction of the lease, with a citation to the page. Stages that exist mainly to move a fact from one tool to the next, such as intake logging, abstraction after closing, and calendar entry, are the strongest candidates for consolidation.

Consolidate across the acquisitions to asset management hand-off

The most expensive gap in most net lease stacks is the moment a deal closes. Acquisitions has read the lease closely; asset management starts over. A stack that carries the diligence record, including the extracted terms, the estoppel comparison and the open issues, directly into the owned asset removes the largest re-keying event in the lifecycle.

Keep specialist tools where the work is genuinely specialized

Complex multi-tenant cash flow modeling, fund-level waterfall calculations and tax structuring may warrant dedicated tools or advisers. The test is whether the tool does something your core platform cannot do well, not whether it has always been there.

Require a source for every number

Whatever stays and whatever goes, the standard should be that any figure in a memo, abstract or report can be traced to a page in a document in one step. This is the property that makes a consolidated system auditable, and it is the property that general AI chat tools, used ad hoc, most often lack.

Treat data handling as a selection criterion, not an afterthought

Consolidating onto fewer systems concentrates the firm’s confidential information. Before consolidating, confirm where data is stored, who can see it, whether it is isolated from other customers and whether it is used to train models. Ask for independent assurance reports, such as a SOC 2 examination, and read what period and controls they cover.

A practical sequence

1. Map the facts, not the tools. List the ten to fifteen facts that drive your decisions and trace where each is created and copied today.

2. Start where re-keying is heaviest. For most net lease firms this is intake and the post-closing abstraction.

3. Keep the ledger and integrate with it. Define what the operating platform sends to accounting and how often.

4. Retire tools only after the replacement is proven on live deals. Run both in parallel on a handful of transactions and compare outputs line by line.

5. Write down the data policy. Decide which tools may receive confidential documents, and close the gap that ad hoc use of general AI chat tools creates.

The aim is not the fewest tools. It is the fewest copies of each fact, each one traceable to its source.

Where Rets fits

Rets is built to hold each fact once. It reads every OM in your inbox and scores it against your buy box, extracts terms with page citations, builds the rent schedule and returns from the lease, and drafts the IC memo in Word and the LOI with track changes. Diligence runs on the PSA clock; estoppels are compared to the lease. After close, cited abstracts feed critical dates, rent and debt. Chat cites sources, also from Claude and ChatGPT. Data is workspace-scoped, never trains models, SOC 2 Type I.