People & HR

How to onboard a new hire as Property Management Founders

People & HRFor Property Management Founders3 apps11 steps~22 min to set up

When you hire a new leasing agent, maintenance coordinator, or property manager at a sub-500-door firm, onboarding lives in your head. You spend the first two weeks answering the same questions: which vendor do we call for HVAC in the Riverside portfolio, how do we log a work order in AppFolio, what's the late-fee policy for month-to-month tenants, where's the owner statement template. There's no wiki. The 'training doc' is a Google Doc nobody's updated since 2023. New hires shadow you for days because the knowledge isn't written down anywhere, which means you're pulled off owner calls and inspections to babysit orientation. By week three they're still emailing you things they should already know.

Build this on Starch → See the apps used

People & HRFor Property Management Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A searchable team wiki built from your actual processes — lease renewal timelines, vendor lists, AppFolio workflows, owner communication standards — so new hires get answers without interrupting you

An automated new-hire task checklist that assigns system access steps, training reads, and first-week milestones with due dates and overdue alerts, tracked in one place

An email triage setup so new hires can manage their own inboxes from day one, with priority filters tuned to tenant, owner, and vendor message types common in property management

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Knowledge Management Task Manager Email Agent

Data sources & config

Knowledge Management connects to Notion (Starch syncs your Notion pages and databases on a schedule) to pull any existing SOPs or vendor docs you've already stored there. Task Manager runs standalone with no external integration required — tasks are captured via chat or manually entered. Email Triage (Email Agent) connects to Gmail (Starch syncs your Gmail on a schedule, including labels and message threads) and to Outlook if your new hire is on Microsoft. AppFolio and Buildium are automated through your browser — no API needed — so Starch can pull unit rosters, vendor records, and work order logs to populate wiki entries and task context without you retyping them.

Prompts to copy

Build me a property management onboarding wiki with sections for: AppFolio work order workflow, our preferred vendor list by trade and property area, late fee and delinquency policy, owner statement schedule and format, lease renewal checklist, and emergency contact escalation tree

Create an onboarding task list for a new leasing agent with P1–P4 priorities: P1 tasks are system access (AppFolio login, Gmail, Slack), P2 tasks are policy reads with due dates in the first 3 days, P3 tasks are shadowing sessions in week one, P4 tasks are solo-run work orders by end of week two — flag anything overdue

Set up my new hire's email triage so messages from tenants in AppFolio-linked addresses are flagged high priority, owner emails are summarized and queued for same-day reply, and vendor invoices are tagged for review — draft replies for anything that matches our standard maintenance acknowledgment or rent reminder templates

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Before the hire's first day, open Knowledge Management and type: 'Build me an onboarding wiki for a new property management leasing agent.' Starch scaffolds sections automatically — you fill in or paste your actual policies, vendor contacts, and AppFolio navigation steps.

2 Connect Notion from Starch's integration catalog if you store any existing SOPs there; Starch syncs your Notion databases on a schedule and surfaces that content inside the wiki so nothing is duplicated.

3 Use browser automation to pull your vendor roster and preferred-vendor list directly from AppFolio or Buildium — Starch automates the login and export through your browser, no API needed — and load that data into the Vendors section of your wiki.

4 Open Task Manager and type: 'Create a new-hire onboarding checklist for a leasing agent starting Monday, with P1 system-access tasks due day one, P2 policy reads due by day three, P3 shadowing sessions due end of week one, P4 solo tasks due end of week two.' Starch builds the list and sets due dates.

5 Share the Task Manager list with the new hire so they can see their own queue, check off completions, and get overdue alerts if they fall behind — without you manually tracking their progress.

6 Set up Email Triage (Email Agent) for the new hire's Gmail account: Starch syncs their Gmail on a schedule and applies priority filters you define — tenant emails high, owner emails flagged for same-day, vendor invoices tagged for AP review.

7 Configure reply draft templates inside Email Triage: maintenance acknowledgment, rent delinquency first notice, and owner update request — so the new hire can send accurate, on-brand replies from day one without guessing your tone.

8 Add a wiki entry for 'What to do with an email you don't know how to handle' — link it directly from the Email Triage setup so the new hire has an escalation path without calling you.

9 Schedule a 30-minute booking link via the Scheduling app (Google Calendar syncs directly with Starch) and paste it into the new hire's onboarding task list as the P3 'check-in with founder' meeting — no back-and-forth required.

10 At end of week one, ask Starch: 'Show me which onboarding tasks are overdue, which wiki sections have had zero views, and what email categories my new hire is spending the most time on.' Use that to close the gaps before week two.

11 Once the new hire is up to speed, publish any wiki sections they improved back to Notion so your institutional knowledge accumulates instead of restarting with the next hire.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

