Email me
AI automation for property management companies

Your buildings, running like you hired three more people.

Resident questions answered, violations enforced, invoices generated, leads booked — automated on top of the software you already use, with your staff keeping final approval.

Everything happens in writing — you'll get a concrete plan back, not a sales call.

Minutes, not days

Residents and leads get answers while your competitors' emails sit unread.

Nothing slips

Fines tracked until paid, deadlines surfaced, follow-ups sent without reminders.

On your stack

Runs on top of Yardi, Buildium, AppFolio, QuickBooks — nothing to migrate.

Services

Four systems that carry the heaviest work

If a process is repetitive and follows rules, it's a candidate. These four are where property managers lose the most hours — and the most money.

"Where's the water shutoff?"
Drafted from your building manual → approved → sent.

Resident questions

An assistant trained on your building documentation handles the questions your managers repeat all day — HVAC, plumbing, electrical, fire safety. It drafts, your staff approves, it goes out. Your team stops being a search engine.

See how it works →
Photo in → letter out.
Checked against house rules, fine applied, tracked to payment.

Violations & fines

A photo or video gets checked against your house rules. The system drafts the violation letter, applies your fine schedule, and tracks the fine until it's paid — late penalties included. Most portfolios quietly write this money off.

See how it works →
Tenant films it. System files it.
Timestamped, checked, attached to the unit.

Move-in / move-out records

Tenants record a short guided video at move-in and move-out. No inspector visit for every turnover — and when a deposit dispute comes up, you hold dated footage instead of "we think we have photos somewhere."

See how it works →
Readings in → invoices out.
Per-unit charges, ready to send.

Utility billing

Meter readings go in; per-unit charges and ready-to-send invoices come out. No spreadsheet step in the middle — which is exactly where the errors and the angry tenant calls come from.

See how it works →

…and the rest of the office

Leasing leadsListing inquiries answered in minutes, qualified, showing booked into your calendar.
Maintenance requestsClassified by urgency and trade, routed to the right contractor, escalated when stuck.
Rent & late feesReminders, automatic late-fee application, polite escalation — no manager memory required.
Leases & documentsDates, amounts and clauses extracted; renewal windows surface before they're problems.
Owner reportingMonthly reports assembled from your software's data — same day every month.
Internal tools & databasesCustom apps and dashboards for what lives in spreadsheets today — inspections, vendors, approvals.

Don't see your process here? If it's repetitive and it follows rules, it can probably be automated — ask me.

Process

How it works

1

You describe the process

In plain words, by email. What happens today, who does it, where it hurts. No preparation needed on your side.

2

You get a concrete plan

What gets automated, what stays human, what it connects to, timeline and cost. In writing, so you can forward it internally and decide without a meeting.

3

I build it on your stack

The automation runs on top of the software you already use. Your staff keeps approval control over anything that reaches a tenant or an owner.

Built with: Make, n8n, Claude API  ·  Works alongside: Yardi, Buildium, AppFolio, QuickBooks, Google Workspace, Outlook, and most tools with an API.

Principles

Built to run every day, not to impress once

Staff stays in control

Anything tenant-facing goes out only after your team approves it — until you decide it no longer needs to.

Your data stays yours

Everything runs in your accounts — your email, your software, your storage. Nothing lives on my servers.

Nothing to migrate

Automation sits on top of your property management software. You keep your systems, your records, your workflows.

Monitored, with fallbacks

Error alerts, retry logic, and a clear fallback to manual — a failed run is a notification, not a surprise a week later.

About

Who you'd be working with

OS

I'm Oleksandr Shylo, an AI automation engineer. I build working automations for property management, e-commerce, and service businesses — systems that run daily in production, handling real residents, real invoices, and real deadlines.

I work in writing. Describe your situation in an email and you'll get back a specific plan — what to automate first, what it takes, what it costs. If it's not a fit, I'll say so and you'll have lost five minutes.

What eats your team's time?

Send two or three sentences about the most annoying repetitive process in your office. You'll get a concrete answer, not a pitch deck.

Email me

or write directly: shulkyn@gmail.com