Two people, one row
Concurrent edits have to merge without anyone losing a change or seeing a stale value — and without a spinner between every keystroke.
Enterprise · Our own product
Real time is an architecture, not a feature
Every project tool claims to be collaborative. The difference shows when two people edit the same row at once, when an automation fires while someone is dragging a card, and when a workspace has to stay invisible to every other company on the platform.
- Live edits and presence
- Automation engine
- Isolated per company
- Client
- Valeur X (in-house product)
- Sector
- SaaS · Work management
- Delivered
- 2026 — in production
- Services
- Custom software, Web, Cloud
Project at a glance
The situation
What makes this class of product hard
Boards and tasks are a weekend project. Keeping them correct for a whole company, live, is not.
01 02 Automations that fire safely
A rule that moves an item, notifies a channel and stops a timer must run once, in order, even when the trigger arrives twice.
03 Four views of one truth
Board, My Work, overview and calendar are different questions asked of the same records. The moment any of them needs its own copy, the product starts lying.
04 Visibility is a permission problem
Public, private and personal boards, plus per-company isolation, mean every query has to answer "who is asking" before it answers anything else.
What we built
How the platform is built
The decisions that make the rest of the product possible.
Live sync with presence
Changes broadcast to every open client as they happen, with presence showing who is viewing a board — so duplicated work is visible before it happens.
A rules engine, not scripts
Triggers and actions are data, not code: pick when and then. Rules are versioned, logged with a run count, and safe to re-run.
One record, many views
Board, My Work, overview and calendar are projections of the same task record, so nothing has to be kept in sync by hand.
Permissions at the query
Workspace, board and personal scopes are enforced where data is read, not hidden in the interface, with role-based access and an audit log.
Time and documents on the row
Timers, files, specs and forms attach to the task itself, which is what keeps reporting honest later.
AI that drafts the plan
Paste a brief and the subtasks, owners and dates are drafted for review — the blank-board problem, solved without taking the decision away.
What changed
A product that replaces a stack
Teams arrive with a tracker, a time sheet, a dashboard tool and a spreadsheet. They leave with one board, and the admin that used to fill an afternoon happens in the half second after a click.
- Edits appear on every screen as they are made
- Automations run the hand-offs nobody wanted to chase
- Hours are logged against the task, not a separate sheet
- Enterprise workspaces are isolated, audited and exportable
- 4
Views generated from one record
- 0
Scripting needed to automate a chore
- 1:1
Isolated workspace per company
Built with
Built for interfaces that stay responsive while the data underneath keeps changing.
- Frontend
- React
- TypeScript
- Optimistic updates
- Virtualised lists
- Real time
- WebSockets
- Presence
- Conflict handling
- Event streams
- Backend
- Node.js
- PostgreSQL
- Queues
- Rules engine
- Platform
- SSO
- Role-based access
- Audit log
- Data export
Need something your team will actually open every morning?
Adoption is an engineering problem before it is a training problem. Tell us what your team is avoiding today.