When Good Software Still Creates More Work

Question

One thing I’ve been noticing while looking at real estate and property management operations is that buying more software doesn’t always fix the workflow.

A company might have good tools for:

•⁠  ⁠Lead management

•⁠  ⁠Property management

•⁠  ⁠Maintenance

•⁠  ⁠Accounting

•⁠  ⁠Email and communication

Yet staff still end up copying information between them.

For example, a new owner signs a management agreement. Someone then has to manually make sure the property gets set up, inspections are scheduled, maintenance is aware, accounting has the right information, and leasing can take over.

The software itself may work perfectly. The gap is often the handoff between them.

The simple way I look at it is:

System A → Someone manually moves information → System B

The bigger the operation gets, the more those handoffs can create extra work or cause things to get missed.

I’m curious how experienced operators here handle this.

Do you intentionally connect your systems together, or do you rely on your team and processes to manage the handoffs between them?

Mark Updegraff · Answer

We run into this constantly.

I think the mistake is assuming software selection and workflow design are the same thing.

Before I automate a handoff I want to know: what triggers it, who owns it, what information is required, what the next system should look like afterward, and what happens when the normal path breaks.

Otherwise you can spend a lot of money integrating systems and just automate a bad process faster.

I’m increasingly interested in AI as an operating layer between systems, but I still want the CRM, PM software, accounting system, leases, etc. to remain the source of truth. The AI should find the dropped baton — not quietly invent a new one.

Cole S. · Answer

I see this a lot too. The biggest thing for me is deciding which system is the source of truth before connecting anything.

Once that’s clear, APIs/webhooks can handle most of the handoffs automatically. Otherwise you can end up with two systems updating the same data and creating an even bigger mess.

Sometimes fewer tools that work well together is better than adding another “all-in-one” platform.

Paul Olusola · Answer

Exactly. That’s the distinction I’m trying to get at.

I’m less interested in connecting two systems and more interested in what happens between them what triggers the handoff, what data has to move, who owns the next step, and what happens when something doesn’t fit the normal path.

That’s actually where I build. I can take that workflow and build the logic/API layer around the systems you already use, with AI only where the process needs interpretation.

Given that you’re running brokerage, property management and investment operations, I’d be curious to see one workflow where your team still has to manually carry something from one system/process to another.

Vaibhav Puranik · Answer

Connecting these systems are not that easy but now a days there is an alternative. Using AI. ChatGPT's Astra model can literally read info in one system and enter it in another system. It's not a permanent solution but it works - 100%. Permanent solution would be something based on n8n.

Paul Olusola · Answer

Yeah,

I agree that AI can make some of those gaps much easier to deal with, especially when the systems don’t have clean integrations.

The part I’d be careful with is treating AI screen-reading as the permanent layer. If the same information needs to move between systems every day, I’d rather have a proper workflow handling the data, validation and business rules, and use AI where the information itself needs to be interpreted.

That’s actually the part I’m interested in   not just moving data from A → B, but deciding what should happen to it once it gets there.

Curious what systems you’re dealing with at Old Money Capital where you’re seeing this problem?

When Good Software Still Creates More Work

When Good Software Still Creates More Work

Most Popular Reply

5 Replies