Turning complex tax-exemption workflows into one transparent digital journey.
This platform digitizes the end-to-end process of submitting, reviewing, validating, approving, and tracking tax-exemption requests for a national government fiscal authority.
One platform. One workflow. Complete visibility.
The platform digitizes a complex government process where applications move through multiple review, validation, approval, and documentation stages — connecting applicants and government stakeholders through a single digital workflow.
Applicant Submission
Requests, references and supporting documents enter through one structured form.
Multi-stage Review
Secretariat, coordinator and financial reviews follow an explicit, ordered sequence.
Financial Validation
Calculations are checked and validated inside the request, not in a separate spreadsheet.
Digital Record
Every action, document and decision is stored as a traceable history.
Delivered end to end — from the first Figma frame to production infrastructure.
The screens on this page were shipped as a real, running system — design, frontend, backend, and infrastructure owned by one team.
React
Tailwind CSS
Laravel 11Laravel Octane
Filament
Livewire
MySQL
AWS S3
AWS EC2
Apache
Twilio / SendGrid
GitHub
Figma
JiraLaravel Octane for sustained throughput
The application server keeps the framework booted in memory between requests instead of a fresh bootstrap each time — a deliberate performance choice for a system handling continuous review traffic.
Filament over hand-rolled admin CRUD
Five internal roles needed dependable, permission-scoped back-office screens fast. Filament's opinionated admin layer let us ship that surface without reinventing table, form, and panel primitives from scratch.
S3-backed document versioning
Every uploaded file — request letters, invoices, contracts, calculation notes — is stored and versioned in object storage, decoupled from the database, so document history survives independent of application changes.
The process wasn't just complex. It was fragmented.
Tax-exemption requests involve multiple stakeholders, supporting documents, financial checks, annotations, approvals, and handoffs.
Role-based interfaces keep each participant focused on the decisions they own.
Five roles, one shared record. Each sees the same request through the lens of its own responsibility.
Applicant
Submits exemption requests. Uploads supporting documentation. Tracks request progress.
Request form & document upload
Tax Cell Secretariat
Reviews submitted applications. Checks completeness and compliance. Requests corrections or forwards applications.
Completeness review & forwarding
Coordinator
Reviews applications. Adds observations. Approves or moves requests forward.
Observations & approval
Financial Authority
Performs financial validation. Reviews calculations. Provides official approval.
Calculation review & validation
Administrative / Senior Authorities
Participate in later-stage validation, document generation, transmission, and final delivery.
Validation, generation & delivery
Before and after, side by side.
From submission to approval — every stage has a place.
Create Account
Applicant registers and verifies identity.
Submit Request
Project reference, amount, dates and description.
Upload Documents
Request letter, invoices, contracts — PDF or DOC, max 10 MB.
Secretariat Review
Completeness and compliance check; corrections requested or file forwarded.
Coordinator Review
Observations added; request approved or moved forward.
Financial Review
Calculations reviewed and validated by the Financial Authority.
Draft Report Preparation
Summary report prepared from the validated file.
Transmission Letter Drafting
Official transmission letter drafted for signature.
Senior Authority Validation
Senior authority validates the file.
Document Generation
Official exemption documents generated and signed.
Final Delivery
Signed documents returned and delivered to the applicant.
Seven principles shaped every screen.
Every handoff becomes an explicit state. Every document has a place. Every request has a traceable history.
A shallow structure — everything is two clicks from the request.
One system, consistent across every role.
Semantic tokens, a fixed type scale, and a strict spacing rhythm let five different roles share one visual language.
3 · 8 · 12 · 16 · 20 · 24
4 · 50
300ms baseline · 700–1200ms transitions
Turn administrative data into actionable insight.
The admin dashboard answers three questions at a glance: how many requests, where they are, and where they are stuck.
At-a-glance request triage.
Every request is one row: who, what, how much, since when, and where it stands. Status is always readable as text — never color alone.
| Applicant | Request ID | Project | Amount | Date | Status |
|---|---|---|---|---|---|
| Solvane Textiles | REQ-2025-0141 | Irrigation equipment import | $248,500 | 12 May 2025 | New |
| Meridian Solar Co. | REQ-2025-0138 | Rural electrification phase II | $1,120,000 | 09 May 2025 | Processing |
| Aldergate Foundation | REQ-2025-0132 | Community health centres | $412,300 | 02 May 2025 | Pending |
| Portway Logistics | REQ-2025-0127 | Port handling equipment | $690,000 | 28 Apr 2025 | Approved |
| Brackenfield Construction | REQ-2025-0119 | Road rehabilitation N1 | $2,050,000 | 21 Apr 2025 | Rejected |
| Northfall Water Systems | REQ-2025-0104 | Water treatment plant | $335,000 | 03 Apr 2025 | Expired |
Information, documents and history — side by side.
Rural electrification phase II
Every handoff becomes an explicit state.
One request, four actors. Each action is recorded with who, what, when, and a comment for the next person.
Applicant
Request Sent
Request letter and invoice files attached.
Tax Cell Secretariat
File forwarded to coordinator
Completeness and compliance checked.
Financial Authority
Prepared a summary calculation note
Calculation_Notes.doc added to the file.
Senior Authority
Return signed documents to Secretariat
Signed documents ready for final delivery.
Every document has a place.
Documents are attached to the request, not to an email thread.
Financial validation, inside the workflow.
Complex financial validation becomes easier to scan and review. The calculation lives next to the documents that justify it.
| Entity | Amount | Tax | With Tax |
|---|---|---|---|
| Equipment import | $250,000 | $40,000 | $290,000 |
| Installation services | $80,000 | $12,800 | $92,800 |
| Transport & insurance | $30,000 | $4,800 | $34,800 |
Communication became part of the workflow.
A supporting module, not a separate product: inbound messages get a status, an owner and a resolution — the same vocabulary as a request.
I would like to inquire about the upcoming community development projects planned for the northeastern region.
Never wonder where the request is.
Status reflects the last recorded action in the workflow history.
Motion communicates progress, flow and connection — never decoration.
Micro-interactions
Hover elevation, chip changes and button states use short, decisive transitions.
Large transitions
Section reveals, frame entrances and workflow line drawing take their time.
cubic-bezier(0.22, 1, 0.36, 1)
A single easing curve keeps every movement feeling like the same system.
Respected everywhere
With prefers-reduced-motion, transforms and chart drawing are replaced by simple opacity.
Designed for clarity across the entire workflow.
Centralized Request Management
Created a single digital workflow connecting applicants and administrative stakeholders.
Transparent Multi-stage Processing
Made request progress easier to understand through visible stages and history.
Structured Document Handling
Attached every document to the request and the decision it supports.
Role-specific Decision Making
Gave each role an interface focused on the actions it owns.
Financial Validation Visibility
Structured document and financial information around the review process.
Digital Request History
Recorded every action with its actor, time and comment as a traceable record.
This platform turns a multi-stage administrative process into a visible digital workflow. The hardest design decision was not what to add, but what to keep visible at every step: the stage, the owner, and the documents that justify the next decision.
Reducing cognitive load without hiding complexity meant designing around roles rather than departments — and treating every handoff as a first-class state.
Ready to simplify complex workflows?
Multi-party approvals, compliance constraints, legacy paper processes — we've delivered systems like this end to end.
Start a conversation →