Case study Legal · New York and New Jersey · Site and intake engine

A law firm that waits for the phone
is waiting behind everyone else.

Schwartz Goldstone Campisi & Kates are a New York trial firm that takes the cases other firms turn away. We built them two things: an eighteen-page website with an intake that actually captures, and an engine that finds qualified cases from public accident records before anyone has picked up a phone.

Schwartz Goldstone Campisi and Kates
90 Broad Street · state and federal courts
Lower Manhattan
The firm's new homepage
Pages built
18
Largest reported recovery
$12.6M
18
pages, built to their brief
16
practice areas, custom icons
2
states, state and federal
11
engine routes behind the intake
Manan Mehta with the AI Crew team in the Mumbai office
From our office
The crew behind the tools.

Founders and professionals talk to Manan. The building, testing and support happens here, in the room.

The AI Crew team at work
Who you work with
Manan Mehta and the crew
arrow_forward
New York street
What we found first: their old site had no enquiry form at all. A phone number, and nothing else.
01 · The situation

Good firm. Invisible pipeline.

A trial firm with real verdicts behind it, competing for attention against national advertisers with enormous budgets. They were buying leads from a service and were not happy with what arrived. The work was excellent and the front door was closed.

call_end
No way to enquire

Somebody reading at eleven at night could not do anything except write down a number and hope to remember.

shopping_cart
Bought leads, sold twice

The same lead reaches several firms at once. You are racing on response time, not on merit.

public
Two states, one story

They do a lot of New Jersey work and federal litigation. Neither was visible anywhere on the old site.

02 · Part one, the site

Eighteen pages, and a front door that opens.

Attorney profiles, sixteen practice areas, a legal insights library the firm writes into themselves, and an intake widget that does not read like a robot. That last part was the client's only strong dislike about a competitor's site, so it became the design constraint.

Homepage
The homepage
Their own words, kept

"We take the cases other firms turn away" was already how they described themselves. It became the first line on the page, over real verdicts rather than adjectives.

Case review intake widget
The intake
Human, one question at a time

Docked to the side, opens by itself a few seconds in, and asks what happened before it asks who you are. Spanish offered on the first screen, because their clients ask for it.

$12.6M
Roadway defect
$8.3M
Construction worker
$7.5M
Automobile accident
$5.93M
Medical malpractice

Their own reported recoveries, carried across from their records onto the new site.

account_treeHow the intake engine works

The public record in. An attorney-ready packet out.

Two front doors: a site that captures, and an engine that finds cases before anyone calls.

Comes in
descriptionNew Jersey crash reportsUnder the public records act
chatThe website intakeEnglish or Spanish
gavel

SGC intake engine

Screens every case against the firm's own rules.

  • check_circleParses parties, injuries, vehicles, insurers
  • check_circleDeterministic screener, same answer every time
  • check_circleBusiness-day clock on every deadline
Goes out
articleA one-page packetRead in under a minute
reportA challenge packWhen a request is refused
mark_email_readEnquiries to the firmFrom the eighteen-page site
Engine
send01Request the record

To the right custodian, with the statutory certification attached.

Engine
document_scanner02Read the report

Parties, positions, injury codes, vehicles, carriers and insurers.

Engine
rule03Screen it

The firm's rules, applied the same way every time, so a decision can be explained.

Engine
article04Build the packet

A one-page summary with the source report underneath it.

Attorney
person05Read and decide

Nothing sends without a human. The switch is the firm's to turn.

Visitor
chat06Or they come to the site

An intake that asks what happened before it asks who you are.

Built withNext.jsSupabasedocument_scannerCrash report parserruleDeterministic screenereventBusiness-day clockmailMailbox adapter
03 · Part two, the intake engine

Stop buying leads. Read the public record instead.

Every serious crash in New Jersey generates a police report, and those reports are obtainable under the state's public records act. The engine requests them, reads them, screens them against the firm's own criteria and builds a packet an attorney can act on. The firm is not competing for a lead. They are first.

01
Request

A records request goes to the right custodian at the right department, with the statutory certification attached.

AI
Read the report

The reply comes back as a crash report. It is parsed into structured facts: parties, positions, injury codes, vehicles, carriers, insurers.

03
Screen

A deterministic screener applies the firm's rules. Same input, same answer, every time, so a decision can be explained.

04
Packet

What survives becomes a one-page summary an attorney reads in under a minute, with the source report underneath it.

Case packet

A packet carries unit and seat position only. Names and contact details stay in the source report and are never restated.

The deadline clock runs on business days

Statutory response windows are counted properly, including holidays, because a missed day is a lost case.

Statutory
The occupant gate

A crash is only worth the firm's attention under specific conditions. The gate runs before anyone spends a minute on it.

Qualifies
A denial is a workflow, not a dead end

If a department refuses, the engine assembles the challenge pack rather than dropping the request.

Escalates
Nothing sends without a human

The certification wording is the firm's to write, and the send switch is theirs to turn. We do not sign anything on a law firm's behalf.

By design
04 · The homework

We sized it on real numbers, not on a guess.

Before writing the engine we went and found out how many crashes New Jersey actually produces, how many involve a commercial vehicle with an injured occupant in the other car, and what the records themselves cost per department. That is what decides whether this is a business or a demo.

276,861
NJ crashes, 2023 full year
59,850
injury crashes
2,780
truck and bus, reportable
~232
of those per month statewide
Where the base rates come from

We also checked every target department against its own published page. Not all of them accept a records request by email, and several of the largest publish no records address at all. That is a finding the firm needed before the first request, not after.

05 · What changed

Two front doors instead of none.

Before
  • closeA site with a phone number and no form
  • closePaying for leads sold to several firms at once
  • closeNew Jersey and federal work invisible online
  • closeNo way to write and publish their own commentary
After
  • checkAn intake that opens itself and asks in plain language
  • checkCases found from the public record, not bought
  • checkTri-state and federal called out across the site
  • checkA legal insights library the firm runs themselves
Decisions screen
How we hand it over

Seven questions, answered by clicking.

Every build reaches a point where only the client can decide. Instead of a long email, the engine has a screen: click the answers, hit generate, paste the block back. It takes four minutes and it removes the week that a question thread usually costs.

Next.jsSupabaseCrash report parserDeterministic screenerBusiness-day clockMailbox adapter
Case studies · built by the crew

More case studies. All live.

All case studies
Lower Manhattan
New York street
Courthouse
Intake widget