About WyattGo

One senior engineer, seventeen years of client work, and a habit of redesigning the products people are stuck with.

Lucas Wyatt

Lucas is a senior software engineer and product designer who has been building web applications for clients since 2009. He started by running small-business engagements end to end, from discovery through delivery, then spent three years as a consulting engineer at Banner Health, where he helped implement the content management system behind the health system's public websites and built the accessible component library those sites shared.

From 2017 to 2025 he was a senior engineer at Optum, where he helped build the shared primitives library and microservices that several internal healthcare and pharmacy operations applications ran on. He was the link between business ideas and working software, shaped the user experience of the tools his teams shipped, and led the adoption of AI-assisted development in planning and delivery before it was standard practice.

Since 2025 he has worked independently: an event staffing platform built to take a business from spreadsheets and text messages to one system, dealership operations tooling on a React and Node stack, and the frontend of a multi-tenant virtual-care platform serving a national health system, where he designed and shipped the platform's first design system. That makes three organizations where he has built the shared component library the rest of the team works from.

The through-line is the same in every engagement: operational software that works but looks and feels like it was built fifteen years ago, and a team that cannot stop the business long enough to rewrite it. Lucas designs the new experience with the people who use it, builds a design language the team can keep, and ships the change incrementally inside the existing codebase.

He lives in Cincinnati and works remotely with teams across the US in Eastern time.

How the work runs

Design delivered as working code. Mockups are built in the browser with real states and your tokens, and they become the reference the build is checked against. Nothing is handed off as a picture.

Whole stack, one pair of hands. Design, frontend, API, data, and deployment are handled by the same engineer, so nothing stalls in a handoff between a designer, a frontend team, and a backend team, and every decision is made by someone who has to live with it in code.

Modernize without a rewrite. New surfaces ship behind flags or scoped styling inside the running application. Users see improvement in weeks, and the old screens retire when their replacements have earned it.

Accessible by default. Keyboard paths, contrast, focus, and screen-reader behavior are design requirements checked in review, not a remediation project, a habit from building WCAG-compliant applications for a health system since 2014.

One home for every piece of data. Every field on a screen is vetted against where it is actually stored. Noise is reduced; the look is not.

Plan first, then execute. Non-trivial work gets a written plan, a decision log, and a review before code, so decisions stay made and nobody re-derives them next quarter.

You own everything. Source code, design files, prototypes, and infrastructure configuration are yours outright on final payment.

Tools and pace

Claude Code and multi-agent workflows are part of daily work: codebase research, planning, verification, and review. This is not new territory. Lucas brought GitHub Copilot into planning and development on his team at Optum before AI-assisted work was common, and the habits carried over: a written plan before code, a decision log, and verification against the real codebase. It is how a one-person practice keeps pace with a team without cutting corners, and it is why the plans and briefs that come out of a design sprint are anchored to your actual code rather than to assumptions. Teams that want the same workflow get taught it as part of the engagement.