StaqOn Projects lets teams create shared workspaces with tasks, members, and status tracking — Active, On Hold, or Completed — directly inside a real chat conversation. Any internal member can create tasks; only the creator can rename the project or reopen it. External partners can be added too, keeping coordination in one place instead of scattered across email.
Product
Introducing Projects: Shared Work in StaqOn
Introducing Projects: Shared Work, Without Losing Track of Chat
If your team has ever tried to run a real project inside a chat app, you know the problem. The conversation is great for quick updates, but the moment you need to track who's doing what and what's actually done, things fall apart. Tasks get buried under messages. Nobody's sure if something is still active or quietly abandoned. And the moment an external partner needs to be looped in, you're back to email.
We built Projects to fix that — without asking you to leave the conversation to do it.
One space for the conversation and the work
A StaqOn Project is a real conversation — the same chat thread you already use for Teams, Circles, and DMs — with a task list, a member roster, and a clear status attached to it. You don't switch tools to see what's been assigned or what's blocking. It's right there, next to the messages.
Creating one is simple: give it a name, add a first task, and choose who's on it — your own internal team, and if the work involves outside partners, they can be added too, either from your existing partner list or by sending a real invite to someone new.
Three states, and each one means something
We didn't want a project to just be "open" or "closed." Real work has more shapes than that, so a StaqOn Project can be:
- Active — the normal state. Tasks can be created, members can be added or removed, everyone can chat.
- On Hold — a genuine pause. Every task automatically pauses with it, no new tasks can be added, and only the creator can still send a message, so the rest of the team isn't left wondering if the project is quietly still moving.
- Completed — a real, final state. The remaining tasks close automatically, and the conversation becomes read-only for everyone, including the creator. If a project truly needs to reopen later, the creator can do that — but a task that's already closed stays closed. That's on purpose. It keeps your history honest.
Built for how work actually gets assigned
Any internal team member can create a task and add people to a project. But changing a task's status — marking it done, putting it on hold — is limited to whoever created that task, or the project's creator. It's a small rule, but it means status updates in your project actually reflect the person who did the work, not whoever happened to click first.
Renaming, without losing the thread
Projects change scope. A name that made sense in week one doesn't always make sense in week four. So the creator can rename an active project at any time — and everyone on it, internal and external, gets notified the moment it happens. No confusion about which "Q3 Launch" chat you're actually in.
Why this matters
We didn't build Projects to replace a dedicated project management tool. We built it because most of the actual coordination — who's doing what, is this still active, can we bring the client in on this — was already happening in chat anyway. Projects just gives that conversation the structure it was missing.
It's live now for every StaqOn workspace. If you manage work with people outside your own team — vendors, clients, contractors — give it a try on your next real project, and let us know what you think.
