Case studies,
shown live
Instead of unverifiable success stories, each industry below ships with a working interactive dashboard you can click through right now. Detailed written case studies are being prepared with the clients involved and go live only once they confirm what we may describe.
What each case study will contain
A case study is only useful if it is specific enough to argue with. These are the six sections every write-up will have.
Context and constraints
The operational problem, the hardware and protocols involved, the regulatory or delivery constraints, and what had already been tried.
What was actually built
Specific systems and interfaces, not a feature list. Screens, services, integrations and the boundaries between them.
Architecture decisions
The trade-offs we made and why, including the options we rejected. Decisions are only useful with their alternatives attached.
Technology stack
Languages, frameworks, protocols, data stores and infrastructure — with the reasoning behind the choices that were not obvious.
Verified outcome
What changed for the client, stated only as far as they can confirm it. Where a number cannot be verified, we will say so rather than estimate.
What we would change
The honest retrospective: what we would do differently with the knowledge we finished the project with.
Two published write-ups
Both are reference implementations, not named client accounts. The six sections match the editorial standard above, and the desk on each page is the same simulator you can open full-screen.
BESS operations desk→
Energy-flow topology, SOC/SOH, peak-shave schedule and string diagnostics on an 11 MWh simulator. The write-up states what was built, which decisions we made and what we would change — then lets you click the desk.
Read the BESS caseCRM operations desk→
Pipeline kanban, deal register, activity feed and invoice aging on one account model. The write-up states what was built, which decisions we made and what we would change — then lets you click the desk.
Read the CRM caseFive interactive dashboards
Each dashboard below runs on a deterministic simulator with fully synthetic data. No client systems, real plant measurements or live network connections are involved. The specification numbers — MW ratings, MWh capacity, connector counts, worker nodes, deal slots — are fixed simulation parameters chosen to exercise the interface across a representative operating range. The purpose is to demonstrate layout, data density and update behaviour, not to represent a delivered project.
CRM operations desk
Simulator parameters: 8 seats, 18 open-deal slots, €420k quarterly target. The dashboard renders a five-stage pipeline, deal register, activity feed and invoice aging. No client CRM data is used.
Open the CRM dashboard →Solar portfolio monitoring
Simulator parameters: a 2.25 MW PV plant, 18 string inverters, 90 DC strings. The dashboard renders synthetic irradiance, performance ratio and per-string health data, with Modbus TCP / SunSpec / IEC 61850 polling cycles run at 120× real time. No real plant data is used.
Open the Solar dashboard →BESS operations
Simulator parameters: 11 MWh of storage across three banks. The dashboard renders synthetic energy flow topology, SOC/SOH analytics, peak-shaving schedules and string-level diagnostics with simulated alarms. No real plant data is used.
Open the BESS dashboard →EV charging platform
Simulator parameters: 6 charging stations, 22 CCS & Type 2 connectors. The dashboard renders synthetic session energy, utilisation metrics, 24-hour load profiles and OCPP-style connector state transitions. No real charging network data is used.
Open the EV dashboard →Video transcoding pipeline
Simulator parameters: 8 worker nodes, ABR ladder generation. The dashboard renders synthetic job progress, worker throughput, quality gate scores (VMAF/PSNR) and pipeline health metrics. No real transcoding workload data is used.
Open the Video dashboard →Judge the engineering, not the marketing
The industry pages above each ship with an interactive dashboard you can click through — a more honest signal of capability than an unverified success story.
What you can inspect today
Send the brief. Estimate in 24 hours.
Describe the domain and the constraint. We say what we can share under NDA and reply within one business day.