Sales & CRM

How to clean up stale deals in your pipeline as Real Estate Founders

Sales & CRMFor Real Estate Founders3 apps10 steps~20 min to set up

Your deal pipeline is a graveyard of 'following up next week' that never happened. You're tracking 40 properties across a HubSpot free tier, a Google Sheet your analyst built two years ago, and a notes app on your phone. A multifamily acquisition you toured in October is still sitting in 'LOI Stage' because nobody moved it. An LP who expressed interest in a retail strip center never got a second email. You don't have a pipeline hygiene process — you have a quarterly panic where you scroll through deals and try to remember what happened. Every stale deal is either a missed acquisition or a wasted hour reconstructing context you should have had documented.

Build this on Starch → See the apps used

Sales & CRMFor Real Estate Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

A real estate CRM with deal stages mapped to your actual acquisition workflow (Sourced → Underwriting → LOI → PSA → Closed / Dead) that flags any deal untouched for more than 14 days

An automated stale-deal audit that runs weekly, surfaces every property sitting in the wrong stage, and drafts a re-engagement email to the broker or seller contact on file

A task list tied to each deal so follow-ups on offers, estoppel certificates, and LP soft-circles don't live in your head or get buried in Gmail

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 Task Manager

Data sources & config

Starch syncs your Gmail data on a schedule so the CRM can pull email thread history for each deal contact automatically. Connect HubSpot from Starch's integration catalog if you're migrating existing contacts — the agent queries it live during import. Google Calendar is synced on a schedule so the task manager can cross-reference follow-up deadlines against your actual calendar. For broker websites or off-market listing portals that don't have an API, Starch automates those through your browser — no API needed.

Prompts to copy

Build me a CRM for real estate acquisitions. Stages are: Sourced, Underwriting, LOI Submitted, Under PSA, Closed, Dead. Fields I care about per deal: property address, asset class (multifamily / industrial / retail / office), asking price, our underwritten cap rate, broker name and email, last contact date, close probability, and notes. Flag any deal where last contact date is more than 14 days ago.

Every Monday morning, pull all deals where last contact date is older than 14 days and status is not Closed or Dead. For each one, draft a re-engagement email to the broker contact on file. Use the deal notes to personalize — mention the property address and the last thing we discussed. Queue them for my review before sending.

Show me all open tasks across my deals sorted by due date. Anything overdue should be at the top. Let me capture new tasks by typing them in chat — for example: 'remind me to send the estoppel checklist to the seller on 412 Oak St by Thursday.'

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

Walkthrough

Step-by-step

1 Open the CRM starter app and describe your acquisition pipeline stages and deal fields in plain language — Starch builds the schema around how you actually track deals, not a generic sales template.

2 Import your existing deal contacts from HubSpot or your Google Sheet. Connect HubSpot from Starch's integration catalog; the agent queries it live during the import and maps fields to your new schema.

3 Tell Starch to flag any deal where the last contact date field is more than 14 days old and the status is not Closed or Dead — this becomes your stale deal view, always live.

4 Wire up Gmail: Starch syncs your Gmail data on a schedule and threads email history to each contact record, so you can see every exchange with a broker without leaving the CRM.

5 Set up the weekly stale deal automation: every Monday at 7am, Starch pulls every flagged deal, reads the deal notes, and drafts a broker re-engagement email personalized to the property and the last conversation.

6 Review the drafted emails in the Email Agent queue — edit if needed, one-click send, or mark the deal Dead if the opportunity has passed. This is a 10-minute Monday ritual instead of a two-hour quarterly scramble.

7 For any deal that gets re-engaged, update the last contact date and stage directly in the CRM via chat — type 'move 412 Oak St to LOI Submitted, last contact today' and it updates.

8 Use the Task Manager to capture deal-specific action items as they come up — estoppel checklists, lender calls, LP soft-circle follow-ups — tied to due dates and cross-referenced against your calendar.

9 Set an overdue alert: any task that passes its due date surfaces at the top of your task list and sends you a Slack message — Starch connects directly to Slack — so nothing quietly expires.

10 At the end of each month, ask Starch: 'How many deals moved from Underwriting to LOI this month, and which ones went stale and why?' Get a plain-English summary with deal names and dates, not a pivot table you have to build yourself.

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

Q1 2026 Pipeline Cleanup — 11 Stale Deals Reviewed

Sample numbers from a real run

47 Commerce Park (Industrial, 85k SF)	4,200,000
1801 Meridian Ave (Multifamily, 32 units)	6,750,000
Westgate Retail Strip (Retail, 12k SF)	1,850,000
Brookfield Flex Portfolio (3 assets)	11,000,000
LP soft-circle re-engagements sent	4

