Skip to content

Independent software studio · Metro Detroit, Michigan

Software that ships. Built by the person you talk to.

Applications, websites and AI automation — one engineer, start to finish, with a shipping product to show for it rather than a portfolio of mockups.

Start a projectSee the work
Windows
desktop application
10
forecast models, ensemble-routed
250 nm
offshore, by the person who wrote it
SailTac — real screen, real racePort Huron → Mackinac · 250 nm
SailTac's routing screen: a nautical chart of Lake Huron with a race route colored by forecast confidence.

What I do

Three things, done properly.

Enough range to build a whole product, narrow enough that none of it is a stretch.

01App developmentDesktop and mobile applications that hold up when the network doesn't.
02Web developmentFast, accessible sites and web apps — including the commerce behind them.
03AI automationPut a model where the tedious work is — and keep a human on the decisions.

Proof of work

SailTac — a real product, not a case study written backwards.

Offshore sailboat racing instruments, multi-model weather routing and an automated post-race debrief. It is a Windows desktop application with its own installer, licensing, self-updating release channel and commerce site — all of it built here.

It also gets used in anger. Its author races the boat it was written for. Software that has to work when you are out of cell range at 3am teaches a different standard than software that has to work in a demo.

Real-time instruments
Boat data off the network, rendered live on every device aboard.
Ten weather models
Routed as an ensemble, then graded against what actually happened.
Automated debrief
Every second logged, turned into a report the crew actually reads.
The whole delivery chain
Installer, offline licensing, signed delta updates, checkout.
Read the case studyVisit sailtacperformance.com →
SailTac's live instrument dashboard: boat speed, heading, wind speed and angle in large numerals.

How this is different

A studio of one, on purpose.

You talk to the person building it

No account manager, no handoff to a team you never meet, no requirements lost in translation. The engineer who scopes the work is the engineer who writes it.

Shipped, not demoed

A prototype proves an idea. An installer that works on a stranger's machine, a payment that clears, and an update channel prove a product. The work isn't done until it's in someone's hands.

You own it afterwards

Source, build pipeline, domains, hosting and accounts are all in your name. If we stop working together, nothing stops working.

How it works

Four steps, no surprises.

  1. 1

    A conversation, free

    Half an hour on what you're trying to do. If it's not something I should build, I'll say so and point you somewhere better.

  2. 2

    A written scope and a fixed price

    What's included, what isn't, what it costs and when it lands — before any code exists. No hourly meter running in the background.

  3. 3

    Build in the open

    You see working software early and often, not a status report. Direction changes are cheaper the sooner they happen.

  4. 4

    Handover, then support

    You get the code, the deployment and the documentation. Ongoing support is a separate, optional arrangement — never a lock-in.