Sales & CRM

How to build a strategic account plan as Small Law and Accounting Practices

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

You're preparing for a meeting with a mid-size real estate developer who's been a client for three years. The relevant context is spread across: a Clio matter file, a QuickBooks invoice history, six months of Outlook threads, a calendar showing four prior meetings, and whatever the billing partner remembers. You spend 45 minutes pulling it together into a Word doc that nobody else will ever find. The next time a junior associate needs to brief themselves on this client, they'll do the same 45 minutes. There's no account plan — there's just institutional memory leaking out the door every time someone leaves.

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 living account plan for each client that pulls matter history, billing totals, upcoming deadlines, and email context into one place — updated automatically, not reconstructed every Monday

A CRM built around how your practice actually works: matter stages instead of sales stages, responsible attorney instead of deal owner, statute of limitations instead of close date

A brief-ready summary you can hand a junior associate in 30 seconds — or send to a client before a quarterly check-in — without opening five applications

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 Knowledge Management

Data sources & config

Starch syncs your QuickBooks data on a schedule (invoices, payments, client billing totals). Starch syncs your Outlook messages and calendar events on a schedule. Clio and MyCase are connected from Starch's integration catalog; the agent queries them live when your account plan app runs. LinkedIn enrichment for client contacts runs through browser automation — no API needed.

Prompts to copy

Build me a CRM for a six-attorney litigation firm. Each record should represent a client, not a matter. Fields: responsible attorney, active matters with status, total billed YTD pulled from QuickBooks, last email date from Outlook, next court date or filing deadline, client tier (A/B/C), and a notes field for relationship context. Pipeline stages: Intake Review, Active Engagement, Pending Renewal, Dormant.

Create a knowledge base template for client account plans. Each plan should have sections for: client background (industry, key contacts, years with the firm), matter history summary, billing relationship (average annual fees, payment history), open items and deadlines, and a 'brief for new associate' section that summarizes everything in two paragraphs. Auto-flag any plan that hasn't been updated in 90 days.

Every Sunday night, pull the prior week's Outlook emails and QuickBooks activity for each active client in my CRM. Update the 'last contact' date, append any new invoice amounts to YTD billing, and flag any client where we had billable activity but no email contact in the past 30 days.

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

Walkthrough

Step-by-step

1 Connect QuickBooks as a scheduled-sync provider. Starch pulls invoices, payments, and client billing history automatically — you get YTD fees and payment status for every client without opening QuickBooks.

2 Connect Outlook (or Gmail) as a scheduled-sync provider. Starch indexes message threads by client so the CRM always knows the last contact date and can surface relevant email context in any account plan.

3 Connect your practice management tool — Clio, MyCase, or Karbon — from Starch's integration catalog. The agent queries matter status, deadlines, and responsible attorney live when any account plan surface needs it.

4 Start with the Starch CRM app and describe your schema: tell Starch you want client records (not matter records), what fields matter to your practice, and what your relationship stages actually look like for a law or accounting firm.

5 Ask Starch to build an account plan template inside the Knowledge Management app. Describe the sections you want — matter history, billing relationship, open deadlines, and a two-paragraph associate brief — and Starch builds the structure.

6 For each of your top 20 clients, have Starch generate the initial account plan by pulling from QuickBooks billing history, Outlook thread history, and your practice management system. Review and annotate; the AI drafts, you approve.

7 Set up a weekly automation: every Monday at 7 a.m., Starch refreshes the YTD billing totals from QuickBooks, checks Outlook for new threads, and updates the 'last contact' and 'open items' fields across all active client records.

8 Add a dormancy alert: ask Starch to flag any client where total billed in the past 12 months exceeded $10,000 but there's been no email contact in 45 days. Send those flags to the responsible attorney as an Outlook email each Friday.

9 Before a client meeting, open the account plan for that client. The plan shows last meeting date, open matters, YTD billing, any unanswered emails, and the associate brief — everything the billing partner would have carried in their head.

10 When a new associate joins a matter, share the account plan link. The associate gets the two-paragraph brief plus full context history. No 45-minute handoff call required.

11 At the end of each quarter, run the investor-reporting-style view of your client book: top clients by fees collected, matters opened vs. closed, average days-to-payment by client tier. Describe the view to Starch and it builds the dashboard from your QuickBooks and CRM data.

12 Publish your account plan template to your firm's internal Starch workspace so every attorney uses the same structure. When a client relationship changes hands, the plan transfers cleanly instead of living in one partner's email archive.

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

Meridian Construction — Q2 2026 Account Plan Refresh

Sample numbers from a real run

