Ever Teams

A focused team workspace on top of Ever Gauzy, with tasks, time tracking, video calls and a shared whiteboard in one place.

Visit the site

Next.js, React, TypeScript, Tailwind CSS, Jitsi Meet, Excalidraw

Ever Gauzy is a large business platform covering payroll, hiring, sales, projects and more. Useful if you run the company. Overwhelming if you are on a team and just want to see today's tasks and start the clock.

Ever Teams is the smaller workspace sitting on top of it. Same data underneath, but only the parts a team touches daily.

I worked on this at Ever Co, on the front end: connecting it to the platform behind it, and building the collaboration features.

The Ever Teams workspace

Meetings and whiteboards where the work already is

Most teams already have a video tool and a drawing tool. The friction is not that they are missing, it is that they live somewhere else. You leave the task, open another tab, find the right room, and lose the thread of what you were discussing.

I embedded video calling directly into the workspace, so a call starts from the task or project you are looking at and arrives with that context attached. Nobody has to explain which ticket the meeting is about.

The shared whiteboard was the harder one. Drawing together in real time means several people editing the same canvas at once, and it has to survive somebody's connection dropping in the middle. Reconnecting cleanly, without losing what was drawn or leaving two people looking at different boards, is most of the work in a feature that looks simple from outside.

Both had the same requirement: they must not feel bolted on. An embed that opens in a different visual language, or forgets where you came from, gets used once.

Talking to a platform built for something wider

The data comes from Ever Gauzy's API, which was designed for the whole business platform rather than for this workspace. So the front end had to pull through organisations, teams, projects, tasks and time entries, keep authenticated sessions honest, and stay in step with backend state, while showing only the slice a team needs.

That tension ran through the whole project. Show too little and the workspace cannot answer real questions. Show too much and you have rebuilt the thing people found overwhelming.

I also worked on the task views, the time-tracking widgets, and the dashboard, which is where loading states and layout behaviour matter most, because those screens are open all day and on every size of screen.

Stack

Next.js, React, TypeScript and Tailwind CSS on the front. Ever Gauzy's NestJS API behind it. Jitsi Meet for calls, Excalidraw for the whiteboard.