# LegalFlow V2 — Reddit & X Content Pack Generated: 2026-04-24 Product: LegalFlow V2 — legal practice management for small firms Target: attorneys, paralegals, small/mid law firms (5-50 people) Pricing: $39-99/user/month, 14-day free trial --- ## REDDIT POST 1 — Pain Point Post (no product mention) **Target subreddits:** r/paralegal, r/lawyers, r/LawFirm, r/legaladvice **Account type:** New/low karma — build credibility first **Goal:** Get people talking about billing/time tracking pain points → DM the most engaged --- **Title:** How do you actually handle time tracking at your firm? Ours is kind of a disaster **Body:** Asking because I genuinely want to know if this is just us or if it's universal. Small litigation team, 8 people. Every month around billing time, same thing happens. One attorney tracks in a spreadsheet, another has sticky notes, one person is honestly just estimating at the end of the week. By the time invoices go out, we've probably lost 15-20% of billable hours just from tracking gaps. I've tried pushing everyone onto standalone tools but the pushback is always the same — nobody wants to open a separate app mid-workday when they're already switching between their case files and email and everything else. Is there something that actually works for small teams? Or is spreadsheet chaos just the baseline expectation for firms this size? --- **Attached DM template (for engaged commenters):** > Hey [Name], saw your comment about [specific thing they said] — that's pretty much exactly the situation I was describing. I've actually been looking at some solutions for this and wanted to ask: when you say [reference their specific pain point], is that mostly a tooling problem or more of a habit/process problem? > > Working on something that might be relevant and would love 20 minutes to hear your take on it, if you're open to it. No pitch, just want to understand the problem better. --- ## REDDIT POST 2 — Builder Story Post (beta invite) **Target subreddits:** r/SaaS, r/entrepreneur, r/startups **Account type:** Need 50+ karma first — post pain point post to r/paralegal first **Goal:** Direct beta signups from builders + legal adjacent people --- **Title:** Built a practice management tool for small law firms. 8 months later, here's where I actually stand. **Body:** I'll be upfront: I underestimated how much the billing problem would dominate everything. About 8 months ago I started building LegalFlow — case management software for small law firms. My assumption going in was that attorneys' main problem was keeping track of cases, deadlines, and documents. So I built that: case tracking, evidence chain, deadline calculations with court rule logic. Shipped it. Attorneys tried it. The feedback was mostly some version of: "This is actually useful. But where's billing?" Right. The tool I'd assumed was the core feature turned out to be table stakes. The actual problem — the one that costs firms money every single month — is that attorneys are losing billable hours because tracking time is annoying enough that people just don't do it until end-of-week, and by then they've forgotten half of what they worked on. So I spent the last 3 months rebuilding around that. LegalFlow V2: - Timer that ties directly to cases (start it when you open a file, stop it when you close) - Invoice generation from actual time entries — no manual re-entry - Stripe integration so clients can pay the invoice online - Client portal where clients can see case progress and download documents without emailing you - Document templates that auto-fill case data (client name, case number, etc.) We're going into beta next week. Looking specifically for small firms (5-50 people) who are currently on Clio/MyCase and annoyed at the price, or who are still on spreadsheets and manually reconciling billing every month. Not looking for feedback on the idea — I've talked to enough attorneys to know the problem is real. Looking for people who will actually use it and tell me what's broken. If that's you: legalflow.app or DM me here. --- **Attached DM template (for people who comment interest):** > Hey [Name], thanks for the comment. I saw you mentioned [specific thing] — that's exactly the use case I've been building around. > > Would you be open to a quick 20-minute call? I want to walk you through where the product is, but more importantly I want to understand how billing actually works at your firm right now — the process, not just the tool. That context helps me build the right thing. > > If video calls aren't your thing, happy to do async — I can send you a Loom walkthrough and you can reply with voice notes or text. Whatever works. --- ## REDDIT POST 3 — Technical Post (for r/webdev, r/nextjs, r/node) **Target subreddits:** r/webdev, r/nextjs, r/node **Account type:** Any karma level **Goal:** Builder credibility, indirect awareness --- **Title:** Building multi-tenant SaaS with Next.js App Router + Prisma — here's what actually tripped me up **Body:** About 8 months into building LegalFlow, a practice management tool for law firms. Multi-tenancy was one of those things I thought I understood going in. I didn't. A few things that cost me more time than they should have: **Row-level security via Prisma middleware:** The obvious approach is adding `where: { firmId: ctx.firmId }` to every query. The less obvious part is doing this without making every query a nightmare to write. Ended up building a middleware wrapper that injects the tenant context automatically, but it took a few iterations to get right without breaking the Prisma query builder's type inference. **Magic Link auth with NextAuth:** The default email provider in NextAuth works fine for consumer apps. For a B2B product where you want to send clients a one-time login link to a specific case (not just to the app), you need to basically build your own flow on top of it. The token verification logic is straightforward, but the redirect logic was fiddly. **PDF generation:** Tried Puppeteer first. Terrible cold start times in a serverless environment. Switched to @react-pdf/renderer. Works well enough for invoices but has some CSS limitations you'll hit immediately if you're used to regular Tailwind. Anyone else building legal or finance SaaS with Next.js? Curious what your stack looks like for the billing side — specifically around invoice PDF generation at scale. --- ## X / TWITTER CONTENT ### Tweet 1 — Build-in-public (week 1) Spent 3 months adding billing to a legal case management tool. Most common complaint from small firms: they know they're losing billable hours but have no idea how much. Usually around 20%. LegalFlow V2 beta opens next week. DM if your firm is still tracking time in spreadsheets. --- ### Tweet 2 — Pain point (for engagement) Law firms are still running billing on spreadsheets in 2026. Not because they want to. Because Clio is $139/user/month and the alternatives are either barely functional or priced the same. There's a gap there. --- ### Tweet 3 — Beta launch announcement LegalFlow V2 is in beta. Built for small firms that are done with spreadsheet billing. - Timer tied directly to cases - One-click invoice from billable hours - Client portal so they stop calling to ask for updates - Stripe payments built in $39/user/month. 14-day free trial. legalflow.app --- ### Tweet 4 — Specific feature highlight (client portal) The thing I didn't expect to get the most positive reaction from attorneys: The client portal. Not billing. Not the timer. The fact that clients can log in and see case status themselves. Turns out a lot of what paralegals spend their day doing is answering "what's happening with my case?" emails. If clients can just check, that time goes somewhere else. legalflow.app — beta open now. --- ### Tweet 5 — Pricing comparison (direct) Clio: $49-139/user/month MyCase: $39-89/user/month PracticePanther: $59-129/user/month LegalFlow: $39/user/month. Full billing, client portal, document templates, mobile. 14-day free trial. legalflow.app --- ## POSTING SEQUENCE **Week 1:** 1. Post pain point post to r/paralegal (no product mention) 2. DM anyone who responds with substantive comments 3. Post Tweet 2 (pain point) to X **Week 2:** 1. Post builder story to r/SaaS (once r/paralegal account has karma) 2. Post technical post to r/webdev 3. Post Tweet 1 (build-in-public) + Tweet 3 (beta launch) 4. Post Tweet 4 + Tweet 5, spaced 2 days apart **Do NOT post all Reddit posts in one day — Reddit will flag as spam.**