Marketing & Growth

How to build lifecycle email flows as Property Management Founders

Marketing & GrowthFor Property Management Founders2 apps10 steps~20 min to set up

You're managing lease renewals, delinquency follow-ups, and move-in sequences across AppFolio, Buildium, or Rent Manager — and none of those systems send the right email at the right time without you manually triggering it. You're copy-pasting tenant names into Gmail templates, forgetting to follow up when a lease is 90 days from expiration, and sending the same late-rent notice three times in a row because there's no logic to stop it once payment lands. A VA helps but they don't know which tenants are on a payment plan. Mailchimp exists but it can't see your PMS data. Every lifecycle email is a manual decision that falls on you or your leasing agent.

Build this on Starch → See the apps used

Marketing & GrowthFor Property Management Founders2 apps10 steps~20 min to set up

Outcome

What you'll set up

An automated email sequence that fires when a tenant hits 90, 60, and 30 days before lease expiration — pulling names, unit numbers, and renewal terms directly from your PMS via browser automation

A delinquency email workflow that checks your rent roll each morning, sends a tiered series of notices (friendly reminder → formal notice → final warning), and pauses automatically when Plaid confirms a payment hit the trust account

A move-in welcome series that sends unit-specific instructions, vendor contact cards, and portal setup links the day a new lease is executed — no leasing agent action required

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

CRM Email Agent

Data sources & config

AppFolio, Buildium, or Rent Manager are automated through your browser — no API needed. Plaid is connected as a scheduled-sync provider so Starch checks your trust account balance on a daily schedule and can pause delinquency sequences automatically when payment clears. Gmail is connected as a scheduled-sync provider for sending and tracking replies. Tenant and lease data flows from your PMS into the CRM so sequences stay current without manual updates.

Prompts to copy

Build me a lease renewal email sequence for residential tenants. Pull tenant name, unit number, lease end date, and current rent from AppFolio through browser automation. Send the first email 90 days out asking if they want to renew, a second at 60 days with the renewal offer attached, and a final nudge at 30 days. If the tenant replies at any point, route the thread to my leasing agent and pause the sequence.

Set up a delinquency follow-up flow that runs every weekday morning. Check my Buildium rent roll via browser automation for any balances past due more than 3 days. Send a friendly payment reminder on day 3, a formal late notice on day 7, and a final written warning on day 14. Cross-check Plaid each morning — if the balance clears, mark it resolved and stop the sequence immediately.

Create a move-in welcome email that fires the day a new lease is signed in Rent Manager. Include the tenant's name, unit address, move-in date, maintenance request instructions, and contact info for my preferred vendors. Pull the lease execution date from Rent Manager via browser automation.

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

Walkthrough

Step-by-step

1 Connect your PMS (AppFolio, Buildium, or Rent Manager) — Starch automates it through your browser, logging in and reading your rent roll, lease expiration dates, and tenant records on whatever schedule you set.

2 Connect Plaid as a scheduled-sync provider so Starch can read your trust account transactions daily and detect when a delinquent tenant's payment lands.

3 Connect Gmail as a scheduled-sync provider — Starch sends on your behalf and monitors replies so it knows when a tenant responds and can route or pause accordingly.

4 Install the CRM starter app and describe your tenant schema: 'I want contacts that include unit number, lease start and end date, monthly rent, delinquency status, and whether they're on a payment plan.' Starch builds the schema around your actual fields.

5 Tell Starch to import your current tenant list: 'Pull all active leases from AppFolio, create a contact for each tenant with their unit, lease end date, and current balance, and flag anyone 30+ days delinquent.'

6 Build the lease renewal sequence by describing it in plain English — which days to send, what tone (friendly at 90 days, more direct at 30), and what to do when someone replies. Starch wires the logic.

7 Build the delinquency flow and set the Plaid check as your exit condition: 'Every morning, query Plaid for any payment from tenants currently in the delinquency sequence. If payment is confirmed, mark them current and stop all further emails in that series.'

8 Build the move-in welcome automation: 'When a new lease record appears in Buildium with a future move-in date, send a welcome email the day the lease is signed with unit-specific onboarding information.'

9 Install the Email Agent app and tell it: 'Flag any tenant reply to a lifecycle email as high priority. Summarize the thread and draft a suggested response from my leasing agent's perspective.' This gives your team one-click replies instead of starting from scratch.

10 Set up a weekly digest: 'Every Monday, email me a summary of how many tenants are in each lifecycle sequence, how many renewal emails got a reply this week, and which delinquent accounts cleared.' Starch pulls this from the CRM and Plaid data.

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

Riverview Properties — March 2026 Renewal and Delinquency Sweep

Sample numbers from a real run

Leases expiring in next 90 days	14
Renewal sequence emails sent (auto)	38
Tenant replies routed to leasing agent	6
Delinquent accounts at month start	9
Accounts resolved by Plaid-triggered sequence pause	7
Manual late notices sent by leasing agent	2
Move-in welcome emails sent (new leases)	5

