Kuhlman.co

Building things
that work.

Product and engineering for teams whose problems outgrew the tools they started with. Fewer moving parts, shipped sooner.

Years shipping
12+
Projects delivered
40+
Industries
6
Referral rate
100%

Selected work

Systems that earn their keep.

Platform

Orbit

A scheduling and dispatch platform that replaced four spreadsheets and a whiteboard. Cut planning time from a full day to under an hour.

Data

Signal

Ingest and reconciliation for a finance team drowning in exports. Every number now traces back to the row it came from.

Interface

Atlas

An internal console used daily by operations. Built to be fast, boring, and learnable in an afternoon.

Approach

Three steps, no surprises.

  1. 01

    Understand the system

    Before anything gets built, the constraints get written down: who does what today, what breaks, and what the deadline is really attached to.

  2. 02

    Ship the thin slice

    The smallest version that touches every layer, in production, early. It surfaces the wrong assumptions while they are still cheap.

  3. 03

    Harden and hand off

    Tests, docs, and a runbook. The work should keep running long after the engagement ends, without a phone call.

About

Ethan Kuhlman.

I build software for teams that have outgrown the spreadsheet and are not ready for the enterprise suite. Most of that work lives in the unglamorous middle: data models, integrations, and the internal tools nobody puts on a landing page.

The through-line is the same everywhere. Understand the system as it actually runs, remove the parts that do not need to exist, and leave behind something the team can maintain without me.

Questions

The usual ones.

What kind of work do you take on?

Product and platform work where the hard part is the system, not the screen: architecture, data models, internal tooling, and the interfaces that sit on top of them.

Do you work solo or with a team?

Both. Solo for discovery, prototypes, and tightly scoped builds. Embedded with an existing team when the work needs to outlive the engagement.

What does a typical engagement look like?

A short paid discovery to agree on scope and risk, then two-week increments with something demoable at the end of each one. No six-month reveals.

How do we start?

Send a paragraph about the problem and the deadline attached to it. If it is a fit, you get a scope and a number within a week.

Contact

Let's talk.

A paragraph about the problem and the date it needs to be solved by is enough to start.