
Pro bono matter scope planner
Make supervised volunteer scope explicit before assignment.
- For
- Legal aid clinic coordinators
- Solves
- Volunteer capacity is allocated before matter scope is clear.
- Delivers
- Supervisor-approved pro bono scope pack
- Built in
- about 5 weeks of creation time, MVP in 6 days
- Investment
- $12,000 for the MVP, $41,000 for the full product
- Run it
- Inside your business, or as part of your offer to clients
What it does
For legal aid clinic coordinators, turn client-consented intake and supervising lawyer criteria into supervisor-approved pro bono scope pack.
- Structure stated requests.
- Identify missing facts.
- Draft task boundaries.
- Map volunteer availability.
- Record supervisor choices.
- Export engagement checklist.
What goes in, what comes out
- Client-consented intake
- Supervising lawyer criteria
AI drafts, people review. Assumption-driven planning and decision workspace.
- Supervisor-approved pro bono scope pack
How it works
The workflow
- InStart with
Client-consented intake and supervising lawyer criteria
- 1
The buyer creates a project
- 2
Supplies client-consented intake and supervising lawyer criteria
- 3
Confirms scope and access
- OutFinish with
Supervisor-approved pro bono scope pack
AI does the heavy lifting, people stay in charge
Organize stated needs without predicting case merit. Keep model suggestions separate from verified facts. Link factual outputs to authorized input evidence and show missing information explicitly. Use deterministic checks for counts, dates, identifiers and arithmetic where applicable. A designated reviewer validates consequential outputs and signs off the delivered result.
What your team sees
Key screens: Scope intake, Task breakdown, Supervisor review. Place editable drivers and constraints beside a clearly labeled scenario output. Include a baseline view, comparison chart or schedule, and an assumptions history. Let users trace a proposed quantity or date back to its inputs. Keep forecasts distinct from actual results. Open with scope intake; move into task breakdown for the detailed task; finish in supervisor review for review and handoff. Show the source record, uncertainty and approval status beside each proposed output.
Accounts and administration
Scenario versions, baseline reconciliation, constraint checks, assumption ownership, reviewer approvals, plan exports and actual-versus-plan tracking. Include organization-scoped access, named project owners, review queues, usage limits, export history and retention settings. Never reuse private customer material for other accounts without permission.
Integrations and data access
Authorized matter files, firm templates and approved legal knowledge collections. Read-only operational exports, calendars and finance or inventory records as relevant. Start with plan exports and retain human approval for execution. Begin with uploads and exports of client-consented intake and supervising lawyer criteria. Any named system or connector is a candidate requiring current access and compatibility checks; no live connection is included by default.
How we build it
We build with our own AI software development factory, so most implementations take days to a few weeks of creation time, not months. You see working software at every step, and exact timing depends on availability.
- 1
Scoping call
Day 1Thirty minutes on your process, your data and how you want to run it: for your own team, or for your clients. You get a fixed scope and price for the MVP.
- 2
MVP
6 daysOne buyer segment, one recurring use case; first modules: structure stated requests; identify missing facts. Manual review in the loop. Built by our AI software factory.
- 3
Paid pilot
7 daysAccounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.
- 4
Full product
3 weeksSelf-serve onboarding, billing, monitoring and the wider integration set.
- 5
Run and improve
MonthlyWe host, monitor and improve it for a fixed monthly fee, or hand it over to your team. How the retainer works.
Why we start with an MVP
An MVP, or minimum viable product, is the smallest version that your users can actually work with. It is not a cheap version of the full solution. It is a test, built to answer the questions that decide whether the rest is worth building.
- Pick the riskiest assumption. Here: will legal aid clinic coordinators use it to solve "volunteer capacity is allocated before matter scope is clear"?
- Build only what tests it. One team, one use case, a few core modules. People do the rest by hand for now.
- Run a paid pilot. Agree the acceptance criteria, input limits and reviewer responsibilities before starting.
- Measure, then decide. Track incomplete scope and assignment preparation time. Then expand, change course or stop, with evidence instead of opinions.
MVP scope for this solution. Costed pilot: No legal advice or automated client eligibility decisions. Start with one buyer organization and a bounded set of representative inputs. Implement the first two modules: structure stated requests; identify missing facts. Support the third task through an assisted review queue: draft task boundaries. Handle the remaining required functions manually until validated. Include input upload, source references, user correction, a reviewer approval step and export of supervisor-approved pro bono scope pack. Authentication, account isolation, deletion controls and basic operational logging are included. Specialized production certification, live write integrations and broader rollout are not included unless explicitly stated.
After the MVP. After paying customers repeatedly accept supervisor-approved pro bono scope pack, automate map volunteer availability; record supervisor choices; export engagement checklist. Add one tested read integration, reusable customer configuration and scheduled repeat delivery. Increase supported formats or teams only when evaluation cases and reviewer capacity cover the new scope. No legal advice or automated client eligibility decisions.
What the build depends on. A defensible calculation model, explicit units, constraint validation and representative boundary tests. Advanced forecasting or optimization needs adequate historical data. Obtain representative authorized inputs, an agreed review rubric and a buyer-side owner. Specific scope: No legal advice or automated client eligibility decisions.
Investment
A planning range to start the conversation, not a quote. You pay per phase, so you can stop after the MVP.
- Phase 1
MVP
One buyer segment, one recurring use case; first modules: structure stated requests; identify missing facts. Manual review in the loop.
- Phase 2
Paid pilot
Accounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.
- Phase 3
Full product
Self-serve onboarding, billing, monitoring and the wider integration set.
Indicative total, MVP to full product$41,000about 5 weeks of creation time · start with the MVP from $12,000
Running costs per month
A rough indication of monthly hosting and AI model costs once it is live, not tested. Real costs depend on usage, file sizes and the models chosen.
| Stage | Hosting and infrastructure | AI usage | Total per month |
|---|---|---|---|
| MVP and paid pilotabout 3 customers | $50–$100 | $50–$100 | $100–$200 |
| Full productabout 50 customers | $190–$380 | $350–$700 | $540–$1,080 |
Run it or resell it
For your own team
Legal aid clinic coordinators run it inside the business: client-consented intake and supervising lawyer criteria in, supervisor-approved pro bono scope pack out, reviewed by your people.
As part of your offer
Agencies, consultancies and software companies can offer it to their own clients under their brand. We build and maintain it; you sell and deliver it.
Your brand, or this one
Run it under your own brand, or start from this concept style.
- primary
#276a91 - accent
#c99554 - surface
#e4ecf1 - ink
#22201e
- Headings
- Fraunces
- Text
- Inter
- Voice
- Precise, measured, defensible
Selling it to your own clients: the go-to-market playbook
Pricing to test
Test USD 750-3,000 for a scoped planning setup and review, then USD 200-900 monthly for refreshes within agreed complexity. Data integration and optimization are separately scoped. All ranges are hypotheses. For this buyer, package the first sale around scope five synthetic matters and the defined supervisor-approved pro bono scope pack. Record actual review effort before offering a recurring allowance. The commercial pilot fee is distinct from the platform development budget.
Message to test
Make supervised volunteer scope explicit before assignment. Demonstrate the result with scope five synthetic matters for legal aid clinic coordinators. Use a concrete before-and-after example without promising unmeasured savings.
Where to find buyers
Legal aid networks and law school clinics
Lead magnet
Scope five synthetic matters
The first 30 days
- Week 1: interview five prospective buyers from legal aid clinic coordinators and inspect how they handle volunteer capacity is allocated before matter scope is clear.
- Week 2: prepare scope five synthetic matters using authorized or synthetic material.
- Week 3: share the demonstration through legal aid networks and law school clinics and seek one bounded paid pilot.
- Week 4: measure incomplete scope and assignment preparation time, review delivery effort and ask for a repeat purchase. This is a validation schedule, not a promise that the full product can be built in thirty days.
Paid pilot
Agree the acceptance criteria, input limits and reviewer responsibilities before starting. Run scope five synthetic matters and deliver supervisor-approved pro bono scope pack. Compare incomplete scope and assignment preparation time with the buyer's current process on comparable cases; include corrections, missed issues and reviewer time. Seek payment and repeat use. Stop or revise the scope if data access, accuracy or unit economics fail.
Success metrics
Incomplete scope and assignment preparation time
Retention and expansion
Build repeat use around supervisor-approved pro bono scope pack. Save approved configurations and review decisions with permission, revisit unresolved exceptions and show progress on incomplete scope and assignment preparation time. Offer a recurring volume allowance after repeat demand; expand to adjacent tasks only when the buyer asks and delivery quality remains acceptable.
Why clients would pick it
A validated domain model, customer-approved constraints and forecast or decision history that improves practical planning. For this concept, accumulate permissioned examples and reviewer corrections around make supervised volunteer scope explicit before assignment. The durable asset is reliable task-specific execution and trusted customer configuration, not access to a general-purpose AI model.
Alternatives and positioning
Spreadsheets, planners, specialist forecasting tools and existing scheduling or configuration software. Position this concept around make supervised volunteer scope explicit before assignment. Compare it against the customer's current process on the same representative task. This is proposed differentiation; no exhaustive competitor study or uniqueness claim has been established.
Main delivery costs
Data preparation, domain modeling, validation, scenario computation, reviewer support and ongoing assumption maintenance. Initial validation additionally budgets for supervising lawyer review. Track model usage, storage, reviewer minutes, exception handling and customer support per accepted deliverable.
Safeguards
Preserve matter confidentiality, access boundaries and original evidence. Qualified professionals review legal interpretations and final client documents. No legal advice or automated client eligibility decisions. Require appropriate access and publication approval. Preserve source material, label AI drafts and make corrections traceable. Measure false positives and missed cases alongside speed.