How to build an outbound email sequence as Small Law and Accounting Practices

Sales & CRMFor Small Law and Accounting Practices2 apps11 steps~22 min to set up

At a six-attorney firm or four-CPA practice, outbound email to prospects and referral sources is a Friday-afternoon project nobody has time for. An associate pulls the last three emails from Outlook, checks the matter notes in Clio or the client file in QuickBooks, tries to remember whether the managing partner already followed up, and writes something that sounds like it came from a template — because it did. Referral partners go cold because no one sent a check-in after the last referral closed. Prospective clients who requested a consultation in October get nothing in November. There is no sequence; there is only whoever remembered to send something that week.

Sales & CRMFor Small Law and Accounting Practices2 apps11 steps~22 min to set up
Outcome

What you'll set up

A rolling outbound email sequence that drafts personalized follow-ups for prospects and referral sources by pulling live context from Outlook and your CRM — so every message references the last interaction, not a generic opener
A contact-stage pipeline in Starch's CRM that tracks where each prospect or referral partner sits (first touch, awaiting response, active matter, closed-won, dormant) so you know exactly who is overdue for contact
Automated draft generation on a cadence you set — Monday morning, Starch surfaces the five prospects who haven't heard from you in 21 days and drafts an Outlook message for each, ready for one-click review and send
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
Data sources & config

Starch syncs your Outlook data on a schedule (emails, calendar events, contacts) so the CRM and Email Agent have fresh thread history without manual imports. Your CRM contact records and stage data live in Starch and are queried live when the Monday automation runs. Outlook drafts are written and queued through Starch's direct Outlook connection — no copy-pasting between tools.

Prompts to copy
Build me a CRM for a six-attorney litigation firm. Stages are: Initial Inquiry, Conflict Check Pending, Consultation Scheduled, Engagement Letter Sent, Active Matter, Closed Won, Referral Source. Fields I care about per contact: last contact date, matter type (employment, commercial, family), referring attorney or firm, estimated matter value, and any open tasks. Pull email thread history from Outlook so I can see the last message without leaving the record.
Build me an outbound email sequence automation. Every Monday morning, pull contacts from my CRM where last contact date is more than 21 days ago and stage is Initial Inquiry, Consultation Scheduled, or Referral Source. For each contact, draft a short follow-up email in Outlook using the contact's name, matter type, and the subject line of the last email thread. Queue the drafts for my review — don't send automatically. Flag anyone who has been in the same stage for more than 45 days.
Set up an Email Agent for my Outlook inbox. Triage incoming messages by whether they are from an active client, a prospect in my CRM, or a referral source. For messages from prospects, summarize the thread and draft a reply. Remind me 48 hours after any message from a prospect if I haven't responded.
Run these in Starch → or paste them into your favorite agent
Walkthrough

Step-by-step

1 Connect Outlook: Starch syncs your Outlook messages, calendar events, and contacts on a schedule. Thread history becomes available inside every CRM contact record automatically.
2 Install the CRM starter app from the Starch App Store and describe your firm's pipeline in plain English — stages, custom fields (matter type, referring attorney, estimated value), and any tagging logic you use today in a spreadsheet.
3 Import your existing prospect and referral-source list. Paste a CSV from your current spreadsheet or describe the contacts you want to seed; Starch maps the fields and cleans up duplicates.
4 Tell Starch what 'stale' means for your practice: 'Flag any prospect I haven't emailed in 21 days. Flag any referral source I haven't contacted in 45 days. Surface both lists every Monday at 8 a.m.'
5 Install the Email Agent app. Configure it to triage your Outlook inbox by contact type: active client, CRM prospect, referral source, or unknown. Summarize threads longer than five messages so you're not re-reading a chain before replying.
6 Set the outbound draft automation: every Monday morning, Starch pulls the stale-contact list from your CRM, reads the last Outlook thread for each contact, and drafts a short follow-up that references the prior conversation — no generic openers.
7 Review the draft queue each Monday. Starch presents each draft with a one-sentence thread summary and the contact's current stage. Approve, edit, or skip. Outlook sends only what you approve.
8 After each send, Starch logs the contact date and resets the 21-day or 45-day clock in the CRM automatically. The pipeline view updates without you touching it.
9 Ask the CRM natural-language questions as needed: 'Who referred the most matters last quarter?' or 'Which prospects have been stuck in Consultation Scheduled for more than 30 days?' — and get a real answer from your live Outlook and CRM data.
10 For referral sources at firms that have a web portal or LinkedIn presence, Starch can automate a check-in comment or connection message through browser automation — no API needed. Describe the rule: 'If a referral source posts on LinkedIn and I haven't contacted them in 30 days, draft a brief comment for my review.'
11 At the end of each month, ask Starch to generate a plain-English outbound summary: how many prospects moved stages, how many referral sources were contacted, how many drafts were approved vs. skipped — so you can see whether the sequence is actually running.

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 Referral Reactivation — March Push

