EliseAI raises $350 million to automate more of the leasing office and the clinic front desk

In EliseAI's version of a leasing office, a prospect who tours a unit gets a follow-up from the Apollo assistant, and a manager who wants the average cost of open repair jobs asks the same assistant ^[7]. Apollo launched earlier this month ^[7].

Apollo is marketed as a teammate, but for a property team the practical question is where it sits. "It's built natively into the same platform that already runs leasing, maintenance, and renewals," co-founder and CEO Minna Song told TechCrunch. "So it can act across every role on a property team." ^[8] That platform includes the CRM where property managers store prospect data ^[4] and the app that picks a technician for each repair job by availability and skill ^[5]. In housing, EliseAI's own software holds the record ^[4].

Healthcare is set up differently. There the software ingests patient documents and syncs key information into the provider's electronic health record ^[10], so the record stays in a system the clinic already runs. Song described the scope for specialty physician groups as running "from the first inbound call through referrals, scheduling, insurance verification, chart prep, and follow-up, so nothing falls through the cracks" ^[11].

Here's what teams tell themselves users do with an assistant: ask it questions all day, with the question count standing in for value. Here's what customers have actually paid for. EliseAI reported passing $200 million in annual recurring revenue this summer ^[12], before Apollo launched ^[7]. Whatever the assistant adds, that revenue was earned without it. Neither report includes retention figures or a count of customers who use more than one module.

The new price assumes those customers buy more. Investors led by Andreessen Horowitz and Bessemer ^[2] paid $4 billion ^[1] for a company with a little over $200 million in ARR ^[12]. The multiple is at most about 20 times recurring revenue ^[17]; the valuation was roughly $2 billion at the Series E last August ^[18]. The money goes to more automation features and to hiring engineers, software deployment staff and salespeople ^[16]. Song wrote that these industries "won't absorb this technology without a tremendous act of building" ^[13]. For a customer, much of that building will arrive as a deployment team and a sales team bringing the next module ^[16].

Any EliseAI module can be sorted on two questions: whose system holds the record while it runs, and whether it does one task or the whole chain. The appointment chatbot is one task ^[9], and on the healthcare side the records sync into the clinic's own EHR ^[10], so it is cheap to trial and cheap to drop. Intake from first call through follow-up is the whole chain on the customer's record ^[11], and the measure there is staff hours returned in the first quarter. Marketing emails generated from EliseAI's CRM are one task on the vendor's record ^[4]. Leasing CRM, maintenance dispatch and Apollo together are the whole chain on the vendor's record ^[8]. In that cell, switching costs sit with the customer and renewal leverage sits with EliseAI.

I'd expand freely in the first two cells and get data-export terms in writing before moving into the last one. The tradeoff is that Apollo's reach across every role, the feature Song is selling, depends on the customer living in that last cell ^[8].