Active matters (Clio)	3
YTD fees billed (QuickBooks)	87,400
Outstanding invoices (QuickBooks)	14,200
Last email contact (Outlook)	9
Next filing deadline (Clio)	14

Meridian Construction has been a client for four years, primarily litigation and contract review. Starch pulls from QuickBooks and shows $87,400 billed YTD across three active matters — up 22% from Q1 — with $14,200 in outstanding invoices, two of which are 45+ days past due. The Outlook sync shows the last partner email was nine days ago, but it was about a personal referral, not the open invoice. The Clio sync shows a contract filing due in 14 days that isn't on the responsible attorney's Outlook calendar. The dormancy alert didn't fire because there was recent email contact, but the account plan flags the invoicing gap automatically. The associate brief Starch generates reads: 'Meridian is a mid-size commercial contractor, primary contact is CFO Dana Reyes. Relationship is strong at the partner level; billing friction has historically come from slow AP cycles, not disputes. Three open matters: zoning appeal (lead), subcontractor dispute (active), and standard MSA review (near close).' A junior associate joining the zoning matter gets that paragraph before the kickoff call.

Measurement

How you'll know it's working

Fees billed per client YTD vs. prior year same period (from QuickBooks)

Days since last substantive client contact by responsible attorney

Outstanding invoice aging by client (30 / 60 / 90+ days)

Number of active matters per client and matter stage distribution

Percentage of top-20 clients with an account plan updated in the past 60 days

Comparison

What this replaces

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

Clio Manage alone

Clio tracks matters and billing well, but it doesn't synthesize Outlook threads, QuickBooks payment history, and relationship notes into a single account plan — you still reconstruct context manually before every client meeting.

HubSpot CRM

HubSpot is built for sales pipelines, not matter-based professional services relationships — you'd spend weeks configuring it to think in terms of matters and billing rates, and it still won't connect to your QuickBooks or Clio data without heavy custom work.

Karbon

Karbon is purpose-built for accounting workflows and handles task management and client emails well, but it doesn't build adaptive account plan surfaces or let you describe and generate custom dashboards across your full data set.

Word doc + shared drive

Free and familiar, but account plans go stale the moment they're written, there's no automatic refresh from QuickBooks or Outlook, and the next attorney on the matter starts from scratch every time.

Notion

Notion works as a static wiki and can hold account plan templates, but it has no live connection to QuickBooks billing data or Outlook threads, so keeping it current is entirely manual — which means it usually isn't.

On Starch RECOMMENDED

One platform — crm, knowledge management 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 for matter management. Can Starch actually pull from it, or do we have to enter everything twice?

Clio is reachable from Starch's integration catalog — the agent queries it live when your account plan or CRM app runs. You don't re-enter matter data. If you also use MyCase or Karbon, those are reachable the same way. Describe what fields you want surfaced and Starch pulls them.

We bill through LawPay. Can Starch see payment status from there?

LawPay doesn't have a public API, but Starch can automate it through your browser — no API needed. For most billing reconciliation purposes, your QuickBooks data (which Starch syncs on a schedule) will have the invoice and payment records you need, since LawPay pushes transactions there.

Is Starch SOC 2 certified? Our clients have data security requirements.

Starch is not SOC 2 Type II certified today. If your firm has clients or engagement letters that require SOC 2 certified vendors for any system holding client data, that's a real constraint to evaluate. It's on the roadmap. Worth asking your malpractice carrier what they actually require before assuming full SOC 2 is the threshold.

Our QuickBooks has seven years of billing history. Will Starch sync all of it?

Starch syncs QuickBooks entities — invoices, payments, bills, vendors, journal entries — with a cap of 50,000 records per entity type. For most small practices that's well above what you'll hit. One note: QuickBooks report views like the standard P&L and Transaction List are temporarily unavailable while an upstream fix is in progress; entity-level data syncs normally, so your per-client billing totals will be accurate.

We use Outlook, not Gmail. Does that change anything?

No. Starch syncs Outlook messages, calendar events, and contacts on a schedule the same way it handles Gmail. The account plan automation works identically — last contact date, thread history, meeting context all pull from Outlook.

Can Starch draft the actual client update email, or just build the account plan it would be based on?

Both. Once the account plan is current, you can ask Starch: 'Draft a client update email for Meridian Construction summarizing the status of their three active matters, the outstanding invoice, and our next steps.' It pulls from the account plan context and drafts the email. You review and send from Outlook. The draft isn't a canned template — it reflects the actual matter status from your data.

We don't want every attorney to have access to every client's billing data. Can we control that?

You can scope which data sources and account plan records are accessible within your Starch workspace. This is worth setting up intentionally before you roll it out — decide at the firm level what each role should see, and describe those permission boundaries when you configure the CRM and account plan apps.