← Union blog
Article
AI & automation

Your team shouldn't have to work around its software

Every CRM asks a leasing team to work the way the software was built. Union Views flips that. Describe how your team works, and Union builds the screen.

Share
  • Leasing teams work around their CRM because the screen was built for how someone else thought they work.
  • Union Views lets a team describe how it works in plain words, in Claude or by asking Juno, and Union builds the screen.
  • It is in early access now for a small group of operators, and read-only, so a view never changes your records.

I work the espresso bar at every trade show we do. Nobody pitches over a milk steamer. People just tell you what is broken.

The thing I hear most is not about AI, or price, or integrations. It is that the software does not fit how the team actually works. So the team works around it.

You have seen the workarounds. The spreadsheet open next to the CRM. The regional manager who exports every Monday morning to build the view she actually wants. The leasing manager who keeps today's tours on a sticky note because the screen leads with something else.

Every CRM is built for an imaginary team

Every CRM, ours included, was built the way its builders thought a leasing team works. Then every team is asked to work that way.

When the fit is wrong, the fix has always been the same. File a request. Wait for a release. Hope your request makes it to the top of someone else's roadmap.

We heard the same ask on sales calls all year. Can I build this report myself, with my own filters? Can the screen look different for my regional managers than for my agents? Can my tasks be a board instead of a list?

Our honest answer was: not yet, but we will build it for you on the back end. It was a fine answer. It was also the answer every vendor gives.

Describe how you work. Union builds the screen.

Today we are launching Union Views.

You tell Union how your team works, in a plain sentence, and it rebuilds the screen around that.

  • "Put today's tours at the top, leads below."
  • "A list doesn't work for me. Turn my tasks into a board."
  • "Show me my best leasing agents, with charts."

Each one is a sentence. No ticket and no developer.

You can build a view in Claude, if your team already uses it, or by asking Juno, Union's AI, inside the CRM. The view lands in Union, ready for the whole team. When the work changes, you ask Juno to change the view.

This is not a dashboard

Dashboards sit beside the work. Someone builds one, someone checks it, and the team still works the way the software was built.

Views changes the work itself. It is the screen your team opens every morning, arranged the way they actually run the day.

Why we can do this

Union built every layer of its product in-house: the CRM, the data underneath it and the AI on top. That matters here. If you only own an AI layer on top of someone else's system, you can answer questions about the screen. You cannot change it.

Views reads from Union's MCP server, which exposes 41 datasets today, so every view works from the same live data as the rest of the platform. It is read-only, so a view never changes your records.

What it does not do yet

Views is new, and I would rather you hear its limits from me.

  • It is in early access, not generally available.
  • It reads your data. It does not write to it yet.
  • It works with Claude and with Juno. Other assistants are coming.
  • We are adding more datasets.

Early access

We are opening Views to a small group of operators first. We will build your first three views with you, you get a named engineer in a shared channel, and there is no charge until general availability. In return, we ask for thirty minutes of feedback every two weeks.

Apply for early access to Union Views.

This week at OPTECH I will be behind the espresso machine at booth 345. Tell me what your team would build first. I will make you a cortado while it builds.

Ethan Lacey
CEO, Union