What the work actually involves

You are given a workflow brief — open a new matter for an intake, link the client and related contacts, generate an engagement letter from a template, set a statute-of-limitations calendar rule, log time against the matter, and produce a draft bill — and you complete it inside Clio while recording your screen. Then you write it up: the exact navigation path, which Clio feature you used and why, where the interface behaves unexpectedly, and what a correct end state looks like. Most tasks also ask you to author a realistic prompt (the instruction an AI agent would receive) plus a rubric a grader could apply without knowing Clio, which is usually the harder half of the job.

Expect volume across the breadth of the product rather than depth in one corner: matters and contacts, custom fields, document automation and templates, tasks and task lists, court-rule and manual calendaring, timers and time entry, trust vs. operating accounting, bill generation and Clio Payments. Some projects touch Clio Grow or Clio Duo; most sit in Clio Manage.

What the screen looks for

micro1's screening is AI-led and follow-up heavy. It is calibrated to separate people who have configured and lived in Clio from people who have watched demos — so questions drill into where a setting actually lives, what happens when a matter is closed with unbilled time on it, how trust requests behave, what a bill looks like after a discount is applied at the line level versus the bill level. Vague, tool-agnostic answers about "legal project management" do not survive the second follow-up. The other thing being measured is whether your written rubrics are gradeable: specific, observable, and tied to end state rather than to style.

Logistics

  • Fully remote, contractor, asynchronous — you pick up batches and deliver against a turnaround window rather than sitting in a shift.
  • You need working access to a Clio environment you can create and modify records in. A firm account you can use for this purpose, a trial, or a sandbox all count; read-only access does not.
  • Screen recording is mandatory on most task types, with clean audio or written narration depending on the project.
  • Observed pay runs $30–100/hr, stated as observed and not guaranteed; rates vary by project, task type, and whether you are producing workflows or reviewing others' submissions.
  • Volume is project-driven and lumpy. Contributors who can absorb 10–20 hours in a week when a batch lands tend to get offered more.