freelance and contract · dallas-fort worth and remote
bring me the problem. I run the shop that fixes it.
if it is software, I build it. if it is sound, I set it up or run it live. if it is photo, it goes to my studio. all three are mine, so you are talking to the person who does the work.
available taking one new project in august
- in production at CBRE
- top 5 of 300+ teams, CBRE Innovate 2026
software
the work that should take one click still takes a spreadsheet and an afternoon.
I read every message myself, and I usually reply within a day or two.
a tool your team opens on a monday with the manual step gone for good, not a prototype that dies after the demo.
I sit with the people who will live with it before I draw a screen, then work in the open with regular demos and the decisions written down. AI goes in as a tool with human review and test gates, never as an authority.
internal tools and dashboards
the number your team rebuilds by hand every week becomes a page that is already correct when they open it.
see where this shippedwebsites and web apps
one place to run the week, wired into the drive, inbox, and calendar you already use, instead of five tabs and a group chat.
see where this shippedAI and LLM automations
the reading, sorting, and drafting that eats an afternoon runs on its own, and every answer shows its work so you can check it.
see where this shippeddata cleanup and reporting
the messy export becomes a clean table and a report that arrives on schedule without anyone touching it.
every one of these started the same way. someone was doing it by hand, and I sat with them until I understood why before I wrote anything.
live sound
the room sounds different every week and nobody can say what changed.
I read every message myself, and I usually reply within a day or two.
a rig the volunteer on shift can run without you, tuned with measurements instead of by ear, and a record of every change so last week is repeatable.
I play in these rooms and I sit behind the console, so the fix has to survive a volunteer rota and a soundcheck that starts late, not just a demo.
build and install the system
I spec the rig and the console, tune the room, set the scenes, and hand it over with the settings written down so it still works after I leave.
see where this shippedrun the room live
I am at the desk for the event mixing front of house, so whoever usually gets pulled into the booth can be at the event instead.
sound aviator exists because a volunteer team could not answer a simple question about their own console, and I was in the room when they asked it.
photo and video
the day happens once, and the footage is only as good as who was ready for it.
I read every message myself, and I usually reply within a day or two.
a set of images and a cut that feel like being in the room, not a folder of raw files and a promise to get to it.
MQ Pro Studio is my studio. booking photo through me books my own team, and I am on set running camera and light, then in the edit setting color.
event coverage
weddings, services, conferences, and performances, covered by a team that walked the shot list with you before the day started.
sessions
portraits, headshots, and product, shot in a session booked around you.
events do not do a second take, so the whole job is being ready before the moment lands.
proof
where this has already worked
four builds, and the numbers each one earned.
GSST
sourcing ran on a vendor tool the business could not bend to its own workflows.
I owned a feature area end to end on the replacement, from the early design discussions through to production. the whole organization moved across and kept every step it relied on.
2,000+users moved off Zycus0workflows lost in the moveP&L Advisor
finance leaders needed answers out of P&L data on their own schedule, and every answer had to respect who is allowed to see which numbers.
as primary engineer I built an agent that plans, queries, and explains itself, with every SQL statement validated before it runs on top of row-level security. it answers questions that used to wait in an analyst queue.
86%of the codebase, primary engineerSVPhighest level of daily usersCD Sync
an 11-person music ministry ran every service across five scattered tools, so schedules, songs, and files lived everywhere and nowhere.
one platform, built solo, with their own Google Drive and Gmail wired in so they kept the tools they already trusted.
5 → 1tools consolidated11people it serves weeklySound Aviator
a volunteer sound team could not say who changed what on the mixer, setup before a service was slow, and the room got tuned by ear.
remote console control, a real-time audit of every fader, EQ, and scene change, and a room analyzer that sets up at a new venue in minutes.
$90total hardware, no cloudeveryfader move logged, with who and when<5 minto set up room analysis at a new venue
the process
how working together goes
the part most people want to know before they email a stranger.
how we start
a free call, about twenty minutes. you describe the problem, I ask questions, and I tell you straight whether this is a thing I should build. if it is not, I will say so on that call.
the first two weeks
you get something you can click, plus a written list of what is in scope and what is not. we work in the open with regular demos and the decisions written down, so you are never waiting to find out how it is going.
how pricing works
work with a clear edge gets a fixed price. open-ended work is hourly. either way you get the number before I start, and it does not move unless the scope does.
who owns the code
you do. it ships in your repository with the credentials in your own accounts, so nothing I built is stuck behind me still being around.
tell me what you need done
this goes straight to me, not to an inbox someone else reads.
available
taking one new project in august
Dallas-Fort Worth