Frequently Asked Questions

Product design and engineering for operational software that works but looks and feels dated: internal tools, clinical and back-office workflows, and multi-tenant platforms. The interface is usually where the problem shows, so the work starts there, but the same engineer designs it, builds it, and ships the API and data changes behind it. Most engagements take one of four shapes: modernizing a legacy interface, designing a complex workflow before it is built, healthcare workflow software specifically, or embedding as a fractional engineering lead.

Fixed fee for defined scope, quoted after a short paid audit or design sprint, and a flat monthly retainer for embedded work. No hourly billing. You know the cost before a phase starts, and you can stop after any phase with a working product.

No. Healthcare is where the deepest experience is, more than ten years across a health system and a national health company, and its constraints transfer well: multi-tenant theming, permissions, audit trails, accessibility, and users who cannot stop to learn a new screen. Work outside healthcare includes dealership operations tooling, an event-staffing platform, and years of small-business web applications. Any regulated or operational domain with the same shape is a fit.

Almost never. Modernization happens inside the existing codebase, surface by surface, behind flags or scoped styling. Framework changes are made only when they pay for themselves, and always incrementally.

Usually within two to four weeks for an audit or a design sprint. Retainer availability depends on current commitments. Ask, and you will get a straight answer.

You do, outright, on final payment: source code, design files, prototypes, and infrastructure configuration. Nothing is licensed back to you.

Cincinnati, Ohio, working remotely with teams across the US in Eastern time. On-site visits for kickoffs or workshops can be arranged.