Riverview manages 210 residential doors across three communities in AppFolio. Coming into March, 14 leases were expiring before June 1. Without Starch, the leasing agent would have pulled a custom report, built a list in a spreadsheet, and drafted individual renewal emails over two days. Instead, Starch read the lease expiration data from AppFolio through browser automation, created CRM contacts for all 14, and kicked off the 90-day renewal sequence automatically. By March 31, 6 tenants had replied — all routed directly to the leasing agent with Email Agent's one-click draft replies — and 8 had not responded, triggering the 60-day follow-up without any manual action. On the delinquency side, 9 tenants started the month with a balance. Starch sent the day-3 friendly reminder automatically, escalated to the formal notice at day 7, and each morning queried Plaid against the trust account. Seven of the nine paid during the sequence — Plaid confirmed the deposits and Starch paused further emails before the formal notice even sent in five of those cases. Two accounts went to the day-14 final warning. The leasing agent touched exactly those two, instead of all nine. Five new leases executed in March triggered the move-in welcome email the same day — unit address, maintenance portal link, and preferred vendor list included — with zero staff time.

Measurement

How you'll know it's working

Lease renewal rate — percentage of expiring leases that renew, tracked against the 90-60-30 sequence engagement

Days delinquent per account — how long it takes from first missed payment to resolution, benchmarked before and after automated sequences

Leasing agent email time — hours per week spent on outbound tenant communication (target: cut by 60%)

Sequence open and reply rate — which emails in each series get responses, so you can improve copy over time

Unresolved delinquencies at 14+ days — the accounts that escalate past the automated flow to legal or manual intervention

Comparison

What this replaces

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

AppFolio / Buildium built-in communications

PMS email tools send basic notices but have no conditional logic — they can't pause a delinquency sequence when Plaid confirms payment, and they don't route replies to an agent with AI-drafted responses.

Mailchimp or ActiveCampaign

Email marketing platforms handle sequences well but have no native connection to your PMS data, so someone still has to manually export your tenant list and keep it current — the exact work you're trying to eliminate.

Property management VA

A VA can execute the manual version of these workflows but costs $1,500–$3,000/month, doesn't work at 6am when a delinquency threshold triggers, and still makes mistakes on payment plan tenants that need exception handling.

Zapier + Gmail + Google Sheets

You can wire up basic automations but Zapier can't read your PMS data directly, can't run browser automation against AppFolio or Buildium, and the Zap breaks every time your PMS changes a field name.

On Starch RECOMMENDED

One platform — crm, 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

My PMS is AppFolio — does Starch have a direct integration?

Starch automates AppFolio through your browser — no direct API needed. It logs in, reads your rent roll, lease data, and tenant records on a schedule you set. The same approach works for Buildium, Rent Manager, and Propertyware. If your PMS has an API Starch can reach from its integration catalog, that works too.

How does the delinquency sequence know when to stop? I don't want a tenant to get a formal notice after they've already paid.

Starch connects directly to Plaid and syncs your trust account transactions on a daily schedule. Each morning, before any email in the delinquency series sends, Starch checks whether the tenant's payment has posted. If it has, the sequence pauses and the tenant is marked current. This is one of the most concrete reasons to wire Plaid in — you're not relying on someone manually updating a spreadsheet to stop the emails.

Can I customize the tone of the emails? My late notices need to be more formal than my renewal outreach.

Yes. When you describe each sequence to Starch, you specify the tone, the exact language you want, and any legal language required in your state for late notices. You're not choosing from templates — you're telling Starch what the email should say and it writes and sends it. You can also give it example emails you've written before and say 'match this style.'

Is Starch SOC 2 certified? I'm handling tenant data and my property owners ask about this.

Starch is not SOC 2 Type II certified today. If a property owner or institutional client requires that certification as a condition of working with you, that's worth knowing upfront. For most independent property managers under 500 doors, this hasn't been a blocker — but it's an honest limit and we'd rather you know before you build.

What happens if a tenant replies to an automated email? Does it just fall into a void?

No — reply detection is built into the setup. When you describe the sequences, you tell Starch what to do with replies: route to your leasing agent, flag it as high priority in Gmail, and pause the sequence. The Email Agent app then summarizes the thread and drafts a suggested response, so your leasing agent isn't starting from scratch — they're reviewing and clicking send.

Can I build a move-out sequence too, not just move-in?

Yes. Describe it the same way: 'When a notice-to-vacate is recorded in Buildium, send a move-out checklist 45 days before the last day, a security deposit inspection reminder 14 days out, and a forwarding address request 7 days out.' Starch builds the sequence from that description. If your PMS records move-out dates in a specific field, Starch reads that via browser automation as the trigger.