I ran the cement jobs.
Then I shipped the software.

Seven years supervising oilfield cementing for Halliburton, NexTier, and Compass — then I taught myself to build. Now there's a 5.0★ app live on the App Store, a document-automation platform running daily inside a law firm, and more on the bench. I build software for people who work in the field, because I was one.

App Store — Cementing Engineer LinkedIn Email me

Cementing Engineer app — job design screen — Job design

Cementing Engineer app — calculator screen — Live calculator

Cementing Engineer app — well schematic screen — Well schematic

Cementing Engineer app — derived results screen — Derived results

Cementing Engineer app — tally book screen — Tally book

Ship log

Every product below exists and ran for real users — logged in build order.

No. 01 2021 – 2022 Internal build

Cement Engineering Application

Independent builder — built while working the field at Halliburton

My first real product: a cement-engineering application for web, iOS, and Android, written nights and days off while I was still supervising jobs. I wrote the calculation logic and fluid-dynamics equations myself, straight from field experience.

6 → 2 A Texas district workflow that took six engineers ran with two, on faster and more consistent job calculations.

Platforms: Web · iOS · Android
Core: Calculation engine
Lesson: Ship for your own crew first

No. 02 2025 – Present Live — App Store

Cementing Engineer

Founder — design, code, pricing, releases, support

A field calculator for oilfield cementing, built by a cementer for cementers. Live job calculations, a live well schematic, a digital tally book, and full offline use at the wellsite. Freemium with Pro subscriptions and free trials; I repositioned it from a hard paywall to freemium based on adoption data.

Status: Live on the App Store
Rating: ★ 5.0
Platforms: Web · iOS · Android
Model: Freemium + Pro subs

Download on the
App Store

No. 03 2026 – Present In production — daily use

Legal Document Automation Platform

Builder & client success lead — for a working law firm client confidential

A law firm runs its case intake on software I built. I sat with the attorneys to map their process, then turned intake data into court-ready filings across four document types — discovery, iterative releases, deployment, adoption audits, and live support, all run solo. No screenshots here: the client's casework stays private.

Case intake

──▶

Notices

Default filings

Judgment packets

Findings & conclusions

Status: In production
Client: Law firm (confidential)
Output: Court-ready filings
Scope: Discovery → support

No. 04 2025 – Present In development

Chirp

Founder — bird identification app

A consumer product structured around a large species dataset — taxonomy architecture deliberately separated from UX decisions so the product can scale without rework. In active development.

Why it works

The unfair advantage isn't the code.

I was the user

Seven years on location running the exact workflows my software now handles. I don't guess what the field needs — I've stood in it at 3 a.m.

I was the customer

I've been on the buying side of oilfield tools and services. I know how field crews evaluate, adopt, and quietly abandon software.

I ship the whole loop

Discovery, requirements, UX, code, app-store releases, pricing, support. Every product here was one person, end to end.

I ran the cement jobs.Then I shipped the software.