Sales & CRM

How to create a sales enablement content library as Small Law and Accounting Practices

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

At a six-attorney or four-CPA practice, sales enablement content doesn't really exist as a category — it exists as a paralegal's muscle memory. When a prospect asks what your estate planning process looks like, someone writes a fresh email. When a referral partner wants to understand your M&A practice, a partner spends 45 minutes pulling together a one-pager from a five-year-old pitch deck and a recent engagement letter. Case studies live in one partner's Outlook drafts folder. Service descriptions are scattered across the website, a Clio matter template, and a Google Doc that hasn't been touched since 2023. There's no single place to find the firm's standard pitch for a new audit client, the onboarding checklist for a tax-planning engagement, or the ROI story from that messy estate settlement you resolved last quarter.

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 searchable, AI-organized content library containing every service description, client FAQ, engagement overview, matter summary, and referral one-pager your firm has — pulled from Outlook, Notion, and existing docs, de-duplicated and categorized so anyone on staff can find the right document in under a minute

A CRM that tracks prospect and referral-partner relationships with deal stage, last communication date, and linked content assets — so you always know which firms have gone quiet and what collateral was last sent to whom

Automated first drafts of practice-area overviews, new-client onboarding packets, and client-status summaries pulled from matter context in your connected systems — so the partner's Friday afternoon email gets written in five minutes, not fifty

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 CRM

Data sources & config

Starch connects directly to Outlook (scheduled sync) for email thread history and contact context, and to Notion (scheduled sync) for existing knowledge base pages, matter notes, and document templates. Outlook Calendar syncs on a schedule to surface deadline and meeting context. QuickBooks is connected via scheduled sync to pull engagement and billing context for matter narratives. Additional tools like Clio and Karbon are reachable from Starch's integration catalog — the agent queries them live when an app, dashboard, or automation needs the data. Any web-based portal (court filing sites, state bar directories, referral network portals) can be automated through your browser — no API needed.

Prompts to copy

Build a knowledge base for our law firm's sales and client-facing content. Pull in our Notion pages and any Outlook emails tagged 'client onboarding' or 'engagement overview.' Auto-categorize by practice area: estate planning, M&A, tax advisory, audit. Flag any document that hasn't been updated in 12 months as stale.

Build me a CRM for tracking referral partners and prospective clients. Fields I want: contact name, firm name, relationship type (referral source / prospect / client), practice area interest, last contacted date, deal stage (introduced / proposal sent / engaged / closed), and a notes field for matter context. Pull email thread history from Outlook so I can see every touchpoint.

Every Monday morning, look at which referral partners we haven't emailed in 30 days, pull the last email thread from Outlook for each, and draft a short check-in message for each contact. Send me the drafts in a Slack message so I can review before sending.

Create a practice-area overview document for our estate planning services. Pull context from our last five estate planning engagement letters in Notion, the FAQ page on our website, and any client-facing emails in Outlook tagged 'estate planning.' Write it as a two-page narrative a prospective client could read, with a plain-English explanation of our process and a typical timeline.

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

Walkthrough

Step-by-step

1 Connect Outlook (scheduled sync) and Notion (scheduled sync) in Starch. These two sources hold the vast majority of your firm's existing client-facing writing — engagement letters, matter notes, FAQ drafts, onboarding checklists — and Starch will index them automatically.

2 Start the Knowledge Management app and describe your firm's practice areas. Tell Starch: 'We are a six-attorney firm with three practice areas: estate planning, M&A, and business tax advisory. Organize all imported content under those categories and flag anything that looks like a client-facing asset versus an internal note.'

3 Review what Starch pulls in. You'll likely find five versions of the same engagement overview, three outdated fee schedule drafts, and two onboarding checklists that contradict each other. Tell Starch which to keep or ask it to merge duplicates.

4 Use the Knowledge Management app to generate clean, current versions of your core assets: service descriptions per practice area, a standard new-client onboarding packet, a referral partner one-pager, and a matter handoff template for when a junior associate joins a file mid-stream.

