Legacy approach
- Hours of data cleaning before a single chart
- Rigid dashboards that can't model your portfolio
- Weather normalization in a spreadsheet, no regression
- Savings figures your finance team won't trust
- AI that guesses instead of computes
Ed is an agentic workspace for energy data analysis. Upload your meters, describe what you need to prove, and get weather-normalized, IPMVP-aligned results your CFO can actually audit.
7-day trial, full access. Cancel before day 7 - you pay nothing.
The problem
Every meter, vendor, and bill speaks its own dialect. Weeks go into cleaning data that should take hours. Then the savings report lands on the CFO's desk and the questions start. Where did that number come from? Can you prove the weather was different? Most teams can't answer. That's the problem Ed solves.
Legacy approach
With Ed
What is actually different
Most AI tools send your question to a model and hope the answer is close enough. Ed is built differently. Every important calculation is a real service - compiled code with a defined input, a defined output, and a traceable result. The AI decides what to call and explains what happened. The service does the math.
When Ed tells you your savings are 12.4%, it ran the regression. It did not estimate.
Regression, Degree Days, baseline scoring - all compiled services. Results include statistical quality metrics and the methodology used. Nothing is inferred from a language model's training data.
Degree Days calculated → regression run → results documentedEach workspace is isolated to your project. Your raw data is never used to train any model, never shared with third parties, and never leaves your boundary.
Your workspace only — never shared, never used for trainingHow a typical session works
You tell Ed what you need. Ed runs the right calculations, checks the results, and hands you something you can use.
Drop any CSV, XLSX, or PDF. Ed reads the structure, maps your columns, identifies the meter type, and confirms what it found before doing anything else.
Reads your files and maps columns automatically"Weather-normalize Building 7 against last year. Option B, Degree Days base 15.5°C." Ed selects the baseline period, explains the choice, and flags any data quality issues before proceeding.
Picks and validates your baseline periodDegree Days are computed for your exact location using the Degree Day Database. The regression runs against your actual consumption data. Statistical quality is checked against IPMVP thresholds automatically.
Local weather → Degree Days → regression → quality checkAdjusted baseline, verified savings, and statistical quality metrics — all saved to your workspace. You get a structured result you can hand to a client or a CFO without explaining how the number was produced.
Quality-checked report, ready to shareWhat you get
One workspace, connected to your data, the Degree Day Database, and the M&V methodology your clients expect.
Degree Days from your location. Proper OLS regression. Statistical quality reported. Savings adjusted for climate, not estimated from averages.
Multiple sites, multiple meters, multiple tenants. World-map overview, site-level drill-down, aggregate KPIs. Describe your structure in English - Ed sets it up.
CSV, XLSX, PDF bills, irregular intervals. Ed maps your columns, normalizes units, and builds clean daily and monthly layers. One upload, done.
Say "monthly kWh by site, last 24 months." A draggable, resizable widget appears - right data, right scale, right resolution. No configuration screens.
Global weather station network. Heating and cooling Degree Days for any location, any base temperature, any historical period. Fetched once, cached, available instantly.
IPMVP Option B output: adjusted baseline, reporting period, verified savings, statistical quality indicators, methodology documented. Numbers your finance team can sign off on.
Under the hood
Ed separates AI orchestration from computation deliberately. Methodology guides the decisions. Ed calls the right steps. Compiled services do the math. You see a traceable result.
Encodes M&V best practice. Tells Ed what constitutes a valid baseline, when to warn, and how to frame uncertainty. Judgment, not guesswork.
Baseline selection
Prefer full calendar years
Exclude structural breaks
Warn if less than 12 months of data Ed decides which calculations to run, passes structured inputs, and receives structured results. It orchestrates — it does not improvise the answer.
Select baseline period
Fetch weather for your location
Compute Degree Days
Run regression analysis Scores candidate periods, runs the regression, validates quality thresholds, and stores the result. Compiled code. Every number traces to your source data.
Score baseline candidates
Check statistical quality
Validate against IPMVP thresholds
Return structured, auditable results Built-in capabilities in Ed today
Jan
Founder - Energy data consultant - Mauritius
I built Ed because I kept doing the same manual work for real portfolios: weather normalization in spreadsheets, savings figures that fell apart under finance scrutiny, no good tool for the job.
Ed is the tool. But I'm still here. If you're on MAX, you get a monthly call with me directly. Bring your messiest dataset - that's what the call is for.
Connect on LinkedInPricing
Seven days, full access. Upload actual meter data and run a weather-normalized regression before you decide if Ed belongs in your workflow.
Trial
7 days, full Pro access
Pro
For active portfolios
MAX
For large portfolios
If Ed doesn't earn its place, cancel before day 7. You pay nothing. See full pricing and FAQ ->
Seven days, full access, real data. If the numbers don't hold up under scrutiny, you haven't paid anything.
No overage charges. Cancel any time.