Lever.is
Proposal · July 12, 2026
Ongoing product & engineering partnership

Lever.is × Junto Law

Updated after the July 10 walkthrough with Shayn & Swati.
From
Matthew Aycoth
Lever.is
To
Shayn Fernandez
Junto Law
Date
July 12, 2026
01

The short version

Practice Panther is good at capturing data, but bad at answering questions. Right now, “what do we owe each person this month?” costs Junto hours of careful spreadsheet work every month, and your partners can’t see their own numbers without pulling reports and doing the math themselves.

Lever.is becomes Junto’s product and engineering team: dedicated build time every week, starting with the compensation and collections dashboard we scoped together, and Junto owns everything we build.

On the full-day plan we agreed Friday, the goal is dashboards live in roughly 5–7 weeks, with payouts cutting over once a month-close run side by side with Swati’s current process matches her numbers. After that, the retainer points at whatever is next most valuable: running a firm is full of tedious manual work that software and AI can take off your plate, and each sprint you decide what we go after.

02

The first build: compensation & collections dashboard

Full detail is in the attached PRD. What it means for each person:

Swati closes a month in one sitting instead of hours of spreadsheet work. The splits, the true-ups, the expense recoveries: computed, itemized, and auditable. She reviews, approves, pays through Melio the way she does today, and marks each payout paid in the tool. For the first closes, she can download a verification report showing every component behind every number. Trust, but verify. The parallel close is how we prove that number before anything switches over.

Every partner logs in and sees their own numbers: what they’ve collected, what they’re projected to be paid and exactly how it was calculated, and which of their invoices are sitting past due, with an email alert when one crosses 30 or 60 days, and a weekly summary. The people with the most incentive to chase an invoice finally know it’s out there.

You see the whole firm: collections over time, who’s producing, who’s originating, where money is stuck. Junto gets its own line, the firm’s 40% plus expense recoveries tracked like a partner, so you see Junto’s net each month separate from your own collections as an attorney. Each partner’s fronted expenses sit next to their aging invoices, and trust money is shown and labeled but never counted as collected until it’s applied to an invoice. That’s the visibility PracticePanther has the data for but can’t deliver. And one more, just for you: ask Claude questions about the firm’s numbers, same login, same numbers as the dashboard.

It includes the full comp settings page from day one: comp types, split percentages, draws, and quarterly true-ups are all configurable. When you bring on the next Matt Jones-level partner with different numbers, that’s a settings change, not a development request.

Timeline

Targets, confirmed after a week-one validation pass against the live PracticePanther API: dashboards live for you and the partners in 5–7 weeks. Month-closes happen on the calendar, not on sprint schedules; the goal is to run the August close in parallel in early September, with the September close in early October as the fallback. Payouts cut over once the tool and Swati’s spreadsheet agree.

03

How the retainer works

One rate, one plan, settled on the July 10 call. $200/hour; the retainer guarantees the time.

A full day, every week
$6,400 /month
8 hours weekly · 32 hours/month at $200/hour
Dashboards live in 5–7 weeks; the August close runs in parallel in early September.

If the workload ever lightens, we drop to a five-hour week ($4,000/month) or pause under the standard terms. That door stays open.

The full day is a full day for a reason: one uninterrupted day a week means momentum instead of context-switching.

Flat and predictable. The monthly fee covers the guaranteed block. No overage invoices, no change orders.

Billed after the work. Invoiced at the end of each month, net 15. You never pay ahead of delivered work.

Need more in a month? Additional work is the same $200/hour, not guaranteed, scheduled as availability allows.

Outcomes, not hours. Work is organized in biweekly sprints. You’ll see shipped work every week, whether that’s extending the dashboard or starting something entirely new. Priorities are yours to reset each sprint. When a better idea shows up mid-build (“now that I see it, can it also…?”), the answer is “sure, next sprint,” not a change order.

A CTO in your corner. Beyond the build: vendor decisions, API strategy, “should we build or buy,” what’s technically possible, answered by someone accountable for the answer.

Three months, then month-to-month. The initial term is enough to ship the dashboard and prove it against parallel closes. After that, pause or stop with 15 days’ notice.

