Energy and utilities software development for reproducible reporting and current trading data.
We build software for energy and utility operators, connecting metering, billing and reporting around your existing systems.
Keep reproducible history for reporting and current data for operations and trading.
- 120+Projects delivered across 12 countries since 2012
- 100+Senior in-house engineers, six countries
- 2 to 4 weeksTypical time from signature to start
- ISTQBISTQB-certified QA engineers
- ISO 27001Certified security practice, audited by Quay Audit UK
01Overview
Utility software built around your operating systems
We start with the meter, telemetry or vendor record you need to use and the billing, operational or reporting workflow that needs it. We establish how current that view must be and which past figures must remain reproducible, then scope the first integration around the supported interface.
- Measure and monitorReadings from physical assets, with a defined path into the systems that use them.
- Meter and telemetry ingestion
- SCADA and historian reads
- Asset and network data
- Trade and settleThe commercial side of the same readings: bought, delivered, owed.
- Deal capture and position
- Scheduling and nominations
- Invoicing and settlement
- Bill and serveConsumption and tariff records connected to billing and customer information systems (CIS).
- Billing and CIS integration
- Customer and field portals
- Tariff and consumption data
- Account and reportHistorical records that support regulatory, sustainability and management reporting.
- Regulatory submissions
- Emissions and sustainability
- Desk and board reporting
02Compare
Reproducible reporting and current operational data
A historical energy report and a live operational or trading view can use the same readings on different terms. We choose the integration workstream around the consumer's need for version history, freshness and reconciliation.
| What we hear | What needs resolving | The integration workstream |
|---|---|---|
| “One warehouse serves the traders and the regulator.” | Historical extracts and current reads share a workload | Separate the consumers: an append-only history for reproducible reporting and a fast read model for current trading data.Data and reporting engineeringOr book a meeting |
| “The same meter and market data lands in four systems, four times.” | Each consumer reads a different copy | Build one ingestion path with versioned corrections and downstream feeds, keeping the vendor platform as the system of record.Platform development and integrationOr book a meeting |
| “A regulator asked what the figure was in March and nobody can rebuild it.” | The reported figure needs its historical inputs | Preserve the readings, estimates and corrections used for a submission, with the version history needed to reproduce it.How we build custom systemsOr book a meeting |
| “Readings arrive as files and somebody types them in.” | Manual entry between a file and a database | Assess recognition and ingestion with operator confirmation. Our German recognition-tool project demonstrates document-to-database automation in an adjacent sector.How we did this in GermanyOr book a meeting |
| “Two systems disagree, so we are replacing the platform.” | The cause of the discrepancy needs establishing | Trace the source, correction history and refresh schedules. Retain or configure the platform where it fits; use a supported connector or custom module where needed.A technology review, not a rebuildOr book a meeting |
Reported and traded energy data come off the same meters. One must be defensible to a regulator months later, and the other must be current. So we keep them apart, with an append-only store for reporting and a fast path for trading.
Vuhar MamedovManaging Partner for Europe, unicrew03Solutions
Custom energy and utility software we build
Our energy software development services connect SCADA, metering, billing and CIS through supported interfaces.
Meter and telemetry ingestion, with market feeds, versioned corrections and downstream data supplied on each consumer's schedule.
- Right when
- Metering feeds need a shared ingestion path
Connectors for supervisory control and data acquisition (SCADA), meter data or billing platforms, using supported reads and writes while the vendor system retains record ownership.
- Right when
- A supported platform remains the record
Trading and settlement extracts and regulatory submissions built from versioned inputs, so a historical figure can be reproduced after readings change.
- Right when
- A submitted figure needs reproducing
Consumption and billing views for customers, document access for partners, and field interfaces connected to the records engineers need.
- Right when
- Customers and field staff need data access
Forecasting models and dashboards using your readings and prices. We assess data quality and the decision the model will support before choosing an AI approach.
- Right when
- The forecast lives in a workbook
Turn a workbook-based billing, reporting or internal operational process into a maintained application connected to its source data.
- Right when
- A workbook runs an operational process
04Obligations
Reporting requirements and our company credentials
We scope energy-data requirements with your reporting and security owners, against the entity, market and records involved. Our company credentials support that work.
Readings get corrected after the fact
Where estimates are replaced by actual readings, preserve the inputs used for each report alongside later corrections. The retention model follows the reports you need to reproduce.
- In a build
- Versioned readings and correction history
Submissions arrive on a clock
For reportable records, confirm the recipient's format, reporting channel and deadline. Wholesale-energy transaction and order reporting under REMIT depends on the market and records involved.
- In a build
- The applicable format and deadline
Consumption data that identifies a person
Consumption records fall within GDPR where they identify a person, alone or with other information. We scope access and retention with your data-protection owner against the actual records.
- In a build
- Retention and access, decided early
ISO 27001:2022 and ISO 9001:2015
Our information-security and quality-management systems are certified, with renewal through a multi-stage audit by Quay Audit UK. These are company management-system credentials.
- What it gives you
- A document trail that already exists
ISTQB-certified QA engineers
unicrew has ISTQB-certified QA engineers. We scope testing around the readings, corrections and billing or reporting outputs in your integration.
- What it gives you
- QA expertise for the agreed scope
Least-privilege access, agreed first
On build engagements, we agree least-privilege access with your technical contact and use read-only access wherever the work allows. Discovery has no production write access.
- What it gives you
- No production write during discovery
Scope requirements against the data and its consumers
Your reporting and security owners confirm applicable duties, including NIS2 requirements by entity and national law. We use those inputs to scope retention, access and the separation of historical reporting from current operational reads.
05Proof
Trading and data-platform work behind our offer
Our commodity-trading build shows connected commercial records. Adjacent climate-tech and recognition projects show the data modelling and automation relevant to utility integrations.
- A trading platform, and the specialists it neededWe built a CRM and B2B marketplace for a Milan commodity trader, signing contracts as Ethereum smart contracts, under our former Artelogic brand. In his verified Clutch review of 7 April 2022, published anonymously, the co-founder and CEO writes that "they were able to use an expert that they had in-house to tackle that part of the project even though this resource wasn't on the team they assigned initially".
- Environmental accounting, at the scale it hasIn his verified Clutch review of 12 June 2025, a German climate-tech CTO describes calculating "the carbon footprint and 15 other environmental factors, such as water and land use". We rebuilt the environmental-accounting platform on React, Next.js and a Neo4j graph database.15other environmental factors, alongside carbon footprint
- Manual data entry, measured before and afterWe built a C# and AWS recognition tool for a German software company, with operator confirmation of recognized data. In his verified Clutch review of 15 April 2022, the CEO writes: "Two people typing data into the database went about 5,000 new data sets per month. With this component, we're reaching twice the amount of data sets per month."2xthe client's own measure of the change
06Client voices
What the clients behind those builds say
I was very satisfied with Artelogic’s project management. They were very good at organizing all the different parts of the project, and our communication was easy; they were always available and proactive. Towards the end of the project, they went the extra mile and worked longer than expected without charging for the extra time, showing a lot of commitment.
We’ve seen enhanced customer satisfaction thanks to unicrew’s work. Our customers love the UI and speed of the application. We’ve received positive feedback, and there are no errors in the system. unicrew meets their deadlines and stays on budget.
07Case studies
Trading, environmental data and recognition projects
TradingTrading software with smart contractsOur client, an experienced commodities trader, came to unicrew with a detailed PRD (Product Requirements Document) to develop the trading platform.- Climate TechRebuilding a carbon-footprint SaaS platform for a European climate-tech startupunicrew embedded three full-stack developers and a UI/UX designer in a European climate-tech startup's SaaS product, rebuilding many parts of it from scratch.
- AutomationDoubling data-entry throughput with a custom recognition toolunicrew automated a manual data-entry bottleneck with a C# and AWS recognition tool, doubling the data sets the team processed each month.2xData sets processed per month
08Questions
Questions about energy and utilities software
Energy and utilities software development builds, integrates and modernizes the systems that measure, trade, bill and report energy.
For a utility operator, this can mean connecting meter data and telemetry to billing, customer information systems (CIS) and reporting. We assess the source, its supported interfaces and the consumer, then scope the integration or module needed. Historical reports can use versioned inputs while operational views use current readings.
Our direct sector proof is a commodity-trading CRM and private B2B marketplace, supported by the client's verified Clutch review of 7 April 2022.
Adjacent projects include an environmental-accounting platform rebuilt with React, Next.js and Neo4j, and a C# and AWS recognition tool for data entry. These demonstrate data-product and automation work relevant to utility integration.
We assess the platform's supported interfaces before confirming an integration scope.
For SCADA, metering, billing or CIS, we establish record ownership, permitted access and the reads or writes the platform supports. We test the agreed interface with your data and define correction handling and reconciliation. Where an API is unavailable, we assess supported exports or connectors with the platform owner before recommending the approach.
We agree release acceptance with your system owners, document the delivered interfaces and hand over operation. Ongoing maintenance is scoped separately where needed.
We quote against your integration or development scope. Most engagements start within two to four weeks of signature; delivery duration depends on the agreed work.
- Time and materials: billed hourly, quoted per project.
- Fixed price: quoted per project against an agreed outcome.
- Team extension: billed monthly per team member, with no recruitment or placement fee.
We recommend the model after discovery. Fixed-scope work includes a post-launch warranty, with its length agreed in the contract.
We scope security and data duties against your entity, market and records, with your reporting and security owners.
On build engagements, access is least-privilege and agreed with your technical contact, read-only wherever the work allows, with no production write access during discovery.
unicrew holds ISO 27001:2022 and ISO 9001:2015 management-system certifications, renewed through a multi-stage audit with Quay Audit UK, and has ISTQB-certified QA engineers. GDPR applies where consumption records identify a person. Applicable NIS2 duties depend on the entity and national law.
Yes. Trading-desk systems and charging products have distinct scopes, covered on their own pages.
CTRM and ETRM software development covers deal capture, position keeping, settlement and integration around a trading package. EV charging software development covers charge points, sessions, roaming and tariffs for charge point operators and mobility providers. This page focuses on the utility data integrations around operating systems.
Plan your next energy-data integration
Discuss which reports need reproducible history and which operational views need current readings. We scope the source systems, supported interfaces and first consumer with you.
What happens after you contact us
- We reply within one business dayTell us which source systems and data consumers you want to connect.
- A call about the dataWe review the records, reporting requirements and freshness each consumer needs.
- Route and engagement model, in writingAgree an integration or development scope and a time and materials, fixed price, or team extension model.
- NDA, then discoveryMost engagements start within two to four weeks of signature.