Strategy & Planning

How to run annual planning as Real Estate Founders

Strategy & PlanningFor Real Estate Founders5 apps12 steps~24 min to set up

Annual planning for a real estate operator founder means pulling together numbers from five different places: your bank feeds, your Stripe receipts, your QuickBooks entities, a deal pipeline spreadsheet someone built two years ago, and a cap table in a Google Sheet you share with your attorney. You spend two weekends in November building a financial model that's already stale by the time your LP call happens in December. Nobody has captured what actually got decided in last quarter's investor meetings. The budget categories don't map to your property-level actuals. And the slide deck you send to investors looks like you made it in 2014 because you did.

Build this on Starch → See the apps used

Strategy & PlanningFor Real Estate Founders5 apps12 steps~24 min to set up

Outcome

What you'll set up

A live financial baseline — actuals from your Plaid bank feeds and Stripe receipts feeding directly into your scenario models, so your 2026 plan starts from what actually happened in 2025, not a number you remembered

A searchable archive of every strategic decision, investor conversation, and planning assumption from the past year, organized so you can find it in 30 seconds instead of digging through Gmail threads

A set of side-by-side acquisition and disposition scenarios — conservative, base, and aggressive — with runway, burn, and break-even calculated automatically so you can walk your LPs through the numbers without a finance hire

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

Scenario Analysis Budgeting Knowledge Management Meeting Notes Presentation Agent

Data sources & config

Starch syncs your Plaid transaction and balance data on a schedule and syncs your Stripe charges and payouts on a schedule — both feed the Scenario Analysis and Budgeting apps with live 2025 actuals. QuickBooks entity-level data (invoices, bills, vendors, payments, journal entries) also syncs on a schedule for any property-level accounting you run through it. Google Calendar and Gmail sync on a schedule so Meeting Notes can cross-reference investor calls and pull context into your Knowledge Management archive. HubSpot connects from Starch's integration catalog for deal pipeline data queried live when your planning apps need it.

Prompts to copy

Build me a 2026 annual plan with three scenarios: conservative (revenue flat, one acquisition), base (revenue up 15%, two acquisitions), and aggressive (revenue up 30%, three acquisitions plus a disposition). Pull my actual 2025 burn from Plaid and Stripe as the baseline and show me runway, burn rate, and break-even for each scenario.

Set up a 2026 annual budget with categories for acquisitions, property operations, investor relations, and G&A. Compare against my actual 2025 spend from Plaid and flag any category where I was over 10% off my original plan.

Create a knowledge base section called '2026 Annual Planning' and populate it with our key assumptions, LP commitments made in Q4 2025, and any strategic decisions we've agreed on. Pull in summaries from my investor meeting notes from October through December.

Summarize my last six LP update calls and extract: any commitments made, any concerns raised, any follow-up items that are still open.

Build a 12-slide 2026 annual plan deck for our LP advisory board: cover page, 2025 performance summary, 2026 market thesis, three financial scenarios with runway charts, acquisition pipeline, team and resource plan, and one slide on risks and mitigants.

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

Walkthrough

Step-by-step

1 Connect your financial sources: Starch syncs your Plaid bank feeds and Stripe receipts on a schedule so your 2025 actuals are available as a live baseline — no manual exports, no copying numbers between tabs.

2 If you run property-level accounting in QuickBooks, connect it. Starch syncs your bills, invoices, vendors, payments, and journal entries on a schedule. Note: QuickBooks report views (P&L, Transaction List) are temporarily unavailable, but entity-level data syncs normally and is enough to build your baseline.

3 Open Scenario Analysis and describe the three scenarios you actually care about — conservative, base, and aggressive acquisition pace. Starch uses your live Plaid and Stripe data as the baseline and lets you adjust only the assumptions you're testing: acquisition volume, revenue growth, headcount.

4 For each scenario, review the runway, burn rate, and break-even outputs. Adjust assumptions interactively — 'what if the third acquisition slips to Q3?' — without rebuilding the model from scratch.

5 Open Budgeting and set your 2026 category targets: acquisitions and due diligence, property operations, investor relations and travel, legal and compliance, and G&A. Let Starch auto-suggest allocations based on your 2025 Plaid actuals, then override the ones where your plan diverges from history.

6 Connect HubSpot from Starch's integration catalog so your deal pipeline is queryable live — acquisition targets in due diligence, LOIs outstanding, deals under contract — and visible in the same planning context as your financial model.

7 Pull in your Q4 2025 LP and investor meeting transcripts through Meeting Notes. For any past meetings where you didn't use Starch, upload notes manually and ask Starch to extract key decisions, commitments made, and open follow-ups.

8 Build your Knowledge Management section for 2026 planning: key strategic assumptions, LP commitments, market thesis rationale, and a running log of what changed from last year's plan and why. This becomes the single source of truth your team can search instead of asking you.

9 Use the Presentation Agent to generate your LP annual plan deck. Describe the structure you want — 'a 12-slide 2026 annual plan deck including 2025 performance, three financial scenarios, deal pipeline, and risk factors' — and iterate on individual slides until it reflects your actual numbers and thesis.

10 Run a sanity check: ask Starch to compare your 2026 budget assumptions against your 2025 Plaid actuals by category and flag any line items where your plan assumes more than a 20% change without a documented reason in your knowledge base.

