Making project work
visible and accountable.
Business problem Paper timesheets and informal project tracking left the practice without a reliable view of effort, budgets, approvals or project progress.
I personally built the working local application with Codex, from business requirements to code, UX/UI, debugging and functional tests. My co-developer handled production deployment.
View the live access page for a short product walkthrough; access to the client workspace is restricted to authorised users.
My hands-on contribution
- 01
Discover & specify
I ran two discovery calls, clarified requirements through client document reviews and agreed the scope. I mapped project roles, permissions, approval chains and the business rules connecting clients, projects, time and budgets.
- 02
Build working code with Codex
I personally built the working local application with Codex: generating and modifying code, designing UX/UI and navigation, debugging and functionally testing modules against business requirements.
- 03
Iterate, validate & train
I made iterative fixes locally and validated workflows on staging, then demonstrated the solution and trained users. Client feedback guided further refinements.
The workflow, in practice
Select a stage to see what happens.
Record time
Employees enter time against assigned projects.
Validate
Project responsibilities determine the approval and reopening chain.
Compare
Managers compare planned effort, budgets and actual progress.
Explain
A dated project report details completed work and supports a budget-extension request.
What changed
Live deploymentA project report, ready in one click.
The most concrete early feedback: the practice can produce a detailed, branded project snapshot to explain a budget-extension request to its own clients.
Early qualitative feedback points to more reliable tracking. The platform now provides a foundation for ongoing measurement.
In use for approximately four to six weeks at the time of this account.