This is what it does
Try it
PreLawyer posts a case without your name, reads it back as a strength estimate and a limitation window, and reveals who you are only to the one lawyer you accept. Post a case to start.
Runs in your browser — nothing to install
- What it does: turns an anonymous case description into a deterministic strength estimate and a limitation window, and exposes your identity to one firm only if you accept its interest.
- What to try: post a case, read the score and the reasons behind it, watch a lawyer express interest, then accept one and reveal yourself to that firm alone.
- What it does not do yet: it is not legal advice and not a prediction of a court outcome — it reads the words you supplied. The demo runs its whole data layer in the page, so no real lawyer sees anything.
Status
What is built, and what is not
- The whole flow runs in a browser. Consumer intake, the anonymous lawyer feed, interest, the identity reveal and the conversation run against an in-browser engine whose seed mirrors the backend’s database fixtures. It opens with no server, no build step and no account.
- The backend implements the contract the interface was written against, with 37 automated tests passing. Two of them are the ones that matter here: an unauthenticated request is refused, and an unaccepted firm’s view of a case carries no name, no e-mail and no owner id in any field.
- The estimate is reproducible and the profiles are not verified. The score is arithmetic over the words you supplied, with no randomness and no clock, so the same case always reads the same — and lawyer profiles are self-declared, which is how you should treat them.
Under the hood
What it is built on
- Stack
- A browser front end over a small REST backend. The demo carries the whole data layer in the page; the backend is a single Node process with a single-file store.
- Runs where
- Entirely in your browser for the demo. The backend runs as one Node process with a store that can be copied, moved and read as one thing.
- Payments
- The person with the problem does not pay. The firms that receive the work pay, which is how this one is intended to be funded.
- Tested by
- 37 automated tests on the REST backend, including the unauthenticated-request refusal and the no-name/no-e-mail/no-owner-id assertion for an unaccepted firm’s view.
Tell us what broke
Whether the flow fits a firm you run, how the estimate reads on a case you know well, or anything the demo got wrong — the feedback form is the way in.