Skip to content

Services

Three ways to work together. Most people start with the audit.

Fixed prices where the scope is known. A monthly retainer where it isn't. You own everything I build.

01 · Start here

Ops & AI Audit

$3,500fixed, two weeks

Two weeks. I map how the business runs, put an hours and dollars figure on where time and money leak, and tell you which fixes pay for themselves. The full fee comes off a build that starts within 60 days.

  • Kickoff call and read-only access to the tools you use
  • Up to two days watching the work, on site in Dallas-Fort Worth or by screen share
  • Map of your three to five busiest workflows
  • Inventory of software, data, devices, and who can see what
  • Bottlenecks measured in hours and dollars per month
  • Where AI fits and where it does not
  • Ranked fixes with build cost, payback, and risk
  • Written report and a one-hour walk-through. Yours to keep, even if you build with someone else
Book a call
02 · Then

Build

Askscoped per project

The fixes from the audit, shipped in small releases. Fixed scope and price per release, so nothing open-ended.

  • Web and Android apps
  • Device and network setup
  • AI assistants with real permissions
  • Integrations with what you already use
Book a call
03 · Ongoing

Run

Askmonthly retainer

I keep it working. Monitoring, fixes, updates, and a set number of hours for changes each month.

  • Uptime and error monitoring
  • Security and dependency updates
  • Monthly change hours
  • Direct line to me
Book a call

What each step looks like

Audit. Build. Run.

Each step ends with something you keep. You can stop after any of them.

01

Audit

I watch how the work gets done, read the data you already have, and write down what is worth fixing and what is not. Fixed price.

  • Process walk-through on site or on a call
  • Data and systems inventory
  • Written plan with costs and risks
02

Build

Small releases into real use, starting with the job that hurts most. You see it working in weeks, not at the end.

  • Web, Android, devices, and AI
  • Tested against your real data
  • Your accounts, your code
03

Run

Software needs someone to keep it working. I monitor it, fix it, and keep improving it on a monthly retainer.

  • Monitoring and alerts
  • Updates and fixes
  • A monthly change budget

What I build

The pieces, and where they show up.

Every capability links to a system in daily use.

Web and Android apps

Staff consoles, crew apps, public sites, and tablet tools. Built on Next.js and Convex, shipped to Android through Capacitor.

See the case

AI assistants with permissions

Assistants that answer to roles. Tools filtered by who is asking, every important action approved by a person.

See the case

Device fleets

Phones, tablets, and TV boxes enrolled, locked down by role, and updated through a canary.

See the case

Networks and phones

Wi-Fi across buildings, point-to-point links between sites, and a phone tree staff can edit.

See the case

Data you can trust

Paper, scans, and old databases turned into clean records. Read-only access when the source system can't be touched.

See the case

Bookkeeping cleanup

Reconstructing books, cost basis, and depreciation from source documents until the numbers hold up.

See the case

What I don't do: stamped design work, or anything else the law reserves for a licensed professional engineer. If your project needs one, I'll say so on the first call.

Questions

What people ask before they call.

Something else on your mind? Ask it on the call.

Book a call
Our data is a mess. Is that a problem?
No. Most of the projects on this site started with paper, spreadsheets, and scanned pages. One started with 66 scanned escrow pages and ended with 1,970 clean rows. Cleaning the data is usually the first release.
We tried AI and it didn't work. Why would this be different?
Usually the AI had access to everything and no rules, or access to nothing useful. I give an assistant a narrow job, the tools for that job, and permissions that follow the person asking. Every action that matters waits for a person to approve it.
What happens after launch?
You pick. I hand over the code, the accounts, and the docs, or I keep running it on a monthly retainer. Either way you are not locked in.
Are you a licensed PE?
I have a B.S. in Mechanical Engineering from the University of South Carolina and worked in facility operations at ExxonMobil's corporate headquarters. I'm not a licensed professional engineer and don't take work that requires one. Licensure is a goal.
Who owns the code?
You do. It lives in your accounts, under your name. I build on common tools so another developer can pick it up.
Do you only work with land and hospitality?
No. That is where most of the examples come from because it is where I run a business. The same patterns fit any operation with people, buildings, vehicles, devices, and paperwork.

Next step

Start with a 30-minute call.

A 30-minute call. You describe the problem, I tell you straight whether it's worth fixing and roughly what it costs.

Book a call