YEAR ONE

I scrapped the original Episode 3. Here's why.We had it recorded — a clean explanation of the process framework we were using to rebuild Northpoint. Then I looked at what was actually happening with our team and realized a lot of what we thought was working... wasn't.This episode is about what we changed.We stopped trying to design processes from a desk and started putting the right people in the room. We built cross-functional work groups — small teams of subject matter experts assembled around a specific process, facilitated by our Operations Enablement team. And we stumbled into something called Discovery Day — where we watch teammates actually use their tools instead of just asking them to describe what they do. The gap between those two things was eye-opening.In this episode: — Why top-down process design failed us — What Discovery Day is and what it revealed — How we structure cross-functional work groups (owner + SMEs) — The role of Operations Enablement: not training, not a help desk — The three-meeting arc: deconstruction → reassembly → documentation — What you can do Monday morning without a dedicated OE teamYear One is a build-in-public series documenting the operational transformation of Northpoint Asset Management — a national single-family rental operator managing 5,300+ homes. New episodes bi-weekly.

When I arrived at Northpoint, we had 14 different software tools in use—PropertyMeld for maintenance, zInspector for inspections, Findigs for screening, Google Sheets for the leasing pipeline, DocuSign for leases, QuickBooks for financials, and more. AppFolio was technically our property management system, but functionally it was almost an afterthought.This episode explains why we're consolidating down to AppFolio as our core operating system, what we're giving up to do it, and how you can evaluate whether consolidation makes sense for your operation.Key Topics & Timestamps[00:00] Cold Open — The SwiftBunny survey: when teams use 10, 20, or 30+ tools[02:00] Why Consolidation Matters — The real cost isn't subscription fees. It's cognitive load.[04:17] Why Integrations Don't Solve It — Shared visibility isn't shared data, and why that matters for AI[05:17] The Lesson from RPM Living — What I learned scaling from 400 to 16,000 units in one system[07:14] The Starting Point — Painting the picture of 14 disconnected tools[09:33] The Forcing Function — Specific operational problems that pushed us toward consolidation[13:06] Tool-by-Tool BreakdownPropertyMeld → AppFolio (14:01)Google Sheets → AppFolio + ClickUp (16:44)Findigs → AppFolio (18:47)zInspector, Contractor+, DocuSign, QuickBooks (20:21)[23:47] The ClickUp Question — Why we're adding a tool while consolidating everything else[26:18] Change Resistance — The hard part of transformation that doesn't get talked about[27:51] Risks and Tradeoffs — Lock-in risk, innovation risk, integration constraints[30:43] Where We Are Now — Current state of the transition[32:21] Early Results — Wins and the challenge of change fatigue[34:56] Framework for Your Stack — 7 questions to evaluate your own tech stack[39:14] Outro — What's next in Episode 3Key TakeawaysCognitive load is the hidden cost. When your team spends mental energy navigating software instead of solving problems, you're paying a tax that never shows up on a P&L.Integration means shared visibility, not shared data. Your team still learns eight interfaces. Your data still lives in different structures. And that matters more than ever as AI tools need unified data to work effectively.A tool is only as useful as the skilled hand that wields it. Best-in-class features don't help if your team isn't trained to extract value from them. Sometimes 80% of functionality in one place beats 100% spread across eight.Resistance comes before learning, not after. People look at an unfamiliar interface, feel discomfort, and conclude the tool is the problem. That's not a tool problem—that's a change problem.Your goal isn't the best tools. Your goal is the best outcomes. Sometimes that means fewer, simpler tools used more deeply.Framework: 7 Questions to Evaluate Your Tech StackCount your tools. How many systems does your team touch in a typical week?Map the handoffs. Every arrow between systems is a place where things can break.Audit your PMS utilization. What percentage of your core system are you actually using?Calculate the real cost. Training time, error rates, cognitive load—not just subscriptions.Can you actually manage performance? Can you see how your team is doing before outcomes go bad?What's the minimum viable stack? If you started from scratch, what would you actually need?Accept tradeoffs. You're not getting best-in-class everything. Decide when the gap matters.Tools MentionedAppFolio (core PMS)PropertyMeld (maintenance coordination)zInspector (inspections)Contractor+ (vendor bid management)Findigs (screening)DocuSign (e-signatures)QuickBooks (accounting)Google SheetsClickUp (work management)Power BI (reporting)ConnectLinkedIn: Steven ReaCompany: Northpoint Asset ManagementNext EpisodeEpisode 3: First Principles for Operator Technology Dropping February 9, 2026Why process comes before technology. Why AI won't save a broken system. Why most operators get the sequence backwards and pay for it later. The intellectual framework guiding every decision we make.

When Steven Rea joined Northpoint Asset Management as Chief Innovation Officer, he asked a simple question on Day 1: "How do we track our leasing pipeline?"The answer wasn't a CRM or a specialized SFR platform. It was a Google Sheet.In this debut episode of Year One, Steven pulls back the curtain on the reality of modernizing a legacy Single Family Rental (SFR) operator. This isn't a story about incompetence; it's a story about how versatile tools like spreadsheets evolve from helpful bridges into permanent crutches that silo knowledge and create friction.Steven introduces the concept of the "20-Year Startup"—a company that has successfully achieved scale over two decades, but whose systems never evolved past the "hero mode" of Day 1. He also shares a candid look at his first major mistake: a "perfect" automation workflow that nearly locked residents out of their payment portals.In this episode, we cover:The "Shadow IT" Reality: How spreadsheets become the de facto operating system in SFR when core platforms don't fully fit.The "20-Year Startup": Defining the unique pain of a company that scales its revenue but not its foundation.The High Cost of Tribal Knowledge: Why "local ways" of doing things make accountability impossible.The Automation Trap: A transparent look at an 11:50 PM launch that threatened to break trust with residents, and the lesson learned about human oversight.The Bias for Action: Why waiting for perfect conditions is just a slower way to fail.Timestamps(00:00) - The "Google Sheet" Reality Check.(01:21) - Defining the "20-Year Startup."(03:17) - The hidden cost of "Tribal Knowledge" vs. Documentation.(05:19) - Why you can't have accountability without defined standards.(06:56) - Failure Story: The 11:50 PM Collections automation mistake.(09:06) - The Real Lesson: Why you have to pilot before you fix.(10:30) - Teaser: The Consolidation Decision.Quote of the Episode"The scary part wasn't the spreadsheet. The scary part was that everyone thought it was normal. That moment told me everything I needed to know."About the ShowYear One is a documentary series following the digital transformation of Northpoint Asset Management. Hosted by Steven Ray, CINO, it offers an unvarnished look at the strategies, failures, and breakthroughs involved in rebuilding a national SFR operator from first principles.