# LegalFlow — Reddit Post Package (English)
Generated: 2026-04-24
Target: r/paralegal, r/Lawyertalk, r/automation, r/CRMSoftware, r/SaaS

---

## POST A — r/paralegal (Pain-point only, NO product mention)
**Strategy**: Build credibility first. Drop the tool naturally in comments when people ask.

**Title:**
How do you track court deadlines when you're managing 15+ active cases? Still using spreadsheets?

**Body:**
I've been helping a few paralegals audit their workflows lately and one thing keeps coming up: the deadline tracking situation is genuinely scary.

We're talking spreadsheets, calendar reminders set manually, and in one case, a sticky note system that nearly caused a missed Answer deadline in a CA civil case.

What I found consistently:
- Calculating deadlines across FRCP vs. state rules (especially CCP §412.20 30-day Answer window) is done manually every single time
- There's no easy way to check if two case deadlines fall on the same day for the same attorney
- Evidence chain-of-custody is still a separate spreadsheet — totally disconnected from deadline tracking

For paralegals managing 10–20 active cases at a small firm, what does your current setup look like? Are there tools you've actually found useful, or is everyone just living in Excel?

Asking because I'm trying to understand whether this is a "our firm is just behind" problem or an industry-wide gap.

---

## POST B — r/Lawyertalk (Builder story / Show HN style)
**Strategy**: Transparent founder story. Invite beta testers.

**Title:**
I spent 3 months talking to paralegals at small litigation firms. Then I built what they kept asking for.

**Body:**
Quick background: I'm not a lawyer. I'm a software developer who kept hearing the same horror story from friends in litigation — someone at their firm nearly missed a court deadline because of a calendar sync failure, and the whole office went into panic mode for a week.

So I started doing interviews. Talked to about 20 paralegals and associate attorneys at firms ranging from 3 to 45 attorneys, mostly in CA, NY, and TX.

**The problems I kept hearing:**

1. **Deadline calculation is manual and error-prone.** Every time a case event happens, someone is manually counting business days, cross-referencing FRCP or CCP rules, and entering dates by hand. CCP §412.20 alone has multiple service method variations — it's easy to get wrong.

2. **Nobody knows what's happening across cases.** If Attorney A has a deposition and an Answer due on the same day, nobody finds out until the morning of.

3. **Evidence custody is a separate system.** Usually a spreadsheet. With no connection to the case timeline or deadlines.

4. **Existing tools are either too expensive or too narrow.** Clio starts at $79/user/mo. CaseFleet is $99/user/mo. LawToolBox only does deadlines. Nothing affordable does evidence + deadlines + conflict detection together.

**What I built (in beta now):**

- Auto-calculate court deadlines from a trigger event (FRCP + CA, NY, TX, FL, IL rules)
- Unified calendar showing all deadlines across all active cases
- Cross-case conflict detection — flags when two attorney deadlines overlap on the same day
- Evidence chain-of-custody logging with immutable audit trail
- Email reminders at 7, 3, and 1 day before each deadline

Pricing target: $29/user/mo (compared to $79–$149 for alternatives).

I'm looking for 3–5 small litigation firms to join a free beta and tell me everything that's wrong with it.

If you manage deadlines for a litigation team and want early access, drop a comment or DM me. Honest feedback is all I'm asking for.

---

## POST C — r/automation (Technical / process-nerd angle)
**Strategy**: Talk about the automation problem, not the product. Community loves "how I built this."

**Title:**
Built a court deadline auto-calculator covering FRCP + 5 state rules — here's what made it surprisingly hard

**Body:**
I've been building a tool for litigation paralegals and the hardest part turned out to be the deadline calculation engine. Sharing what I learned in case others are building in the legal space.

**Why it's harder than it looks:**

Legal deadlines aren't just "add X days to a date." There are at least 4 layers of complexity:

1. **Business days vs. calendar days** — FRCP Rule 6 uses calendar days for most deadlines but business days for shorter windows. CCP (California) mixes both depending on the motion type.

2. **Service method extensions** — If a document is served by mail (not hand delivery), California adds 5 calendar days. If served by fax or overnight mail, different extensions apply. You have to track how service was made.

3. **Holiday adjustments** — Federal holidays shift deadlines to the next court day. But state courts have their own holiday lists. CA adds Cesar Chavez Day. NY has Lincoln's Birthday. You need state-level holiday tables, not just federal.

4. **Jurisdiction-specific rules** — The same "Answer deadline" is 21 days under FRCP and 30 days under CCP §412.20. A firm handling cases in multiple states needs both applied correctly per case.

**What I ended up with:**

