Many teams. One place to ship from.

For organisations with many teams: one release page with a section for every team, roles for every person, and requests that reach the right one.

A Kanso release page, Release 3.4, with its ship date and progress, and the 1 blocked and 1 overdue filters above its Product section.

One workspace across the organisation

A Kanso task board with Backlog, To do, In progress and Done columns of cards showing priority, due date and owner.

Every team on the same release.

Product, QA and go-to-market each own a section under one ship date, and one checklist says when it is ready.

More about Releases
A launch checklist, Release 3.4 launch checklist, opened in Kanso with Before launch, Product and Quality headings over their checklists.

Requests that reach the right person.

Ask in a channel beside the work; the @mention lands in that person’s inbox.

More about Chat
Kanso chat messages that mention @Corvin Kestfeld, with a reaction, a reply and a linked release task.

What Enterprise adds

Compare the plans
  • Everything in Team

    Unlimited members, roles, chat and the inbox.

  • Who can see each page

    Keep each page to the people it is for.

  • Dedicated support

    Help from us as you set up and grow.

  • Security review

    Answers for your security team before you sign.

  • Custom terms

    Annual terms, written for your organisation.

  • Invoicing

    Pay by invoice instead of a card.

Questions

Yes. Team has unlimited members in one workspace, with roles and permissions, and Enterprise is quoted for an organization. Kanso is a young product, so a large group should start with one team on one real release.

Kanso at other sizes

All teams

Start with one team.

Run one real release in Kanso, then bring in the rest.