SERVICES / 2026

Complicated data, made explorable.

I build interactive data visualizations for technical domains: energy, climate, infrastructure, anything with a real model underneath. The work starts where a static chart stops being enough. It usually ends with something people can poke at themselves.

THE ENGAGEMENT

The data pilot

2 to 3 weeks starting at $5,000

2 to 3 weeks

One dataset, one audience, one question worth answering. You end up with a working interactive piece you can put in front of people, not a deck about one.

The most recent one is a model of the entire U.S. energy system: three decades of history, a forecast out to 2050, and backtests that land within about 18% at six years out. Every input carries its source, how reliable it is, and the date it was last checked. A number you can't trace is a number nobody has to believe.

WHAT YOU GET

  • A working visualization, deployed and linkable, with every number traceable
  • The code, and a written note on how to update it
  • One revision round after you've shown it to real people, which is the round that actually matters

A GOOD FIT IF

  • Your data is dense enough that a static chart hides more than it shows
  • You need to persuade someone smart and busy and skeptical
  • There's a model underneath rather than just a table

Larger builds start the same way. The pilot is how we both find out whether this works before either of us commits to more.

Start with a call

HOW IT GOES

No mystery about the process

01

A call

Thirty minutes. You describe the problem and I ask about the data. No deck.

02

A written scope

Fixed price, fixed dates, and a list of what isn't included. You approve it before I start.

03

Build in the open

You see progress every few days. Steering is cheap early and expensive late.

04

Handoff

The running thing, the code, and enough documentation that you aren't dependent on me.

ALSO IN THE TOOLKIT

Data work is what I lead with

It isn't all I do, and projects rarely stay in one lane. If your idea spans a few of these, that's usually a good sign we should talk.

Rapid prototyping

Concept to physical part with CAD, 3D printing, and as many iterations as it takes.

IoT & smart devices

Connected devices meant to be repaired rather than sealed, running embedded firmware inside custom enclosures.

Workflow automation

Workflows, integrations, and pipelines that hand the repetitive work to a machine and then run themselves.

FAQ

Your questions

What if my data is a mess?

That's normal, and part of the work. Getting to a number you can defend is usually most of the effort. I'll also tell you early if the data can't support the claim you want to make. Better to hear that in week one than after you've paid for a chart that says it anyway.

How do you price?

Fixed price per engagement, agreed in writing before I start. No hourly billing and no surprise invoices. If the scope changes mid-project, we agree the change first.

How long does it take?

The pilot runs two to three weeks, and larger builds run four to ten. You get real dates in the scope, not a range that quietly drifts.

Can you work from a rough idea?

Yes. Some of my best projects started as a sketch and a hunch. If you can describe what you want someone to walk away understanding, that's enough to start.

Who do you work with?

Startups, research teams, and independent makers. I do my best work with small teams where I can talk directly to the person who knows the data.

Not sure it's a fit? Ask anyway.

Get in touch