How do we decide what is being added to Phonemos?

Development of Phonemos follows two parallel development tracks. On one hand, we continuously invest in strategic developments we think will benefit our customer base in the broad sense best. But in parallel, we often recognize that individual customers require very specific and often only small features in order for their project to tip over to full success. Thus, we always have a set of customer-driven developments going on in parallel to our own efforts.

If you are missing something, just reach out to us. Our product management is very happy to talk about your suggestions.

Our self assessment and product development strategy

Phonemos has grown into one of the best Wiki systems in the global marketplace. The feature set holds up to comparison with every major platform, often outperforming others in terms of flexibility of configuration and deployment, retrievability of information and asset protection.

In the upcoming 12 months, our main quest is to extend Phonemos into the project management tool that offers a seamless integration between project documentation and project tracking for business teams. While Phonemos can be used by technical DevOps teams as well, we believe that Phonemos will best serve the needs of business users (requirements, planning & tracking to product acceptance) and then integrate with multiple development stacks that are often different depending on technical target platforms, e.g. Azure DevOps, GitHub, GitLab, and so on.

As a side quest that is already ongoing in smaller steps, but where we have a more relaxed overall timeline, we will target specific niche markets where we will outperform other general purpose tools with a tailored feature set that addresses specific user’s needs and outperform classic specialised tools on price and flexibility.

Objective 1: Extensibility and Custom Automation

With this objective, we want to enable customers and partners to extend Phonemos with better Workflow support, custom automations and data structures and functional features.

We have already delivered:

• A configurable metadata system (Manage structured metadata) that can be used to label Phonemos objects or build inventories and configuration management databases CMDB.

• A publishing workflow for documentation (Page publishing workflow) with preconfigured workflow scenarios.

• A natively supported MCP Server to integrate Phonemos into any LLM supporting this interface standard (AI agent support: Model Context Protocol (MCP) server).

• A public REST API with downward compatibility (Phonemos REST API)

• A fully featured GraphQL API (private), that can be used to do nearly everything; but beware: will change with new releases as features are added.

What key results we are about to deliver yet:

• The Phonemos Apps and Plugin Architecture is about to be published in Summer 2026. This will allow third parties to write custom automations and UI components without changing the source code.

• An App store for Phonemos extensions is about to be launched afterwards.

Objective 2: Integrated project and portfolio management

With this objective, we will overhaul and extend our task management system so that users can not only track simple teamwork, but entire complex projects and project portfolios. Many customers will no longer need a separate issue tracking system afterwards or only connect one for the technical development team. This will include several major new features.

Add workflows to your Phonemos objects

Whether you have your product requirements written up as a Wiki page or maybe in a file document, you can add workflows to these objects in order to track them through a series of configurable processing stages.

In order to visualize work, you will be able to track work with Kanban boards (Advanced task management with Kanban).

 

Prioritize product ideas and risks

Slightly modified versions of the Kanban board will allow you to visualize work also in two dimensional matrices (Matrices for risks, ideas etc.). This will allow you to prioritize a portfolio of product ideas, risks or do user story mapping in a very easy way.

 

Project planning

Features will be added to plan your project and communicate those plans.

• Work breakdown structures

• Milestones & Timelines

 

We have already delivered:

• A configurable metadata system (Manage structured metadata) that can be used to configure fields for any object.

• Object references for dependencies and multi-level work breakdown structures.

What key results we are about to deliver yet:

• Gantt planning has been implemented and is in test. It is going to be released in early summer 2026.

• Kanban and Risk boards are under development.

• The portfolio reporting features already exist as part of custom customer projects, but is being standardised and converted into a Phonemos App using the Phonemos Apps and Plugin Architecture.

Objective 3: Service Management Portal and AI-based ticketing

With this third objective, we will add a service management portal that allows end users to create tickets in service scenarios. These tickets can then be processed using support queues and workflows that share a common basis with the project management features from objective 2. We will deliver this feature towards end of 2026.

We have already delivered:

• We have a working proof of concept / prototype that we can demo.

What key results we are about to deliver yet:

• Service Management Portal

• AI-based information collection for service requests.

• Real-time and asynchronous conversation features with the end user