Sales & CRM

How to clean up stale deals in your pipeline as Small Law and Accounting Practices

Sales & CRMFor Small Law and Accounting Practices2 apps12 steps~24 min to set up

Your pipeline in Clio or a shared spreadsheet has thirty open matters or prospects that haven't moved in sixty, ninety, sometimes a hundred and twenty days. Nobody deletes them because nobody's sure if they're truly dead — maybe opposing counsel went quiet, maybe the client said 'call me after tax season.' Your intake coordinator is tracking follow-ups in Outlook drafts. Your partners are reconstructing last contact dates from calendar searches on Friday afternoons. You have no single view that shows every stale matter, the last email sent, who owns the follow-up, and whether the deal is genuinely dormant or just waiting on a third party. So stale deals sit, inflate your pipeline, and make your capacity look fuller than it is.

Build this on Starch → See the apps used
Sales & CRMFor Small Law and Accounting Practices2 apps12 steps~24 min to set up
Outcome

What you'll set up

A live deal-hygiene dashboard that surfaces every matter or prospect that hasn't had an Outlook or Gmail thread in 30+ days, sorted by partner and practice area
Automated weekly digest that drafts a status-check email for each stale contact so you can review and send in minutes instead of reconstructing context from five places
A clean, archived pipeline that reflects real capacity — so intake decisions, staffing, and partner reviews are based on actual open work, not ghost matters from Q3
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
Data sources & config

Starch syncs your Outlook data on a schedule (messages, events, contacts) and your QuickBooks data on a schedule (invoices, payments — to cross-reference whether a matter has any open billing before archiving it). The CRM and Email Agent apps are wired to both. Clio and MyCase are reachable through Starch's integration catalog, queried live when the pipeline view loads. LawPay can be automated through your browser — no API needed — to pull outstanding balance status per client.

Prompts to copy
Build me a CRM for our law practice. Pipeline stages are: Intake Inquiry, Conflict Check, Engagement Letter Sent, Active Matter, Awaiting Client, Awaiting Third Party, Closed Won, Closed Lost. Fields per deal: client name, matter type (litigation / transactional / tax / estate), originating partner, last contact date, last contact method (email / call / meeting), days since last contact, and a free-text status note. Flag any deal where days-since-last-contact exceeds 30 and the stage is not Closed.
Connect our Outlook inbox. Every Monday at 8 a.m., scan all deals flagged as stale (30+ days, stage not Closed). For each one, draft a short client-status email that references the matter type, the last thing we discussed, and asks a specific next-step question. Put drafts in a review queue so the originating partner can approve or edit before anything sends.
Show me a pipeline view grouped by partner. For each partner, show total open deals, average days since last contact, and count of deals stale over 30 / 60 / 90 days. Let me click into any deal and see the last three email threads pulled from Outlook.
Run these in Starch → or paste them into your favorite agent
Walkthrough

Step-by-step

1 Connect Outlook (or Gmail) so Starch syncs your message history on a schedule — this is what powers last-contact-date and thread-preview without anyone manually logging calls.
2 Connect QuickBooks so Starch syncs invoice and payment data on a schedule — you need to know whether a 'stale' prospect still has an unpaid engagement invoice before you archive them.
3 Start from the CRM app in the Starch App Store and fork it for your practice: tell Starch your pipeline stages (Intake Inquiry through Closed), your matter types, and which fields matter to your partners.
4 Import your existing contact list — from a CSV export of Clio, a spreadsheet, or directly from Outlook contacts — and let Starch map the fields and flag obvious duplicates.
5 Run the prompt: 'Which matters or prospects have had zero email activity in the last 30 days and are not in a Closed stage? List them by partner with the last contact date and last subject line.' This is your first real stale-deal report.
6 For each stale deal, decide on one of three dispositions: Re-engage (draft a follow-up), Waiting on Third Party (update stage, snooze 30 days), or Archive (move to Closed Lost with a note). Starch lets you do this inside the CRM view.
7 Set up the Email Agent automation: every Monday morning, for every deal still flagged stale, draft a re-engagement email pulling the client name, matter type, and last thread subject from Outlook. Drafts go to a review queue — nothing sends without a partner's approval.
8 Add a QuickBooks cross-check step: before any deal is auto-archived, Starch checks whether there's an open invoice in QuickBooks for that client. If yes, the deal gets flagged 'billing open — do not archive' so your bookkeeper can reconcile first.
9 Build a partner-level pipeline dashboard: total open matters, average days since last contact, and a stale-deal count by 30 / 60 / 90-day buckets per partner. This becomes the standing agenda item for your weekly partner meeting.
10 Schedule a monthly 'pipeline cleanse' automation: on the first Monday of each month, Starch generates a list of all deals stale 60+ days, attaches the last email thread summary, and Slacks it to the managing partner for a go / no-go decision on each.
11 For matters in Clio or MyCase, connect those tools from Starch's integration catalog so deal status updates you make in the Starch CRM can reference the official matter record without double-entry.
12 After the first cleanse, use the cleaned pipeline to reset capacity estimates: 'Show me total active matters per partner, excluding anything Closed or snoozed. Which partners have capacity to take a new engagement this month?'

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

April 2026 Pipeline Cleanse — 4-Partner Accounting Practice

