Why we started writing in public
Most of the conversations our team has with property managers happen behind a 15-minute Zoom call, then disappear. A question about tour no-shows, a workaround for a PMS that doesn't expose calendars, an objection about AI-drafted messages sounding generic — useful, all of it, and none of it makes it back to the rest of the portfolio managers who would have asked the same thing the day after.
This blog is where we publish those answers, in long form, without a demo CTA at the bottom of every paragraph. Expect field notes from our own portfolio, teardowns of workflows we tried and dropped, and the occasional round-up of what we're seeing across the 200+ unit portfolios we run today.
If a lesson is worth telling one operator, it's worth writing down so the next fifty don't have to ask the same question again.
Lane one — Leasing Ops
Everything that sits between a prospect's first message and a signed lease: inquiry response, tour booking, no-show recovery, and the day-of handoff from your leasing agent to your PMS. The bulk of what we publish lives here, because the bulk of what fills units lives here. Expect case studies of portfolios that cut response time from 4 hours to under 90 seconds, post-mortems of tours we lost for predictable reasons, and tear-downs of inquiry loops we rebuilt after watching real operators run them by hand.
Lane two — AI Automation
Where the model lives, how we keep a manager in the loop on every send, and the trade-offs we accepted to make AI-drafted replies sound like your team instead of a chatbot. This is the lane we go deep on — model selection, prompt design, the review queue UI, and the failure modes we've caught and shipped around. We also publish what didn't work: tone miscalibration, drift after a PMS change, and the one time we shipped a reply that quoted a unit we don't manage.
Lane three — PM Productivity
The broader shape of a property manager's day once the inquiry loop is automated: where the saved hours actually go, what the team picks up next, and the dashboard patterns we've seen correlate with retained residents. Tied to leasing ops but aimed at the portfolio and operations leaders who don't answer inquiries — the people whose Monday morning looks different after a layer like Fillment ships. Expect pieces on weekly review cadence, manager-to-leasing-agent ratios, and what to ask when you evaluate any AI tool for this layer of the stack.
How to publish into this lane
Every post is a static route at /blog/<slug>, declared in this file. To add a post: write a new entry in POSTS_RAW, drop a new folder under src/app/blog/<slug>/, and the rest of the page — header, byline, read time, JSON-LD, sitemap entry, route metadata — gets wired automatically from the post's frontmatter-style fields. No CMS, no API, no DB; the build reads these rows and emits a fully prerendered route for each one.