What Software Does JLL Use? A CRE Stack Guide for Brokers
What software does JLL use?
Short answer: nobody outside JLL knows the full list, and any article claiming to have it is guessing. Global firms run hundreds of applications across brokerage, capital markets, valuation, property management, and facilities — and vendor rosters change with every acquisition and renewal cycle.
What is publicly documented, from JLL’s own newsroom and press releases (verify current status there before quoting any of it):
- Corrigo — a facilities/work-order management platform that is a JLL company.
- Building Engines — building operations software JLL Technologies acquired in 2021.
- JLL Azara — a data and analytics product built on JLL’s own portfolio data.
- JLL GPT / JLL Falcon — JLL’s publicly announced large-language-model and AI platform work, positioned as internal-first tooling trained on the firm’s proprietary data.
- Skyline AI — an AI investment-analytics company JLL acquired in 2022.
Everything else — email and identity, CRM, data warehouse, BI, document management, e-signature, accounting — sits in commodity enterprise categories JLL doesn’t announce deal by deal.
The five layers of an enterprise CRE stack
Strip any large firm’s stack down and you get five layers. Naming them makes it obvious which ones you can copy.
- System of record — where deals, contacts, properties, and comps live. One place, not four.
- Market data — subscription data on ownership, comps, availabilities, tenants.
- Production — the documents the business runs on: OMs, LOIs, tour books, BOVs, proposals, abstracts.
- Data layer — a warehouse or structured store the front-end tools read from and write to.
- Intelligence — dashboards, forecasting, and the AI features stacked on top of layers 1–4.
The common failure at every size is trying to buy layer 5 before layer 4 exists. AI tools trained on messy, half-populated records produce confident, wrong answers faster than a junior analyst does.
You cannot automate your way out of a data problem. Layer 4 before layer 5, always.
What actually transfers to a 5-50 person brokerage
Three things transfer cleanly:
One system of record, enforced. The most expensive problem in small-brokerage ops isn’t software cost — it’s four versions of the truth (a CRM, a shared drive, a broker’s personal spreadsheet, and someone’s inbox). Consolidation costs nothing but discipline and returns hours immediately.
A data layer you own. Even a well-structured shared database or warehouse that your CRM, financial model templates, and reporting all read from means you can switch tools later without losing five years of comps and contacts. This is the single highest-leverage unglamorous investment available to a brokerage.
Automation aimed at the seams. Enterprise firms automate between systems, not inside them. The hours in a brokerage don’t disappear inside the CRM — they disappear in the handoffs: signed listing agreement → property record created → marketing package kicked off → data room built → prospect list pulled → outreach sequenced → tour scheduled → LOI logged.
How can AI help commercial real estate operations — realistically
The honest read on artificial intelligence in commercial real estate right now: it is reliably good at drafting, extracting, and summarizing, and unreliable at deciding. That maps to a narrow but valuable set of brokerage jobs:
- Lease and rent-roll extraction into structured fields (with human verification on economic terms).
- First drafts of property descriptions, tour recaps, and outreach copy.
- Summarizing long documents — PSAs, estoppels, third-party reports — into review checklists.
- Cleaning and deduplicating contact and property data before it enters your system of record.
- Answering internal questions against your own document set, if you’ve built the data layer.
What it does not do well: pricing judgment, market read, relationship strategy, or anything where being 90% right 100% of the time is unacceptable.
The hour math: a labeled worked example
Run this with your own numbers — every input below is an assumption, not a finding.
The arithmetic: 12 brokers × 6 hours/week × 46 working weeks = 3,312 admin hours/year. Assume a well-targeted automation program cuts 35% of that = 1,159 hours recovered.
Now be conservative on conversion. Assume only 30% of recovered hours become genuinely revenue-producing activity (the rest is absorbed by slack, meetings, and life) = 348 hours. If a producing broker generates $250,000 in gross commission across roughly 1,800 productive hours, that’s ~$139/revenue hour → ~$48,000/year in modeled captured value, before touching ops headcount.
Add the ops side: if one coordinator spends 10 hours/week on data entry and package assembly and you remove half of it, that’s ~230 hours/year returned to broker support — which usually shows up as faster time-to-market on listings rather than payroll savings.
Against that, price the full cost: software subscriptions, build or configuration cost, integration maintenance, and the 20–40 hours of internal time it takes to define the workflow properly. If your modeled captured value doesn’t clear total cost by 2x in year one, the scope is probably wrong — not the idea.
What is the 3 3 3 rule in real estate?
There is no official body that defines a “3-3-3 rule.” It’s an informal coaching heuristic, and at least three versions circulate:
- A daily prospecting cadence — roughly 3 hours of prospecting, 3 new contacts, and 3 follow-ups per working day. This is the most common usage and originates in residential coaching.
- A deal-horizon framing — what closes in 3 months, 3 quarters, and 3 years, used to keep a pipeline balanced across near-term and long-lead opportunities.
- A tenant/renter affordability shorthand — versions involving three months of savings or income multiples, unrelated to brokerage production.
For CRE ops teams, the version worth caring about is the second one, because it’s a measurable pipeline health check you can automate: tag every opportunity with an expected-close horizon and report weekly on the mix. A pipeline that’s all 3-month deals is a revenue cliff in nine months.
The first version is where automation earns its keep. Brokers rarely miss their prospecting targets because they’re lazy — they miss them because list-building, data cleanup, and follow-up logging eat the block. Automate the prep, and the cadence becomes achievable without heroics.
Is there a commercial real estate automation certification?
Not as a recognized industry credential. There is no CRE-specific automation certification with the standing that CCIM, SIOR, or RICS designations carry on the brokerage side.
What exists instead, and what’s actually useful on a résumé or an ops job posting:
- Platform certifications — CRM and low-code/automation platform credentials from the vendors themselves. These prove tool fluency, not CRE judgment.
- Data and analytics certifications — general BI and SQL credentials, which transfer well to CRE ops work.
- CRE designations — CCIM, SIOR, and similar for the domain side.
If you’re hiring for commercial real estate operations roles, the combination that actually predicts performance is domain literacy (can they read a rent roll?) plus one platform certification plus a portfolio of workflows they’ve actually shipped. Ask candidates to walk you through a process they automated end to end, including what broke.
A 90-day sequence for a boutique brokerage
-
Weeks 1-2: Time-and-motion, not tool shopping
Have three brokers and one coordinator log where hours actually go, in 30-minute blocks, for two weeks. You are looking for the top five repeated tasks by total hours — not the most annoying tasks. These are rarely the same.
-
Weeks 3-4: Pick the system of record and freeze it
Decide which platform is the single source of truth for deals, contacts, and properties. Write down what lives there and what explicitly doesn’t. Every shadow spreadsheet you tolerate now becomes an integration cost later.
-
Weeks 5-8: Automate one seam, end to end
Pick the highest-hour handoff from step one — usually new listing intake or deal-stage document production. Automate it completely rather than automating five workflows halfway. Measure the before/after in hours, not in vibes.
-
Weeks 9-12: Build the data layer and instrument it
Stand up structured reporting on pipeline by close horizon, cycle time per deal stage, and hours recovered. This is the layer that makes AI features useful later and makes vendor switching survivable.
What to measure after
Four metrics, reviewed monthly:
- Cycle time per deal stage — listing signed to marketed, LOI to PSA, PSA to close.
- Admin hours per closed deal — the number that should fall as volume rises.
- Data completeness rate — percentage of active records with required fields populated. Below ~85%, don’t bother with AI on top.
- Pipeline mix by close horizon — your 3-month / 3-quarter / 3-year balance.
If a tool or build doesn’t move one of those four, it’s a preference, not an investment. That’s the actual lesson from how the large firms operate: they don’t buy software because it’s impressive, they buy or build it because a specific number is supposed to move — and they check whether it did.
Not sure where to start?
Get a free automation audit: we map your deal pipeline, marketing, and back-office workflows and show you what's worth automating — before you spend a dollar.
Get a free automation audit