Customer Support

How to build a customer knowledge base as Small Law and Accounting Practices

Customer SupportFor Small Law and Accounting Practices2 apps12 steps~24 min to set up

At a six-attorney firm or four-CPA practice, client knowledge lives in three places at once: a paralegal's memory, a Clio or QuickBooks matter file, and a chain of Outlook threads nobody has time to read top-to-bottom. When a junior associate picks up a matter mid-stream, they spend 45 minutes reconstructing context from email history and billing notes. When a client calls asking where their amended return stands, someone has to dig through Outlook, QuickBooks, and the wall calendar before they can answer. There is no single place that holds what happened, what's due, and what the client was last told. That gap costs every billable-hour practice more than it should.

Build this on Starch → See the apps used

Customer SupportFor Small Law and Accounting Practices2 apps12 steps~24 min to set up

Outcome

What you'll set up

A matter-by-matter knowledge base that pulls from Outlook threads, QuickBooks billing records, and calendar events into one searchable surface — so anyone on the team can answer a client question in under two minutes without hunting across five tools

A client-status summary that auto-generates a draft update email for each active matter, pulling the last communication date, outstanding deliverables, and next deadline from connected data

A new-matter onboarding doc that Starch assembles automatically when a new client file opens, so the paralegal is not the only person who knows the backstory

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

Knowledge Management Email Agent

Data sources & config

Starch syncs your Outlook email and calendar data on a schedule, and syncs your QuickBooks invoices, bills, payments, and vendor data on a schedule. Clio and MyCase are connected from Starch's integration catalog and queried live when a matter dashboard or knowledge-base entry loads. Any practice management portal that lacks a direct connector — such as TaxDome or Karbon — is automatable through your browser with no API required.

Prompts to copy

Build me a client knowledge base organized by matter. Each matter entry should show the client name, matter type (litigation, estate planning, tax return, audit), last Outlook communication date, open tasks from my calendar, and the most recent billing note from QuickBooks. Make it searchable by client name and matter status.

For each active matter, draft a one-paragraph client status update I can review and send. Pull the last email thread summary, any calendar deadlines in the next 30 days, and the outstanding invoice balance from QuickBooks. Flag any matter where we haven't contacted the client in more than 14 days.

When a new matter is created, generate an onboarding summary for the associate picking it up: who the client is, what the engagement scope is, what's been done so far based on email history and billing records, and what the next three action items are.

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

Walkthrough

Step-by-step

1 Connect Outlook to Starch (scheduled sync). Starch will pull your inbox and calendar events going back 12 months — every client thread, every scheduled deadline, every internal note.

2 Connect QuickBooks to Starch (scheduled sync). This brings in invoices, payments, bills, and vendor records at the entity level — enough to surface outstanding balances and billing history per matter.

3 Connect your practice management tool (Clio, MyCase, or Capsule CRM) from Starch's integration catalog. The agent queries it live when a matter dashboard loads, so contact records and matter status stay current.

4 Open the Knowledge Management starter app in the Starch App Store. Fork it and tell Starch: 'Reorganize this by matter, not by document type. Group each entry under the client name and show matter status, last contact date, and next deadline.'

5 Tell Starch to index your Outlook threads by client name and matter keyword. Starch builds a searchable layer so any team member can type a client name and immediately see the full communication history, summarized.

6 Set up the client-status draft automation. Describe it to Starch: 'Every Monday morning, for each active matter where the status is open, draft a one-paragraph client update email using the last email thread, the next calendar deadline, and the current outstanding balance from QuickBooks. Drop them in a review queue in Outlook.'

7 Build the new-matter onboarding trigger. Tell Starch: 'When a new contact tagged as a client is created in Clio, generate a matter summary doc and post it to our Notion workspace. Include engagement type, client background from the intake email, and the first three action items.'

8 Add a 14-day silence alert. Tell Starch: 'Flag any active matter where the last outbound Outlook email is more than 14 days old and there is no calendar event scheduled. Post the list to a Slack channel every Friday at 4 PM.'

9 Build a deadline tracker view. Tell Starch: 'Show me a dashboard of every matter with a due date in the next 60 days. Pull deadlines from Google Calendar and Calendly bookings. Group by attorney and sort by date ascending.'

10 Set up the conflict-check lookup. Tell Starch: 'When I give you a new client name and adverse party, search my Outlook contacts, QuickBooks vendor list, and Clio contacts for any existing relationship and return a plain-English summary of what you find.'

11 Train your team by sharing the knowledge base app inside Starch. Anyone searching a client name gets the matter summary, last communication, open balance, and next deadline — without calling the paralegal.

12 Review the first week's auto-drafted status emails, correct tone or facts, and send feedback to Starch in plain language so the drafts improve to your firm's standard voice.

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

Hartley Estate Matter — April 2026 Associate Handoff

Sample numbers from a real run

