- Professional servicesIndustry
- Software ProductsCategory
- Phased rolloutTime to impact
The challenge
- Clients on hour-pack engagements had little visibility into how their hours were being used
- time tracking and approvals were manual and disconnected from the tools delivery teams actually work in.
Clients see live hours consumed; teams log time; admins approve, synced with Jira.
A client-facing portal that gives customers real-time visibility into the hours they have purchased and consumed, with a full staff time-logging and approval workflow behind it.
What we built
- 01Clients view live consumption of purchased hours, their projects and shared documents.
- 02Staff log time against tasks; admins review and approve entries.
- 03Approved hours draw down hour packs automatically.
- 04Two-way Jira and Confluence sync keeps delivery and billing aligned.
How it works
What it can do
Live hours dashboard
Real-time view of purchased vs. consumed hours.
Time-entry review
Staff log time; admins review and approve.
Hour-pack drawdown
Approved hours decrement packs automatically.
Jira & Confluence sync
Two-way OAuth sync with delivery tooling.
Who stays in the loop
The call the system deliberately does not take, and what the person is given to take it with.
A client-facing portal that gives customers real-time visibility into the hours they have purchased and consumed
The account admin
Decideswhether a logged entry is approved and draws down the client’s hours
Seeseach entry with its task, its hours, and the pack balance approving it would leave
The payoff
What is different once it is running. No invented numbers: these are the changes the work was built to make.
Clients stop emailing to ask how many hours are left. They log in and see it, live.
Clients get real-time visibility into hours and projects.
Time logging and approvals run in one place, synced to Jira.
Approved hours draw down packs automatically, no manual tallying.
Built with
The layers this runs on, from what comes in to what it plugs into.
- Runs on
- Supabase
- Cloudflare Workers
- What people use
- Next.js
- Connects to
- Resend
Common questions
The same answers as above, written out.
A client-facing portal that gives customers real-time visibility into the hours they have purchased and consumed, with a full staff time-logging and approval workflow behind it.
Clients on hour-pack engagements had little visibility into how their hours were being used, and time tracking and approvals were manual and disconnected from the tools delivery teams actually work in.
Staff log time against tasks; admins approve it. Approved hours draw down the client’s pack. Clients see live consumption and synced Jira work.
The account admin decides whether a logged entry is approved and draws down the client’s hours. They see each entry with its task, its hours, and the pack balance approving it would leave.
Runs on: Supabase, Cloudflare Workers. What people use: Next.js. Connects to: Resend.
Clients get real-time visibility into hours and projects. Time logging and approvals run in one place, synced to Jira. Approved hours draw down packs automatically, no manual tallying.
Where this fits
The practice it belongs to, how an engagement like it runs, and what we have written about the subject.
Business & OperationsOptimising your operations with AI: start with the process, not the model
A practical playbook for optimising operations with AI: find the one slow step, automate it, keep a person in the loop, and measure the before and after.
Miguel Vicente JrJun 202612 min read
Business & OperationsHow to spot an AI use case worth doing
The six prerequisites that decide whether an AI use case is worth building, with a scoring rubric, two worked examples, and the red flags that say walk away.
Miguel Vicente JrJun 202611 min read
Business & OperationsWhy your best AI work belongs in a marketplace
Built a few AI tools and now fighting duplication and drift? The case for an internal AI marketplace, what goes in it, how to layer it, and how to curate it.
Miguel Vicente JrJun 202611 min read
Other projects in this line.
Bring us the problem nobody has cracked yet.
We are a small team of senior specialists. We pick the right model and the right layer, and we build the least machinery that does the job. You get a call with an engineer, not a sales deck.