All work

Concept project: a sample build that shows how we approach this kind of product. The client, features and figures are illustrative.

Full stack · React + NestJS · Productivity · SaaS

teamsync

A real-time project workspace where tasks, boards, timelines and conversations live in one place.

Client
Concept: distributed product agency
Year
2026
Services
Product design, React front end, Node.js backend, Real-time systems, Cloud & DevOps
Live site
Concept build
TeamSync interface

Overview

The brief

A remote agency ran projects across chat, spreadsheets and a task tool nobody updated. Decisions were lost in threads, status meetings existed only to find out who was doing what, and clients could not see progress. TeamSync puts boards, timelines, comments and activity in one live workspace, so everyone sees the same state at the same moment.

Problems & fixes

What was in the way

Pick a problem to see what was wrong, what we built and what changed.

The problem

Tasks lived in one tool, discussion in chat and deadlines in a spreadsheet, so nothing was ever up to date.

What we built

Tasks carry their own comments, files, due dates and activity history, shown on Kanban boards, timelines and personal task lists.

What changed

One place to find the status of any piece of work.

1 / 4

Impact

What it changed

<150 msLive update latency
4Tools replaced
30%Fewer status meetings
100%Tenant-isolated queries
  • The team stops asking for status updates because the board is always current.
  • Clients see progress without a weekly report.
  • Chat, spreadsheets and the old task tool are retired.

How it works

Under the hood

Click any part of the system, or play the flow from start to finish.

Step 1 · React · dnd-kit

Web app

Boards, timeline, task detail and dashboards with optimistic updates.

01 —

Live presence

See who is online and what they are moving, as they move it.

02 —

Stable ordering

Drag-and-drop order is saved exactly, even with concurrent edits.

03 —

Secure by tenant

Authorisation is tested on every endpoint, not just the UI.

Timeline

  1. Weeks 1–2Task-first navigation, data model and design
  2. Weeks 3–5Boards, task detail, NestJS API and permissions
  3. Week 6WebSockets, presence and notification queues
  4. Week 7Concurrency tests, AWS deployment and monitoring

Tech stack

ReactTypeScriptdnd-kitNestJSPostgreSQLPrismaRedisWebSocketsDockerAWS ECS

got an idea?let's lift it.

Tell us what you're building. A senior engineer, not a salesperson, replies within one business day.

Start a project
Start a project