Law students and legal professionals need a local desktop application to process messy folders of client invoices and purchase orders (POs) without uploading sensitive data to cloud AI services.

Target User

Law students and legal interns working in law firms

Product Idea

Local desktop application (Electron/Python): Secure, offline document processing tool for law firms that uses structured JSON logic to extract and categorize data from invoices and POs.

Evidence

• “I realized that a lot of AI tools are useless for finance because you can't upload sensitive client ledgers to OpenAI, and chatbots hallucinate numbers. +”

  https://www.reddit.com/r/SideProject/comments/1tl7kkr/i_got_tired_of_dealing_with_invoices_and_pos_at/

• “So I built a desktop app that runs entirely locally. Instead of a standard chatbot, it uses strict JSON contracts to chain together 6 different "agents" (a Cost Analyst, a Vendor Risk Assessor, etc.). +”

  https://www.reddit.com/r/SideProject/comments/1tl7kkr/i_got_tired_of_dealing_with_invoices_and_pos_at/

Why this opportunity matters

This opportunity surfaced from multi where Law students and legal interns working in law firms are actively describing the problem in their own words. We classified the demand intensity as high — meaning users are not just complaining, they are openly looking for paid solutions and willing to switch tools to find one. When users self-select to post a problem on a public platform like multi, they are usually already trying to solve it — which makes them strong candidates for the right paid alternative.

How to validate this before you build

Before writing a single line of code, three lightweight steps will tell you whether this opportunity is worth pursuing:

1. Read the original conversation. The evidence links above lead to the exact threads where users described this problem in their own words. Read every comment — what people argue about in the replies often matters more than the original post.
2. Talk to five real users. Find five people who match the target user description above and ask how they handle this today. You are looking for two signals: a consistent workaround they hate, and a willingness to pay for something better. If both show up in three of five conversations, the demand is real.
3. Test willingness to pay before building. Put up a one-page landing site describing the proposed product, with a deposit or pre-order checkout. If even a small fraction of traffic converts to a real payment, you have validated more than most products that ship to production.