11 Schedule a recurring monthly budget-vs-actuals review. Starch monitors your Plaid and Stripe data on a schedule and can alert you when a category hits 80% of its quarterly budget before the quarter ends.

12 Archive the completed plan — scenarios, budget, deck, and decision log — in your Knowledge Management system so next November you're starting from a structured baseline instead of a blank spreadsheet and six months of Gmail threads.

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

Q4 2025 → 2026 Annual Plan, Meridian Capital Group (12-unit multifamily portfolio, two GPs, 8 LPs)

Sample numbers from a real run

2025 actual operating burn (Plaid)	387,000
2025 Stripe receipts (management fees + promote distributions)	214,000
2026 base scenario acquisition budget (2 properties)	1,800,000
2026 projected G&A (base scenario)	420,000
2026 LP capital committed (from meeting notes archive)	3,200,000
Runway at base scenario (months)	22

Meridian's two GPs spent the first two weeks of December doing what they do every year: pulling 2025 bank statements from three accounts into a spreadsheet, manually reconciling Stripe payouts against their QuickBooks vendor bills, and trying to remember what they'd promised LP #4 about the Q2 acquisition timeline. This year they connected Plaid and Stripe to Starch at the start of the process. The 2025 actuals — $387K operating burn, $214K in management fee and promote income — populated automatically. They described three scenarios: conservative (one acquisition, revenue flat), base (two acquisitions, 15% revenue growth from two new management contracts), and aggressive (three acquisitions plus one disposition, 30% revenue growth). The base scenario showed $420K projected G&A for 2026 and 22 months of runway — enough to make the second acquisition without needing to call capital early. The meeting notes from their October and November LP calls surfaced a commitment from LP #3 for an additional $800K that hadn't made it into their cap table model yet. That changed the aggressive scenario runway from 14 months to 19. The LP deck took one prompt and 20 minutes of iteration instead of a Sunday afternoon in Google Slides.

Measurement

How you'll know it's working

Runway by scenario (months to zero cash at each acquisition pace)

Budget-vs-actuals variance by category at end of each quarter (G&A, acquisitions, property ops, investor relations)

LP capital committed vs. deployed ratio going into the new year

Number of acquisition targets in active due diligence vs. annual plan target

Open LP follow-up items from Q4 investor calls cleared before year-end

Comparison

What this replaces

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

Excel + QuickBooks + manual LP email threads

You control every formula and every cell, but your 2025 actuals don't update automatically, your LP commitments live in Gmail, and you rebuild the model from scratch every time an assumption changes.

Juniper Square

Strong LP portal and waterfall modeling for established fund managers, but it doesn't touch your operating budget, deal pipeline, or the meeting notes where half your planning decisions actually live.

Argus Enterprise

Best-in-class for property-level DCF and asset management analysis, but it's priced for institutional shops, doesn't connect to your bank feeds, and won't help you build an LP deck or track G&A.

Google Slides + a finance consultant for the annual model

You get a polished deck and a credible model, but you're paying $5K–$15K for something you redo every year and still have to manually update when your assumptions change in January.

On Starch RECOMMENDED

One platform — scenario planning, quarterly budgeting, knowledge management 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

Does Starch connect to Juniper Square for LP reporting data?

Juniper Square isn't currently in Starch's scheduled-sync providers, but if you can navigate to it in a browser, Starch can automate data extraction through browser automation — no API needed. Alternatively, most real estate operators running Starch pull LP financial data from Plaid and Stripe directly and use Starch's Knowledge Management to track LP conversations and commitments.

Can Starch pull my QuickBooks P&L for the 2025 actuals baseline?

QuickBooks report views — including P&L and Transaction List — are temporarily unavailable while an upstream connector issue is fixed. Entity-level data syncs normally: bills, invoices, vendors, payments, and journal entries are all accessible and are usually enough to reconstruct your actuals. If you need the full P&L view right now, export it from QuickBooks and upload it to your Starch knowledge base while the fix is in progress.

Is my financial data stored securely? Starch isn't SOC 2 Type II certified yet.

Correct — Starch is not currently SOC 2 Type II certified, and we won't claim otherwise. Your Plaid and Stripe connections use standard OAuth flows; your data lives in Starch's database and is not shared externally. If SOC 2 Type II is a hard requirement for your LP agreements or compliance obligations, that's worth knowing before you commit.

What if my scenario assumptions change in February after I've already published the plan to LPs?

Because your Plaid and Stripe data syncs on a schedule, the baseline is always current. You can reopen Scenario Analysis, adjust the one assumption that changed — say, an acquisition slipped to Q3 — and get updated runway and burn numbers immediately without rebuilding the model. The Presentation Agent can regenerate affected slides from your updated scenario outputs.

Can I track deal pipeline (acquisition targets, LOIs, under contract) inside the same annual plan?

Yes. Connect HubSpot from Starch's integration catalog and your deal pipeline data is queryable live — active due diligence, outstanding LOIs, deals under contract — and visible in the same context as your financial model. If you track deals in a different CRM, Starch connects to 3,000+ apps through its integration catalog, plus any pipeline tool that's web-accessible can be automated through your browser.

The Budgeting and Presentation Agent apps say 'currently in development' — can I use them now?

The Budgeting app and Presentation Agent are in development. You can request beta access through Starch to get notified when they launch. In the meantime, Scenario Analysis is live today and covers the financial modeling work; you can use the Knowledge Management app to structure your planning assumptions and decision log while you wait for Budgeting to ship.