Sales & CRM

How to clean up stale deals in your pipeline as CPG Founders

Sales & CRMFor CPG Founders3 apps11 steps~22 min to set up

Your wholesale pipeline is a graveyard. You've got 15 accounts sitting in 'proposal sent' that you emailed three months ago — a regional grocery buyer, a couple of natural food distributors, a few food service leads from a trade show — and you have no idea which ones are actually worth chasing versus which ones ghosted you permanently. You're tracking this in a spreadsheet or a cobbled-together HubSpot trial you never fully configured, and neither tells you that the UNFI buyer hasn't responded in 47 days or that you promised to send updated slotting terms to a Midwest chain and never did. Stale deals don't just waste your time — they distort your revenue forecast and delay decisions about your next production run.

Build this on Starch → See the apps used

Sales & CRMFor CPG Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A CPG-specific deal pipeline with fields that actually matter to wholesale sales — buyer name, chain/distributor, door count, slotting status, expected first-order date, and last contact date — so you can see at a glance what's alive and what's dead

Automated stale-deal alerts that flag any account with no email activity in 21+ days and draft a follow-up you can send in one click, pulling context from the actual thread history

A weekly pipeline review task that surfaces your top three overdue accounts every Monday so you're never walking into a forecast conversation blind

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 email thread history and last-contact dates flow directly into your CRM deals without manual logging. Connect your existing spreadsheet or HubSpot export from Starch's integration catalog — the agent queries it live to import your current pipeline on day one. Task Manager surfaces follow-up tasks inside the same workspace.

Prompts to copy

Build me a wholesale CRM for a CPG brand. Stages should be: Prospect, Intro Sent, Sample Requested, Proposal Out, Negotiating, Slotting Confirmed, First PO Received, Churned. Fields per deal: buyer name, account type (independent retailer / regional chain / national chain / distributor / food service), door count, slotting fee agreed, expected first order date, last contact date, and notes on SKUs discussed. Flag any deal where last contact date is more than 21 days ago.

Every Monday morning, look at my CRM and email history. Find every deal that's been sitting in 'Proposal Out' or 'Negotiating' for more than 3 weeks with no reply. For each one, draft a short follow-up email that references the last thing we discussed, and create a P1 task for me to review and send it.

Show me all deals tagged 'Intro Sent' where I never logged a follow-up and the intro was sent more than 14 days ago. Create a task for each one with a suggested next action.

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

Walkthrough

Step-by-step

1 Connect Gmail: Starch syncs your Gmail data on a schedule, pulling in thread history, sent timestamps, and contact metadata — this is what powers the 'last contact date' field across all your wholesale accounts.

2 Import your existing pipeline: paste your spreadsheet or connect HubSpot from Starch's integration catalog so the agent queries your current deals live and maps them into the new schema. Starch cleans up duplicate contacts and normalizes stage names during import.

3 Tell Starch how CPG wholesale actually works: describe your stages (Prospect → Intro Sent → Sample Requested → Proposal Out → Negotiating → Slotting Confirmed → First PO Received) and the fields you care about — door count, slotting fee, expected first-order date, SKUs in discussion.

4 Set your staleness threshold: tell Starch that any deal with no email activity for 21+ days should be flagged automatically. You pick the number — 21 days is aggressive for a national chain buyer; 10 days may be right for an independent retailer.

5 Let Email Agent scan your existing threads: it reads your Gmail history and backfills last-contact dates for every account in your pipeline, so you're not starting with blank fields on day one.

6 Review the stale-deal report Starch generates on first run: you'll likely find 30–50% of your 'active' pipeline is actually cold. Triage each one — archive it, restart with a fresh angle, or mark it lost.

7 Use Email Agent's drafted follow-ups: for each flagged account, review the AI-drafted email (it will reference the last thing you discussed — a sample request, a pricing conversation, a show meeting), edit if needed, and send.

8 Set the Monday morning automation: tell Starch to run a pipeline review every Monday at 8 AM, surface your top three most-overdue accounts, and create a P1 task in Task Manager for each one with a one-sentence recommended next action.

9 Ask the CRM natural-language questions as you work: 'Which accounts requested samples but never moved to Proposal Out?' or 'Show me every distributor contact I haven't spoken to in 30 days' — Starch answers from live deal and email data, not canned reports.

10 Close or archive dead deals deliberately: once you've followed up twice with no response, use a prompt like 'Mark the Kroger Midwest opportunity as lost, note reason as unresponsive after two follow-ups, and remove it from my active forecast.' Clean pipeline, honest forecast.

11 Use the pipeline to inform your next production run decision: a clean view of deals in 'Slotting Confirmed' and 'First PO Received' gives you the demand signal you need to plan inventory, instead of guessing based on a stale spreadsheet.

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 wholesale pipeline cleanup — natural snack brand, 12 active deals

