Selected work · 2025 – 2026
Prodily
Type
AI productivity platform
Duration
3 months
Year
2025 – 2026
Role
Chief Technology Officer
Outcome
A demonstrable platform inside one quarter
Tools
- React
- TypeScript
- Vite
- Tailwind CSS
- TanStack Query
- Zustand
- Socket.IO
- React Hook Form
- Zod
- Framer Motion
- GSAP
- Vercel
An AI productivity platform that bills itself as an operating system for human potential: intelligent agents that amplify a team's output, surface burnout early, and give leaders a read on culture before it becomes a problem. React across the platform.
Prodily positions itself as an operating system for human potential: intelligent agents that amplify what a team already does, catch burnout while it is still fixable, and give leaders an honest read on culture rather than a survey once a quarter.
The engineering interest here was restraint. A platform framed that broadly can absorb any amount of work, so the first release deliberately covered the agent surface end to end and left the deeper analytics alone until there was real usage to analyse. React across the platform, Vercel for hosting.
Inside Prodily
The product's argument, put on the front page
Prodily bills itself as an operating system for human potential, which is a large claim, and this screen is where it either means something or does not. Headcount and attendance are table stakes. The two figures that matter are attrition risk and burnout alerts, sitting at the top rather than buried in a report, because the entire pitch is catching a problem while it is still fixable. Framing the org view as live telemetry rather than as a quarterly survey is the product decision; everything else here follows from it.
Where the numbers upstairs actually come from
A lead lands on a daily mood check-in, a weekly streak, today's progress and upcoming meetings, with Assign Task and Schedule Meeting in the header. Every figure the admin view aggregates is entered here, by someone with thirty seconds and no interest in filling in a form. That constraint set the design: one tap for mood, one for a task, and the streak exists to make the second day easier than the first.
Three products from one data model
The same daily surface with the team management removed. No headcount, no risk indicators, nobody else's numbers. This is the view that decides whether the whole thing is trusted: an employee who suspects their mood check-in is feeding a dashboard their manager reads will stop being honest in it, so the member view shows exactly what is theirs. It is not the lead view with elements hidden in CSS, it is a separate set of permissioned queries, which is where most of the engineering went.