- Court rules stored as JSON fixtures (jurisdiction, case_type, trigger_event, days_offset, day_type, service_extensions)
- A calculation function that takes: jurisdiction + trigger event + trigger date + service method → returns all applicable deadlines
- US federal holidays + state court holidays for CA, NY, TX, FL, IL as a lookup table

The most surprising discovery: most paralegals I interviewed weren't aware of all the service method variations. They were applying the "standard" window and hoping for the best.

Anyone else building tools in the legal workflow space? Curious what edge cases tripped you up.

---

## POST D — r/SaaS (Build-in-public / transparent metrics)
**Strategy**: Founder narrative, early-stage data transparency.

**Title:**
6 weeks of building LegalFlow — what I learned talking to 20 paralegals before writing a line of code

**Body:**
Building in public. This is week 6 of LegalFlow, a deadline + evidence workflow tool for small litigation firms.

**The research phase (weeks 1–3):**

Before any code, I did 20 user interviews with paralegals and associate attorneys at small litigation firms (3–45 attorneys). Here's what I found:

- 18 out of 20 were tracking court deadlines in spreadsheets or manual calendar entries
- 14 out of 20 had experienced at least one "close call" with a missed deadline in the past year
- 0 out of 20 were using a tool that integrated evidence chain-of-custody + deadline tracking together
- The price anchors they mentioned: "If it's under $40/user I could probably get it approved without a partner conversation"

**The competitive gap:**

Clio and Filevine dominate the market but start at $79–$149/user/mo and are full practice management suites. Most small firms need maybe 20% of those features. LawToolBox handles deadlines only. CaseFleet handles evidence only. Nothing affordable does both.

**What I'm building:**

A focused tool that does one job well: evidence chain-of-custody logging + court deadline auto-calculation + cross-case conflict detection + email alerts. That's it. No billing, no DMS, no client portal.

Target price: $29/user/mo.

**Current status:**
- Core deadline engine done (FRCP + CA, NY, TX, FL, IL)
- Evidence custody logging with audit trail: done
- Cross-case conflict detection: done
- Calendar dashboard UI: in progress
- Beta: looking for first 5 firms

**What I'm curious about:**

For anyone who has sold B2B SaaS to law firms — what's the actual sales motion that works? Direct outreach? Legal tech communities? Referrals from existing clients?

---

## COMMENT TEMPLATES (Insert into existing threads)

### Comment 1 — For "what CRM do you use for law firms" threads
> If the pain is specifically around deadline tracking and evidence management rather than full CRM, there's a really specific gap here. Most of the big tools (Clio, Filevine) are full practice management suites that cost $79–149/user/mo. If you just need court deadline auto-calculation + evidence chain-of-custody logging + conflict detection, that's actually a narrower problem. I've been building something in this space — happy to share when it's ready for beta. The core issue is that deadline calculation under FRCP vs. state rules (especially service method variations) is genuinely complex and that's where people make mistakes.

### Comment 2 — For "what's the ROI of legal automation" threads
> The highest-ROI automation target I've seen in litigation is court deadline calculation. Missing a deadline is the #1 cause of legal malpractice claims (ABA data) and the average claim is $30K–$150K. Even if a tool just eliminates manual deadline counting and cross-case conflict checking, the ROI math is obvious. The tricky part is that most tools either nail deadlines (LawToolBox) or nail evidence management (CaseFleet), but not both together at a price point small firms can actually afford.

### Comment 3 — For "paralegal workflow" / "how do you manage cases" threads
> Honest question back: how are you handling cross-case conflict detection? Like if Attorney A has an Answer due AND a deposition on May 15 for two different cases — is there a system that flags that, or does it only surface the morning of? That specific gap came up in almost every workflow conversation I've had with paralegals at small firms. Most calendar systems show deadlines per-case but don't aggregate across cases per-attorney.

---

## POSTING NOTES

**Account requirements:**
- Account karma: 100+ before posting (spend 2–3 weeks commenting genuinely in r/paralegal, r/Lawyertalk)
- Recommended posting order: Comment Template 1/2/3 first → Post A (no product) → Post B (beta invite) → Posts C/D
- Space posts at least 3–5 days apart
- Never post to the same subreddit twice in the same week

**Anti-ban checklist:**
- [ ] All posts provide standalone value (readable without knowing the product)
- [ ] Post A has zero product mentions
- [ ] Post B is framed as "builder looking for feedback," not an ad
- [ ] No promotional language ("best", "amazing", "game-changing")
- [ ] Comments are genuine contributions, not just drops
- [ ] Domain/link only appears in Post B (and only in body, not title)
