Internal tool for a team
Instead of spreadsheets and chat threads: the tasks, the statuses and the next step in one place.
- Buildfrom $2,850
- Timeline4–7 weeks
- Supportfrom $570/mo
Who this suits: Teams whose work lives in a few spreadsheets and a chat thread, where the next step is held in somebody’s head.
What is in the first version
- tasks and owners
- your own statuses
- roles and rights
- Telegram notifications
The figures above are the package this sits on: CRM or client portal. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
A task arrives with an owner
It records who does it, by when and what counts as done; a task with no owner does not save.
- 02
The doer moves the status
One screen with your own tasks, a move between stages in one tap, and the comment beside the task.
- 03
Closing sets the next step
A task closes with an answer to what happens next: another task, a return date, or an explicit «nothing further».
What decides whether this works or annoys people
The stages are named first
While «in progress» and «in review» mean different things to different people, the board shows a disagreement about words rather than work.
Not a second place to type
If a chat enquiry becomes a hand-typed task, soon it is not typed at all, so the sources are wired in first.
Notifications turn into noise fast
If everything is sent, nothing is read, so a person hears only about what they own or are mentioned in.
What to measure once it is live
- tasks entered without a reminder
- tasks with no owner
- closed tasks with a next step
- spreadsheets still in use
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- InterfaceTypeScriptReactNext.js
- Backend and dataNode.jsPostgreSQLPrismaRedisS3
- Notifications and operationsTelegram Bot APIn8nDockerGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- hosting and servers
- the domain, if the tool gets one
- SMS and telephony beyond a messenger
- AI model calls, if it summarises
Asked before the first call
- Why not Notion or Trello?
- Often you should, and we say so. A ready-made board is cheaper while your process fits it; your own tool earns its place when you need calculations, rights by role and links to your systems.
- Who will actually use it if the team lives in a chat?
- That is why the interface is often Telegram itself: a task is created and closed without opening anything new. A tool that demands a new habit does not survive a busy week.
- What happens to the current spreadsheets?
- We move what is alive and leave the archive where it is. Spreadsheets carry duplicates and abandoned rows, so cleaning them is planned work rather than a surprise on launch day.