WorkAboutAfter Hours
← Back to work
Design Engineering

Runwise Growth Tools

Three live tools on runwise.com, designed, AI-coded, shipped, and instrumented end to end by one designer (me). Each exists to do the same job: turn Runwise's data into a sales conversation.

Role
Lead Product Designer
Contribution
Product strategy, UX and interaction design, copywriting, front-end build with AI coding agents, PostHog instrumentation, live iteration
Live
The Challenge

Good ideas were waiting in line

Runwise's growth ideas had a bottleneck: every new marketing or sales surface needed an engineering ticket, a sprint slot, and a wait. Ideas that couldn't justify a sprint didn't ship at all.

Meanwhile, the sales team's hardest problem was starting conversations. Prospects couldn't picture Runwise's footprint in their own neighborhood, and reps couldn't show a building its water waste without first getting its usage data. Design could solve both, but not from inside a sprint queue.

The Approach

Design straight into production

I collapsed the handoff. Pairing with AI coding agents (Claude Code is my daily driver), I design and build these surfaces directly in production code, instrument them with PostHog, and iterate on live behavior instead of static mockups. The design decisions are the same ones I'd make in Figma. The difference is the deliverable: not a handoff file, a shipped tool. Everything below is live on runwise.com right now.

The DEP Tool

A funnel that earns trust before it asks

To show a building its potential savings, Runwise first needs its DEP water data, and getting that means asking a prospect to share access to an account they treat like a utility login. The design problem isn't layout, it's anxiety. I built the six-step funnel around progressive disclosure: one decision per screen, read-only permissions spelled out before any credential is touched, and a 90-second promise up front that the flow actually keeps.

148
Unique visitors since late June
6 steps
One decision per screen
The Map Tool

Proof of density, on a map

Every prospect quietly asks the same question: who else is doing this? The map answers it in one interaction. Enter an address, set a radius, and see every Runwise building around it, drawn from a network of 10,000+ buildings. It turns an abstract claim into something a rep can show on a screen in the first minute of a pitch.

This is the kind of interactive, data-backed surface that usually requires an engineering team. It shipped without one, and it found an audience beyond the sales floor when it was picked up and shared on LinkedIn.

441
Views since March
146
Unique visitors
The Elevate Page

A conference site against a date that couldn't move

Elevate is Runwise's industry event: seven speakers, a customer panel, a CNBC correspondent, and an event date that did not negotiate. The full site (agenda timeline, speaker profiles, venue gallery) had to be live in time for the invite push, and the sprint path couldn't hit the date. This pipeline could.

It shipped on time and reached 69 unique visitors in the event month, which for an invite-only industry event is meaningful reach into exactly the right room: building operators, real estate executives, and investors.

On time
Against a fixed event date
69
Unique visitors in event month
The Impact

Design as a revenue lever

Together, these tools changed what design means at Runwise. Marketing and sales experiments now ship in days instead of sprints. Ideas that couldn't justify engineering time get to exist. And design stopped waiting at the end of the pipeline and started feeding it: these surfaces have reached 360+ unique visitors and influenced $76K+ in pipeline for the sales team.

The pattern keeps compounding. Internal reporting tools, customer story pages, and event sites at Runwise now ship the same way.

$76K+
Pipeline influenced
360+
Unique visitors across tools