What Does Your Second AI Use Case Cost?

Nothing. Everybody in this market charges per door, so the rate isn't the question. What the door price buys is. Right now you pay per door for leasing, then per door for collections, then per door for reporting. The same doors, three times over. A platform is one cost, and whatever you build next sits inside it.

Ask most operators what AI does for them today and you'll get a version of the same three things.

A bot answering questions after hours and taking maintenance requests. Follow-ups chasing leads. Reminders on collections.

All of it useful. And yes, you can build every one of those on Travtus, in a sentence, without waiting on a vendor to add it.

But look at where that work sits. Every one of those jobs happens at the edge of your business, with a resident or a prospect on the other end. The bot takes the maintenance request. Then everything after it runs the way it always did. Somebody still prioritizes it. Somebody still finds a tech who isn't already on another job.

The perimeter gets faster. Nothing behind it changes.

Two things would change it, and neither one is on that list.

The first is your own people getting answers without waiting on the data team. That changes who gets to make the call, not just how fast.

The second is work that starts inside your business instead of with a resident. Between a regional and maintenance. Between asset management and operations.

Nobody sells you that. Your own operations aren't a vendor's product. They're yours. That's the point, and it's also why this is hard to put in a budget.

How do you build the budget?

Start with the easy part. Everybody charges per door, so the rate isn't where this gets won or lost. What matters is that it's one cost for the platform, not a cost per function. When somebody asks for another workflow or another report next year, that isn't a new product, a new contract, or a new integration. It's the same line.

Count how many times you're already paying per door on the same portfolio. One vendor for leasing, one for collections, one for reporting, one for procedures. That's the number your CFO hasn't seen laid out in one place, and it's the real shape of AI vendor sprawl.

The hard part is what sits next to it. A brand new line with nothing above it looks like brand new money. And brand new money gets one question: what comes out?

So have the answer ready before anybody asks. For most operators the list looks about the same:

• The data warehouse work, and more to the point, what it costs to keep it fed and mapped.
• Reporting and analysis you're paying for on the side.
• The small tools that each do one job - pushing procedures out to site teams, sending somebody an alert when a number moves, reading resident messages for sentiment.
• The workarounds. The spreadsheet that holds the real version of the number. The report somebody rebuilds by hand every month. The requests stacked up on your analyst's desk.

That last one is the biggest item on the list and it isn't a vendor at all. You're already paying for it, out of payroll. It just never had a line of its own.

Then phase it. Nobody funds the whole thing in year one. Give people access to the information first, and add the automation the year after. That halves the first ask, and it gives you a plan instead of a number.

What does it replace, and what doesn't it?

This is where most business cases fall over, so be blunt about it. Start with what actually comes off the budget.

• Mystery shopping. You're paying somebody to sample a handful of calls a quarter and score them. Every conversation your team has is already being scored, all of them, every day.
• Your survey program. Run the outreach here instead. And notice what you're really buying with a survey: you're asking a slice of residents once a quarter how they feel, when most of them have been telling you all year in ordinary messages.
• Replying to online reviews. Generated and posted, without somebody on your marketing team writing them on a Friday afternoon.
• Chasing reviews. Instead of blasting every resident with a review request, you ask the ones who just said something good, at the moment they said it.
• BI seats. When regionals can ask their own questions, you need far fewer licenses for people who only ever opened a dashboard to find one number.
• The monthly reporting pack. Built once, runs on a schedule, and arrives with the people who need it instead of being rebuilt by hand every month.
• Procedure and SOP tools. Guides built from how your teams actually work, and kept current, rather than a library somebody updates once a year.
• Resident communication. Inbound and outbound, on your rules, in your voice.

Here's the part worth putting in front of your CFO: every one of those is a separate vendor today, and most of them charge you per door. Same doors, over and over.

Now the other half of the list, and it matters just as much. These stay exactly where they are:

• Your property management system
• Your leasing CRM
• Rent pricing
• Compliance training and certification

This sits on top of what you run and works with it. Nobody is moving your ledger, your leases, or your payments.

Say that early, and say it to everybody. It costs you nothing and it does two jobs at once. It kills the worry that this is a system migration wearing a different hat, which is the first thing your IT lead will suspect. And it stops you promising savings you can't deliver, which is what gets a sponsor in trouble next summer when finance comes looking.

Only promise what you'll actually cancel. A short honest list beats a long hopeful one.

How do you make the case inside your own company?

The number is the easy part. What you're really being asked is whether anybody will build anything with it. Here's how to have that answered before you walk in.