Junto owns everything. The code, the data, the accounts. If we ever part ways, everything keeps running and any competent developer can pick it up.

Junto’s data stays protected. Client and billing data encrypted in transit and at rest, living only in Junto-owned accounts, used for nothing outside this engagement.

Infrastructure billed directly to Junto (hosting + database, roughly $50–150/month), in Junto-owned accounts, no markup.

The math to hold me to: this pays for itself if it does two things. It gives Swati her close time back every month, and it gets aging invoices chased sooner. Collected dollars are the pool everyone gets paid from, including Junto’s 40%. And every payout number can be verified line by line before anyone has to trust it.

04

After the dashboard: what the retainer is really for

The dashboard is the first project, not the point. The point is a standing capability: every month, find the most tedious, manual, error-prone thing about running the firm and hand it to software, so your time and your attorneys’ time goes to clients, billable work, and bringing in the next partner, not to admin.

There’s deliberately no committed roadmap here. You set the priorities each sprint, and you’ll have ideas I haven’t thought of. That’s the model working, not a problem for it. To make it concrete, here’s the kind of thing we’d go after:

Firm analytics. Tag the data (client / investor / fund, work type) and actually answer: where does revenue come from, which clients and work types pay best, what should Junto sell more of.

A profitability dashboard. Pull QuickBooks and the Capital One card statements into the same ledger as collections, catch the expenses that never made it into PracticePanther (the Delaware Secretary of State fees), and see true per-partner and per-client profitability.

Collections automation. The v1 exports already carry the client name, email, invoice number, and days past due; Claude can draft the reminder emails from them today. A later sprint makes the sending automatic, so chasing aging invoices is nobody’s job.

Intake and document automation. Engagement letters, new-matter setup, recurring document generation, templated instead of hand-built each time.

AI on the practice itself. First-pass trademark research memos, contract review summaries, drafting support: prepared by AI, finished and signed off by the attorney who bills for it.

Owning the stack. When it makes sense, progressively replace PracticePanther (time entry, invoicing) and retire the ~$700/month PracticePanther spend. Fair warning from our call: that’s a real project, not a feature. But the dashboard’s database is being designed as Junto’s own system of record from day one (PracticePanther feeds it; it doesn’t mirror it), so that path builds on this work instead of starting over. And it’s a recruiting weapon: “our systems were built around how we pay you” is something no other small firm can say to the next partner they’re courting.

You set the list; we rank it together each sprint.

05

What we need from you

1

PracticePanther API access Done · July 6

2

The open policy questions Answered · July 10
In writing and on the call. Nothing blocks the build.

3

One potential process change: we may need to add a custom “Originating Attorney” field on each client in PracticePanther. Matters would inherit it, and we’ll pre-fill the history for Swati’s review. This may work better than the field being used currently.

4

Swati to validate: one walkthrough of her close process; her numbers are the benchmark the parallel close has to match.

5

Swati marks payouts paid in the tool as the last step of each close, after the money moves through Melio. The human-in-the-loop step you asked for.

6

During onboarding week (non-blocking): decide who receives the overdue digests, how often, and who owns collections follow-up.

06

Terms at a glance

Rate
$200/hour, one rate for retainer and additional work
Plan
Full day: 32 hours/month, $6,400 (five-hour pull-back, $4,000, available if the workload lightens)
Billing
Invoiced at the end of each month, net 15
Additional work
Same $200/hour, subject to availability
Commitment
Three-month initial term, then month-to-month with 15 days’ notice
Scope
A guaranteed weekly block of product & engineering capacity; outcomes tracked in biweekly sprints
IP & ownership
Junto owns all work product, code, data, and accounts
Infrastructure
Junto-owned accounts, billed direct (~$50–150/month), no markup
First project
Comp & collections dashboard per the PRD: target 5–7 weeks to live dashboards; payout cutover after the first matched parallel close
Proposed start
Monday, July 20, 2026
07

Next steps

Today · July 12

The agreement is on its way for signature, sent separately.

Mon · July 20

Kickoff. Goal is data syncing from PracticePanther within the first week.

Early September

The August close runs in parallel; payouts cut over when the tool matches Swati’s numbers.

Questions? Text me.
Technology, handled.