Centralised tickets
Work requests are created and managed in one place, with clear descriptions and ongoing discussion attached to each ticket.
Internal software · Workflow automation · Operations
From scattered contractor conversations to a complete management platform in under a week.
When a small internal team works with multiple external specialists, even simple requests can become difficult to track. I built Saturday to make contractor work easier to request, discuss, approve and account for — without adding unnecessary project-management complexity.
Live interface01 / The challenge
Work with external Salesforce, UX and development specialists was often coordinated through a mixture of email and WhatsApp. Requests, estimates, approvals and changes could end up scattered across different conversations. Some contractors also found more traditional tools such as Jira cumbersome for this kind of work.
I wanted a lighter system that matched how the team actually operated.
02 / My involvement
I independently designed, built and deployed Saturday in under a week. The speed of delivery came from keeping the scope focused on the specific operational problem rather than trying to recreate a full enterprise project-management suite.
03 / What Saturday does
Work requests are created and managed in one place, with clear descriptions and ongoing discussion attached to each ticket.
Contractors can provide estimates and work can be approved through a more structured process before time is committed.
Tracked hours, associated costs and invoice information help the team understand what has been delivered and what it costs.
Either side can request additional hours when a task requires more time, keeping changes visible rather than burying them in chat threads.
Email updates keep participants informed when relevant ticket activity changes.
A consolidated view of contractor hours makes it easier to review work across specialists and understand the month's activity.
04 / The outcome
Saturday is live and provides a single place for managing contractor work. It has made coordination clearer and gives the team complete visibility of tracked monthly contractor hours. I would not claim a specific time or cost saving without measurement.
05 / What I learned
A useful internal product does not need a long development cycle or an enormous feature list. Sometimes the best solution is a focused tool built around a handful of repeated frustrations. Saturday is a good example of using modern development methods to solve an operational problem quickly.
Project imagery
Approved project imagery. Confidential details are anonymised or omitted where required.



