Centralized budgeting and project management

An internal web app that keeps, in a single repository, the master data a construction and engineering company uses to budget its projects: line items, activities and resources, with sale and cost prices.

It is used by the client company's technical and budgeting teams.

Budget data was scattered across each project's files, in industry-standard formats. The platform imports them into a central catalog that every project reuses, and controls who can change it through a change request and approval flow.

The main challenge: fine-grained permissions per feature and per project, and the approval flow over shared data.

• Full edit-permission module: requests on line items, activities and resources; pending and rejected inboxes; approve, reject, revoke and restore permissions; request history.
• Permission-based access control in the UI, with protected routes and actions.
• Data tables with sorting, filters and pagination wired to the API.
• Forms with validation and confirmation dialogs for unsaved changes.
• Refactored data hooks to group them by entity, and improved the HTTP client for file uploads.

• Proposed and applied the reorganization of data hooks by entity, to make the project easier to maintain.

• Keeping the frontend cache in sync after approving or rejecting requests, by invalidating the right queries.
• Reflecting each user's permissions accurately in the UI.

Decoupled SPA with typed file-based routing, an API layer organized by entity, TanStack Query data hooks and a component library documented in Storybook. JWT login.

The project had Vitest and Storybook set up for component tests; my test contributions were occasional.

Modern React with the TanStack ecosystem (server state, caching, typed routing), permission-driven UI design and AI-assisted development (AI-DLC).