Hartley Estate — unbilled hours (March)	4,200
Hartley Estate — outstanding invoice (Feb)	8,750
Court filing deadline — May 2, 2026	0
Last outbound Outlook email	0
Days since last client contact	18

Sarah, a senior associate, is going on parental leave. The Hartley estate matter — a contested probate with $8,750 outstanding and a May 2 court filing deadline — is being handed to Marcus, who joined the firm six weeks ago. Without Starch, Marcus spends half a day reading a 140-message Outlook thread, asking the paralegal for context, and trying to reconstruct what was last communicated to the client. With the knowledge base in place, Marcus opens the Hartley matter entry in Starch, reads a two-paragraph summary of the engagement scope and dispute history, sees that the last outbound email went out 18 days ago (already flagged by the Friday silence alert), reviews the $4,200 in unbilled March hours sitting in QuickBooks, and gets a draft client-introduction email ready to edit and send. Total time to get up to speed: under 20 minutes. The May 2 deadline is already on his calendar because Starch pulled it from Google Calendar into the matter dashboard. He sends the client update with one edit — changing the tone from formal to the warmer register this client prefers — and bills the 20 minutes of review time.

Measurement

How you'll know it's working

Average time-to-context for a matter handoff (target: under 30 minutes from current ~3 hours)

Percentage of active matters with a client communication in the last 14 days (tracked weekly via the Slack alert)

Outstanding invoice balance per matter, reconciled weekly against QuickBooks billing records

Number of client status emails sent per week vs. drafted-but-not-sent (measures how much the drafts actually save time)

Days between new matter creation and first complete matter summary being available to the team

Comparison

What this replaces

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

Clio Manage alone

Clio holds matter records and billing, but it does not draft client update emails, surface 14-day silence alerts, or pull context across Outlook threads — you still reconstruct narrative manually.

TaxDome (for CPA practices)

TaxDome covers client portals and tax workflow, but building a cross-matter knowledge base that includes email history and QuickBooks billing context requires exporting to another tool or doing it by hand.

Notion + manual copy-paste

A shared Notion wiki is better than nothing, but it goes stale the moment the paralegal gets busy — Starch keeps the knowledge base current by pulling from live connected data rather than requiring manual updates.

Karbon

Karbon is strong for accounting firm workflow and client communication, but it is a purpose-built accounting platform — it does not let you describe a custom surface in plain language and build it, nor does it connect to Outlook threads and QuickBooks billing in the same query.

A shared spreadsheet for conflict checks and deadlines

Spreadsheets break when more than two people edit them and go out of date within a week; a Starch dashboard pulling live from Outlook and QuickBooks stays accurate without a designated person maintaining it.

On Starch RECOMMENDED

One platform — knowledge management, 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

Does Starch actually read the content of our client emails, or just metadata?

Starch reads the message content of your Outlook threads — subject, sender, body, and date — when you connect Outlook as a scheduled-sync provider. That full-text access is what lets it summarize a matter's communication history and draft status updates. You control which email labels or folders Starch indexes. Starch is not SOC 2 Type II certified yet, so if your firm requires that certification for any vendor handling client communication data, that is worth factoring into your decision.

We use Clio for matter management. Does Starch connect to it?

Yes. Clio is reachable from Starch's integration catalog, which the agent queries live when your matter dashboard or knowledge base loads. If you also use a tool like TaxDome or Karbon that does not have a direct connector, Starch can automate those through your browser — no API required.

What about QuickBooks? We have five years of billing history in there.

Starch syncs your QuickBooks data on a schedule — invoices, bills, payments, vendors, and journal entries are all available. The one honest caveat: QuickBooks report views (pre-built P&L, Transaction List, Vendor Expenses) are temporarily unavailable due to a connector fix in progress. Entity-level data — meaning the actual invoices, payments, and billing records — syncs normally and is what powers the matter dashboards and outstanding-balance alerts.

Can a junior associate or paralegal use this, or does it require technical setup?

The setup — connecting Outlook, QuickBooks, and Clio, and describing the knowledge base you want — takes one person about an hour. After that, anyone on the team can open the knowledge base app, search by client name, and read the matter summary without any technical knowledge. The knowledge base is a surface Starch builds once and keeps updated automatically from the connected data.

Will the client status email drafts sound like our firm, or like generic AI output?

The first drafts will sound like a competent but generic legal correspondent. You will need to edit them for tone in the first week or two and tell Starch in plain language what to change — 'be less formal with individual clients,' 'always include the next deadline in the first sentence,' 'sign off with the attorney's first name only.' Starch adjusts based on that feedback. By week three most practices find the drafts need one small edit, not a rewrite.

Does Starch store our client data permanently, or just query it on demand?

For scheduled-sync providers like Outlook and QuickBooks, Starch stores a copy of the synced data in its database so your knowledge base can load quickly and run searches without hitting your source systems every time. For live-queried apps like Clio from the integration catalog, data is fetched fresh each time rather than stored. Starch does not currently offer a self-hosted or on-prem option, so all data lives in Starch's cloud infrastructure.