Iordanis Felekidis · Atlassian Cloud Consultant
For teams without their own Atlassian specialist: fixed monthly hour budgets for Jira, JSM, Confluence, Jira Assets and automations – remote and flexible.
Jira Cloud
Setup • Process optimization • Automation • Consulting
Confluence Cloud
Structures • Templates • Knowledge Management
Jira Service Management
Portals • ITSM • Workflows
Jira Assets (CMDB)
Object schemas • Asset linking • Automation
For several years I have been fully responsible for Jira Cloud, Confluence Cloud and Jira Service Management Cloud in an internal enterprise environment.
In addition, I worked at an Atlassian Platinum Partner, supporting companies of different sizes – from small teams to enterprise customers.
I know the real pain points and build solutions that work in day-to-day use – without unnecessary complexity.
Focus: efficient setups, automation and scalable knowledge management for teams of any size.
Solutions that work in day-to-day use
Exclusively Atlassian Cloud
No unnecessary complexity
For teams of any size
Focused on Atlassian Cloud – clear, practical and without unnecessary complexity.
Process optimization: streamlining workflows, building automations, cleaning up permissions.
Building clear structures, templates and scalable knowledge management.
Service desk, ITSM processes, customer portals and ticket workflows.
Structured asset data, directly linked to your service processes.
Jira automation; getting started with Rovo: identifying suitable use cases and supporting first pilot applications.
A monthly hour budget for your Atlassian Cloud: one dedicated contact for changes, improvements and questions – without having to create a dedicated position.
Retainer S
For small teams with a stable setup: ongoing adjustments, role and permission concepts and smaller automations.
Retainer M
For teams actively evolving their processes: new workflows, service desk adjustments and regular improvements.
Retainer L
For multiple teams or larger initiatives: continuous development of Jira, JSM, Confluence and Jira Assets.
Handling of unused hours: as agreed.
Analysis of your Jira or JSM instance with a prioritized list of actions – a good way to estimate the right retainer size.
Fixed scope, e.g. a service desk portal or introducing Jira Assets.
Remote, one dedicated contact – personal support instead of a ticket queue.
Discuss a retainerTell me briefly where things are stuck – I will reply within 2 business days and we will schedule a free 30-minute intro call.