Legal intake and portal engineering
We build the handoff between your intake system, your client portal and the practice-management system that stays your record. We prove it small first: an approved intake becoming a matter-ready record, without anyone retyping it.
The problem
A firm rarely buys one system for this. It buys an intake tool, a practice-management system, a signature tool and a portal, at different times, from different vendors.
The intake CRM captures the inquiry and the engagement decision. The practice-management system holds the open matter, conflicts and billing. Moving a record from one to the other takes engineering work.
Documents sit in a shared drive, a signature goes through a separate tool, and a follow-up lands in a personal inbox. The client experiences one relationship. The firm's systems do not.
Conflict checks and client acceptance belong to an attorney. Intake software is built to move an inquiry forward fast, and that speed can bury the approval step instead of surfacing it.
An intake tool, a portal, a signature product and a document system each earn their place over time. What is usually missing is the connection between them.
What gets built
The practice-management system stays the record of the matter and the billing. What we build is the handoff around it, so an intake tool and a portal agree with it instead of a spreadsheet.
| Intake staff | Log an inquiry once, see which stage it is in, and know which document or signature is still missing. |
|---|---|
| Attorney | Reviews the summary, clears the conflict question and approves the engagement. Nothing earlier counts as acceptance. |
| Client | Uses a permissioned portal to send documents, sign forms and see where the matter stands. |
| Office or practice manager | Sees where a handoff is stalled and whether it is waiting on a system or on a person. |
| Intake CRM (for example Clio Grow or Lawmatics) | Captures the inquiry, the consultation and the engagement status. |
|---|---|
| Practice management (for example Clio Manage) | Stays the record of the open matter, conflicts and billing. Nothing we build replaces it. |
| Document and e-signature tools | Signed agreements and engagement letters stay where they are already trusted. We connect to them. |
| Client portal | The permissioned view a client sees, built on the systems above. |
Synthetic demonstration: invented records
Larkspur Estate Partners is a firm we invented to show how an approved intake becomes a matter-ready record. It does not exist. No real firm, client or matter appears in this demonstration.
The prototype takes a completed intake through identity verification, an attorney's conflict and engagement decision, and a handoff to the practice-management system with the right permissions set. It writes once, even on a retry, so a slow connection never creates a duplicate matter.
| No. | Entry | What happens |
|---|---|---|
| 1 | Inquiry | An inquiry arrives in the intake CRM with a name, a matter type and a preferred contact method. |
| 2 | Verification | Staff confirm identity and matter type before anything moves further. Nothing here decides a conflict. |
| 3 | Attorney approval | An attorney reviews the summary, clears the conflict question and approves the engagement. The software waits for that decision; it never makes it. |
| 4 | Matter-ready handoff | The approved record writes once to the practice-management system, with permissions set and no duplicate entry, even on a retry. |
Ownership and maintenance
How it goes
Every step leaves you with something useful, even if you decide to stop there.
We learn which systems you run today, where the handoff breaks and what a good result looks like. You get a short written summary.
A map of one handoff, for example intake to engagement: who does what, in which system, and where an attorney's decision belongs.
A fixed scope for a pilot: what gets built, for whom, how we judge it and what it costs.
A small group of your staff use it with real intakes, while the systems you run today keep working.
You compare the pilot with how the handoff worked before, and choose: stop, extend it, or plan a wider rollout.
A staged rollout to more staff or matter types, with maintenance agreed in writing before it starts.
A short decision aid
Most firms can gather this in an afternoon. It shortens every conversation that follows, ours or anyone else's. If you are still sorting out the categories, the guide to which system owns what compares intake, the matter record and client collaboration.
Who you would work with
Legal Workflow Studio is a site of The Goodstack Company. There is no sales team. You talk to the people who would do the work, and we say plainly what we know and do not know about legal practice.
Engineering and delivery
Legal is a new industry for us and we have not delivered a legal system yet. What David brings is the handoff engineering: he runs beLoved Health, a distribution company, and built the system it runs on, where an approval in one place has to become a record in another without anyone retyping it. He writes the code here, and he will ask your intake staff how your firm actually works before proposing anything.
Product and design
Vidur is the co-founder of Goodstack and leads product and design. He designed the original Goodstack and ran the studio with David. On this work he owns what intake staff and the approving attorney see at the moment a decision is recorded, and he has experience with SOC 2 compliance, which shapes how client data is scoped and logged.
Questions buyers ask
Tell us which systems you run today and which handoff breaks most. We will reply with what we would look at first, including whether legal software fits yet.