One workspace for software teams and the people around them

Where software work actually gets stuck

Most software companies already have an issue tracker for engineers. The friction is elsewhere: the product decision made in chat that never reaches the ticket, the spec that lives in a doc nobody links, the client asking the account manager for a status the engineers already posted somewhere else, and the time log for a fixed-price build kept in a spreadsheet. Engineers switch between five tools and the non-engineers cannot follow any of them.

This is especially true for software services companies that build for clients, where delivery, communication and hours all matter as much as the code. The information silos article covers why splitting chat, tickets and docs hurts.

Spaces for products, teams and client builds

In Emitii each product, squad or client build gets a space. The Project type is the usual pick because it turns on the Board and the Timesheet. Switch on Docs & Files for specs.

The Board for the sprint

• Columns are free text: "Backlog", "Ready", "In progress", "Code review", "QA", "Done". A card limit on a column caps work in progress, for example three cards in Code review.
• Cards carry a Markdown description, several assignees, a due date, priority (Urgent, High, Medium, Low), labels such as "bug" or "frontend", and a checklist. A checklist item can be turned into its own card when it grows.
• Mark as blocked with a reason flags a card that is waiting on something, and the reason says what it is waiting for.
• Filters by people, labels, priority or blocked status, plus board search across descriptions, checklists and comments.
• Rules automate the board: when a card enters "Done", complete it; when a blocked card enters QA, set its priority to High. Rules have a preview, a run log and undo.

The software development template suggests columns and labels you can set up by hand, and the Emitii vs Jira comparison shows how the board compares with an issue tracker.

Pulse for the standup, Posts for release notes

Pulse is the space's group chat, with threads, code blocks, pins and @mentions. A daily async standup thread works well here. Posts suit longer updates such as release notes or a decision record, and can notify everyone in the space.

Docs & Files for specs

Specs, architecture notes and runbooks live as Markdown docs, with comments for review and "Download as PDF" when a client needs a copy. Uploaded files keep versions.

For services companies: clients and hours

If you build software for clients, invite the client's product owner as a guest to the build's space. They see only that space and the cards and docs you share, comment on them and talk with the team in Guest Pulse. Developers log time per card in quarter hours as billable or non-billable, and the weekly approval gives the delivery lead a clean CSV at month end.

The Emitii CLI and MCP server

Emitii ships a CLI, the @emitii/cli npm package, that runs an MCP server so coding agents can work with Emitii. Setup is automatic for Claude Code, Codex, Cursor and OpenCode. A developer can ask their agent for their tasks, update a card, read or write a doc, comment, or log time and submit the week, without leaving the editor. Tokens are read or read-and-write, expire after 90 days and can be revoked. The CLI is off by default and is enabled per organisation by the Emitii team.

Emit inside the space

With AI switched on, Emit answers questions like "What is blocked or overdue?" or "Summarise what is in progress" from the board. It can write a sprint recap into Docs & Files or draft release notes as a Post, and it asks for approval before every change. It knows only that space. See the AI assistant feature page for details.

A software team live demo

A live software team workspace is available without signing in, with a sprint board, tasks and chat already set up. Try the industry demos; your changes stay in your browser.