Tell Us What You Need & We'll Handle the Rest.

See our services →

Please take a moment to complete the following 6-step questionnaire, Your responses will help us design a precise and customized solution to your needs.

1
2
3
4
5
6

Business & operations

About you

So we know who to send the quotation to.

Your operation

Envera is priced by the size of the estate it reports on, not by how many people are allowed to look at it. Users are unlimited on every plan.

Plants, facilities or branches — count each one you need reported separately.
A rough band is fine. It tells us how much of your emissions sit in fuel combustion versus purchased electricity.

Your IT infrastructure

So we can scope any on-premise deployment, single sign-on, or system integration work correctly — including how you want the platform itself hosted.

Included either way.

A few things don't depend on your answers above — they're just how Envera works, on every quotation. Anything that does depend on your setup — on-premise deployment, single sign-on, role-based access, custom conversion factors, AI Engineer — is one of the questions in the form above, not a separate add-on to ask for.

Included on every quotation
INCLUDED
Unlimited users — pricing scales with your estate, not your headcount
INCLUDED
Energy, emissions and the overview, on every plan before you pick anything else
INCLUDED
Full double-precision analytics & full-precision CSV export
INCLUDED
Arabic / RTL interface, structurally enforced, on every plan

What people ask before they buy.

Why per site rather than per user?
Because the failure mode we exist to fix is one person holding the numbers. If we charged per seat, you would ration access, and the operations manager who needs to see the flare figure would go back to asking for a screenshot. The cost should scale with the size of your estate, not with how many people are allowed to look at it.
What happens to our existing workbook?
Nothing. We take an offline, read-only extract. The file is never modified and your production instance is never contacted. Many customers keep running the workbook in parallel for the first two or three reporting cycles — we would encourage it, because that parallel run is what proves the migration.
What if your numbers disagree with ours?
They will, in places — that is the point. Reconciliation is part of onboarding: every historical figure is recomputed and compared to the original, and each difference is traced to a cause. Usually it is compounded rounding, a silent exclusion, or a factor that was updated in one tab and not another. You sign off the differences before go-live.
How long does implementation take?
The extract and first load take days, not months, because we are reading a structure you already maintain. Reconciliation and sign-off is the longer part and depends on how much history you want verified. A single site with five years of history is a matter of weeks.
Do you support Arabic?
Yes — the full interface, right-to-left, on every plan. Not a translated veneer over a left-to-right layout: the layout itself mirrors. It's enforced automatically, too — an automated check blocks any release where the English and Arabic interfaces fall out of structural sync, so the Arabic side can't quietly rot behind the English one.
Can we host it ourselves?
Yes — on-premise or in your own private cloud; that's one of the options in the IT infrastructure section of the form above, not a separate request. Envera runs as a container against a read-only database connection, so it fits inside an existing security boundary without needing an exception written for it.
What does it cost to add a site later?
Adding a site changes the scale of the subscription, but the increase tapers as the estate grows rather than charging the single-site price again. We reprice the remaining annual term so the quotation reflects the sites you actually operate.