25%
Ongoing operations
Two hours a day cover support requests and small changes in an established environment. Larger projects are spread over several days.
One subscription instead oftwo or three positions.
Anyone who wants to manage Jira and Confluence reliably in-house keeps at least two or three people on staff. Otherwise support comes to a halt during vacations and sick leave.
Our monthly subscription is usually less expensive. We configure, document and support your environment at a fixed price with an SLA, permanently and as partial outsourcing of your IT.
The cost argument
Staffing always costs.
Subscribing costs what you need.
Staffed in-house
Two or three positions, so that someone is always there.
All of them are paid, even if only part of their time is needed once the rollout is done. Vacations and sick leave still leave gaps.
By subscription
One point of contact, always staffed.
You pay for the hours per day your environment needs, as a fixed monthly price. We absorb absences, not you. Usually that is less expensive than in-house resources.
Your subscription: four capacity models
Like a part-time position. Just without the gaps.
In all four models we are available Monday to Friday from 9 am to 6 pm and get back to you within one hour. The models differ in how much time we reserve for you each working day: 2, 4, 6 or 8 hours.
The same in every model
- Office hours
- Mon to Fri, 9 am to 6 pm
- First response
- within 1 hour
- Outside office hours
- from 9 am on the next working day
- Public holidays
- German nationwide holidays excluded
- Reserved hours
- same day only, unused hours expire
- Additional demand
- can be booked at short notice
- Cover
- vacations and sick leave included
- Price
- fixed monthly price
- Term
- 1 year, 3 months’ notice
50%
Active development
Four hours a day: alongside support, new workflows, fields and templates are created continuously. The sensible choice once Jira and Confluence are actively being developed or the number of users is growing.
75%
Growing environment
Six hours a day for environments with many teams and regular change requests. Several projects run in parallel without support having to wait.
100%
One full position, no gaps
Eight hours every working day, the full working capacity of one person. We absorb vacations and sick leave, not you.
Included in the subscription
Four services, one point of contact.
-
Customizing
Workflows, project structures, data fields, permissions, dashboards and templates, adapted to the way you actually work. No off-the-shelf standard configuration.
-
Documentation
Configurations, processes, changes and decisions, recorded in writing. What was changed, why, and how the system is structured.
-
First- and second-level support
A direct point of contact for your team. Simple questions we answer right away; more complex problems we analyze and resolve technically.
-
Consulting
When new requirements arise or processes change, we show sensible solutions within Jira and Confluence.
Compliant operations
Complete. Traceable. Accurate.
Every change to Jira and Confluence goes through documented change management. What was changed, why, by whom, when and with which approval is settled before the change goes live. For regulated companies and for every audit.
- Completeness
- No change without an entry. Configuration, processes, changes and decisions are documented without gaps.
- Traceability
- Every entry answers the same questions: what was changed, why, by whom, when, with which approval.
- Accuracy
- Changes are reviewed and approved before they go into production. What is documented matches the system.
WhatWhyWhoWhenApproval
CHG-0117Workflow “Risk assessment”: status “Under review” added Four-eyes principle before approval Risk Management department Mar 12, 2026 · 09:41 approved
CHG-0118Role “Internal Audit”: read-only access to the “ICS” project Segregation of duties, need-to-know Head of IT Mar 12, 2026 · 14:07 approved
CHG-0121Required field “Approved by” in the “Change Request” template Evidence of approval in the ticket Internal Audit Mar 19, 2026 · 10:15 approved
CHG-0124Automation “Reminder seven days before due date” Meet the deadlines in the control plan Compliance department Mar 24, 2026 · 16:32 under review
Experience and blueprints
We rarely start from scratch.
Years of work with Jira and Confluence have produced proven blueprints, templates, solution approaches and configuration patterns. We use them to implement requirements efficiently instead of reinventing every implementation.
What a blueprint brings.
A blueprint is not an off-the-shelf standard configuration but a proven starting point: structure, workflow, permissions, automation and documentation fit together and are adapted to the way you work. That saves the weeks in which everything would otherwise be created for the first time.
Our use cases show what that means in practice: document control, measuring equipment management, project portfolio, procurement with compliance checks.
View use cases- 01 Project templateIssue types, fields, screens
- 02 WorkflowStatus sequence, approvals, validators
- 03 Permission schemeRoles, groups, visibility
- 04 Automation rulesAssignments, reminders, handovers
- 05 Confluence spacePage templates, structure, links to Jira
- 06 Dashboards and filtersReports for team and management
- 07 DocumentationStructure, decisions, changes
End to end
Handover is not the end.
We do not only accompany the implementation but the entire life cycle. Whoever has built and documented an environment knows it. That is why support is the eighth step and continues by subscription.
- Consulting
- Business analysis
- Design
- Implementation
- Testing
- Training
- Documentation
- Supportcontinues by subscription
Next step
We take a look at your environment and propose a capacity model.