Sample numbers from a real run
Deals in pipeline (before cleanse)47
Deals flagged stale 30+ days19
Deals flagged stale 60+ days11
Deals with open QuickBooks invoice (do not archive)4
Re-engagement emails drafted by Email Agent9
Deals archived after partner review8
Clean active pipeline after cleanse35

Going into April, the practice's shared spreadsheet showed 47 open prospects and active client matters across four CPAs. Nobody had touched 19 of them in more than 30 days. Starch pulled the Outlook sync and surfaced that 11 of those 19 had zero email activity in 60+ days — including three tax planning engagements from November that the client had never formally declined, they'd just gone quiet after the initial proposal. The QuickBooks sync flagged four of the stale deals as having open invoices (two for prior-year returns, two for bookkeeping retainer balances), so those were held out of the archive queue automatically. For the remaining nine stale-but-not-billed contacts, the Email Agent drafted individual re-engagement emails referencing the specific service discussed and the last email subject line — 'Following up on the S-corp election analysis we outlined in November' — which one of the CPAs said took her thirty seconds to review and send rather than the usual twenty minutes of context-reconstruction. Eight deals were archived as genuinely lost. The live pipeline shrank from 47 to 35, but those 35 were real — and for the first time, the managing partner's Monday morning dashboard showed which of the four CPAs had actual capacity for new April engagements.

Measurement

How you'll know it's working

Average days since last client contact, by partner and by matter type
Stale-deal rate: percentage of open pipeline untouched in 30+ days
Pipeline-to-capacity ratio: active matters per partner vs. target billable capacity
Re-engagement response rate: replies received within 7 days of stale-deal outreach email
Time from intake inquiry to engagement letter sent (reveals where matters stall most often)
Comparison

What this replaces

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

Clio Manage
Tracks official matters well but has no cross-partner stale-deal view, no AI-drafted re-engagement emails, and can't pull in QuickBooks billing status to gate archiving decisions.
HubSpot CRM (free or Sales Hub)
More feature-complete as a standalone CRM, but requires an admin to configure stages for legal or accounting workflows, doesn't sync Outlook threads automatically without paid add-ons, and can't draft matter-specific follow-up emails from thread context.
Karbon or TaxDome
Purpose-built for accounting workflow management, but neither generates natural-language pipeline health queries ('who haven't I spoken to in 60 days?') or drafts client emails from your actual thread history.
Spreadsheet + Outlook reminders
What most small practices use today — zero cost, but the 'last contact date' field is only as accurate as whoever remembered to update it last Friday, and there's no automated draft queue for re-engagement.
Salesforce (Essentials or Starter)
Handles pipeline tracking at scale, but setup time for a 4–6 person professional services firm is measured in weeks, and it won't draft a client-status email that references your actual Outlook thread without a paid Einstein add-on and custom configuration.
On Starch RECOMMENDED

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

We use Clio as our official matter management system. Does Starch replace it or sit alongside it?
Alongside. Clio handles the official matter record, time entries, and trust accounting — Starch connects to it from the integration catalog and queries it live when your pipeline dashboard loads. You're not re-entering data; you're building a layer on top that does what Clio doesn't: cross-partner stale-deal views, AI-drafted follow-up emails, and QuickBooks billing cross-checks.
Will Starch send emails automatically, or do we have to approve each one?
You control that. The default setup puts every draft into a review queue — the originating partner sees a draft, edits if needed, and clicks send. If you eventually trust the drafts enough to auto-send certain categories (e.g., a standard 30-day check-in for tax planning prospects), you can configure that, but nothing sends without your explicit choice to set it up that way.
Our Outlook OAuth screen shows a connector name we don't recognize. Is that normal?
Yes — the Gmail and Outlook OAuth consent screens currently show the underlying connector's name rather than 'Starch.' A Starch-branded verification is on the roadmap. Your data still syncs to Starch only; this is a display issue, not a security one.
We use MyCase, not Clio. Does that work?
MyCase is reachable from Starch's integration catalog, so the agent can query it live when your apps run. It's not a scheduled-sync provider the way Outlook and QuickBooks are, so data is pulled on demand rather than stored in Starch's database. For pipeline hygiene purposes — checking stage, matter type, last update — live querying is fine.
Is Starch SOC 2 certified? Our clients ask about data security.
Not yet — Starch is not SOC 2 Type II certified as of today. If your firm's client agreements or bar compliance requirements mandate SOC 2 certification in your tooling, that's a real constraint worth knowing upfront. It's on the roadmap.
What happens to a deal that has an open QuickBooks invoice when we try to archive it?
Starch flags it and blocks the archive action, tagging it 'billing open — do not archive.' Your bookkeeper or billing coordinator sees it in a separate reconciliation queue. You decide whether to write it off, collect first, or keep the deal open. Starch won't make that call; it just makes sure you don't accidentally lose billing context.
We already have a paralegal who manages this manually. Why does she need Starch?
She probably doesn't need Starch to replace what she does — she needs it to stop doing the parts that take an hour and could take five minutes. Reconstructing last-contact dates from Outlook search, drafting a dozen status emails from scratch, pulling QuickBooks to check invoice status before archiving: those are the tasks Starch automates. What stays with her is judgment — which deals are actually dead, which clients need a call rather than an email, how to handle a sensitive re-engagement. That's not automatable and shouldn't be.

Ready to run clean up stale deals in your pipeline on Starch?

Request closed-beta access. Everything is free during beta.

You're on the list! We'll be in touch soon.