Proof

Real systems. Clear demonstrations.

Two systems Mitchell designed and shipped, plus professional-services demonstrations for intake and document triage. Longer build notes for shipped work are on the engineering journal.

Shipped · Sheet-first

Sheet-first coach tools

An installable hub for a football staff that already lived in Google Sheets. Check-in writes back to the same cells. Dashboards read a published CSV. The workbook stayed the database.

Problem: the sheet was right and the phone was not
Shipped: check-in, dashboards, practice timer, one home screen
Tradeoff: reads lag the sheet, and logic lives in two places

Open the studyarrow_forward

Shipped · Weekly reports

Weekly film reports

Receiver film logs stayed in a sheet. A pipeline grades the week file and publishes player PDFs, a staff summary, group film, and dashboards — including a second season on the same hub.

Problem: reports depended on a local script
Shipped: CSV in, grades and packets out
Tradeoff: the sheet’s columns are the contract

Open the studyarrow_forward

Demonstration · Professional services

Document triage with human approval

Inbound documents and emails draft structured fields into a review queue. A person approves exceptions before anything reaches accounting or the CRM.

Problem: every PDF is opened by hand
Would ship: triage queue with confidence thresholds
Tradeoff: the review queue is the product

Open the studyarrow_forward

Demonstration · Client intake

Inquiry to CRM follow-up

Website inquiry creates a CRM record with campaign attribution intact, opens a same-day follow-up task, and leaves the first reply to a person.

Problem: leads sit in an inbox for days
Would ship: form → CRM → task with UTMs
Tradeoff: custom mapping when native connectors fall short

Open the studyarrow_forward

calendar_monthDirect availability with Mitchell Dawkins II

Have a similar operational problem?

The fit call is a direct look at your workflow with the engineer who would build it.

Request a 20-minute fit call