5 Start the CRM app and describe your relationship pipeline. Referral partners, active prospects, and clients each need different pipeline stages. A referral partner moves through 'connected → sending business → dormant'; a prospect moves through 'introduced → proposal sent → engaged → closed or lost.'

6 Import your Outlook contacts into the CRM. Tell Starch: 'Pull all contacts from Outlook who appear in emails about legal services, filter out internal staff, and map them to the CRM with their last email date and any deal-stage signals you can infer from subject lines.'

7 Link content assets to CRM records. When you mark a prospect as 'proposal sent,' Starch logs which document was sent. When a referral partner goes dormant, you can see the last piece of content they received and whether it matched their practice-area interest.

8 Set up the Monday morning referral-partner check-in automation. Starch queries Outlook for last-contact dates, identifies dormant relationships, drafts a short personalized email for each, and sends you a Slack summary before the week starts.

9 Set up the client-status email automation. Tell Starch: 'When I flag a matter in Notion as needing a client update, pull the most recent email thread from Outlook, the last billing entries from QuickBooks, and any deadline notes from Calendar, and draft a two-paragraph client-status email for my review.'

10 Build a practice-area content refresh automation. Tell Starch: 'Every quarter, check all knowledge base documents in the estate planning and M&A categories. If a document hasn't been updated in 90 days and mentions a specific fee or timeline, flag it for my review and draft an updated version using the context from recent Outlook emails on the same topic.'

11 For referral partner outreach, use the Presentation Agent (note: currently in development — request beta access) to generate a polished one-pager or slide deck from your knowledge base content when you need something more formal than an email.

12 Publish the finalized content library to your whole team through Notion (scheduled sync keeps it current) so every associate, paralegal, and billing coordinator can find the right document, the right pitch, and the right client-status template without asking the managing partner.

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

Hartwell & Osei LLP — Q1 2026 Referral Partner Re-engagement

Sample numbers from a real run

Dormant referral partners identified (>30 days no contact)	11
Personalized check-in drafts generated by Starch	11
Partners who responded and sent a new matter referral	4
Estimated billable hours attached to new referral matters	38
Hours spent by partners on outreach prep	1

Hartwell & Osei LLP is a five-attorney firm in Atlanta — two partners focused on estate planning, two on business tax advisory, one on M&A. Before Starch, the firm's 'sales enablement' was a shared Dropbox with 40 files, half of them outdated, and a managing partner who rewrote the estate planning overview every time a referral came in from the financial advisor network. In January 2026, they connected Outlook and Notion to Starch, built the Knowledge Management app with their three practice areas, and had Starch consolidate 40 documents into 12 clean, current assets in one afternoon. They then built the CRM and imported 140 Outlook contacts, mapping 27 as active referral partners. The Monday check-in automation identified 11 partners who hadn't heard from the firm in more than 30 days, including two financial advisors who had sent multiple estate planning matters the prior year. Starch drafted 11 short check-in emails — each one referencing the last matter the partner had sent and asking if any new clients had come through — and delivered them to the managing partner as a Slack summary at 8 a.m. Monday. She approved nine, edited two, and sent all eleven before her first call. Four responded within the week, and three of those sent new matters in Q1 totaling 38 billable hours. Total prep time: one hour of the managing partner's attention over the whole quarter.

Measurement

How you'll know it's working

Referral partner contact frequency (days since last outreach per partner)

Time from prospect inquiry to proposal sent (days)

Content asset staleness rate (% of library documents not updated in 90+ days)

Hours spent per week drafting client-facing communications (partner and associate combined)

Referral-to-engaged-client conversion rate by practice area

Comparison

What this replaces

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

Clio Manage + manual document folder

Clio handles matter management well but has no content library, no CRM for referral partners, and won't draft a client-status email or flag a stale one-pager for you.

Karbon

