Trackmint Use Cases — Software Development & Law Firm

Date: July 18, 2026 · Companion to the PRD (doc 05) and the working prototype/app.

Screenshots are taken from the actual clickable prototype (desktop) and the Expo mobile app built in this project.

The one idea behind every use case: the work item you track is the same thing you bill. An hour logged on a board card flows — with no export, no second tool — into budgets, invoices, and payment.

Part 1 — Software Development pack (“Jira × QuickBooks”)

Who: Barry’s dev shop — a contractor (Barry, $120/h) with two subcontractors (Dana $95/h, Sam $80/h), serving two clients: Acme Corp and TechFlow. Today this shop would need Jira/Asana + Toggl/Harvest + QuickBooks. In Trackmint it is one tool.

Use case S1 — Run the sprint (Basic tier)

1. Barry opens the Sprint Board: Backlog → In Progress → In Review → Done.
2. He creates an issue “Payment webhook retries failing” (type: Bug, client: Acme Corp, estimate 6h) and assigns it to himself.
3. During the week the team drags cards across columns; each card shows type, client, logged vs. estimated hours (green, red when over), and assignee.

What competitors miss: Jira does this but knows nothing about money; PracticePanther can’t do boards at all (its own help docs tell users to bolt on Trello).

Use case S2 — Capture billable hours (Mid tier)

1. Barry opens the webhook bug card and taps ▶ Start timer as he begins debugging.
2. The timer runs across the whole app (visible in the header) while he works; he stops it 2h 15m later — the time is logged to that exact issue at his $120/h rate.
3. Dana logs 3h manually on the dashboard feature (“Add hours: 3”).
4. Time & Billing now shows: unbilled value per issue, per member, and Acme’s budget bar climbing — it turns amber at 80% of the $8,000 budget, red if over.

Design requirements from research: timers included in every time-tracking plan (Asana paywalls this at $24.99+add-on; Jira needs Tempo which charges for every seat), and reliable (PracticePanther’s “timers reset themselves” was a top complaint).

Use case S3 — Scan a receipt into a billable expense (Advanced tier)

1. Barry uploads the June AWS invoice PDF into Documents (AI).
2. The AI extracts vendor, amount ($214.37), date, category (“Cloud hosting”), and — at 72% confidence, flagged for review — matches it to client Acme Corp’s project.
3. Barry confirms; the expense joins Acme’s unbilled work.

This is the “QuickBooks side”: no official government forms exist for software work, so the dev pack’s AI is receipts → categorized billable expenses.

Use case S4 — One-tap invoice, get paid (Mid tier)

1. On Invoices, Trackmint shows “Acme Corp — $2,062.40 unbilled.”
2. One tap: a draft invoice appears with line items pulled from real work — “Payment webhook retries failing — 4.5h @ $120,” “Build client billing dashboard — 5.2h @ $95,” “Expense — AWS June $214.37” — subtotal, total, done.
3. Barry taps Send; Acme receives it with an online payment link (card/ACH). Items are marked billed so nothing is double-invoiced. When money arrives, the invoice flips to Paid.

The gap this closes: 14 of our 145 mined complaints were exactly “no bridge from tracked work to a client invoice.”

Part 2 — Law Firm pack (matters + billing + AI forms)

Who: a solo consumer-bankruptcy attorney with a paralegal. Today she’d need PracticePanther (billing) + Trello (boards) + Best Case or Glade (petitions). Trackmint’s Legal pack renames the same engine: issues become matter tasks, the Sprint Board becomes the Matter Board (Intake → In Progress → Attorney Review → Filed/Done).

Use case L1 — Track a matter from intake to filing (Basic tier)

1. New client T. Nguyen retains the firm for a Chapter 7. The paralegal creates matter tasks: “Nguyen — Ch. 7 petition prep,” “Nguyen — client doc collection.”
2. Tasks move across the Matter Board; the attorney sees at a glance which matters are stuck in Intake and which await her review.
3. Each card carries the client, task type (Filing / Research / Hearing Prep), and hours logged vs. estimate.

Use case L2 — Bill every minute, respect the budget (Mid tier)

1. The attorney starts the timer on “Rivera — means test analysis” during research; the paralegal logs collection time on Chen’s matter at her lower rate.
2. Time & Billing shows each matter’s budget bar — Nguyen’s $1,500 flat-fee budget at 51%, warning before the firm eats unbillable overrun.
3. Month-end: unbilled time per client is already assembled; invoices go out with payment links (the research showed lawyers wait ~a week for PantherPayments deposits and hate it — payments status is visible in-app).

Design requirements from research: flat-fee budget visibility (“no way to check whether you are about to exceed the budget” — real PracticePanther complaint), and no seat-banding pricing for a 2-person firm.

Use case L3 — The signature move: scan client docs → filled official form (Advanced tier)

1. The attorney requests documents from T. Nguyen through the app; he uploads his W-2, six months of pay stubs, and a bank statement from his phone.
2. The AI reads all three documents and extracts the fields a Chapter 7 income schedule needs — employer, gross monthly wages (6-month average across pay stubs), payroll deductions, and a rideshare side income it detected in bank deposits.
3. Every value shows a confidence score and its source (“← pay stubs, 6-mo avg”). The rideshare income is at 64% confidence, so it’s flagged red — the attorney reviews and confirms it. Nothing fills a form without attorney sign-off.
4. One tap: Official Form 106I (Schedule I: Your Income) is filled and attached to the Nguyen matter, ready for the petition packet.

Roadmap beyond this demo: the full petition packet (B101, B106 schedules, B107, B122 means test), creditor matrix, CM/ECF e-filing — then new profession packs reusing the same extractors (family-law FL-150, SSDI, probate).

Use case L4 — Same firm, same tool, different work (cross-pack)

The attorney’s spouse runs a small dev consultancy. Same Trackmint account, different workspace, different pack — the engine is identical; only the language, board columns, seed templates, and AI target forms change. That is the modular thesis from Barry’s original idea.

Tier summary across both use cases

Prices are the illustrative tiers from the financial research (doc 06), not final.

Where to try each use case

• Clickable prototype (desktop, in your Cowork sidebar as “caseboard-prototype”): all four S and L flows, including drag-and-drop and the full AI scan wizard.
• Mobile app (~/projects/caseboard-app, npx expo start): the same flows adapted to phone — the TestFlight build will behave identically.