Dashboards, workflows, and public websites
I turn messy work into usable software.
I build practical tools for CRM, compliance, telemetry, planning, and public-facing sites: clean interfaces, guarded workflows, and dashboards people can act on.
See the system previews here
Dashboards, workflows, and sites.
- CRM and proposal flow
- Compliance and file handoffs
- Telemetry and planning views
Useful software
Should feel clear, safe, and finished.
The point is not another pretty screen. It is working software for records, files, follow-ups, customer paths, and decisions that cannot stay scattered.
Fig 0.2
Operational dashboards
Scattered records, proposals, renewals, projects, and field status become focused screens people can use without hunting through tabs.
Fig 0.3
Private work stays controlled
Compliance records, exports, files, and operator actions need guardrails. I think through the review path before the risky click exists.
Fig 0.4
Interfaces people trust
Complex tools need clean hierarchy, fast paths, and enough polish that users and clients can believe in the system from the first screen.
Build with confidence. The right interface makes the next step obvious: what changed, what needs attention, and who can act.
System previews
Four previews of the work I can build.
CRM, compliance, telemetry, and planning dashboards are shown as public-safe previews so you can see the interface thinking without exposing private data.
What this shows
Proposal work in one place.
- Company, contact, proposal, task, file, note, and history flow.
- Search, exports, integrity checks, and dashboard widgets.
- Outlook notes and Teams handoffs for follow-through.
Operations CRM
CRM
Incoming
Pipeline
Follow-through
Website work
Public-facing sites are a separate lane from the internal systems work: brand fit, clarity, speed, and trust.
Live Wire Fireworks
Open live siteRetail brand site built around visual impact, product paths, and event-season urgency.
Michael's Painting & Drywall
Open live siteLocal service site shaped around trust, clear offerings, and a faster path to contact.
Academic range
Computer science depth, now pointed at security.
The security direction started before school: hardware curiosity, research, and early exposure to exploitation concepts. Montana State turned that interest into formal systems work: compilers, robotics, interfaces, networks, and security.
Compiler construction
Built CatScript compiler work in Java, including tokenizer and recursive-descent parser pieces, with bytecode direction documented as the strongest current school artifact.
- Parsing and language structure
- Machine-oriented reasoning
- Low-level implementation discipline
Robotics and embedded behavior
Built a Raspberry Pi and servo-based robot with movement, vision, and OpenAI-connected speech capability.
- Hardware and software integration
- Autonomous behavior constraints
- AI-assisted interaction layer
Human-centered interface work
Interface and HCI coursework shaped the product side: clearer hierarchy, better interaction paths, and software that stays usable under real pressure.
- Usability and design rationale
- Interactive system evaluation
- Front-end judgment
Security, systems, and networks
The cybersecurity master’s direction builds on computer systems, networks, systems administration, and computer security coursework.
- Security-minded software decisions
- Network and systems context
- Private workflow discipline
Connect
Let's make the next system easier to use.
The cleanest public paths are email, LinkedIn, and the detailed resume. Other public profiles can be added once they are ready to point somewhere real.
Contact form