Karbon is strong for accounting workflow and client task tracking but is built around work items, not sales content or referral-partner relationships — and it won't generate a practice-area overview from your existing documents.

HubSpot CRM (free tier)

HubSpot gives you a CRM out of the box, but you'll spend weeks configuring it for a legal or accounting sales motion, it has no knowledge base for content assets, and there's no connection to Outlook threads or Notion pages without expensive add-ons.

Google Drive + shared Notion wiki (manual)

This is what most small practices actually use — and it works until someone leaves or a document goes stale, because nothing enforces freshness, surfaces what exists, or drafts new content from what's already in the system.

TaxDome (accounting practices)

TaxDome covers client portal and engagement letters for accounting firms but is purpose-built for the delivery workflow, not for building a content library, managing referral-partner outreach, or drafting new practice-area materials.

On Starch RECOMMENDED

One platform — knowledge management, crm 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, not Notion. Can Starch still pull content from there?

Clio is reachable from Starch's integration catalog, so the agent can query it live when an app or automation needs data from your matters. The scheduled-sync depth (stored data, schema) is deepest for Notion, Outlook, and QuickBooks, so if you want Starch to index a large volume of historical matter notes, the most reliable path is to export key documents into Notion and let Starch sync from there. For live lookups — pulling a specific matter's status or contact details mid-automation — the live-query connection to Clio works fine.

Will Starch actually store our client documents and matter notes? That raises confidentiality concerns.

Starch is not SOC 2 Type II certified today — that's worth naming honestly if you're evaluating it against your firm's data-handling obligations. What Starch indexes from Notion and Outlook are the documents and emails you explicitly connect; it doesn't crawl your whole system. For a sales enablement library of service descriptions, referral partner contacts, and pitch materials, most small practices find the risk profile acceptable. For privileged client matter files, your judgment call on what to connect matters, and you should review your bar association's guidance on cloud storage before wiring in anything privilege-sensitive.

Our content problem is partly that no one agrees on which version of the estate planning overview is current. Can Starch fix that?

That's exactly the use case the Knowledge Management app handles. When you import documents from Notion and Outlook, Starch identifies duplicates, flags version conflicts, and asks you which to keep. You can also set a rule — 'if two documents cover the same topic and one is more than 90 days older, flag the older one as stale' — and Starch will surface those for review automatically. It won't delete anything without your direction, but it will stop everyone from fishing through a 40-file Dropbox and grabbing the wrong version.

We don't have a formal sales process — most work comes from referrals. Is a CRM actually useful for us?

Referral-dependent practices often have the most to gain from a simple CRM, because the work of nurturing referral partners is almost entirely invisible until a partner goes cold and stops sending work. The CRM Starch builds doesn't have to look like a Salesforce pipeline. Describe it as: 'a contact list of referral sources with last-contact date, the practice areas they typically refer, and a notes field' — and that's what Starch builds. The value is in the Monday-morning automation that flags the 11 partners you haven't touched in a month, not in a complex pipeline with 12 stages.

Can Starch draft client-status update emails, or just organize the content library?

Both. Once Outlook (scheduled sync) and Notion (scheduled sync) are connected, you can tell Starch: 'When I flag a matter as needing a client update, pull the last three email threads, the most recent billing entry from QuickBooks, and any deadline notes from Google Calendar, and draft a two-paragraph update for my review.' Starch generates the draft; you review and send. The drafts aren't generic — they pull actual matter context from your connected systems, so the output reads like something you wrote, not a mail-merge.

What about QuickBooks report views — can Starch pull P&L or billing summaries to include in client-facing content?

QuickBooks report views (P&L, Transaction List, Vendor Expenses) are temporarily disabled in Starch while an upstream fix is in progress. Entity-level data — invoices, bills, payments, vendors, journal entries — syncs normally. For a sales enablement library, the most useful QuickBooks data is billing history by client or engagement, which is available through entity-level sync. Full P&L pulls for client-facing reporting will be available once the report-view connector is restored.