How a startup grows inside Emitii
- 1
Founding space
Create one Project space for the core team with Board, Tasks and Docs & Files.
- 2
Sprint board
Put this sprint's work on cards with priorities, labels and checklists.
- 3
Standup and decisions
Run standups in a Pulse thread and record big decisions as Posts.
- 4
Split by team
As the team grows, add spaces for go-to-market and operations.
- 5
Onboard hires
Invite people and grant access by group so new starters see the right spaces.
- 6
Bring in outsiders
Add contractors and advisors as guests to the spaces they need.
- 7
Monthly update
Write the investor or team update as a Post or doc from the board.
The startup tool trap
A startup's first month usually adds a chat app, a task board, a docs tool, a shared drive and a calendar, each free on day one. By month twelve there are ten tools, three places where decisions might be written, and every new hire spends a week learning where things live. The founders pay for it twice: in subscriptions and in the time spent asking "where did we decide that?". The why teams use too many tools article explains how that happens, and if your team lives in Notion today, Emitii vs Notion compares the two.
Startups also change shape fast. The team that was one group of six becomes product, sales and operations, then adds contractors and an agency. The workspace has to split along those lines without a migration.
Start with one space, then split
A small founding team can start with a single space, "Product, Sprint 12" for example, holding the board, the standup chat and the docs that explain why things were built. As the company grows, add spaces:
- Product (Project type): the Board for the build, Timesheet if you track effort, Docs & Files for specs.
- Go-to-market (Project or Internal type): launch tasks, the sales pipeline as board columns, pitch material in Docs & Files.
- Operations (Internal type): hiring checklists, finance to-dos, office admin, company policies.
- Investors or Advisors: a small space where outside advisors join as guests and read monthly Posts.
Space types only decide which tabs start switched on. Every space can have its modules changed later, and Pulse is always on. The startup template sketches this layout.
How a sprint runs
Cards on the Board carry priority, labels, assignees and a checklist. Free-text columns match however your team works this quarter, and you can rename them next quarter. The Board's filters (people, labels, priority, blocked, hide done) give a founder a quick view of what is stuck. For developer teams, the software companies page covers the board and the CLI for coding agents in more depth.
Standups can be a thread in Pulse. Decisions worth keeping become a Post ("Why we chose usage-based pricing") so they are pinned, commented on and searchable later. Specs and investor updates are Markdown docs in Docs & Files. If AI is enabled, Emit can write the sprint recap from the board and save it as a doc, after you approve it.
Onboarding people fast
When a new hire joins, an admin invites them and adds them to the spaces they need. Groups and Departments let you grant a whole team access to a space in one step, and access always adds up: a person gets the sum of their grants, never less. Home shows a new starter what needs them, what is overdue and what is coming up, so they are useful in their first week. The employee onboarding template is a checklist you can copy into Tasks.
Keeping decisions findable
Startups make many decisions quickly and forget why. A simple rule helps: a discussion can start in Pulse, but the outcome goes in a Post or a doc. Posts can be pinned and filtered, docs are searchable by name, and the Ctrl+K palette jumps to any space, person or conversation. When someone asks "why did we do that?" six months later, the answer has a date and a comment thread.
Contractors and agencies
Freelancers and outside agencies join as guests. They see only the spaces you add them to and the items you share there, and can contribute but never manage. When the contract ends, remove them from the space.
Getting access
Emitii is invite-only: request access and the Emitii team sets up your workspace. You can also try a live demo first, without signing in.
Frequently asked questions
- Can our developers use Emitii from their coding agents?
- Yes. The Emitii CLI connects coding agents such as Claude Code, Codex, Cursor and OpenCode to your spaces, so they can read and update tasks, docs and time entries. The Emitii team enables it per organisation, so contact them to set it up.
- Can we add contractors without giving them full access?
- Yes. Contractors join as guests, see only the spaces they are added to and only what you share with them.
- How should a startup organise its spaces?
- Start with one space for the founding team, then add spaces for product, go-to-market and operations as the team grows. Space types only set which tabs start switched on, and modules can be changed later.
Related
- Startup workspaceA simple Emitii setup for startups: a product space, a company space, board columns, standups in Pulse, decisions in Docs and weekly Posts.
- Team communicationEmitii Messages covers direct messages, group chats and each space's Pulse, with threads, mentions, reactions, pins, reminders and file sharing.
- Project managementSee how Emitii runs each client, project or team in its own space, with a board, tasks, schedule, docs, chat and timesheet turned on as needed.
- Product developmentHow software and product teams run features, bugs, specs and standups in an Emitii space, with board rules, docs and the CLI for coding agents.
- Software companiesSoftware companies use Emitii for sprint boards, standup chat, specs and client delivery in one place, with a CLI and MCP server for coding agents.
- Emitii vs NotionCompare Emitii and Notion on docs, wikis, projects, chat, calendars, time tracking, AI and access, and learn which workspace fits your team's way of working.