Energy and building practice, not slide decks
We come from HVAC, controls and energy engineering — and ship live APIs and apps (SpotpriceAPI, Sparvo). The PoC speaks the language of your plant, not only a generic tech stack.
Prototypes & APIs
Working PoCs for energy, load and buildings
We turn an idea into a working prototype — with live interfaces, measurable results and a clean handoff. One person joining automation, energy engineering and software.
In short
A working PoC (proof of concept) is a functioning slice — API, dashboard or signal path — that shows whether an idea holds in the plant. We do not replace your EMS and we are not an agency production line. Goal: validate, document, hand off.
Why run PoCs with M.ZEILER
Large agencies excel at volume and headcount. For working PoCs at the energy–load–API boundary, other strengths usually matter more.
Direct line to the person who builds
No account-manager telephone game: scope, architecture and code sit with the same contact.
Lean and straightforward
Few alignment loops, clear scope, kill criteria from day one — without onboarding a fifteen-person machine.
More budget in the prototype, less in overhead
Without agency layers, most of the budget goes into concept, working prototype and handoff. Fixed quote after the intro call — no team markups listed on the site.
Validate and hand off — no lock-in
The goal is a solid PoC plus specs, tests and material for your software partner or in-house team. We do not lock you into an agency retainer.
What we already run live
Capabilities from our own products — as proof, not a dump of the full API reference.
-
Forecast API
Multi-day electricity price forecasts for integrators.
-
Decision windows
Windows when switching and load shifting pay off — for EMS logic.
-
EMS in the field
Hooks into plant control, not lab mocks only.
-
Signals, not core logic on site
Intelligence on the server; the plant gets a clean interface.
-
Sparvo app
Consumer PWA with prices, switch-on windows and PV logic.
-
Data behind the API
Time series and forecast pipelines, not a dummy endpoint.
Forecast and decision logic stay on the server. The plant receives well-defined signals — not open core logic on site.
SpotpriceAPI · Sparvo More on SpotpriceAPI and Sparvo
What we offer
Four building blocks — combinable, always with kill criteria.
Scoping
Goal, data, interfaces and abort criteria — in writing before code grows.
Working prototype
A running API, UI or signal path you can operate and measure.
Handoff
Docs, tests and artefacts for your software partner or team.
Follow-up (optional)
Short support after handoff — not a production SLA for critical plant.
How we work
One focused engagement at a time. Duration depends on data access and scope — not a two-week slogan.
-
01
Intro call
Free, 30–45 minutes: goal, data, who will run it later.
-
02
Scope and fixed quote
Clear frame, kill criteria, and what is out of scope.
-
03
Build and review
Iterative with checkpoints you can see.
-
04
Hand over
Spec, tests, access and a session with your partner team.
What you get
- Scope and kill criteria
- Working prototype (API and/or UI)
- OpenAPI or equivalent interface docs
- Test and acceptance scenarios
- Handoff pack for operations or a partner
- Optional: short case write-up
Who it is for
R&D, controls, utility innovation and integrators with an energy or building brief — not the mass market for “any REST API”.
PoC, MVP, handoff
A PoC tests whether something holds. An MVP would already be a first product for users. We deliver the working PoC plus handoff — not 24/7 operation of your critical plant.
Working together
After the intro call you get a clear fixed quote. No hourly rates on the website, no open hours without a budget frame. Languages: German and English.
FAQ
What is a working PoC with you — and what is it not?
A working PoC is a bounded, running slice (API, UI or signal path) with a measurable result. It is not a finished product, not 24/7 operations, and not closed-loop control of critical plant. Advisory and prototype — not a production SLA.
Do you replace our EMS or software partner?
No. We validate and hand off. Your EMS vendor or software team stays in the lead for day-to-day operations. We sit in between as a specialist, not a second EMS.
Who owns code, spec and data after the PoC?
Agreed artefacts are yours under the quote. Your operational and meter data stay yours. Third-party software and our existing products (SpotpriceAPI, Sparvo) stay with M.ZEILER or the respective rights holders.
How do you handle privacy / on-prem vs cloud?
We settle this in scoping: which data may go where, what must stay on-prem, what may live in an isolated cloud. Without data access there is no serious forecast or load PoC.
How do we start — and how is billing done?
A free intro call, then a fixed quote after scoping. No euro amounts on the website. We work in German and English.