Personal project · In progressBilling-operations workspace

Ledgerleaf Billing.

Less searching. More clarity.

A personal billing-operations project in progress, focused on provider enquiries and planned team work queues. Every record is illustrative; no patient or financial account data is used.

Ledgerleaf / Project preview
Ledgerleaf Billing current interface preview. Personal project in progress with illustrative content.
Current interface / 01Personal project · In progress
Project type
Independent personal project
Current work
Interface & project planning
Previews
Two original interface screens
Next milestone
Functional build
01 / THE PROJECT BRIEF

A useful idea.
A considered direction.

The problem to solve

Administrative work can be difficult to coordinate when status and ownership are scattered. This project explores a task-based overview without reproducing real claims, patient identifiers or revenue records.

Who it is for

A fictional service-operations team. These previews do not represent operational billing software, a payment service or a compliance-certified product.

Real development experience. Independent projects.

I have built client websites and web applications as part of an agency team. Those deliveries are separate from the independently branded projects shown here; client code, screenshots and private data are not reused.

02 / INTERFACE PREVIEWS

A closer look at the project.

Explore the current interface direction and sample content. Open either preview for a closer look.

Ledgerleaf Billing / Personal project · In progress
Operations overview: work-in-progress interface preview with illustrative content
Operations overview

Project preview · 1 of 2

03 / PLANNED WORKFLOWS

Where the project
is headed.

The intended user journeys that will guide the functional implementation.

01

Review the queue

Illustrative work items are grouped by state and ownership, with no actual claim references or patient records.

02

Assign a next action

The proposed interaction would assign administrative follow-up to an authorised team member and record the change.

03

Close the loop

A planned activity trail would show status transitions and outstanding questions without exposing unnecessary account data.

04 / DESIGN DECISIONS

More than a
different colour palette.

Forest green, off-white and restrained tabular typography establish a quiet operational interface. Queue cards and clear owners take precedence over decorative revenue charts.

Operational, not clinical

The visual deliberately uses generic task identifiers and avoids patient names, diagnoses, amounts and insurance details.

Accountable status changes

Ownership and timestamps will need implementation as part of the planned status-change workflow.

No compliance claims

A real healthcare billing product would require specialist legal, security and workflow review; this project does not claim certification.

05 / PROJECT ROADMAP

Progress so far.
The next milestones.

Created so far

Original branding, two interface previews, a project brief and an implementation roadmap.

Planned technology stack

Implementation details will be added as the build progresses.

Next.js (planned)TypeScript (planned)PostgreSQL (planned)Audit logging (planned)
  1. 01
    NEXT MILESTONE

    Will define an appropriate minimal data scope and authorised roles.

  2. 02
    NEXT MILESTONE

    Will implement task states and validated transition rules.

  3. 03
    NEXT MILESTONE

    Will add access control, audit events and retention rules.

  4. 04
    NEXT MILESTONE

    Will complete domain-specific security and legal reviews before using real data.

A CLEAR PICTURE

About this project.

Working brand names and sample content are created for these personal projects, not used as client testimonials or results.

What is the current project status?

This is a personal project in progress. The original branding, interface previews and project scope are in place. Functional implementation and integrations are the next milestones; the preview screens use illustrative data.

How does this relate to previous client work?

I have built client websites and web applications through an agency. That experience informs my work, but this is a separate personal project with its own brand and implementation plan. It is not a renamed client delivery or a completed copy of an employer project.

What do the previews demonstrate?

They show the current interface direction, content structure and planned user journeys. The backend, authentication and third-party integrations described in the roadmap remain planned, not completed engineering work.

How will progress be shown here?

As the personal build progresses, this page will be updated with verified features, implementation details and new screenshots. The project status will distinguish work in progress from a completed implementation.

YOUR IDEA, ITS OWN DIRECTION

Have a project in mind?

Let's discuss an original build around your requirements—not reuse an employer's work.

All previews stay inside this portfolio.
Discuss your project