qurix compared — when we fit and when we don't.
We are a data-tech boutique for the energy sector, not a full-service provider. For part of what your organisation needs, we are the obvious call — for another part, explicitly not. This page sorts the provider landscape and says both.
Five categories of provider
Anyone awarding data and AI work in the German-speaking energy sector is effectively choosing between these five types. Each has an area where it is structurally the best option — and one where its business model works against the project.
1 · Industry standard software
Examples: Schleupen, powercloud, Robotron, SOPTIM
- Strong at
- Billing, market communication and energy data management as a maintained product. Regulatory change arrives as a release — you don't rebuild EDIFACT format changes yourself.
- Stops at
- Anything outside the product scope. Standard software ends where your own data landscape begins: analysis across several systems, process data from assets, your own models.
2 · Sector IT providers and data centres
Examples: items, rku.it, caplog-x, arvato Systems, BTC, GISA
- Strong at
- Operations and outsourcing. One platform shared by many municipal utilities cuts operating effort and headcount significantly — with full accountability for availability.
- Stops at
- Individuality. Standardising across many tenants is the business model; deviating from it is the most expensive and slowest thing you can ask for there.
3 · Large management and IT consultancies
Examples: Accenture, Capgemini, Deloitte, Sopra Steria, msg, BearingPoint
- Strong at
- Large programmes. When something needs 50 or more people over years, group-level steering, change management and regulatory breadth across all business units — only they scale that way.
- Stops at
- Work that depends on a few experienced people and short paths. Ramp-up time, pyramid staffing and day rates only pay off above a certain programme size.
4 · Generic data and AI boutiques
Examples: b.telligent, Alexander Thamm, INFOMOTION, statworx
- Strong at
- Data engineering craft. Lakehouse, dbt, orchestration, ML pipelines on any cloud stack — technically clean and proven across industries.
- Stops at
- The domain. Balancing groups, Redispatch 2.0, REMIT, ETRM position logic and the time-series quirks of power and gas get learned during the project — on your project time.
5 · Specialist products and SaaS
Examples: envelio, gridX, enersis, epilot, Volue
- Strong at
- One clearly bounded problem that is already solved — grid calculation, flexibility control, sales processes. Faster and cheaper than any in-house build.
- Stops at
- Integration and data ownership. The product solves its slice; bringing the data back together and keeping it analysable stays your job.
And qurix?
Data-tech boutique, Hamburg, focused on the German-speaking energy sector
- Strong at
- The transition zone between energy market data (market communication, ETRM, market prices) and process data (SCADA, asset telemetry, OT) — and at moving the result into sustained operation rather than into an architecture deck.
- Stops at
- Standard products and mass scaling. We don't build billing systems, we don't take over data centres, and we don't staff a 60-person programme.
Side by side
The criteria that actually decide our pitches.
| Criterion | qurix | Sector IT provider | Large consultancy | Generic data boutique |
|---|---|---|---|---|
| Energy domain language from day one | Default vocabulary: market communication, balancing groups, Redispatch 2.0, REMIT, ETRM | Deep, but tied to their own product | Present, depth varies with the team staffed | Built up during the project |
| Market plus process data (SCADA/OT) | Core topic | Rarely in product scope | Possible, usually spread across several units | Technically feasible, functionally new |
| Custom data platform | Snowflake, Databricks or Fabric — by context, not by house standard | Tied to their own product | Yes, with programme overhead | Yes, core competence |
| AI inside audited core processes | Deterministic core, agentic shell, audit trail included | Occasionally as a product feature | Strong on strategy, operations often contracted separately | Strong on models, approval process rarely considered |
| On-premise without US cloud | Deliverable — local LLMs, local RAG, KritisV/NIS2 context | Often yes, in their own data centre | Possible, usually not the default route | Cloud is generally the prerequisite |
| Operations after go-live | Part of the engagement, over years | Core service | Separate contract, separate unit | Often ends at handover |
| Scaling to 50+ people | No — deliberately not our model | Limited | Yes, that is the strength | Limited |
| Rolling out standard billing or market communication | No — a product vendor does this better | Yes, core service | Yes, as an implementation project | No |
Company names on this page serve to illustrate the respective category, not to rate individual providers. The category descriptions refer to typical business models, not to individual projects. As of October 2026.
The short version
If you read only one section of this page, read this one.
Call us when …
- market and process data have to meet — trading positions next to asset telemetry, balancing groups next to SCADA.
- you need your own data platform that stays alive after go-live and doesn't break at the first format change.
- AI has to pass an audited approval process — with traceability, an audit trail and a clear line between deterministic logic and model output.
- the data cannot leave the building — KritisV, NIS2, the BNetzA security catalogue, or simply a firm group policy.
- regulatory reporting needs automating that currently lives in spreadsheets and people's heads.
- you want a small, experienced team that shows something running in weeks rather than quarters.
Call someone else when …
- a billing or market communication system is being rolled out. That is product business — category 1 does it better and cheaper.
- you want to outsource IT entirely, data centre and first-level support included. The sector providers exist for that.
- 60 people are needed from next quarter. We don't field that number, and we won't pretend otherwise.
- an off-the-shelf specialist product already solves it — grid calculation or flexibility control, for instance. Buying then beats building.
- the lowest day rate wins the award. We don't win those tenders and generally don't bid on them.
- a PowerPoint architecture without delivery is what's wanted. That is not what we are built for.
How to check this
Delivered work you can read up on in the showroom — rather than a claim about ourselves.
Not sure which category your project falls into?
Describe it in three sentences. If a different type of provider fits better, we'll say so — and usually also what to look for there.
Describe your project