SaaS / Internal tool · 2026Studio product · internal

AFES Project Management

Roadmaps in a spreadsheet, tasks in chat, blockers found at stand-up. We built the workspace our own team needed instead.

Team: Rahimi (lead) · Haziq (back-end) · Amir (QA)
When: September to October 2026
Services: Web development · AI solutions
Stack: Next.jsTypeScriptSupabasePostgreSQLVitestVercel
Access: Internal, approved accounts only

An internal tool behind a login. The screens on this page and in the film are rebuilt from the product’s own design tokens, navigation and copy; the data shown is illustrative.

01Film

Under a minute through the workspace: the overview, a blocker reaching the manager, and the team’s workload.

02Problem

Three tools, and no single view of the work.

The roadmap lived in a spreadsheet nobody trusted, tasks were assigned in chat, and a blocker surfaced days late at stand-up. Nobody could say who had room for more work, and every client update meant rebuilding the same report by hand.

03Constraints

01Managers need the whole portfolio; staff need only their own tasks.
02Client data stays private: no public sign-up, private file storage, row-level security.
03Outside agents must be able to read and act on work through an API, with the same permissions as a person.

04What we built

Two role-based workspaces. Managers get an overview of milestones, delivery pace and active blockers, a six-stage delivery template (Discussion, Design, Implementation Plan, Coding, Debug & QA, Publish), a task board, a calendar, team workload and CSV reports. Staff get a focused queue, a blocker flag that requires a note, and deliverables attached straight to the task. A private AI agent reads the task you send it, and a documented /api/v1 REST API lets outside agents work alongside the team.