Working Modes
Operator mindset. Builder speed.
- AI systems with rollout, guardrails, and adoption plans
- Full-stack products built around real workflows
- Infrastructure, security, and reliability pulled into the design process early
01 / Systems
Selected systems, not vague bullet points.
The work that suits me best usually lives in the messy middle: real users, real constraints, and systems that need to deliver more than a polished screenshot.
Vertical SaaS / Founder-led build
Suitflow
I'm building a wedding-focused operating system for formalwear shops so fittings, tailoring, communication, and billing stop living across disconnected tools.
Problem
Most shops still manage complex wedding workflows with spreadsheets, texts, memory, and generic CRM tooling.
Built
Multi-tenant product architecture, core frontend and backend systems, auth, payments, messaging, reporting, and release operations.
Why it matters
The product is shaped around actual store operations, which makes it faster to use and easier to trust on busy days.
AI Knowledge Systems
AI intranet, LMS, and workflow tooling
At Garmann Miller, I co-lead internal AI initiatives that centralize knowledge, improve training, and make AI more useful in day-to-day work.
Problem
Good AI ideas fall apart when knowledge is scattered, governance is unclear, and people do not trust the rollout.
Built
System design, use-case evaluation, cloud AI infrastructure, governance patterns, and cross-functional delivery for internal platforms.
Why it matters
The result is better onboarding, easier information access, and AI that feels grounded in actual work instead of hype.
Workflow Automation
Operational routing, onboarding, and handoff systems
I've designed internal automations for preboarding, onboarding, communications, and project information routing across teams.
Problem
Manual handoffs create hidden delays, duplicate effort, and onboarding that depends too much on whoever remembers what.
Built
Maintainable workflows with clear notifications, business logic, and operational visibility instead of one-off scripts nobody wants to own.
Why it matters
Teams move faster, fewer details get dropped, and the system keeps helping after the original project excitement wears off.
02 / Proof
How I like to work.
I do my best work when a team needs somebody who can zoom from strategy into implementation without losing the operational details.
01
Start with workflow, not tech.
I want to know who owns the work, where it breaks, and what "better" means before I get attached to a tool or architecture.
02
Make AI earn its place.
If AI adds latency, risk, or confusion without changing outcomes, it should not be in the system. I care about fit, not novelty.
03
Ship the whole system.
Product, infrastructure, reliability, permissions, monitoring, support, and rollout all matter. Production is part of the design.
04
Keep leaders and users aligned.
I like translating between executives, operators, and technical teams so the build has sponsorship, context, and a chance to stick.
Tools I reach for
Broad enough to move across the stack without pretending every problem needs the same answer.
React
TypeScript
Node.js
Python
C#
SQL Server
Azure
AWS
GitHub Actions
Stripe
RAG
Automation
NIST
Observability
03 / Timeline
Career route.
My path started in IT and cybersecurity, which is why uptime, supportability, and safer defaults show up in the software I build.
Software Developer / AI Lead
Leading internal AI and software initiatives across knowledge systems, governance, workflow tooling, and adoption.
Founder & Full-Stack Engineer
Building a vertical SaaS platform end to end across product, engineering, infrastructure, billing, and production readiness.
Founder / Owner
Delivering AI automations, software systems, and web experiences for small to mid-sized businesses.
IT Manager (Technology Administrator)
Owned infrastructure, cybersecurity, vendor relationships, and reliability in a manufacturing environment where downtime had immediate cost.
Information Technology Intern
Built early internal tooling, improved support workflows, and developed the operational foundation that still shapes how I ship software.
04 / Field Notes
Curiosity outside of work feeds the work too.
The mountain photos are here on purpose. I like long drives, hard trails, new cities, and places that clear your head.
That same part of me is why I enjoy technical work that starts fuzzy and gets better through observation, iteration, and staying calm when the route changes.
Hiking
Backpacking
Travel
Reading
Woodworking
Weightlifting
Music
Favorite Reset
White Mountains
Fourteen hours one way, late November weather, and still one of the easiest trips to recommend.
Perspective Shift
Travel that changes your pacing.
Trips abroad and time away from routine are a reliable way for me to come back with better questions and cleaner priorities.
Side Quest
The maps stay.
They are not the main point of the portfolio, but they are a truthful one: I like exploring, and that curiosity carries into the work.
United States
States visited
0
/
0
Visited
Not yet
World
Countries visited
0
/
0
Visited
Not yet
05 / Contact
If the work needs range, ownership, and follow-through, let's talk.
Open to connect
I'm especially useful in roles and projects that need someone who can move between strategy, engineering, and operational execution.
That can mean internal AI systems, workflow-heavy software, founding engineer work, or technical leadership where the job is not just to build something, but to help it stick.
AI Systems
Internal Tools
Founding Engineer
Workflow Automation
Technical Leadership