1. Start with a decision somebody really makes. Not a feature, a decision. Sit down with whoever owns the outcome and ask them to name one call they make regularly where better information would change what they do. That single sentence turns "a platform" into something with a dollar figure attached. It also makes the value theirs, not yours.
2. Look at your own data before you pick the first project. This feels backwards, and it's the strongest move you've got. A product demo turns into a feature comparison. Sitting down and looking at what you actually hold, and what shape it's in, turns into a conversation about what you could do with it. Then the first project gets picked against something real.
3. Get other people to own it with you before you ask for money. You want three people in this: you, somebody who owns the business outcome, and your sponsor. This isn't politics. It's the defense against the one objection that ends champions, and it's coming up next. If operations and asset management picked the first project, it's a business decision. If you picked it on your own, it's your bet.
4. Pick the worst workaround, not the biggest opportunity. The biggest opportunity has the most people involved and the longest road to proof. The worst workaround has a team that will use the thing on day one, and a before and after anybody can see. Maintenance coordination is usually sitting right there.
5. Brief your sponsor in their own words. Find the phrase they already use about this part of the business and hand it back to them. You're not translating your idea into their language. You're showing them something they already believe now has a way to happen.
6. Ask for a commitment, not just a check. Most people skip this and it's the one that holds the case together. Don't ask for approval to spend. Ask for approval to spend, plus a commitment from named teams to build a certain number of things in the first year.

That last one matters more than it looks. A platform is poor value if you build two things and stop. Saying that yourself, before anyone else does, is what makes the rest of your case believable.

What will you get asked?

Seven questions. Knowing who asks each one is half the work.

"What comes out?" Your CFO, and it'll be first. You've got the list. Keep it short and keep it real.

"We already tried this." Usually somebody in IT or data, and this is the one that ends people. It's rarely an argument about the product. It's a reminder that money went into data once before and not much came back. You don't win it with a better answer. You win it by not being the only person in the room who wants this. If operations picked the project, the answer comes from them, not you.

"Why can't we just use Claude or ChatGPT?" Often your CIO, and increasingly your CEO, because they've been using it themselves all year and it's genuinely good. Don't argue with them on that. Travtus runs on those models. This was never a choice between them.

The question is what sits around the model, and there are three things a chat window doesn't have.

• It doesn't know your business, and keeping it knowing your business is the actual work. A chat assistant answers from whatever you paste into it. Knowing what's going on at one community this week, across the work orders, the conversations, the lease and the ledger, kept current, is a data problem and not a prompting problem.
• Nothing starts on its own. A chat window waits for somebody to open it. It won't notice a number moved on Tuesday and go tell the regional who owns that region.
• It's per person, not per company. Everybody builds their own version in their own window. Nothing is versioned, tested, approved, published to a named audience, or scoped to a portfolio, and nobody can see what anybody else built. When they leave, it leaves with them.

If your own team would rather wire a model up to your data themselves, that's a real option and worth pricing. Just go in clear-eyed that you're taking on the pipelines, the permissions and the housing know-how, and you'll own all three forever.

"Why not just buy a leasing AI?" Nearly everybody asks some version of this, and it's fair. Three honest answers.

First, a packaged set of workflows is a fixed set of somebody else's assumptions about your business. You can automate what they built and nothing else, and the work that's particular to how you run is out of scope for good.

Second, none of it is internal, because your own operations aren't that vendor's product.

Third, and this is the one to sit on: the second thing you want to automate is another purchase. On a platform, it's already paid for. That's the whole platform versus point solution question in one line.

Worth mentioning quietly too, that small AI companies in this market have a habit of getting bought by bigger ones, and the product you signed for isn't always the product you end up with.

"Our PMS already has AI agents. Isn't it included?" Bundled looks free. Four questions sort it out.

1. Who owns the logic you build?
2. Who owns the path your resident information travels, and how many companies does it pass through?
3. Who picks the model?
4. Who can change how it behaves - you, today, or somebody else's development list?

Bundled agents also only reach as far as that vendor's own products, and they don't come with you if you ever leave. Those four belong on the shortlist in any enterprise AI platform evaluation, and the first one is really a question about whose data model you're building on.

"My teams won't use it." Your COO, and they're right to ask. Worst workaround first. One team, one region. Make the first thing small enough that it can't fail quietly.

"Another vendor, another security review." Procurement, legal, or IT, usually late and usually the thing that costs you a quarter. Fewer vendors is less to govern. Every extra tool is another agreement, another review, and another company handling resident information. Bring your counsel in early and briefly, rather than late and alarmed.

How Travtus approaches this

Travtus is the everyday AI platform for multifamily. Somebody on your team describes the workflow, report, or score they want, and they build it themselves, in a sentence. It stays yours. It sits on top of the systems you already run instead of replacing them, and it's built for the governance an enterprise actually needs.

A tool that does one job automates that job. A platform changes how the company runs. The budget question is really just a question about which one you're buying, and that is most of what it means to be an AI-native operator.

Before your 2027 budget locks

We put together the one page a CFO will actually read: what the line looks like for your portfolio, what comes out to pay for it, and the questions you'll get asked with the names attached.