Sample numbers from a real run

KeHE Distributors — intro sent Jan 8, no reply	0
Sprouts regional buyer — proposal out Feb 2, slotting terms pending	45,000
Foxtrot (regional) — sample sent Dec 2025, went cold	12,000
Whole Foods Midwest — negotiating since Jan 15, 38 days stale	90,000
UNFI — first contact Nov 2025, never followed up	0
3 independent natural retailers — intro sent, no follow-up logged	8,400

A founder running a better-for-you snack brand used Starch to audit their Q1 pipeline on March 3rd. Of 12 deals they considered 'active,' Starch flagged 7 as stale based on Gmail sync data. The Whole Foods Midwest deal — a potential $90,000 first order across 180 doors — had been sitting in 'Negotiating' for 38 days with no outbound email after the buyer asked for a revised slotting fee structure. Email Agent drafted a follow-up that referenced the January 15th call and the specific $1.20/SKU slotting ask, which the founder sent within 10 minutes. The UNFI lead — contacted in November and never followed up — was marked lost and removed from the forecast, which had been inflating the brand's projected Q2 revenue by roughly $60,000. After the cleanup, the founder had 5 genuinely live deals with a realistic combined pipeline of $155,400 and a Monday task list that told her exactly who to call that week.

Measurement

How you'll know it's working

Days since last contact per deal (staleness metric — CPG wholesale cycles are slow; 30+ days in Negotiating without contact is a red flag)

Deals in 'Proposal Out' older than 21 days as a percentage of total active pipeline

First PO conversion rate by account type (independent retailer vs. regional chain vs. distributor)

Slotting fee total committed vs. recovered in first orders

Pipeline-to-production lead time: how many 'Slotting Confirmed' deals are 60+ days from expected first PO (informs your co-packer scheduling)

Comparison

What this replaces

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

HubSpot Starter/Professional

HubSpot has far more features and a mature ecosystem, but you'll spend weeks configuring it for CPG-specific fields, pay $500–$1,600/month for anything useful, and still need to manually correlate email activity with deal stage updates.

Airtable pipeline tracker

Airtable is flexible and free to start, but it doesn't read your Gmail to auto-update last-contact dates, so staleness tracking only works if you log every email manually — which you won't.

Google Sheets + manual review

Zero cost and infinite flexibility, but there's no automation, no email integration, and your 'pipeline review' happens whenever you remember to open the tab, which is not every Monday.

Salesforce Essentials

More robust than HubSpot at similar price points, but the configuration overhead is higher and it's built for sales teams, not solo CPG founders who also run co-packer calls and FSMA compliance in the same week.

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

Does Starch actually read my Gmail, or does it just pull contact metadata?

Starch syncs your Gmail data on a schedule — that includes the actual message content, thread history, timestamps, and labels. This is how it knows the last time you emailed the Sprouts buyer and what you discussed, not just that a contact exists. Worth noting: Gmail message sync is capped at 30 messages per page to avoid errors on long HTML threads, and the OAuth consent screen currently shows the underlying connector's name rather than Starch's — that's on the roadmap to fix.

I already have deals in HubSpot. Do I have to start over?

No. Connect HubSpot from Starch's integration catalog — the agent queries it live — and tell Starch to import your existing deals into the new pipeline. It will map your HubSpot stages and fields to the schema you describe, clean up duplicates, and carry over contact history. You can run both in parallel while you migrate, or cut over immediately.

Will this work for distributor relationships (KeHE, UNFI) as well as direct retail buyers?

Yes. The CRM schema is whatever you describe — you can have separate pipeline stages or account types for distributors versus direct retail versus food service, with different fields per type if you want (e.g., distributors might have 'authorized SKUs' and 'warehouse location' fields that don't apply to a direct retailer). Just tell Starch how your relationship structure works.

What if a broker manages some of my accounts? Can I track broker relationships separately?

Yes. You can add a broker field to any deal and use the Sales Agent CRM template as a starting point — it's designed for tracking deals and tasks through intermediary relationships. Tell Starch to include broker name, commission rate, and last broker check-in date as fields, and you can query across them the same way you would any other deal data.

I'm not SOC 2 certified — is Starch?

Starch is not SOC 2 Type II certified today. If your retail or distributor partners require vendor SOC 2 compliance (some larger chains ask for this), that's worth knowing upfront. For most CPG founders at the early wholesale stage, this isn't a blocker — but it's an honest limitation.

Can Starch help me send follow-ups directly, or just draft them?

Both. Email Agent drafts the follow-up with context from your thread history, and you can review and send it with one click — the send goes through your own Gmail account, not a third-party sender, so there's no deliverability issue. You can also set rules to auto-send low-stakes follow-ups (like a 'just checking in' after 30 days of silence) without reviewing each one, though for high-value wholesale accounts you'll probably want eyes on every outbound.