DEV3 Writfold – Law Firm Case Management SaaS Laravel Script with Conflict Checks, Deadlines, Trust Ledger

Writfold is a matter-management system for law firms, built by DEV3 Technologies on Laravel 12 and Filament 4. You run it as the operator: you sell plans to firms, and each firm opens matters for its clients after a conflict check, tracks deadlines from its own rule sets, keeps documents with versions, records time and expenses, bills with invoices, holds client money in a trust ledger and gives clients a portal.

What it does

• Conflict check before a matter opens. Names and aliases are normalised (case, punctuation, company suffixes, initials) and searched across the firm's contacts and matter parties. A matter cannot move from intake to open without a cleared or waived check that covers every party. Adding a party to an open matter starts a new check automatically.
• Ethical walls. A walled matter is visible only to the people on its list, in every list, search, report, notification, download and API call. A hit on a walled matter shows only as "restricted matter".
• Deadlines from rules the firm configures. A trigger event such as "Claim served" creates deadlines in calendar or business days, rolled past weekends and holidays. Edit the trigger date and generated deadlines recompute while dates set by hand are kept. A calendar, the Docket Line timeline and an ICS feed are included.
• Documents. Folders, numbered versions, check-out locks, version-conflict protection, templates with merge fields to DOCX and PDF, search, files kept private and scanned, and signed five-minute downloads that re-check matter access.
• Time, expenses and invoices. A timer and quick entry in six-minute or one-minute units, rate cards by person, role and activity, approval, invoices built from work in progress with a write-down line, partner approval, pay links, partial payments and refunds.
• Trust ledger. An append-only client ledger, withdrawals and transfers that need a second approver, apply-from-trust to pay an invoice, and a three-way reconciliation report as a PDF.
• Client portal. Matter status, shared documents, upload requests, shared hearing dates, invoices with a pay link, a trust statement, secure messages, on the firm's own subdomain or custom domain.
• Operator panel and API. Firms, plans, subscriptions, client payments, payouts, pending refunds, an outbox, a metadata-only audit view and audited view-only support sessions that cannot open documents or trust ledgers. A scoped REST API with OpenAPI and signed webhooks.

Quality checks

The release passed seven gates on the final code: Larastan level 6 with 0 errors, 281 Pest tests, a build inside the page budget, migrations and the demo seed on MySQL 8 and SQLite, a headless smoke test with the MySQL race groups (parallel trust withdrawals, double approval, parallel invoicing from the same work in progress, apply-from-trust against an online payment, parallel uploads to one document), the installer driven from the zip, and a secret scan. The home page scores 99 for performance and 100 for best practices on mobile.

What you should know before buying

• Deadline rules are aids, not legal advice. They are templates the firm configures; they are not court-certified calendaring. Every date must be checked by the firm.
• Trust money is recorded, not collected. The trust ledger follows a simple three-way reconciliation report. Check your local bar rules; this is not a compliance certificate. A wrong transfer has no undo button: corrections are new, approved reversing entries.
• You are the merchant of record for online invoice payments (simulated by default). Firms cannot connect their own payment account in this version.
• No e-filing and no e-signatures. Export a PDF to your own signature tool. The conflict check searches only data inside the firm's own workspace.
• Complex Word templates may need adjusting. DOCX output is simple text and paragraphs.
• Forward-to-matter email needs an inbound mail provider. Provider webhooks are signature-verified, but a captured valid request could be replayed inside the provider's timestamp tolerance.
• Simulated drivers. Mail, payments, virus scan and inbound mail have working simulated drivers; real ones need your own accounts.
• The billing unit is locked while unbilled time exists. A cron entry every minute and a queue worker are required. Web only: there are no mobile apps. Node.js is not needed (assets are prebuilt).

Included

Source code, the web installer, a buyer guide with the API contract and the race and tenancy notes, demo data with four fictional firms, clients and people, and six months of support.