Technical consulting with execution in mind
Consulting, in our hands, is not a substitute for execution but its starting point — and sometimes the execution itself. We help companies, education providers and public bodies select, roll out and configure standard software, especially in the Atlassian universe and in digital education setups. What we recommend is usually something we have built, introduced or operated ourselves: as product makers today and as IT consultants in enterprise environments before that. Conversations get shorter and decisions more durable. If a standard product is enough, we'll say so. If a dedicated tool is the better answer, we'll say that too — and help build it.
Jira, Confluence and their ecosystem
In the Atlassian space we accompany the usual projects: consolidating multiple Jira instances, migrating off legacy systems, introducing structure for projects, workflows and permissions, wiring SSO and LDAP, cleaning up historically grown custom-field landscapes. We know the traps — workflow transitions with lost required fields, permission layers nobody understands anymore, mountains of comments that have to move after years. When a tool solves it faster than manual clicking, we bring Jira Synchronizer and Task Automater with us; when the standard is enough, we use the standard.
Learning platforms, identity, course administration
In education we accompany academies, universities and education providers on the way to a continuous digital education flow: selecting and rolling out learning platforms (Moodle, other LMS), connecting to existing administration systems like Antrago, identity strategies with Keycloak or comparable OIDC providers, designing lecturer and participant views. Same logic: whatever our Digitalplattform and Lernhefte already solve, you don't need to have rebuilt. Anything beyond that, we advise on as honestly as on what fits.
From a four-hour workshop to a multi-year project
Some projects start with a four-hour workshop that sorts requirements and makes decision options visible. Some run for weeks as a guided rollout. Some grow into multi-year hands-on projects where we build the custom piece ourselves. We work on fixed prices or time & material — often leaning toward fixed prices, because clear outcomes are easier to plan for both sides than open-ended hourly lists. Our day-to-day work is not writing documents but co-building products: sharpening requirements, preparing decisions, using standards and extending them where the standard is not enough. Remote works well for daily routines; we come on-site where collaboration benefits from it.
Engagement formats
Four typical ways to work with us — from a lean clarification hour to a full custom implementation. In practice the formats often combine: a workshop clarifies, an audit recommends, a rollout puts the standard in place, a hands-on phase adds the custom piece.
Workshop
Clarify requirements, sort options, bring focus to your own ideas. Typical length: hours to days. Useful as an entry point when a project is still hazy and a structured session unlocks the next step.
Audit
Examine the status quo, formulate a recommendation — for an existing tool landscape, a migration path, a governance construct. With AI assistance today often in days instead of weeks, without sacrificing depth.
Rollout & configuration
Pick the standard product, install, configure, run first training. Typical examples: Jira setup for a new team, Moodle rollout for an academy, Confluence structuring for an existing knowledge base. You receive the…
Hands-on implementation
When the standard product isn't enough, we build the additional custom piece ourselves — as an extension, a dedicated tool, or an integration layer between existing systems. Weeks to months, with AI workbench support,…
Discuss your situation