Every other part of NearSync is organised around a subject. Sales HQ is about deals. Finance HQ is about money. People HQ is about employees. That is the right way to organise a business, and the wrong way to organise a morning.
Your morning is not about deals. It is about the four things that happened overnight, across four different subjects, that need something from you. Nobody has a job that fits inside one HQ, and the cost of that mismatch is paid every day in the twenty minutes spent checking six screens to find out whether anything is on fire.
Workspace is the surface organised around you instead.
The eight tabs
| Tab | What it is for |
|---|---|
| Cockpit | Everything that wants your attention, ranked, from every part of the platform |
| Conversations | The assistant, with your live data, your history, and the web |
| Calendar | Every calendar you have, on one grid |
| Plan | Your tasks, and the day you are going to spend on them |
| Pins | Anything worth keeping: live records, links, your own notes |
| Meeting Intelligence | What was said in your meetings, and what came of it |
| Coach | How you conduct meetings, measured over time |
| Reports & Analytics | Your own numbers about all of the above |
They are deliberately in that order. The first four are a working day. The next three are how you get better at it. The last is how you check whether you did.
The idea underneath
Most tools solve "too much to keep track of" by adding notifications. A notification tells you something happened. It does not tell you whether it matters, it does not survive being dismissed, and it is gone the moment you clear the badge. Three days later nobody can reconstruct what came in, what was handled, and what quietly fell through.
Workspace does something different. Anything that wants you becomes a durable item with a state.
A meeting summary that needs reading. An expense waiting on your approval. A mention in a channel you were not watching. An action item somebody assigned you in a call you half remember. All of them become the same kind of object, all of them sit in one list, and all of them stay there until you do something about them.
That has a cost and a benefit, and they are the same thing: you cannot make something disappear by ignoring it. The list is honest about what you have not dealt with, which is uncomfortable for about a week and then becomes the reason you trust it.
Why it can do this at all
This works because NearSync runs on one database rather than several.
An expense approval lives in Finance. A meeting summary lives in Meeting Intelligence. A mention lives in Sync Chat. In most stacks those are three separate products, and gathering them into one list means three integrations, three sync delays, and three sets of data that disagree with each other by the afternoon.
Here they are three tables in the same database. The Cockpit is a query, not an integration.
That is not an architectural footnote, it is why the surface behaves the way it does. An item can be acted on where it sits rather than deep-linking you into the tool it came from. Approve the expense from the Cockpit and the expense record changes, because it is the expense record. There is nothing to sync back and nothing to be stale.
The same property shows up all over the rest of Workspace. A pinned deal shows today's stage rather than the stage it had when you pinned it. A task created from a meeting keeps a permanent link back to the sentence that created it. Your calendar shows approved leave without anybody remembering to block it out.
Who it is for
Everybody, which is unusual for a surface this dense.
An engineer uses the Cockpit for mentions and sprint items and mostly ignores approvals. A finance manager lives in approvals. A salesperson lives in Meeting Intelligence and Pins. The list is filtered by what actually routes to you, so the same surface is a different surface for each of them.
The parts that are genuinely universal are the Cockpit and the Calendar. Everything else earns its place depending on the job.
What is not in here
Doing the work. Workspace tells you a deal needs attention; the deal is worked in Sales HQ. It tells you an invoice is overdue; the chasing happens in Finance HQ. This is a surface for deciding what to do, not for doing all of it.
Anything team-wide by default. Almost everything here is scoped to you. Where a team view exists it is explicitly labelled, and it is for a manager understanding load, not for watching people.
Configuration. Meeting types are configured in Operations HQ. Notification policy sits in system settings. Workspace consumes those decisions rather than owning them.
The first week
Day one, do nothing but the Cockpit. Work it top to bottom once, and notice how much of it you did not know about. That number is the argument for the whole surface.
Day two, connect your calendar. Google or Microsoft, whichever you use. The calendar is worth very little until it has everything on it and worth a great deal afterwards.
Day three, ask the assistant three real questions. Not test questions. Things you would otherwise have gone looking for. The point is to find out where the faster path is.
By the end of the week, make one Pins collection for whatever you are actually working on. That is the habit that compounds.
Everything else can wait. Saved views, coaching, auto-scheduling and reports are all worth having and none of them are worth learning before the daily rhythm is in place.
What to read next
If you read one more piece, read The Cockpit. It is where you will spend most of your time and it has the most behaviour worth understanding.
If you are setting the platform up rather than working in it, read Meeting Types and Outcomes, because it is the one piece of configuration that changes what everybody else gets out of the product.
Did this answer your question?
No, ask a person