Video summary
10 Things You NEED as a DIY Landlord (Self-Managing Rental Properties)
Main summary
Key takeaways
Business-focused summary: 10 essential systems & tools for DIY/self-managing landlords
1) Property management software (PMS) to run operations + reduce errors
What it replaces: manual tracking (e.g., paper checkmarks) and scattered communication. Why it matters: creates accurate records for rent/ledger disputes, centralizes messaging, and automates guest/work-order workflows.
Key use cases mentioned (long-, short-, mid-term):
- Rent tracking + payment verification (reduces disputes; provides an audit trail)
- Guest communication: unified inbox across multiple booking platforms
- Messaging: SMS/email/platform messages through the PMS
- Vendor/cleaning notifications & turn management: cleaners flagged issues during turnovers
- Calendar blocking / booking synchronization: e.g., block Airbnb dates on another channel (Verbbo mentioned)
- Maintenance + inventory workflow (via integration and/or within the PMS)
Software examples (no endorsements; based on personal use/hearsay):
- Long-term: AppFolio, Buildium (not cost-effective at 1–2 units; “makes sense at scale,” ~50 units cited)
- Long-term basics: RentReady, TurboTenant
- Short-term / mid-term: Hospitable, Guesty (more features; higher cost), Hostfully
- Mid-term approach mentioned: often handled via the short-term toolset unless using dedicated mid-term platforms (Furnished Finder mentioned as “possibly building”)
Framework / scaling principle implied:
- Invest in tooling only when unit count supports ROI (threshold described: ~$400/mo minimum for some platforms; 1–2 units can harm cash flow).
2) Maintenance & back-of-house cleaning software (beyond PMS)
Purpose: operational execution for cleaning tasks, checklists, inventory, and maintenance workflows.
Examples mentioned:
- Breezeway (separate “back of house operations” once portfolio is large)
- Turno (integrates with Hostfully; described as similar functionality)
3) Reliable vendor list + relationships (mini procurement system)
Objective: eliminate panic when repairs are needed; ensure fast response and pricing consistency.
How to structure it (example process):
- Maintain multiple lists, including:
- Preferred vendor(s) (e.g., go-to plumber/HVAC)
- Backup/referral vendors
- “Sourcing” list from local discoveries (e.g., capture truck info/photo)
- Track per vendor:
- Contact info
- Whether they were used
- Outcome / quality
- Whether you’d use them again
- Include service availability windows (e.g., 24/7 vs weekday hours)
- Account for practical constraints (e.g., a “mom & pop” vendor requiring house phone scheduling, not weekends)
Actionable recommendation:
- Build the list via Google/Facebook groups and investor referrals—tradespeople are more shareable than wholesaler-style deals.
Relationship-based operating rule:
- Don’t obsess over “pennies and nickels” if paying a bit more protects long-term consistency and goodwill (win-win ripple effect across tenants/guests + vendors).
4) Dedicated landlord contact number (routing + boundaries)
Goal: centralize calls/messages so tenants/vendors can reach you without disrupting personal life or losing control of responsiveness.
Examples mentioned:
- Google Voice (often free with Gmail; dedicated number)
- OpenPhone (more robust for call routing; routes calls to a VA first; has call recording/training potential)
Operations detail emphasized:
- Visibility into call/text volume, voicemails, answer rates, and response timeliness (leadership oversight).
5) Virtual mailbox (reduce admin chaos; improve financial control)
Problem solved: physical mail sorting, check writing, frequent missed mail, and outsourcing cost.
Operational workflow described:
- Mail sent to virtual mailbox location
- Provider scans envelope exterior; landlord receives images in a dashboard/portal
- Landlord/VA selects:
- What to open
- What to shred
- What to forward
- Physical check flow still exists for some tenants:
- Checks forwarded to home
- Landlord deposits and uploads/organizes bills
Why it’s a business system:
- Automates visibility + routing of documents
- Reduces time spent on admin tasks
- Supports a VA-driven mail processing process (with a decision spreadsheet/rules)
Cost expectations (ranges given):
- Roughly ~$200–$300/year for simpler plans; higher for scan/open volume and multi-LLC setups
- Example plan target: ~$300/year (~$25/month)
Example provider mentioned:
- PostScan Mail (chosen for multiple LLCs under one mailbox without extra high fees)
6) Organized file storage (Google Drive as the “source of truth backup”)
Problem solved: risk of being locked into a single property/project management system and losing access later.
Recommended operating practice:
- Store documents in Google Drive (receipts, notices, leases, closing docs, surveys, etc.)
- Use a consistent folder structure:
- By entity (LLC) and property (varies by speaker/team)
- Use property/project management tools only as indexes/links to Drive files
Risk mitigation described:
- Avoid “data trapped inside software” (e.g., manual downloading during migration).
7) Unit information sheet (“one-pager” property knowledge base)
Purpose: operational continuity—faster troubleshooting and handoffs when you’re remote or when issues require immediate answers.
What to include:
- Purchase/closing documents & IDs (parcel number, escrow/settlement docs)
- Rental compliance: permits + expiration dates
- Property facts: bedrooms/bathrooms/sq ft
- Utility info and where shutoffs are
- Location guides: electrical panel, propane tanks, lockbox locations
- Media: video walkthroughs (interior/exterior)
- Turn-critical admin: trash day schedule, Airbnb profile linkage
Concrete example:
- A vendor couldn’t proceed because they needed the water shutoff location—the property sheet prevents delay and repeat confusion.
8) Emergency fund / reserves + reinvestment fund (cash discipline)
Rookie mistake called out: treating projected cash flow as profit rather than setting aside reserves.
Targets/timelines:
- Aim for 3–6 months of reserves at purchase (if feasible)
- Reserves cover:
- Repairs
- Vacancies
- Unexpected costs
Implementation approach:
- Store in high-yield savings (Baselane, Wealthfront mentioned)
- Or use business banking reserves (Relay mentioned; ~3.5% mentioned)
Portfolio accounting tactic (short-term focus):
- Keep reserves per property (especially with multiple partners so cash can’t be reallocated across deals)
Additional fund for short-term rentals: reinvestment budget
- Set aside money monthly to improve amenities/experience and protect competitiveness
- Examples: gaming consoles, redesigns, amenity additions (sauna, mini golf)
- Reasoning: guests/occupancy and nightly rates benefit from continuous upkeep (example cited: a Cancun resort always improving small details)
9) Insurance + legal protection (strategy-specific coverage)
Execution points:
- Ensure correct policy type:
- Homeowner policy ≠ landlord policy
- Short-term rental policies often differ in coverage due to guest volume/risk
- Don’t accept quotes blindly:
- Ask agent to walk through what’s covered, deductibles, and exclusions
Operational insurance hygiene:
- Reshop annually to find better rates; don’t “set and forget.”
Short-term rental coverage add-ons mentioned:
- Bed bug coverage
- Lost rents
- Squatter coverage and evictions
- Liquor liability
- Animal/pet liability
- Hot tub/pool amenities liability
- Assault and battery
Governance recommendation:
- Be transparent with insurers about what you do/provide (example risk: hidden wood-burning stove coverage gap in due diligence).
10) Communication boundaries + proactive self-service to reduce burnout
Core principle: define what counts as an emergency and limit constant inbound communication.
System described:
- Most requests become work orders inside the PMS (not direct interruptions at 1–2am)
- Guests/tenants get answers through:
- Digital guidebooks
- On-property signage
- Automated messaging windows (availability ranges)
Concrete short-term example:
- Problem: guests couldn’t see keypad instructions at night, pressed buttons incorrectly, and locked themselves out.
- Fixes:
- Add solar light above the door handle to illuminate keypad
- Add placard with written instructions + QR code linking to a video in the guidebook
- Outcome aim: reduce call volume by fixing root causes and trends.
Scaling beyond DIY (systems + capital + checklists)
Recommended scaling levers
- Build systems/processes from day one (checklists, SOPs)
- Maintain reserves/capital so you can outsource/automate without cash anxiety
Operational delegation examples mentioned
- Hiring property managers (outsourcing ops/asset management)
- Using part-time VAs (5–10 hours/week) for admin tasks
- Creating SOP checklists so tasks run repeatably:
- Example: acquisition setup checklist (utilities switch, insurance setup, tenant handbook creation, listing tasks, etc.)
Frameworks explicitly referenced
- Checklist Manifesto (Atul Gawande) — checklists reduce failure
- Clockwork (Mike Mallowitz) — apply checklist/SOP thinking to small businesses
- Top-down vs bottom-up scaling model:
- Top-down: VC-funded, build entire team, salaried structure, runway-based
- Bottom-up: operator builds systems while “being the team,” then hires for roles over time based on highest leverage tasks
Key metrics / KPI targets mentioned
- Cash reserve target: 3–6 months at purchase (if feasible)
- Tooling cost expectations:
- PMS like AppFolio/Buildium: ~$400/month minimum (implied affordability threshold)
- Virtual mailbox: ~$200–$300/year (scan/open tiers can increase)
- Insurance & interest-rate examples (illustrative, not universal):
- Relay reserves account: mentioned ~3.5% (vs >4% higher-yield accounts)
- Call volume / response oversight metrics (qualitative):
- Track incoming calls, answered vs missed, voicemail counts, callback timeliness, and text content (no numeric targets given)
Presenters / sources
- Ashley Care
- Tony J. Robinson
- Podcast: Real Estate Rookie (BiggerPockets Rookie referenced)
- Mentioned authors/books:
- Atul Gawande (The Checklist Manifesto)
- Mike Mallowitz (Clockwork)