home work services about blog contact home work services about blog contact

Home
Work
Services
About
Blog
Contact
Start a Project →

webdmamun.

I build web applications that run businesses.

Ideas into useful solutions

Site

Home
Work
Services
About
Blog
Contact

Elsewhere

GitHub
LinkedIn
hello@webdmamun.com
AM IT Solution ↗

home work services about blog contact

Case Management & Fee Ledger | WebdMamun

← all work

INTERNAL TOOLSlive· 2026

Case Management & Fee Ledger

A case-management platform for a regulated advisory practice: stages, statutory deadlines, tasks, document control and an internal fee ledger.

my role: Sole developer
industry: Legal and immigration advisory
status: live

Next.jsReactTypeScriptPostgreSQLPrismaVercel

note — this system holds sensitive client data, so it is described without naming the client, without a link, and without screenshots of real records.

The problem

Cases lived in folders and inboxes. Statutory deadlines were tracked by whoever remembered them, caseworker load was invisible to the people responsible for it, and the fees agreed with a client existed only in the conversation where they were agreed.

What was needed

A system that makes the deadline the first-class object, shows who is carrying what, and records money agreed against the case it belongs to.

What I built

A case workspace where every case carries its stage, its deadlines, its tasks and its documents. Attention items surface what is due rather than waiting to be searched for. An internal ledger records agreed fees, instalments and payments received, giving the practice a financial view of the caseload without turning the tool into an accounting system.

Key features

Case intake and stages
Structured intake, then an explicit stage for every case.

next case study

AM IT Solution →

The operating system for my own software company: public website and internal CRM in one application, from lead through proposal, project, invoice and payment.

Deadline control

Statutory and internal dates tracked per case, with what needs attention surfaced first.

Tasks and allocation

Work assigned to caseworkers, visible to managers.

Document handling

Case documents held against the case rather than in a shared drive.

Internal fee ledger

Agreed fees, instalments and receipts recorded against the case.

Management view

Caseload, stages and outstanding items in one place.

Technical challenges

Sensitivity as a design constraint

The data is about people in the middle of a legal process, which rules out the usual conveniences: no third-party analytics on authenticated pages, no error reporting that captures request bodies, no screenshots of real records ‚Äî including in this case study, which is why it names no client and links to no live system.

Deadlines that mean something

A date field is easy; a deadline that changes the order of the day is not. Attention is derived from the case state rather than stored as a flag, so a completed step stops shouting on its own and nothing depends on someone remembering to clear a checkbox.

Money without becoming an accounting system

The practice needed to see what was agreed and what had arrived, but a full ledger would have been the wrong product. The fee record is deliberately internal and deliberately simple: agreed amount, instalments, receipts ‚Äî enough to answer the question, not enough to pretend it is bookkeeping.

Architecture

A Next.js application with an ORM over PostgreSQL. Authentication gates the whole workspace; there is no public surface other than the sign-in page.

Outcome

In daily use by the practice: cases, deadlines and fee records live in one system, and managers can see caseload without asking for it.