Services

Three practice areas, one engineer. Every engagement below is scoped in writing before any code is written.

Custom software development

I take on systems where the rules are complicated and the cost of a wrong answer is high. That usually means financial technology, tax software, or an internal process that has outgrown the spreadsheet it lives in.

Work typically starts with a fixed-scope discovery: I read the code and the process, then hand you a written plan with risks called out. From there it runs in milestones with working software at each one.

Typical engagements

A filing or calculation engine that has to match a specification exactly.
A reporting layer that reconciles several upstream systems.
An internal tool replacing manual work that breaks every quarter end.
An integration between systems that were never meant to talk.
Rescue work on a codebase that lost its original author.

Engagement shapes

Discovery: One to two weeks
Build: Monthly, milestone by milestone
Ongoing: Retainer for support and changes

AI consulting

The useful question is not which model to use. It is whether the task can be made reliable enough to depend on, and what it should do when it cannot. I answer that with measurements rather than opinions.

I do not sell access to a model or a platform. I build the surrounding system that makes a model safe to put in front of real work.

What that looks like

A workflow review that ends in a written recommendation, including "do not use a model here".
Document extraction where every field has a confidence score and a review path.
Retrieval over your own documents, with citations back to the source.
An evaluation suite that catches regressions before your users do.
Cost and latency budgets, with a defined fallback when a provider is down or slow.

What I will not do

Promise accuracy numbers before measuring anything.
Put a model in a decision path that has no human review.
Build a chatbot when a form solves the problem.

Entertainment development

Games are a different set of constraints with the same engineering underneath: hard frame budgets, state that changes sixty times a second, and players who will find every edge case you left in.

What I take on

Gameplay and systems programming.
Tools and pipelines for teams of one to ten.
Prototypes built to answer a single design question.
Performance work on a build that has stopped keeping up.
Technical review of a design document before it becomes code.

Also available

Brand and interface work for games, including title art, loading screens, and store assets, using a mark designed to hold up at every size.