Sales & CRM

How to forecast quarterly revenue as Real Estate Founders

Sales & CRMFor Real Estate Founders3 apps12 steps~24 min to set up

You're modeling Q2 acquisition targets in Excel, but your Plaid transactions are in one tab, your Stripe rent-collection data is in another, and your deal pipeline is in HubSpot with no connection to either. Every quarter you spend two to three days pulling CSVs, reconciling actuals, and building a forecast slide you'll present to LPs who want to see net operating income by property, not blended ARR. Your broker relationships are in a CRM that doesn't know about your cap rate assumptions. Your revenue forecast is a snapshot the moment you save it and stale the moment anything changes.

Build this on Starch → See the apps used

Sales & CRMFor Real Estate Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live quarterly revenue forecast that pulls actual transaction data from your bank feeds and rent-collection records automatically, so your baseline is always current without a manual export

A scenario model that lets you test acquisition timing, rent increases, and disposition events side-by-side — with runway and NOI impact shown per property

An investor-ready forecast summary that formats into a polished update and emails your LP list on the cadence you set, without a separate deck-building session

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 Investor Reporting CRM

Data sources & config

Starch syncs your Plaid transaction data on a schedule for operating expense actuals. Starch syncs your Stripe data on a schedule for rent collection and payment history. Gmail is connected so email thread history surfaces inside deal records in the CRM. For any property management portal or county assessor site without an API, Starch automates it through your browser — no API needed.

Prompts to copy

Build me a quarterly revenue forecast that shows projected NOI by property. Pull actuals from Plaid for operating expenses and Stripe for rent collections. Let me add acquisition scenarios — if I close on 123 Maple in Q3, show me how that changes Q4 revenue and cash position.

Generate a Q2 investor update that includes actual rent collected, burn rate, runway, and a one-paragraph narrative on the two acquisitions we're evaluating. Send it to my LP list on the first Monday of each quarter.

Build me a CRM that tracks deals by property address, deal type (acquisition vs. disposition), cap rate, close probability, and which broker brought it. Connect my Gmail so I can see email thread history inside each deal record.

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

Walkthrough

Step-by-step

1 Connect Plaid in Starch — Starch begins syncing your bank transactions on a schedule, categorized by account. Your operating expense actuals are live from day one.

2 Connect Stripe — Starch syncs rent collection records, invoices, and payout history. If you collect rent through another portal with no API, Starch automates it through your browser instead.

3 Open the Scenario Analysis app from the Starch App Store. Your baseline revenue and burn populate automatically from the Plaid and Stripe sync — no CSV import.

4 Type your first scenario: 'Show me Q3 and Q4 revenue if I acquire 123 Maple Street in August at a 5.8 cap rate and add $18,400/month in gross rent.' Starch models it against your live baseline.

5 Add a second scenario for comparison: 'Show me the same period if the acquisition closes in October instead of August, and Q3 occupancy on my existing portfolio drops to 91%.' Run both side-by-side.

6 Open the CRM app. Describe your deal tracking needs: 'I want to track acquisitions and dispositions by property address, broker contact, cap rate, close probability, and which LP has expressed interest.' Starch builds the schema to match how you actually work.

7 Connect Gmail so broker email threads and LP correspondence sync into each deal record. When you search 'what did Marcus from Eastside Realty say about 123 Maple?' you get the actual thread, not a reminder to go check your inbox.

8 Wire the CRM deal stages into your forecast: tell Starch 'when a deal moves to 90% probability in my CRM, add its projected NOI to my Q3 revenue scenario automatically.'

9 Open the Investor Reporting app. Tell Starch: 'Draft a Q2 revenue update for my LPs. Include actual rent collected ($214,000), operating expenses ($87,300), NOI ($126,700), and a paragraph on the two acquisitions we're evaluating in Austin.' Starch drafts the narrative, formats the numbers, and adds charts.

10 Review the draft, adjust the tone or emphasis where needed, and set a send schedule — first Monday of each quarter, to your LP distribution list.

11 Each subsequent quarter, your actuals pull in automatically. You answer a few questions about what changed — a new acquisition, a lease-up, a vacancy event — and Starch updates the forecast and the investor narrative without rebuilding from scratch.

12 When your forecast assumptions change mid-quarter (a deal falls through, a major tenant gives notice), update the scenario in plain language: 'Remove the 123 Maple acquisition from Q3 and shift my hiring plan back by one quarter.' Starch recalculates runway and NOI impact immediately.

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

Q2 2026 Forecast — Austin Portfolio, May Review

Sample numbers from a real run

