Why We Build

With nine months partnering directly with EdTech nonprofits, agentic coding tools have fundamentally changed the speed I can work at. The deeper shift is everything downstream of that acceleration — how it changes why we build in the first place.

The Three Familiar Buckets

For most of my career, almost everything I built fell into three buckets:

Build to Build: The core work to build products and production systems (80%).

Build to Validate: Technical spikes to validate approaches or rapid prototypes to show customers (15%).

Build to Learn: Learning new technologies and refining my skills (5%).

These are still relevant as always, but when I can build something in hours that used to take weeks, building stops being just execution. It becomes a thinking tool.

A New Landscape of Reasons to Build

Working with partners, I've found there's a whole new landscape of reasons to build that go way beyond shipping.

Build to Experience: When the vision is clear but not yet shared. I build so stakeholders can feel what they've only been hearing about. It turns "imagine if..." into "try this."

Build to React: When nobody's sure what they think yet. I build something real not to confirm a direction but to discover one. It's building as a way to get unstuck.

Build to Explore: When there are too many directions to reason through in the abstract. I build multiple paths quickly to find what's possible before committing.

Build to Scope: When the complexity is hidden. I build a rough version specifically to surface the edge cases and questions I'd never find in a planning doc. The build is the discovery.

Build to Reveal: When data or models are opaque. I create a thin interface to make what's already there visible.

Build to Accelerate: When the process is the bottleneck. I build tools that make the rest of the work faster - sometimes for partners, sometimes just for me. Small investments that compound quickly.

Build to Explain: When the idea is complex. I turn it into an interactive artifact that makes it click. Letting the idea speak for itself.

Build to Persuade: When the idea needs to be felt, not explained. I build something that brings people to the same page faster than any conversation could.

Build to Set a Bar: When I want to quietly change expectations. A working artifact recalibrates what "possible this quarter" means before anyone has to argue about it.

Build to Push Boundaries: When I want to know what's actually possible. I build something ambitious just to see where it breaks. Stress-testing the ceiling of current tools.

This list is still growing. Every new partner reveals more reasons to build and more moments where a working artifact unlocks something a slide deck never could. If you've found reasons I'm missing, tell me. And if you're reading this and thinking "we need someone doing this with us", let's connect.