← Nuanced Design Flux Energy Next: Atlas Freight →

Case Study · 01 · Enterprise SaaS

Flux Energy

An operating system for wind power — telemetry, maintenance, and money in one place.

  • RoleProduct Design · Full-Stack Engineering
  • SectorRenewable Energy / Wind
  • Year2026
  • Livefluxenergy.app
The Flux Energy operations platform
$1B+in wind assets managed on the platform
6 → 1point tools consolidated into a single pane of glass
Liveturbine telemetry, work orders, and portfolio finance

OverviewOne platform for the whole wind farm

Flux Energy is an enterprise SaaS operating system for wind power operators managing more than $1B in assets. It brings the three worlds an operator lives in — machine health, field maintenance, and portfolio finance — into one coherent product.

Before Flux, that picture was scattered across SCADA exports, spreadsheet trackers, a legacy CMMS, and accounting software that never agreed with any of them.

The ProblemSix tools, zero shared truth

Wind operations teams burn hours stitching together turbine telemetry, technician schedules, and asset-level P&L. When a gearbox starts vibrating at 2 a.m., the alert, the work order, the parts inventory, and the revenue impact all live in different systems — and downtime is measured in thousands of dollars per hour.

The brief: design a system an operations director trusts at a glance, a field tech can drive from a truck, and a CFO can pull numbers from without asking anyone.

My RoleDesign and build, end to end

I owned the product end to end: research with operations teams, information architecture, the design system, and the full-stack build. Designing in the same codebase the product ships from kept the distance between a Figma idea and a deployed screen close to zero.

ProcessFrom control room to component library

  • Shadow the operators

    Sat with ops directors and field techs to map a day of real decisions — what they check first, what they ignore, and where the spreadsheets hide.

  • Model the domain

    Built a shared vocabulary — sites, turbines, alerts, work orders, contracts — so the data model and the navigation are the same mental map.

  • Design the system

    A dense-but-calm UI language: dark control-room surfaces, tabular numerals, status color used only for status. Every component built for live data first, empty states second.

  • Ship and iterate

    Weekly releases against real turbine feeds. The dashboard you see today is the boring survivor of a dozen louder drafts.

Key ScreensThe single pane of glass

F Fleet Overview High Plains · 3 sites · 142 turbines All systems nominal FLEET AVAILABILITY 97.2% ▲ 0.8% vs last 30 days OUTPUT NOW 412 MW wind 11.4 m/s avg OPEN ALERTS 14 3 high priority REVENUE MTD $8.2M 102% of forecast Power output — 24h 00:0012:0024:00 Turbines needing attention WTG-117 · Gearbox vibration High Plains North · alert 02:14 · WO drafted WTG-042 · Pitch motor temp Mesa Ridge · trending 6h · watch WTG-088 · Yaw misalignment Mesa Ridge · 1.2% energy loss est. WTG-009 · Service complete High Plains North · back online 14:40 View all 142 turbines
Fleet overview. Availability, live output, alerts, and revenue share one screen — status color is reserved for status, so amber means something.
HIGH PRIORITY WO-2381 · Gearbox vibration — WTG-117 Opened automatically from alert FLX-90412 · High Plains North Confirm vibration signature against SCADA history Reserve crane window & lockout-tagout plan Replace planetary bearing — part #GB-P114 (in stock, Bay 3) Post-service vibration baseline & sign-off Dispatch crew Impact if deferred $3,400/day estimated revenue at risk Assigned crew MR JT Rodriguez & Tran · ETA 06:30 Vibration trend — 14 days alert threshold crossed Feb 12
Work orders that know what they cost. Every maintenance task carries its revenue impact, parts availability, and crew logistics — the 2 a.m. alert arrives pre-triaged.

OutcomeThe control room, consolidated

Flux now runs the daily operating rhythm for portfolios totaling over $1B in wind assets. Six disconnected tools became one product: the morning fleet check, the maintenance queue, and the monthly investor numbers all read from the same source of truth.

The measure of an enterprise tool isn’t how impressive it looks in a demo — it’s whether the operations director still trusts it at 2 a.m.
Next case study Atlas Freight