Is CRE Tech New York worth going to?
It's worth it if you arrive with a specific operating problem to solve — a broken leasing tracker, lease expirations nobody owns, broker updates lost in email. Then the show floor becomes vendor diligence. If you go looking for inspiration or a general "AI update," you'll leave with a tote bag and no decision.
CRE Tech is a long-running proptech conference series that brings owners, brokers, and technology vendors into one room. The recurring question on forums like r/CommercialRealEstate is whether the event serves operators — brokers and analysts — or mainly software developers and vendors. The honest answer: it serves whoever comes prepared.
Who is CRE Tech New York actually for?
It's for two audiences at once, which is the source of the confusion. Vendors and proptech founders come to sell and network. Owners, brokers, and analysts come to evaluate. The event rewards the second group only when they treat it as structured diligence rather than a trade show to wander.
- Brokers and leasing teams get value scoping tools against a real pipeline problem — not browsing.
- Analysts get value pressure-testing data claims: where does a number come from, and can it be wrong?
- Owner-operators get value comparing how vendors handle approval and audit, not just features.
- Proptech vendors and developers get value selling and partnering — that's their job.
If you're a broker expecting a masterclass, recalibrate. Expect a marketplace, and shop with a list.
What should a broker or analyst bring to get value?
Bring a written problem and a decision-maker's checklist. A rent roll (the tenant-by-tenant record of leases, rents, and terms) that's drifting out of date is a problem. A stacking plan (a floor-by-floor map of who occupies what) rebuilt by hand every month is a problem. Name the artifact, then go find the two vendors who touch it.
Bring these to every booth:
- What artifact does this touch? The leasing tracker, the broker packet, the rent roll — not "your data."
- Where can it be wrong? Ask for the failure mode, not the demo reel.
- Who approves before anything sends or changes? In governed software the rule is propose, never commit — the system stages an action, a human approves it, and it lands on an audit trail.
- What does setup actually take? A weekend or a quarter?
Will you learn where CRE tech is heading?
Yes, but read the trend through your own numbers. The loud theme is AI, and the gap between interest and results is real. According to Deloitte's 2024 Commercial Real Estate Outlook, a majority of surveyed firms planned to increase technology spending even amid cost pressure — appetite is not the problem. Follow-through is.
The pattern worth watching on the floor: vendors demoing autonomous "agents" that act on their own versus tools that stage work for human approval. For an operating company handling live leases and rent numbers, the second design is the one that survives a bad month. A slick demo tells you the tool can generate; it doesn't tell you who's accountable when it's wrong.
How do you avoid wasting the trip?
Set a decision, not an itinerary. Decide in advance what you'll walk away having ruled in or ruled out — a leasing-tracker replacement, a way to capture broker updates (the running deal notes reps text or email in), a lease-expiration alerting system. Book three vendor conversations against that decision. Skip the keynote if the keynote doesn't touch it.
- Before: Write the one problem you'll solve. Name the artifact and the owner.
- During: Ask the four questions above at every booth. Take notes by problem, not by company.
- After: Pilot one tool against real data. Measure whether it reduced manual work without adding risk.
That turns a conference expense into a scoped evaluation — and answers "was it worth it" with something you can point to.
FAQ
Is CRE Tech New York for brokers or for software developers?
Both, which is why brokers sometimes feel out of place. Vendors and developers come to sell and partner. Brokers and analysts get value only when they treat the floor as vendor diligence against a specific problem, rather than browsing for general inspiration.
What's the single best way to prepare?
Write down one operating problem before you go — a drifting rent roll, untracked lease expirations, broker updates lost in email. Name the artifact and who owns it. Then book vendor conversations against that problem and rule tools in or out.
Should I trust the AI tools demoed on the floor?
Judge them on accountability, not the demo reel. Ask where the tool can be wrong and who approves an action before it sends or changes a record. Tools that stage work for human approval — propose, never commit — beat autonomous ones in live operations.
What questions should I ask every vendor?
Four: What artifact does this touch? Where can it be wrong? Who approves before it acts? What does setup actually take? Concrete answers separate real fits from listicle neutrality.
How do I know if the trip was worth it afterward?
Set a decision goal beforehand and measure against it. If you piloted one tool against real data and it cut manual work without adding risk, the trip paid for itself. A tote bag and vague notes mean it didn't.