People & HR

How to onboard a new hire as Small Law and Accounting Practices

People & HRFor Small Law and Accounting Practices3 apps12 steps~24 min to set up

When a new associate or staff accountant joins a six-attorney firm or four-CPA practice, onboarding is a patchwork of forwarded emails, a tour of the shared drive, and two hours with the paralegal or senior partner who still holds everything in their head. The new hire gets a Clio login, a QuickBooks password, and a stack of matters to review — but no structured path through client naming conventions, billing codes, deadline cadence, or how conflicts get flagged. Three weeks in they're still interrupting billable time to ask questions that should have been answered on day one. There's no wiki. There's no checklist that survives beyond a PDF that went stale eighteen months ago.

Build this on Starch → See the apps used

People & HRFor Small Law and Accounting Practices3 apps12 steps~24 min to set up

Outcome

What you'll set up

A living onboarding wiki built from your actual matter files, billing guidelines, and deadline conventions — searchable by the new hire without pulling anyone off billable work

A task checklist that issues itself automatically when a new hire starts, with P1-P4 priorities, due dates, and overdue alerts so nothing gets skipped

An inbox triage setup so the new hire's first client emails get drafted correctly from day one, not reconstructed from memory after the fact

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 Task Manager Email Agent

Data sources & config

Starch connects directly to Outlook (scheduled sync) to pull tagged onboarding-reference threads into the Knowledge Management wiki. Starch connects directly to Notion (scheduled sync) for any existing documentation. Clio and LawPay are reachable from Starch's integration catalog — the agent queries them live when the task list or wiki needs matter or payment data. QuickBooks is connected via scheduled sync for billing code and payment references. Any onboarding portal or HR system your firm uses that doesn't have a formal API can be automated through your browser — no API needed.

Prompts to copy

Build me a Knowledge Management wiki for onboarding new legal/accounting staff. Include sections for: client naming conventions, matter numbering in Clio, billing code categories, conflict check process, deadline escalation rules, and how we handle LawPay reconciliation with QuickBooks. Pull from our Notion pages and any Outlook threads I tag as 'onboarding reference.'

Create an onboarding task list for a new associate joining next Monday. Assign P1 tasks for week one (Clio access, conflict check walkthrough, first matter review), P2 tasks for week two (shadow a client call, draft a status email, submit first timesheet), and P3 tasks for week three (independent matter handling, billing code audit). Set due dates from their start date and send me an overdue alert if any P1 task slips past day three.

Set up Email Agent so that when I forward a client email to our new hire, it automatically summarizes the matter context from our Knowledge Management wiki and drafts a suggested reply they can review and send. Flag any email mentioning a deadline, opposing counsel, or LawPay transaction for my review before it goes out.

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

Walkthrough

Step-by-step

1 Connect Outlook or Gmail via scheduled sync and tag the last six months of internal threads that contain billing instructions, matter walkthroughs, or process explanations — these become the raw material for your onboarding wiki.

2 Connect Notion via scheduled sync if you have any existing documentation there; Starch pulls it in and merges it with the email content so the wiki isn't starting from zero.

3 Open Knowledge Management and tell Starch what sections you want: client naming conventions, Clio matter numbering, billing codes, conflict check process, LawPay reconciliation steps, deadline escalation. Starch drafts each section from your tagged content; you review and correct in plain language.

4 Set a staleness rule — tell Starch to flag any wiki section that hasn't been updated in 90 days and ping you to confirm it's still accurate. This is how the PDF problem stays solved.

5 Open Task Manager and describe the onboarding checklist you want. Name the start date, assign priority levels (P1 = must complete week one, P2 = week two, P3 = week three), and set overdue alerts. Starch builds the task list and issues it automatically each time you tell it a new hire is starting.

6 Wire Clio from Starch's integration catalog so that the new hire's task list can include a 'review these three open matters' step that pulls actual matter numbers and client names — not a generic placeholder.

7 Set up Email Agent for the new hire's inbox: tell Starch to summarize any client thread before the new hire drafts a reply, flag emails mentioning deadlines or opposing counsel for partner review, and draft suggested replies that match your firm's tone conventions as documented in the wiki.

8 Run a dry-run onboarding with a current staff member acting as the new hire for one day. They use only the wiki and the task list — no asking colleagues. Note every question they have to ask anyway; those are wiki gaps.

9 Patch the wiki gaps in plain language and tell Starch to update the affected sections. The AI re-categorizes and cross-links automatically.

10 On the new hire's actual start date, share the wiki link and activate their task list. Their first P1 task is to read the conflict check process section and run a practice check on a dummy matter using Clio.

11 At end of week one, review the new hire's Email Agent drafts together — correct tone or content issues in the wiki so the AI improves for future hires.

12 After 30 days, check Task Manager completion rates. Any task category with a high skip or overdue rate is a process gap, not a people gap — rewrite that part of the onboarding sequence.

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