Gross rent collected (Q2 actuals, Stripe)	214,000
Operating expenses (Q2 actuals, Plaid)	87,300
Net operating income (Q2 actual)	126,700
Projected NOI if 123 Maple closes Aug 1 (Scenario A)	163,400
Projected NOI if 123 Maple closes Oct 1 (Scenario B)	144,800
LP equity distributions (Q2)	38,000

Going into May's LP call, your Q2 actuals are already in Starch: $214,000 gross rent collected via Stripe, $87,300 in operating costs from Plaid, leaving $126,700 in NOI. You have two open acquisition scenarios running in parallel. Scenario A assumes 123 Maple Street closes August 1 at a 5.8 cap — that adds $36,700 in projected Q3 NOI and pushes your full-year NOI to $163,400 for Q3. Scenario B shifts the same close to October 1, which drops Q3 projected NOI to $144,800 and changes your LP distribution timing. You walk your investors through both on the call, share the Starch-generated update that went out Monday morning, and they can see the actual Q2 numbers and the two forward paths in one document. No deck. No 'let me pull the latest numbers.' The CRM shows you that two of your LPs expressed interest in co-investing on 123 Maple — their email threads are right inside the deal record.

Measurement

How you'll know it's working

Net operating income (NOI) by property, quarterly and trailing twelve months

Gross rent collected vs. projected rent — variance by unit or property

Cash runway (months) under each acquisition scenario

Deal pipeline close probability weighted by projected NOI contribution

LP equity distributions as a percentage of NOI

Comparison

What this replaces

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

Excel + QuickBooks + HubSpot (manual export stack)

You probably already have this and it works until you're running three properties — then the reconciliation time exceeds the value and you're always presenting stale numbers.

Juniper Square

Purpose-built for real estate fund accounting and LP reporting, with strong compliance features — but it won't build you a custom deal pipeline CRM or let you model acquisition scenarios in plain language; you still need Excel for that layer.

Argus Enterprise

Industry standard for asset-level cash flow modeling and valuation, and your LP may require it — but it doesn't pull live bank actuals or connect to your deal CRM, so your forecast is still a manual exercise every quarter.

Notion + Airtable (DIY ops stack)

You can connect both from Starch's integration catalog if you want to keep using them, but rebuilding a financial model in Airtable that stays current with live Plaid and Stripe data is the kind of project that takes a weekend and breaks the next time a field changes.

On Starch RECOMMENDED

One platform — scenario planning, investor reporting, crm 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 rent collection runs through a property management portal that isn't Stripe — can Starch still pull that data?

If your portal has no API, Starch automates it through your browser — no API needed. You log in once through Starch's browser automation, and it navigates the portal the same way you would, pulling the data your forecast needs. If it's a web-based portal you can log into, it's reachable.

Can Starch model property-level NOI, or is everything blended at the portfolio level?

Describe what you want and Starch builds it. Tell Starch 'track NOI separately for each property address and roll them up to portfolio total' — that's the schema it will build. The Scenario Analysis app starts from a blended view, but you can fork it and customize the structure to match how you actually report to LPs.

Is Starch SOC 2 certified? My LPs ask about data security.

Starch is not SOC 2 Type II certified today. That's a real limit worth naming. If your LPs have a hard compliance requirement for SOC 2 on financial tooling, it's worth asking Starch directly about their timeline. For most early-stage real estate operators, the bigger risk is a spreadsheet that lives only on one laptop.

I use QuickBooks for my entity-level accounting. Will the QuickBooks integration give me P&L data for the forecast?

Starch syncs QuickBooks entity data — invoices, bills, payments, vendors, journal entries — on a schedule. One honest note: QuickBooks report views like the built-in P&L summary are temporarily unavailable due to a connector fix in progress. Entity-level data syncs normally, so you can build a P&L view in Starch from the underlying records — it just won't pull the pre-formatted QuickBooks report view today.

How does this compare to just hiring a CFO or finance contractor for quarterly modeling?

A good fractional CFO brings judgment that Starch doesn't replace — especially on deal structuring, LP negotiations, and lender relationships. What Starch replaces is the prep work: pulling actuals, formatting the update, maintaining the scenario model between calls. If you're paying a contractor $150/hour to spend four hours pulling Plaid exports and reformatting a deck every quarter, that's the specific thing Starch handles.

Can I share forecast scenarios with my LPs or co-investors directly?

The Investor Reporting app sends formatted updates to your LP distribution list on the cadence you set. The scenarios themselves live inside Starch — you'd share the output (the formatted report) rather than giving LPs direct access to the model. If you want a specific export format your LPs expect, describe it to Starch and it will build that output format.