Senior Solutions Architect at Perficient
Frontend architecture / Design systems / AI-assisted development, on a .NET and SQL Server background
I am a Senior Solutions Architect at Perficient. I lead frontend architecture and AI development for my business unit, across engagements in grocery, healthcare, insurance, energy and manufacturing. My background spans .NET and SQL Server, React and TypeScript, design systems and development team leadership. I have written both ends of nearly everything I have shipped.
Selected work
For a global commercial vehicle manufacturer, I built a digital platform in Next.js, React and TypeScript through a corporate rebrand. For a national healthcare provider, I built the frontend infrastructure, including the build and deployment pipelines, testing strategy and monitoring.
At a national grocery chain, I led the central team that built and ran the design system, then led the corporate site rewrite onto it. On the same property I co-led the order-ahead commerce team of twelve developers and worked on the dedicated performance team.
Before Perficient, I was the UI lead for the Medicare and Medigap online sales teams at Priority Health, working on shopping, quoting and enrollment applications under HIPAA throughout.
At 2G TechWorks I co-owned the company and ran engineering for twelve years, with a development team that grew to eight. I built the multi-tenant .NET platform behind more than 100 client sites and served as the primary SQL Server DBA, including tuning, maintenance and backups.
Design systems
I led the small central team that built the design language and component library from scratch on atomic design principles and rolled it out to the consuming product teams, among them commerce, savings, operations and marketing. Our team owned and ran the system and the product teams built on it. It started in vanilla JavaScript and CSS, the component layer later moved onto Vue, and I led the corporate site rewrite on it.
In 2026 I built a design system from atomic components through to the renderings for the utility's public site and customer self-service platform, which are built in Next.js on Vercel.
FORGE has its own design system, Anvil, with eighteen components, each with stories and tests, and one theme. FORGE also includes a token generator that outputs CSS, SCSS, TypeScript, W3C JSON and Tailwind formats.
Recent example
I conceived FORGE and wrote the overwhelming majority of it over about fourteen months. It is a TypeScript and Node monorepo covering agentic code generation from a Figma selection to typed React with unit tests and Storybook stories, a legacy site migration engine that is still being built, one MCP server, and Anvil, its design system. I designed every FORGE screen myself.
FORGE is hosted in Azure at Perficient, in use by many people and demoed live, including by me at the Perficient booth at Sitecore Symposium 2025. Code generation runs on Claude through Perficient's AI gateway: an Opus coordinator, Haiku writing the files and a separate Sonnet review, with write tools hidden until a person approves the plan and a person approving each refine round.
On a Fortune 500 energy utility engagement I used FORGE to create some of the components, and the engagement's two business analysts used it for user stories and requirements. A second engagement is starting.
Recent example
On my current engagement at Perficient, I wrote most of sixteen agentic skills for Claude covering planning, component development, review and release work. Leadership asked for a common repository as the business unit's source of truth, mine went in first, four or more teams now pull them into new projects, and our team still runs on them every day.
On my current engagement at Perficient, I wrote most of a library of sixteen agentic skills for Claude that covers the delivery workflow. They plan and estimate work from Azure DevOps and Figma, build components, review code, prepare pull requests, document the work and support releases. I also built one MCP server covering Sitecore and Azure DevOps, so a session loads only the tools it needs instead of everything the two default servers expose.
About a third of the skills exist so a person can check the work. One stands up a real page with the rendering in place, and another drives the Sitecore editor to check the authoring experience. The PR review skill grades each acceptance criterion as met, partial, not met or untestable, checks for accessibility regressions and never approves a PR itself.
Leadership asked for a common repository as the business unit's source of truth. My skills went in first, four or more teams now pull them into new projects, and our team still runs on them every day.
I also wrote the skills that run FORGE's backlog through parallel Claude Code agents in Orca, Stably's open-source orchestrator. Each issue gets its own worktree and builds to a pull request through adversarial review, and no agent merges anything; I review before it is squashed.
This work is part of rebuilding an energy utility's public site and customer self-service platform.
Workflow coverage
Azure DevOps + Figma
One MCP server + React
Rendered page + Sitecore
Selected skills
plan-workbuild-componentcreate-demo-pagecode-reviewsitecore-pagesverify-work 2020 to present
Senior Technical Consultant to Senior Solutions Architect
Frontend architecture and AI development for the business unit, with remote teams across the country. Career concierge, Perficient's career-manager role, for up to four developers from 2021 to 2025.
2019 to 2020
Senior Software Engineer
Dealership management software on .NET.
2015 to 2019
Lead Application Development Analyst
UI lead for the Medicare and Medigap online sales teams at Priority Health.
2014 to present
Owner
Software hosting and support, alongside full-time employment, and building Draw Your Thoughts, a woodworking-plan product with AI-assisted generation, as its only developer.
2002 to 2014
Co-owner and head of software development
Built a multi-tenant .NET content platform serving more than 100 client sites, and was the production DBA.
About this site
Run Lighthouse, navigate with the keyboard and check the page at 400% zoom. The build records its asset sizes, and the test page explains the implementation and the checks that need a person.
Inspect the build and testing detailsFor an interactive product, visit gameca.st, a site I co-own. The measurements here describe this personal site.