People & HR

How to plan headcount as Real Estate Founders

People & HRFor Real Estate Founders3 apps10 steps~20 min to set up

You're running a 12-person real estate shop and headcount planning happens in a Google Sheet that three people are editing at once, referencing a Plaid export someone pulled last Tuesday and a Stripe revenue number nobody trusts. You don't have an HR software budget. Your bookkeeper closes the books 30 days late. So when a property closes and you need to decide whether to add a junior analyst or a second asset manager, you're making that call off gut feel and a stale cash number — because modeling it out in Excel takes half a day you don't have, and your CPA charges $300/hour to run scenarios you'll change anyway the next morning.

Build this on Starch → See the apps used

People & HRFor Real Estate Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

A live headcount model that ties your actual bank burn and Stripe revenue to your payroll run rate, so you can see exactly how many months of runway each new hire consumes before you sign an offer letter

Side-by-side hiring scenarios — 'hire one analyst now vs. wait until the Q3 close' — built on your real revenue and expense baseline, not a spreadsheet with made-up assumptions

A quarterly budget view that tracks people costs as a category against actual spending, with pace indicators that tell you when payroll is running ahead of plan

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

Runway Analysis Scenario Analysis Budgeting

Data sources & config

Starch syncs your Plaid bank feed data on a schedule — transactions, balances, and categorized expenses update automatically. Starch syncs your Stripe revenue on a schedule — charges, invoices, and payouts come in daily. For payroll detail, connect your ADP or Paylocity account and Starch syncs employees, pay statements, and pay runs on a schedule. If you use a different payroll provider that's web-based, Starch can automate it through your browser — no API needed.

Prompts to copy

Connect my Plaid bank feeds and Stripe account, then show me my real net burn for the last 6 months broken out by payroll, property expenses, and overhead — and project forward 24 months at the current pace

Build me three hiring scenarios side by side: (1) no new hires, (2) one junior analyst at $85k starting August 1, (3) one senior asset manager at $140k starting August 1. Use my actual Stripe revenue and Plaid burn as the baseline and show me runway and break-even for each

Set up a quarterly budget that tracks payroll as its own category. Pull actual spending from my connected accounts, show me how we're pacing against plan, and flag if we go more than 10% over in any month

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

Walkthrough

Step-by-step

1 Connect your Plaid bank feeds in Starch. Starch syncs your transactions and balances on a schedule — the baseline numbers in every model update automatically from that point forward.

2 Connect Stripe so Starch syncs your revenue on a schedule. For a real estate shop, this might be property management fees, investor distributions, or transaction commissions — whatever flows through Stripe.

3 If you run payroll through ADP or Paylocity, connect that account. Starch syncs employee records, pay runs, and benefits costs on a schedule, which means your payroll line item is real, not a rough estimate.

4 Open the Runway Analysis starter app. Tell Starch how to categorize your expenses — 'split my Plaid expenses into payroll, property ops, G&A, and deal costs' — and it builds the breakdown. You now have real net burn, not an averaged guess.

5 Open Scenario Analysis and describe your hiring question in plain language. Tell Starch the specific roles, target start dates, and fully-loaded costs. It builds the scenarios using your actual Plaid and Stripe baseline, not placeholder numbers.

6 Review the scenario outputs. Each one shows runway, monthly burn, and break-even under its assumptions. If your Q3 acquisition closes on time and adds $18k/month in management fees, add that as a revenue assumption in the relevant scenario and see how the math changes.

7 Open the Budgeting app and set your quarterly people budget. Tell Starch to track payroll, benefits, and contractor costs as a single 'team' category. Set the target and let it compare actuals against plan going forward.

8 Ask Starch to flag anomalies: 'Alert me if any month's payroll spend runs more than 8% over the budgeted amount.' This catches payroll processing errors, unexpected overtime, or a contractor invoice that hit at the wrong time.

9 When you're ready to make the hire, go back to Scenario Analysis and refine the model. Update the start date, benefits load, and any expected revenue from new properties coming online. The baseline is still live — you're only changing the assumptions you care about.

10 Export or share the scenario output with your LP or board contact before the hire. Real estate investors want to see runway discipline. Showing a data-backed model — 'we have 19 months at this burn before the hire, 14 months after, and the new property covers the gap by month 6' — is a different conversation than 'we think we can afford it.'

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

August 2026 analyst hire decision — Meridian Capital Partners

Sample numbers from a real run

Current monthly burn (Plaid)	87,000
Stripe management fee revenue (monthly)	62,000
Net burn today	25,000
Cash on hand (Plaid balance)	1,140,000
Current runway (months)	46
Junior analyst fully-loaded cost (monthly)	9,500
Net burn post-hire	34,500
Runway post-hire (months)	33
Hargrove Commons management fee (starting month 4)	7,200
Runway with new property revenue post-hire	39