Sample numbers from a real run
Referral sources contacted (January–February)4
Referral sources flagged stale by Starch on March 311
Drafts generated by Starch on March 3 morning run11
Drafts approved and sent by managing partner9
New matters opened attributed to reactivated referral sources by March 313
Estimated matter value (blended avg $18,500 per matter)55,500

Going into March, the managing partner at a four-attorney employment firm realized she had personally emailed only four of her fifteen referral partners since the new year — the rest had gone cold while she was handling a trial. On Monday March 3, Starch's weekly automation ran against her CRM and flagged eleven referral sources with no Outlook contact in more than 45 days. It pulled the last email thread for each — a mix of case referral acknowledgments, holiday notes, and a lunch invitation that was never answered — and drafted eleven short follow-ups, each referencing the last interaction by name and matter type. The managing partner spent 22 minutes reviewing the queue, approved nine, edited one to add a specific case outcome the referring attorney would appreciate, and skipped one who had since retired. By month-end, three of those nine contacts had sent new matters: a wage-and-hour case ($22,000 estimated), a wrongful termination referral ($18,000), and a non-compete dispute ($15,500). The sequence ran without a paralegal touching it.

Measurement

How you'll know it's working

Referral-source contact rate: percentage of active referral sources contacted within the last 45 days
Prospect stage velocity: average days a prospect spends in Consultation Scheduled before moving to Engagement Letter Sent or Closed Lost
Draft approval rate: percentage of Starch-generated outbound drafts approved as-is vs. edited vs. skipped — a proxy for prompt quality
Matters attributed to reactivated contacts per quarter
Inbox response time on prospect emails (target: under 48 hours)
Comparison

What this replaces

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

Clio Manage built-in email tools
Clio tracks matter communications but has no outbound sequence logic and won't draft emails from thread history or flag stale referral sources.
HubSpot Sequences
HubSpot does outbound sequences well but requires an admin to configure, doesn't connect to Clio or QuickBooks, and bills at a scale that makes no sense for a six-attorney firm.
Mailchimp or Constant Contact
Fine for newsletters; useless for personalized one-to-one follow-ups where each draft needs to reference the specific last Outlook thread and matter type.
Karbon
Karbon is strong for CPA workflow management and client communication tracking, but it doesn't generate outbound drafts or run automated referral-reactivation sequences from your contact history.
Manual Outlook + spreadsheet
What most small practices actually do today — costs roughly three hours of attorney time per week and produces inconsistent follow-up with no visibility into who fell through the cracks.
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

Will Starch send emails automatically without my review?
Only if you tell it to. The default setup queues drafts in Outlook for your review before anything goes out. You approve, edit, or skip each one. If you want a specific category — say, a 'thanks for the referral' note — to send automatically after you describe and approve the template, you can configure that separately.
Does Starch connect to Clio or MyCase for matter context?
Clio and MyCase are reachable from Starch's integration catalog of 3,000+ apps, so the agent can query them live when building your CRM or drafting emails. They don't have a scheduled-sync connection today, so Starch queries the data live rather than storing a copy on a refresh cycle. For most outbound sequence use cases — pulling a client name, matter type, and last-contact context — live querying is enough.
What about conflict checks — can Starch flag a conflict before I send an outbound email to a prospect?
You can describe a conflict-check rule in plain English and Starch will build the logic: 'Before generating a draft for any new prospect, check whether their employer or opposing party appears in my active-matter list in the CRM.' It won't replace a formal conflict-check system, but it can surface a flag so you don't send an email to someone you're already adverse to.
Is my client and prospect data stored in Starch? What are the security considerations?
Starch stores the data it syncs from your connected tools (Outlook threads, CRM records you create inside Starch). Starch is not SOC 2 Type II certified today — that's worth knowing before you decide how sensitive the data you sync should be. For a small practice, most attorneys find the risk profile comparable to other SaaS tools they already use, but it's a real question and you should evaluate it against your state bar's guidance on cloud storage of client data.
We use Gmail instead of Outlook. Does this work?
Yes. Starch syncs your Gmail data on a schedule — messages, labels, thread history — exactly the same way it connects to Outlook. The Email Agent and CRM work identically whether you're on Gmail or Outlook.
Can the CRM track both prospects and existing referral-source relationships in the same place?
That's exactly what it's built for at a practice this size. You describe the contact types you need — Prospect, Referral Source, Active Client, Former Client — and Starch builds the pipeline with separate stages and field sets for each. You can ask it 'show me all referral sources who sent more than two matters last year and haven't heard from us in 60 days' and get a real list, not a manual filter exercise.

Ready to run build an outbound email sequence on Starch?

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

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