Skip to main content
VSI Technologies

Tenant service that does not wake anyone up.

Portfolio operations, tenant service and the reporting underneath both.

Industry overview

Inside a real estate operation

Tenant requests arrive at all hours through every channel anyone has ever published. They get triaged by whoever is available, tracked in whatever they use, and reported on monthly by someone rebuilding a spreadsheet. Portfolio performance is knowable in principle and unavailable in practice.

Property operations run on relationships and improvisation, and both work until the portfolio gets big enough that nobody holds the whole picture. Requests arrive by phone, email, text, a portal somebody set up, and occasionally by stopping a member of staff in a lobby. Each channel has a different record, and the aggregate is that nobody can say how many open requests exist across the portfolio.

After-hours is where this is felt most sharply. A leak at eleven at night reaches whoever answers, and what happens next depends on their judgement and their contact list. Sometimes that produces an excellent outcome. It is never repeatable, and it is entirely dependent on individuals who cannot be on call permanently.

Lease administration is a slow-motion version of the same problem. Critical dates, renewals, breaks, rent reviews, options, live in the leases, are abstracted into a system at varying quality, and are actioned when somebody notices. A missed option date is a direct financial loss that appears as nothing at all until it is too late to act.

Vendor coordination is where the time goes. Dispatching a contractor, confirming they attended, confirming the work was done, and closing the loop with the tenant is four exchanges per request, done by phone, by a person whose time is worth more than the coordination.

And reporting sits on top, rebuilt monthly by hand from the operating systems, arriving too late in the cycle to change anything about the month it describes.

Common challenges

Challenges we see across real estate

If three or more are true, the rest of this page is about your operation.

  • Nobody can say how many open tenant requests exist across the portfolio
  • After-hours outcomes depend on who happened to answer
  • Critical lease dates are actioned when somebody notices them
  • Closing the loop with a tenant takes four phone calls
  • Portfolio reporting is rebuilt in a spreadsheet each month
  • A tenant’s experience varies noticeably by property

How we help

Five practices, applied to real estate

AI, cloud, cybersecurity, hardware and programme delivery, one integrated bench, each practice applied to how real estate actually operates.

  1. Agents for the portfolio’s daily churn: maintenance-request intake and dispatch in Yardi or AppFolio, lease-abstraction into the data your asset managers actually query, renewal and delinquency outreach on schedule, and vendor-invoice matching against work orders before payment.

  2. One data plane across an acquired portfolio: property systems consolidated or integrated after each acquisition, building-system feeds landed where asset management can see them, and reporting that survives the next property-management-system migration.

  3. Controls for a business that moves deposits and rent: payment-redirection defences on the accounts-payable path, tenant-data protection aligned to state privacy laws, and access management across the high-turnover site-staff population.

  4. Site and leasing-office technology as a managed fleet: leasing kiosks, site-office workstations, smart-building gateways, deployed per property spec, monitored centrally, replaced on lifecycle rather than after the leasing weekend they fail.

  5. Technology transitions run against real-estate deadlines: PMS migrations cut over between billing cycles, acquisition onboarding done to a repeatable playbook, and capital-project technology scoped before the GC mobilises.

Where we start

Automation candidates

Deliberately mundane. The impressive-sounding workflow is rarely the one worth doing first.

  • Tenant requests: intake across channels, triage and dispatch
  • After-hours coverage without an after-hours team
  • Lease abstraction and critical-date tracking
  • Vendor coordination and work-order follow-up
  • Portfolio reporting from the operating systems rather than by hand

Systems we integrate with here

If you run one of these, this is the conversation.

  • Yardi
  • MRI Software
  • AppFolio
  • Salesforce
  • Procore

Our solutions

How we transform real estate operations

What happens today, what changes, and what to watch for as each workflow is automated.

Tenant request intake

Today
Requests arrive through every channel anyone has ever published, get recorded inconsistently, and are triaged by whoever is available.
After
Every channel lands in one record with the same structure, triaged by category and urgency against defined rules, and dispatched to the right vendor or person with the property context attached.
What to watch
Emergency categories, anything involving safety, water, gas, electricity or access, bypass triage and reach a person immediately. The classifier must fail toward emergency, not away from it.

After-hours coverage

