Overview
Context
In project work the plan, the progress marks, what is expected from the client and the reports usually live in different files and chats. The longer a project runs, the harder it is to tell what is done, what the client still owes and where last month’s results are.
Goal
Bring it all into one working document. The project owner builds the plan and attaches the results, the team marks what is done, and the client can open the current picture by link at any time — with no sign-up and no way to change anything.
Architecture
Hover a node or pick a module in the table below to see what it does.
Stage Checklist
Modules
Stack
- Frontend
- React, TypeScript, Vite, Tailwind CSS
- Backend
- Node.js, Express, PostgreSQL, Drizzle ORM
- Access and files
- Clerk, object storage
- API contract
- OpenAPI, Zod
Results
- Plan and report in one document
- Tasks, progress, waiting items and results are no longer scattered across files and chats.
- Clients see progress for themselves
- The current picture opens by link — no sign-up and no way to change anything.
- It is clear who is waiting for whom
- Waiting blocks show what is holding the project up and on whose side.
- A report in one link
- A monthly summary or an interactive report goes to the client separately from the working document.
- No edits are lost
- Autosave and version checks protect the document when several people work on it.
- From idea to launch, solo
- The product, interface, server, database and access control were all built by one developer.