The friction I couldn't ignore

I finished my civil engineering degree at UT Austin at age 19 and went straight into heavy civil construction: deep foundations, pipelines, and power plants. On a Samsung water-reclamation facility we drilled 3,967 ACIP piles, each 60–70 feet deep. On my next project I ran up to $60M+ of self-performed civil and concrete scope as a superintendent.

The work was world-class. The tools weren't. Quantities lived in spreadsheets, procurement ran on email and paper invoices, and schedules broke the moment the field changed. I kept watching great crews lose hours to bad software, or no software at all.

So I started building

Instead of complaining, I built the tools I needed on the job. A three-week "flow-map" scheduling system to coordinate across disciplines. A procurement tracker that kept 3,000+ engineered embeds and 550 tons of rebar landing on time.

They worked. We delivered critical scopes two weeks ahead of schedule on a $200M+ plant. That's when it clicked: the biggest leverage in construction wasn't more concrete. It was better software.

From hard hat to keyboard

So I taught myself to ship real products. I built LinkedResume, a full-stack platform sustaining 100 req/s at sub-200ms; ApolloSki, a MERN e-commerce store with Stripe checkout; and an iOS field calculator that saved foremen roughly an hour a day.

Why Build Plan

In 2025 I moved to San Francisco to build Build Plan full-time: AI-powered planning, procurement, and billing for contractors. It's the software I wish I'd had in the field. I know the problem because I lived it, and I can build the fix because I've already shipped it.