Going into Q1 review, 11 deals had been sitting untouched for more than 21 days. The Monday automation surfaced all of them on January 6th. For 47 Commerce Park — an $4.2M industrial asset in Underwriting since November — Starch drafted a re-engagement email to the listing broker referencing the November site visit and asking if the seller had reconsidered pricing given the December rate move. That email went out Tuesday morning, and by Thursday the broker had come back with a $180k price reduction. 1801 Meridian Ave had slipped because the GP forgot to send a revised rent roll request after the first one came back incomplete; the task that should have tracked that never got created. With Starch, that follow-up task would have been auto-generated from the deal note that said 'rent roll needs revision.' Four of the 11 stale deals were marked Dead — legitimate, but having that logged means the next time a similar asset hits the market, you have context on why you passed. The Brookfield Flex Portfolio re-engagement led to a second call and is now back in active Underwriting.

Measurement

How you'll know it's working

Number of deals with last contact date > 14 days (stale pipeline count)

Stage conversion rate: Underwriting → LOI submitted (monthly)

Average days from first contact to LOI for closed acquisitions

Broker re-engagement response rate (drafted emails sent vs. replies received)

Number of overdue deal tasks per week

Comparison

What this replaces

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

HubSpot (free or Starter tier)

HubSpot's pipeline works fine for SaaS sales teams but its deal schema doesn't map to real estate fields like asset class, cap rate, or property address without heavy custom property setup and an admin to maintain it — and it won't auto-flag stale deals or draft broker emails without a paid Sales Hub seat.

Google Sheets deal tracker

Fast to set up, zero cost, and you already have one — but it won't email you when a deal goes stale, can't pull Gmail thread history, and turns into an archaeology project when you need to reconstruct why a deal died six months ago.

Salesforce (with a CRE-specific overlay like Rethink or REsimpli)

Purpose-built for commercial real estate pipelines, but you're looking at $150–$300/user/month, a multi-week implementation, and a platform that still won't connect your deal pipeline to your LP investor communications or your bank feed without a second integration layer.

Pipedrive

Clean pipeline UI and easier to configure than Salesforce, but custom fields require manual setup per deal type, there's no native 'stale deal' alert logic without a third-party automation tool, and it doesn't read your Gmail threads to surface deal context automatically.

On Starch RECOMMENDED

One platform — crm, email agent, task manager 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

I already have contacts in HubSpot. Do I have to rebuild everything from scratch?

No. Connect HubSpot from Starch's integration catalog and the agent queries it live during import, pulling your contacts, companies, and deal history into your new Starch CRM. You'll describe how you want the fields mapped — for example, 'map HubSpot's Deal Name to Property Address in Starch' — and Starch handles the translation. You're not starting from zero; you're cleaning up the mess you already have.

Will Starch actually send re-engagement emails automatically, or does a human still have to approve them?

You control the send step. The automation drafts the emails and queues them for your review every Monday morning. You read, edit if needed, and send with one click — or delete the ones for deals you've decided to pass on. Starch doesn't send unsupervised emails to brokers on your behalf unless you explicitly configure it to. For a $4M acquisition relationship, you probably want to stay in the loop.

What if my broker contacts aren't in Gmail — they're in a separate spreadsheet or a business card app?

You can import contacts manually into the CRM by uploading a CSV, or connect Google Sheets from Starch's integration catalog and have the agent pull the contact list directly. Once the contacts are in Starch, Gmail sync ties email thread history to each record going forward.

Is Starch SOC 2 certified? I have investors who ask about data security.

Starch is not SOC 2 Type II certified today — that's honest. If SOC 2 is a hard requirement for your LP agreement or fund documents, that's worth factoring in. For most operator founders running their own deal pipeline, it's not a blocker, but you should make that call based on your own data governance requirements.

Can Starch track deals that come from off-market sources, like a broker's deal sheet they email as a PDF?

Yes. If the broker emails you a deal sheet, Gmail sync surfaces that thread in your CRM automatically. You can then tell Starch 'create a new deal from this email — property is 412 Oak St, asset class industrial, asking $3.8M, broker is Mike Torres' and it populates the record. For deal sheets posted on broker portals or CoStar, Starch automates those sites through your browser — no API needed — so you can pull property data into a deal record without copy-pasting.

What happens to deals I mark Dead? Can I search them later?

Dead deals stay in your CRM — they're just filtered out of active pipeline views. You can search them by property address, asset class, broker, or the reason you logged for passing. That history matters: when a similar asset hits the market a year later, you want to know you passed on a comparable at $180 cap rate in Q3 because of deferred maintenance, not rediscover it from scratch.