How to run a performance review cycle as Small Law and Accounting Practices
At a six-attorney or four-CPA firm, performance reviews happen once a year, badly. The managing partner sends a Google Form in November, waits two weeks for responses, then writes evaluations from memory in a Google Doc. Billable hours are in Clio or QuickBooks. Client feedback lives in Outlook threads nobody exported. Meeting notes from one-on-ones were never written down. The result is a review that reflects whoever was visible in October, not who actually performed. Junior associates and staff accountants leave because they felt blindsided. The process takes the managing partner a full week to run and still feels unfair.
What you'll set up
Apps, data, and prompts
The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.
Starch syncs your QuickBooks data on a schedule (billable hours, compensation data for context). Starch connects directly to Outlook so it can send self-assessment forms, collect peer review submissions via email, and draft review summaries from thread history. Starch connects directly to Google Calendar or Outlook Calendar to pull one-on-one meeting history. Clio is reachable from Starch's integration catalog — the agent queries it live for matter assignments and workload data per attorney. Meeting Notes and Knowledge Management run inside Starch with no additional setup.
Step-by-step
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
November 2025 Review Cycle — six-attorney firm, four support staff
| Sarah Chen (Associate, 3 yrs) | 1,840 |
| Marcus Webb (Associate, 1 yr) | 1,210 |
| Diane Rojas (Paralegal, 5 yrs) | 0 |
| Office Manager | 0 |
The managing partner runs a firm of six attorneys and four staff. In past years, review season meant two weeks of the partner's time reconstructing who did what. This year: QuickBooks syncs show Sarah Chen billed 1,840 hours year-to-date against a 1,750 target; Marcus Webb billed 1,210 against a 1,600 target. Starch drafts Sarah's review by pulling four one-on-one meeting notes from the knowledge base (March, June, August, October), two peer reviews from associates who worked the Hendricks matter with her, and her self-assessment. The draft flags a consistent theme: strong client communication, slower-than-expected brief turnaround. The managing partner edits two paragraphs. Marcus's draft surfaces a different picture — peer reviews mention strong research but one-on-one notes from August and October both reference the same deadline miss on the Calloway file. The partner didn't remember this was a pattern; the notes did. Total drafting time for ten reviews: four hours, down from the usual 30+. Diane Rojas's review pulls her one-on-one notes and the two client emails the partner forwarded to her with praise, which Starch found in Outlook thread history and filed automatically. Her review writes itself in eight minutes.
How you'll know it's working
What this replaces
The other ways teams handle this today, and how the Starch version compares.
One platform — meeting notes, knowledge management, task manager all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.
Try it on Starch →Frequently asked questions
We use Clio for matter tracking. Can Starch pull Clio data into the review?
What if our staff doesn't use the same email platform — some are on Outlook, one is on Gmail?
Is this secure enough for HR data about attorneys and staff?
Can Starch actually draft a review summary, or does it just organize the inputs?
What happens to the review data after the cycle ends? Do we lose it?
We only do reviews once a year. Is it worth setting this up for a single annual event?
Related guides for Small Law and Accounting Practices
A 13-week cash flow forecast is a rolling, week-by-week view of what hits your account and what leaves it — covering roughly one quarter ahead.
Read guide →A strategic account plan is a documented, living view of a specific customer or prospect — their business goals, the stakeholders who matter, the gaps your product fills, the risks to the relationship, and the actions your team is taking.
Read guide →A customer knowledge base is the document — or collection of documents — that answers the questions your customers ask repeatedly.
Read guide →An outbound email sequence is a structured series of messages sent to prospects who haven't heard from you yet — or haven't responded.
Read guide →Run a Performance Review Cycle for other operators
The AI stack built for small HR teams.
Read guide →The AI stack built for the founder's office.
Read guide →The AI stack built for boutique professional services firms.
Read guide →The AI stack built for independent clinic owner-operators.
Read guide →Ready to run run a performance review cycle on Starch?
Request closed-beta access. Everything is free during beta.