The status gets written three times. Once in the work item, once in the deck, once in the report.
The work sits in the item list, the roadmap in a presentation, the weekly report in a document next to it. Every week the same numbers are moved by hand into a second shape, and the workload lives in a spreadsheet exactly one person maintains.
In the sprint review someone looks for the page behind the story in a second tool.
Capacity planning lives in a spreadsheet beside the initiative.
The report and the board show different numbers.
Four things that shorten Monday morning. All in the same space, none of them behind an export.
ABT-14
Q3 campaign spring promotion
ABT-27
Review quote for Muster AG
ABT-31
Onboarding Marie Keller
ABT-32
Set up workstation and accounts
ABT-08
Checkout system outage Bern
ABT-05
Budget website relaunch
Cycles and sprints
Estimate, capacity and burndown hang off the same initiative. What gets estimated in planning shows up as a number in the review.
Portfolio across initiatives
Several projects side by side, with status, ownership and open points. The view comes out of the work items, not out of a second set of records.
Roadmap from real work items
The timeline reads the items your team moves anyway. When a cycle shifts, the roadmap shifts with it.
Status report as a flow
Weekly report and status update come out of the cycles as an automation and land as a page in the space or a message in the channel.
Monday morning, sprint planning. From the backlog to the published status, without switching tools.
Review the backlog
The team opens the space. Open items, estimates and the pages behind them sit side by side; the discussion needs no second screen.
Check capacity
The workload for the next two weeks sits on the cycle. Anyone away is recorded, and the plan accounts for it.
Start the cycle
The cycle starts with what fits. The rest stays visible in the backlog instead of in someone's notes.
Publish the status
An automation writes the summary as a page in the space and posts it to the channel. Nobody retypes numbers.
The apps behind it. All in the same space, no second tool.
Projects carries the work items, Docs holds the knowledge beside them, Time records effort on the item itself, and Automation takes the repetition off your hands.
Projects
Agile project management for product and engineering teams, with cycles and releases.
Docs
The wiki for your team's knowledge, with version history and export to PDF, DOCX and Markdown.
Time
Time tracking and billing, directly on tasks and projects.
Automation
Workflows without code, triggered by events from any app.
Connected where it counts. Six connections from everyday project work.
Commits on the work item, effort into accounting, meetings into the calendar, updates into the channel.
One product, one vendor. Every module belongs to it.
Work items, documentation, time tracking and automation belong to the same product. There is no add-on for the roadmap and no second tool for the report; what a project lead needs sits in the same space as the work.
One contract, one contact, one roadmap.
No marketplace and no third-party add-ons to run.
Operated in a Swiss data centre or on your own hardware.
Questions from project leads. Five that come up in almost every first conversation.
How many initiatives can run in parallel?
The number of spaces and initiatives is not capped. The portfolio view brings them together; which ones appear is governed by permissions.
Can we bring content over from Jira and Confluence?
The migration tool for Jira and Confluence Data Center is next on the roadmap. Until then we take content over as part of the migration; we set the route against your actual content.
How does capacity planning work across teams?
Workload hangs off people, not off a single initiative. Anyone planned into two cycles appears in both with the same available time.
Is there a calendar or timeline view?
Cycles carry a start and an end, and the roadmap places them on a timeline. A dedicated calendar view is next on the roadmap.
Can we define our own flows?
Yes. Status sequences, approvals and recurring steps are built in Automation, without code.
Evidence for the compliance review
Information security is certified to ISO 27001 and processing meets the nFADP and the GDPR. The documents are ready before you ask for them.
Other disciplines in the same system.
Test it against your own content.
A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.