Talk about a build
Menu

Custom software for law firms.

When no tool your firm pays for does the job, Ergonomc builds it: client portals, online questionnaires, dashboards and CRM connections.

If software you already pay for can do it, we'll show you the setting.

What a build replaces

  • Retyping web-form answers into the CRM

    A CRM connection

  • Chasing documents by email

    A client portal

  • Rebuilding the same report every Monday

    A dashboard

  • A long PDF questionnaire

    A step-by-step online questionnaire

By hand What your staff do todayBuilt What does it instead

Client portals

A client portal holds client details and case documents, in place of email threads and shared drives.

We built the client portal for Cohen & Cohen, P.C., a Colorado law firm. We've also built two-way document sync on a firm's own servers.

Example

Your case

Dana Ruiz, car crash on May 14

Where it stands

Collecting your medical records

Next: the demand letter to the insurer

Documents we need from you

  • Photos of the carUploaded May 20
  • Insurance cardUploaded May 20
  • Emergency room billUpload

Messages

Jen Ortiz, paralegal, May 22

Thanks for the photos. Please upload the ER bill when it arrives.

Online questionnaires

We rebuild long PDF questionnaires as step-by-step online forms, where each client sees only the questions that apply.

For Cohen & Cohen, P.C., we turned a 70-page PDF questionnaire into a step-by-step online form. We've also built lead qualification forms, such as a screener for bankruptcy Chapter 7 or 13, and a form builder.

Example

Before

A 70-page PDF

Every client gets every page.

After: one question at a time

Do you own the home you live in?

YesNo, I rent

Never shown to this client

  • Who holds the mortgage?
  • How much is still owed on it?
  • What is the home worth today?

Next, because they rent

How much is your rent each month?

Internal dashboards

We build browser screens that answer a question your other tools can't.

The Ghost Intake dashboard shows where prospects stop, question by question, and which pages and ad sources the leads came from. Only addresses on your allow-list can sign in, every view and deletion is logged with who did it, and it updates when you reload it.

We've also built dashboards for leads, clients, attorneys and admins, with user management.

Example

LeadsFunnelPagesSources

Last 30 days

Where do people stop on our form?

How many people reached each intake question, and how many stopped there
QuestionReachedStopped here
What happened?Includes forms whose questions never loaded5812
When did it happen?464
Got medical treatment?423
Any report?395
Spoke to insurance company?342
Have you missed work?321

Signed in as intake@yourfirm.example. Every view and deletion is logged.

CRM connections and WordPress plugins

We connect your website and forms to your CRM, where its API (the connection it offers other software) allows.

If the CRM can't be reached, each record waits and is retried, and someone is alerted if it still fails. An outage delays a lead. It doesn't lose it.

Our WordPress plugins put a form on any page, or a pop-up that opens from any button your web team marks. Your theme stays as it is.

We've built both for Ghost Intake, our intake software. Its Lead Docket connection creates the record and adds a plain-English transcript of the answers to its notes.

Example
  1. On your website

    What happened?

    Car crash

    Saved as it's tapped

  2. In Lead Docket, seconds later

    New lead: Motor Vehicle Collision

    Created at the first answer, which sets the case type

  3. About a minute after they stop

    Answered 4 of 6 questions, then stopped.

    The transcript of their answers, in the record's notes

If Lead Docket can't be reached

The record waits and is retried, and someone is alerted if it still fails.

How a build works

We build the missing piece and hand it over with notes another developer could work from.

  1. The call

    We spend 30 minutes on where the work stalls and who handles it. You'll leave knowing whether it needs a build.

  2. Mapping and a written plan

    We walk through the work with the people who do it. We read the documentation for every tool the build touches and test the parts that matter by hand. Then you get a written plan.

  3. Screens, then a test copy

    You approve the screens before we build them. We build on a test copy loaded with invented data, and your staff try it before anyone outside the firm sees it.

  4. Launch

    We install it, run a written launch checklist and send one labeled test record all the way through.

  5. Handover

    You get documentation another developer could work from: how it works, how to change it, what each alert means and how to restore a backup. You also get a list of every account the build uses and who can get into each one, and the support terms from the plan: what's covered after launch, and how quickly we respond when something breaks.

What the written plan states

You get it after the mapping, before work starts.

  • What the build does, and what it leaves out
  • Which accounts it runs on
  • What data it stores, where each copy is kept, for how long and who can see it
  • The milestones, with dates, and the price

Builds we can name

Intake software
Ghost Intake was first installed at Rudin Law, a personal injury firm, in August 2026. It saves each answer as it's tapped, and Lead Docket gets the record at the first one.
Client portal and online questionnaire
We built the client portal for Cohen & Cohen, P.C., a Colorado law firm, and turned its 70-page PDF questionnaire into a step-by-step online form.

How we built Ghost Intake

The job: a person who stops halfway through the form should still reach the firm's CRM with what they answered.

Before writing the delivery code, we tested Lead Docket's API by hand. Its integration can't change two fields after it creates a record, so the record waits for the first answer, which sets the case type. If the visitor never answers, the record still goes out within about a minute and a half.

What we built

  1. A short contact step on the firm's WordPress site leads to six questions answered with a tap.
  2. Each tap is saved as it happens, and the Lead Docket record is created at the first answer.
  3. About a minute after the visitor stops, the transcript lands in the record's notes. Its first line says how far they got.
  4. The questions are stored as settings, not code, and each lead keeps the exact wording it was shown.

Two rules it keeps

  • It never emails a prospect. The sending service's allow-list blocks it, and so does the code.
  • The intake code sends Google only that a step was reached, never answers or contact details.

What we don't do

We don't promise an integration before we've read the API.
Some case management vendors open their APIs only through partner programs, and some charge for access. We check before the plan is written.
We don't certify compliance or give legal advice.
Your firm approves consent wording and advertising copy. Ghost Intake stores the exact consent wording each prospect agreed to, with the time.
We don't add AI by default.
Ghost Intake has no AI in it and doesn't score leads. Six questions and careful plumbing did the job. When a build needs a model, such as speech to text, we decide first where it runs and how your firm can check it.

Questions about custom builds

Will it work with our CRM?

Yes, if the CRM's API allows what the build needs. We've built a Lead Docket connection. For another CRM, we test its API by hand during mapping, and the plan says what's possible.

How long does a build take?

The written plan gives dated milestones before work starts.

What does it cost?

We don't list prices here. The written plan states the price.

Will you have access to our client data?

Yes, during the build and while we support it. The test copy uses invented data.

Tell us the job.

A few lines will do: what the job is, how often it happens and which tools it touches. We'll reply by email, usually with a few questions before a call.