Meridian Capital Partners is deciding whether to bring on a junior analyst before the Hargrove Commons acquisition closes. Their Plaid feeds show $87k/month in actual expenses — payroll is $54k of that, property ops $18k, G&A $15k. Stripe shows $62k in recurring management fees. Net burn is $25k/month with $1.14M in the bank: 46 months of runway on paper. The Scenario Analysis app builds three paths. Scenario 1, no hire: runway stays at 46 months and the two existing analysts keep running at capacity through the Hargrove due diligence. Scenario 2, hire now at $9,500/month fully loaded: net burn climbs to $34,500 and runway drops to 33 months. Scenario 3, hire now and assume Hargrove's $7,200/month management fee starts in month 4: runway recovers to 39 months. The Budgeting app is already tracking payroll as a category — it's running 3% under budget YTD because of a delayed Q1 bonus. That $8,400 variance creates room in the Q3 people budget. The decision isn't gut feel anymore: the model says Scenario 3 makes sense if Hargrove closes on schedule, and the founder can show that math to their LP advisory board in the next quarterly update.

Measurement

How you'll know it's working

Net burn per month (total expenses minus management fee and transaction revenue, from live Plaid and Stripe data)

Runway in months at current headcount vs. runway post-planned hire

Payroll as a percentage of total operating expenses — real estate operators watch this to keep people costs from crowding out deal capital

Revenue per full-time employee — how much management fee or transaction fee revenue each head is generating

Payroll budget variance — how much actual payroll spend differs from the quarterly budget, by month

Comparison

What this replaces

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

Excel or Google Sheets

You can build anything in a spreadsheet, but every model starts stale the moment you close it — you're manually updating Plaid exports, Stripe CSVs, and ADP payroll summaries every time you want a current number, which means the model only gets refreshed when you have time to do it.

Rippling or Gusto workforce planning module

Good for companies where HR is the primary workflow, but neither pulls your bank burn or Stripe revenue into the same view — so you still have to manually bridge the people cost data to your financial model.

Mosaic or Planful

Purpose-built FP&A tools with more financial modeling depth, but they're priced for Series B+ companies with a finance hire to set them up, not a 12-person real estate operator building their own models on a Sunday afternoon.

QuickBooks + a CFO-for-hire

Accurate books are a real advantage, but waiting 30 days for your outsourced bookkeeper to close the month before you can model a hiring decision is the exact problem Starch's live data connections are built to solve.

On Starch RECOMMENDED

One platform — runway analysis, scenario planning, quarterly budgeting 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 payroll is through a provider that's not ADP or Paylocity — can Starch still pull that data?

If your payroll provider has a web interface you can log into, Starch can automate it through your browser — no API needed. That means it can pull pay run summaries, employee counts, and cost totals from almost any web-based system. For providers like Gusto, BambooHR, or Rippling, you can also connect them from Starch's integration catalog and the agent queries them live when your model runs.

The Scenario Analysis baseline pulls from Stripe — but most of our revenue is management fees that don't go through Stripe. Will the model still work?

Yes. Starch syncs your Plaid bank feeds on a schedule, which captures all cash coming in regardless of how it's processed. You can tell Starch to use Plaid inflows as your revenue baseline instead of Stripe, and to categorize management fee deposits separately from other income. The model works off your actual cash, not just what's in Stripe.

Is the data stored securely? We have LP financial information flowing through here.

Starch is not SOC 2 Type II certified yet — that's worth knowing before you decide. Your data is stored in Starch's database and the scheduled syncs pull from your connected accounts on an ongoing basis. If SOC 2 certification is a hard requirement from your LPs or compliance team, that's an honest limit right now.

Can Starch integrate with Juniper Square or AppFolio for property-specific cost data?

Neither is in Starch's scheduled-sync provider list today. Both are web-based platforms, so Starch can automate them through your browser — logging in, pulling report data, and feeding it into your headcount model — without needing a formal API connection. If you want to describe the specific data you need from either platform, Starch can build a browser automation to extract it on a schedule.

How often does the runway number update? I need to know if a large check clears before making a hiring call.

Starch syncs your Plaid balance and transaction data on a schedule — typically daily. So your runway number reflects yesterday's bank balance, not last month's. It won't update the moment a wire hits, but it's close enough that you're not making hiring decisions off a number that's weeks old.

We model headcount at the property level, not just company-wide. Can Starch handle that?

Yes — describe it and Starch builds it. Tell Starch to build a model that breaks payroll and revenue down by property, with a scenario layer that lets you test adding headcount to a specific asset. The natural-language authoring means you define the structure; Starch isn't locked into a company-wide view.