Back to projects
Operational dashboard

Kulla Ledger

A complete Albanian project-ledger dashboard for shared building/community projects with payments, expenses, evidence, and reporting.

Outcome
A localized workflow app that makes financial status, resident participation, photo proof, volunteers, and printable reports visible in one dashboard.
TypeScriptDashboardWorkflow UXVercel
Kulla Ledger dashboard for shared building payments and project reporting.
Challenge
Small shared-building projects often track money, residents, photos, volunteer work, and reporting in disconnected chats and spreadsheets.
Approach
01

Build around one active project ledger instead of a generic admin template.

02

Expose plan, collected amount, balance, photos, volunteer hours, residents, payments, and expenses as first-class dashboard states.

03

Support practical reporting needs with A4-style output, browser photo capture, and resident-facing status language.

Project article

Why this project matters.

A short review of the product surface, workflow signal, and portfolio value.

Kulla Ledger is one of the strongest non-AI portfolio pieces because it solves a concrete local workflow. The interface is in Albanian and models a recognizable community/building project rather than a generic dashboard.

The app makes the core operating state visible: planned amount, collected money, remaining balance, participant count, payment status, expenses, photos, volunteer work, and report readiness. That is the kind of data model that helps a real coordinator explain what happened.

For the personal portfolio, Kulla Ledger demonstrates product judgment in local-language UX, dashboard information architecture, and the practical translation of messy community coordination into software.

Proof points

What the system makes visible.

These are the artifacts that make the project usable beyond the first demo.

Financial evidence dashboard
Resident/payment workflow
Printable reporting
Discuss a similar project
Contact
Bring the product pressure, system constraints, and expected business outcome.
Send the desired outcome, users, current bottleneck, stack, and timeline. I will respond with a practical senior engineering path for the build.