Today
Whoever answers uses their judgement and their contact list. Outcomes are good and unrepeatable.
After
Every call answered, routine matters handled and logged, urgent matters dispatched against the defined escalation, and genuine emergencies reaching a named person immediately.
What to watch
A tenant in genuine distress must not be processed. The escalation has to be fast, obvious, and available at any point in the interaction without navigating a menu.

Lease abstraction and critical dates

Today
Leases abstracted at variable quality, critical dates tracked in whatever system, and actioned when noticed.
After
Abstraction with the source clause cited for every extracted term, and critical dates tracked with notice periods worked backwards so the action window is flagged rather than the date.
What to watch
Every abstracted term cites its clause. An abstraction the asset manager cannot verify against the lease is one they will re-read, which removes the point of it.

Vendor coordination

Today
Four exchanges per request by phone, done by someone whose time is worth more than the coordination.
After
Dispatch, attendance confirmation, completion confirmation and tenant notification handled automatically, with exceptions, no-shows, disputes, repeat visits, raised to a person.
What to watch
Vendor relationships are local and matter. Communication that reads as automated chasing damages relationships with the contractors you depend on at short notice.

Portfolio reporting

Today
Rebuilt monthly by hand, arriving after the period it describes.
After
Assembled from the operating systems on a schedule, with the same definitions across properties, early enough to be acted on.
What to watch
Property-level idiosyncrasies are real, different service charge structures, different lease types. Flattening them for reporting convenience produces a comparable number that is wrong.

The operating picture

Where the agent layer sits in the lease lifecycle

Your operating loop todayThe agent layer we deploy into it
01

Market and lease

Enquiries, tours and applications compete for leasing-agent hours.

Agent layer

Answers availability questions, schedules tours, and assembles complete application files for decision.

02

Operate

Maintenance requests, vendor dispatch and rent collection never stop.

Agent layer

Triages requests by urgency and trade, dispatches per your vendor rules, and follows up to confirmed completion.

03

Account

Invoices, CAM reconciliations and owner reporting stack up monthly.

Agent layer

Matches invoices to work orders, drafts owner packages from live ledger data, and flags the variances.

04

Renew

Expirations arrive silently and vacancy is the most expensive outcome.

Agent layer

Surfaces every expiration on your notice calendar and runs the outreach sequence your team defined.

The loop every unit and every suite runs: market, lease, operate, renew. Agents carry the coordination and the paperwork; pricing decisions and fair-housing-sensitive judgements stay with your team, inside your policies.

Platforms and systems

Technology we work with in real estate

The systems of record this sector runs on, and why each one matters to a deployment.

Yardi
Property management of record across much of commercial and multifamily. The work-order model is what dispatch has to align to.
MRI Software
Common in commercial portfolios, with a lease administration model that shapes critical-date handling.
AppFolio
Frequent in residential and smaller commercial portfolios, where tenant communication volume is highest.
Salesforce
Where tenant and prospect relationships are managed when they are managed deliberately.
Procore
Construction and capital projects, which is where the larger vendor coordination lives.

The constraint

What makes this sector harder

Property operations are local and relationship-led, and a tenant who feels processed is a tenant who does not renew. The automation belongs on the routing, the tracking and the chasing, not on the conversation that decides whether somebody stays.

Renewal is the economics of this sector and it is decided by accumulated experience rather than by any single interaction. A tenant who felt attended to renews; a tenant who felt processed shops the market. That makes tone a commercial variable rather than a nicety, and it argues for automating everything around the conversation while leaving the conversation itself to a person who knows the property.

Emergencies are the specific case where automation can do real harm. Water, gas, electrical, access, and anything involving personal safety must reach a person immediately, and the classification has to be biased heavily toward emergency. Being wrong in the safe direction costs a call; being wrong in the other direction costs something that does not get repaired by an apology.

Properties differ more than portfolio-level thinking assumes. Service charge structures, lease types, local vendor markets, building systems, and the individual arrangements that accumulate over years. A design that standardises these away produces reporting that is comparable and inaccurate, which is worse than reporting that is honest about the differences.

And the vendor market is a relationship you depend on at short notice. The contractor who comes out at midnight does so partly because of a relationship with a named person at your firm. Automated coordination that feels like chasing puts that at risk, and the value of a good contractor on a bad night substantially exceeds the coordination time saved.