Onboarding a New Associate — Walters & Chen LLP, March 2026

Sample numbers from a real run

Partner hours diverted to onboarding questions (before Starch)	14
Partner hours diverted to onboarding questions (after Starch)	3
Days until new hire handled first client email independently (before)	12
Days until new hire handled first client email independently (after)	4
Wiki articles auto-drafted from Outlook and Notion content	23
Onboarding tasks issued automatically on start date	31

Walters & Chen, a six-attorney estate planning and business law firm in Austin, hired their third associate in two years. The previous two onboardings each cost roughly 14 hours of partner time spread across the first three weeks — time that would have billed at $450/hour. For the March 2026 hire, the managing partner spent one afternoon tagging Outlook threads and correcting the Knowledge Management wiki Starch drafted from those threads and the firm's Notion pages. On the new associate's first Monday, she received a Task Manager list with 31 tasks spanning three weeks: P1 items included completing the Clio conflict check walkthrough (linked directly to the wiki section), reviewing three open estate matters pulled live from Starch's Clio connection, and shadowing the LawPay-to-QuickBooks reconciliation the bookkeeper runs weekly. By day four she drafted her first client status email using Email Agent — Starch summarized the matter thread from Outlook, flagged a statute of limitations date mentioned in a prior email, and drafted a reply the partner approved with one edit. Partner onboarding hours dropped to three. The managing partner's note at the 30-day mark: 'She asked me two questions in the first week. The last two associates asked me two questions a day.'

Measurement

How you'll know it's working

Partner hours diverted to onboarding questions per new hire (target: under 4 hours in first 30 days)

Days to first independent client communication (new hire drafts and sends without review)

Onboarding task completion rate at end of week one (P1 tasks: target 100%)

Wiki staleness alerts triggered per quarter (tracks whether documentation is being maintained)

Billable hour capture rate for new hire in weeks 3–4 vs. firm average

Comparison

What this replaces

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

Clio's built-in matter templates and task lists

Clio task templates are matter-level, not person-level — they don't issue a cross-matter onboarding sequence, don't connect to your Outlook history, and don't draft client emails for a new hire.

Notion wiki (manual)

Notion is a good place to store documentation but it doesn't draft the docs from your existing email and matter history, doesn't detect staleness, and doesn't issue tasks — you're still maintaining it by hand.

Karbon or TaxDome (for accounting practices)

Both handle workflow templates and client work well, but neither builds a searchable onboarding wiki from your existing email threads or drafts client emails for a new hire using your prior matter context.

A shared Google Drive folder and a PDF checklist

Zero cost, but the PDF goes stale within a quarter, search doesn't work across documents, and there's no alert when a new hire falls behind on a step.

On Starch RECOMMENDED

One platform — knowledge management, task manager, 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 connect to Clio?

Yes — Clio is reachable from Starch's integration catalog, which covers 3,000+ apps. The agent queries it live when your onboarding task list or wiki needs matter data. It's not a scheduled sync, so it won't store a historical archive of your Clio data inside Starch — but for pulling current matter names, client lists, or billing codes into an onboarding workflow, live querying is exactly what you need.

Can Starch actually draft the wiki content, or do I have to write it myself?

Starch drafts it from your existing content — tagged Outlook or Gmail threads, your Notion pages, whatever you connect. You describe the sections you want, Starch produces a first draft, and you correct it in plain language. Most firms find the draft is 70-80% right and the corrections take less time than writing from scratch. You're editing, not authoring.

We use MyCase, not Clio. Does that work?

MyCase is reachable through browser automation — Starch automates it through your browser with no API required. You won't get the same live-query depth as a catalog-connected app, but Starch can navigate MyCase screens to pull matter information into your onboarding workflow. Describe what data you need and Starch figures out how to get it.

Is Starch SOC 2 certified? We handle client data.

Not yet — Starch is not SOC 2 Type II certified today. If your firm's security policy requires SOC 2 Type II for any tool that touches client communications or matter data, you should know that upfront. It's on the roadmap. For firms where that's not a hard requirement, Starch handles data with standard encryption and access controls.

What happens to the onboarding wiki when a process changes — say, we switch billing codes or add a new conflict check step?

Starch flags wiki sections that haven't been updated in whatever window you set (we suggest 90 days). When you get that alert, you open the section, correct it in plain language, and Starch updates it. You can also just tell Starch 'update the conflict check section — we now require a second partner sign-off on matters over $50k' and it rewrites that section. The new hire who joins six months from now gets the current version, not the one from your last offsite.

The Task Manager says it's in development. Can we use it?

Task Manager is currently in beta — you can request access. For firms that want to start now, you can describe the same onboarding task sequence to Starch and have it surface as a custom app while you wait for full Task Manager availability. You'd tell Starch: 'Build me a task tracker for new hire onboarding with P1-P4 priorities and due-date alerts' and it builds you that surface directly.