May 2026 — New Maintenance Coordinator, 210-Door Residential Portfolio

Sample numbers from a real run

Onboarding wiki pages built	14
Vendor contacts loaded from AppFolio (browser automation)	38
Onboarding tasks created in Task Manager	22
P1 tasks completed by end of day one	6
Email templates configured in Email Triage	4
Founder hours spent on direct onboarding questions, week one	3

A 210-door residential firm in Phoenix hired a maintenance coordinator in May 2026. The founder spent about 20 minutes before the start date typing the onboarding wiki prompt into Knowledge Management. Starch pulled 38 vendor records directly from Buildium through browser automation — HVAC, plumbing, electrical, landscaping, pool service — and populated the vendor section without any copy-pasting. The Task Manager checklist had 22 items across four priority levels; the coordinator knocked out all 6 P1 system-access tasks by noon on day one. Email Triage was configured with four reply templates (work order acknowledgment, estimated completion update, tenant delinquency first notice, and owner maintenance approval request), and the coordinator sent 11 accurate replies in the first two days without escalating a single one. The founder fielded 3 hours of direct questions that week, down from the usual 10–12 hours of shadowing the previous maintenance coordinator had required. By the end of week two, the coordinator had added two new vendor contacts and a note on the after-hours emergency escalation path directly into the wiki.

Measurement

How you'll know it's working

Time to first solo work order closed (target: end of week two)

Founder hours spent answering new-hire questions in week one (target: under 4 hours)

Percentage of onboarding tasks completed on time vs. overdue

Number of owner or tenant email replies sent without escalation in first 10 business days

Wiki pages created or updated by the new hire before 30-day mark (measures knowledge transfer, not just consumption)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Google Docs + a shared folder

Free and familiar, but docs go stale fast, there's no AI search, new hires can't find answers without already knowing what to search for, and you're still the index.

Notion (standalone)

Better structure than Docs, but building the onboarding wiki, task tracker, and email setup in Notion requires significant manual setup time and three separate tools — Starch connects to your Notion and builds on top of it rather than replacing it.

AppFolio or Buildium built-in training

Covers the PMS itself but says nothing about your vendor relationships, owner communication standards, or the dozen workflows that live outside the PMS — which is most of what a new hire actually needs to learn.

BambooHR or Rippling onboarding modules

Solid for HR paperwork and benefits enrollment, but they don't know your AppFolio workflow, your vendor list, or how you handle a late-rent escalation — you'd still need a separate knowledge base and task tracker on top.

Hiring a part-time operations manager to run onboarding

Effective but expensive at this portfolio size — Starch handles the structured, repeatable parts of onboarding so a human ops resource focuses on judgment calls instead of answering 'where's the vendor list' for the fourth time.

On Starch RECOMMENDED

One platform — knowledge management, task manager, email agent all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

We use AppFolio as our main system. Can Starch actually pull data from it?

Yes. AppFolio doesn't have a public API that Starch integrates with natively, but Starch automates AppFolio through your browser — no API needed. That means it can log in, navigate to your vendor list, pull work order history, or export unit rosters the same way you would, and use that data to populate your wiki or task context. You stay logged in; Starch does the clicking.

We already have some SOPs in Notion. Do we have to start over?

No. Connect Notion from Starch's integration catalog and Starch syncs your Notion pages and databases on a schedule. Existing content surfaces inside your Knowledge Management wiki automatically. You're adding to what you have, not rebuilding from scratch.

Is Starch SOC 2 certified? We handle tenant payment data.

Not yet — Starch is not SOC 2 Type II certified today. If your compliance requirements make that a hard requirement, that's worth knowing upfront. For most sub-500-door operators, the onboarding wiki and task tracking workflows covered here don't touch payment data directly, so it's less likely to be a blocker — but you should make that call for your situation.

The Task Manager app says it's in development. When can we use it?

Task Manager is currently in beta — you can request access from the Starch team. The onboarding checklist workflow described here can also be approximated today using Knowledge Management with structured task lists, or by describing a custom task-tracking app to Starch directly.

What if we hire someone who uses Outlook instead of Gmail?

Email Triage works with both. Starch syncs Outlook messages, events, and contacts on a schedule, the same way it handles Gmail. The priority filters and reply templates you set up apply to whichever account your new hire uses.

We turn over a leasing agent every 12–18 months. Does this pay off if onboarding is infrequent?

The wiki is the durable asset — you build it once and it compounds. Every hire adds to it rather than starting from zero. The first onboarding takes 20–30 minutes of setup; the second one is mostly just spinning up accounts and sharing the link. The bigger return is the 8–10 founder hours per hire you stop spending on in-person shadowing.