A high-rise under construction with two tower cranes above it.

Compliance

Compliance that shapes real estate deployments

The regimes your organisation operates under, and what each one constrains in a deployment. We design to these from the first architecture diagram, they describe your obligations rather than our credentials, and VSI's own position publishes only once it is substantiated.

Habitability and repair obligations
Certain repair categories carry legal timeframes. Triage has to recognise them and escalate rather than queue them.
Fair housing considerations
Anything touching applicant or tenant treatment must be consistent and inspectable. Automated handling has to be uniform by category, never by person.
Lease terms and notice periods
Critical dates need the notice period worked backwards, because the actionable window closes before the date does.
Building safety records
Inspection and certification records have retention obligations and are evidence. They are maintained rather than reconstructed.

How we work with public-sector and regulated buyers

Success stories

The track record behind the practice

Published engagements from adjacent sectors carry the same disciplines, programme governance, systems integration, workflow automation, that a real estate deployment draws on. Every figure publishes under a named attestation.

Browse the case-study library

The first month

What starting looks like

What actually happens, week by week. Note where the design conversations sit, before the build, not after it.

  1. 01Week 1

    Request volume by channel, category and hour across the portfolio, usually the first time anyone has seen the whole picture in one place

    Request volume by channel, category and hour across the portfolio, usually the first time anyone has seen the whole picture in one place.

  2. 02Week 2

    Emergency taxonomy and escalation with property management: exactly what bypasses triage, and how fast it reaches a named person

    Emergency taxonomy and escalation with property management: exactly what bypasses triage, and how fast it reaches a named person.

  3. 03Weeks 3-4

    Unified intake across channels at one or two properties, with after-hours coverage live and every interaction reviewed daily

    Unified intake across channels at one or two properties, with after-hours coverage live and every interaction reviewed daily.

  4. 04End of month

    Reviewed against the week-one picture, with tenant feedback taken directly rather than inferred, before widening

    Reviewed against the week-one picture, with tenant feedback taken directly rather than inferred, before widening.

Next step

A free 20-minute real estate assessment

Portfolio operations, tenant service and the reporting underneath both.

No preparation required and nothing to install. Bring the workflow that costs you the most hours; leave with a view of what we would automate first, what it depends on, and what we would not touch.

Book the free assessment

Questions

Asked often enough to answer here

What happens if a tenant has an emergency at two in the morning?
It reaches a person immediately. Emergency categories, water, gas, electrical, access, anything involving personal safety, bypass triage entirely, and a tenant can reach a human at any point in the interaction without navigating a menu. The classifier is deliberately biased toward emergency: being wrong in that direction costs a phone call, and being wrong in the other direction costs something an apology does not fix.
Will tenants feel like they are dealing with a machine?
For logging a routine request they are, and it should be obvious rather than disguised, most tenants prefer a request logged at eleven at night to a voicemail nobody hears until morning. What stays human is the conversation that decides whether somebody renews. Automating the routing, the tracking and the chasing while leaving that conversation alone is the whole design.
Does this replace our property managers?
No, and a portfolio owner who tries it will find out why the hard way. The relationship with an on-site manager is a substantial part of what a tenant is paying for. What this removes is the coordination overhead, the four phone calls to dispatch, confirm, verify and close a work order, which is the part of a property manager’s week that produces no relationship value at all.
How does lease abstraction avoid getting terms wrong?
Every extracted term cites the clause it came from, so verification is one click rather than a re-read. Abstraction is proposed rather than authoritative, and an asset manager confirms anything with financial consequence. The value is in never missing a critical date, and the design tracks the notice period rather than the date itself, the actionable window closes before the date does.
Can you start at one property?
Yes, and you should. Properties differ more than portfolio-level thinking assumes, service charge structures, lease types, local vendor markets, and years of individual arrangements. Proving the pattern at one property before widening is both lower risk and a considerably easier internal conversation.
What about our vendors and contractors?
They get coordinated, not chased. The distinction matters commercially: the contractor who comes out at midnight does so partly because of a relationship with a named person at your firm, and automated communication that reads as pursuit puts that at risk. Exceptions, no-shows, disputes, repeat visits, go to a person precisely because those are the conversations where the relationship is at stake.