About
Björn Rödiger
Power Platform & Azure Architect
Rubj IT is a boutique Power Platform & Azure architecture consultancy founded by Björn Rödiger, active across the DACH region and Eastern Europe.
Over two decades of building integration systems, cloud architectures, and business applications — from enterprise middleware to modern low-code platforms.
Point Of View
Why Rubj IT exists
I started Rubj IT because I wanted to work across the full spectrum — different technologies, different industries, different people. One week it's a Dataverse schema for an energy company, the next it's an Azure integration architecture for a logistics platform. That variety is the point.
Along the way, I kept seeing the same pattern: teams shipping features without agreeing on what 'done' means. So every project I take on starts with a specification — not code. What are the acceptance criteria? Who approves at each gate? Answer those first, then build. That became the Forge Method.
See the Forge Method →Background
A career shaped by integration and delivery.
The through-line is consistent: connect systems, reduce ambiguity, and make delivery hold up outside the happy path.
Commercial apprenticeship
- First IT integration projects: time booking system, Outlook sync
IT operations & energy market software
- System operations for Dynamics NAV 4.0 — project & timesheet integration
- Server and infrastructure maintenance
- Participant in the EDNA Initiative Germany
- Maintaining and extending an energy market communication tool for the German market
System integration developer & architect
- Pre-sales and development with model-driven integration tooling
- Projects across UK, Austria, Germany, France
- Sectors: finance, utilities, banking, automotive
- Integration of webshops, risk management systems, ERP systems
Development lead — integration & architecture
- Lead for integration and RPA tooling at a utility group
- System integration architecture across energy generation, sales, grid operation, market communication
- Established CI/CD guidelines, development pipelines, and quality gates
Azure integration
- Building solutions with Logic Apps, API Management, Service Bus, Azure Functions
Transition to self-employment
- MES redesign and development
- QM software development
Rubj IT founded
- Azure & Power Platform integration and customisation: Power Pages, Dynamics Sales, Power Automate, custom connectors, Service Bus, Functions, API Management, Azure DevOps
- Sectors: utilities, insurance, fire & safety, industrial manufacturing
- Projects: Dynamics Sales / SAP IS-U integration, Power Pages SharePoint integration, Dynamics customisation for manufacturing, on-prem to cloud migration, Sugar CRM to Dynamics migration, Infor ERP integration, Azure B2C Power Pages, custom Dynamics integrations
- Workshops: best practices for Power Platform integration patterns
- Roles: lead developer, integration developer, system integration architect
Why Rubj IT exists
Method before momentum.
Along the way, I kept seeing the same pattern: teams shipping features without agreeing on what 'done' means. So every project I take on starts with a specification — not code. What are the acceptance criteria? Who approves at each gate? Answer those first, then build. That became the Forge Method.
Now that AI agents are writing code alongside people, this structure isn't optional — it's the only way to stay in control of what reaches production.
Working Stack
Technology matters, but only in service of delivery discipline, operational clarity, and maintainable systems.
What This Means In Practice
A consultancy shaped by architecture, but judged by what reaches production.