LegalTech platform

AllawLegalTech · B2B SaaS

Full-stack work on Allaw: building case management, contributing to multi-office pages and improving public-facing journeys, with a focus on UX and reusable components.

Montage of Allaw interfaces: professional search, appointments and client cases

Overview

From appointments to cases, a connected legal experience

The problemLegal professionals need to manage cases, appointments and sometimes multiple locations, while clients need a clear public-facing journey.

The solutionBuilt a case-management module linked to the calendar, helped design pages for multi-office structures and created a shared UI component library for the interfaces.

User workflow

Search and discovery

A starting point for exploring legal professionals, their services and public information.

1 / 4: Find a legal professional. Previous step / Next step

Technical architecture

Documented application structure: Next.js interfaces, Node.js APIs and MongoDB data serving public and professional workflows.

Web interfaces

Next.js / React

Public experiences and practice administration
Business requests

Business API

Node.js

Case, organisation and appointment operations
Read and write

Data store

MongoDB

Persistence of business information
  • Web interfaces: Next.js / React. Public experiences and practice administration Business requests.
  • Business API: Node.js. Case, organisation and appointment operations Read and write.
  • Data store: MongoDB. Persistence of business information

Technical challenges

01

Building case management from scratch

Constraint

No existing module: data needs, administration screens and the client experience all had to be defined.

The solution

Designed the module end to end, adding responsive interfaces and components consistent with the design system.

02

Connecting business workflows

Constraint

Client cases could not remain disconnected from appointments already managed in the calendar.

The solution

Linked cases and appointments, connecting case follow-up with scheduling.

03

Modelling multi-office organisations

Constraint

A firm may run several offices, and a professional may work across multiple locations.

The solution

Designed a shared representation of offices and professionals for the office pages and their map.

04

Controlling office page editing

Constraint

The person creating a page is not necessarily authorised to manage everything in the organisation.

The solution

Factored invitations and role-based permissions into the design of access to office administration.

Main technical stack

Next.jsReactTypeScriptNode.jsMongoDBPlaywright

Outcomes and learnings

Case management connected to the calendar

A module built from scratch, with practice interfaces and the ability to link cases to appointments.

Pages for complex office structures

Public pages designed to display offices, maps and teams, with office-editing access requirements.

Reusable UI component library

An NPM component package expanded over time and available to other frontend developers.