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

System workspace Workflow
Practical systems Clarity

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.

01 Dashboards Status, activity, and metrics shaped into views people can act on.
02 Workflows CRM, compliance, project, and handoff paths that keep the process moving.
03 Websites Public sites that explain clearly, load cleanly, and turn interest into contact.

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

New proposal Owner, next step, due date Ready
Search result Company record matched

Pipeline

Client activity Outlook notes and Teams context Review

Follow-through

Saved export Filtered package Queued
Reminder Follow-up assigned

Website work

Public-facing sites are a separate lane from the internal systems work: brand fit, clarity, speed, and trust.

Public website

Live

Live Wire Fireworks

Open live site

Retail brand site built around visual impact, product paths, and event-season urgency.

Retail pathBrand impactSeasonal urgency

Public website

Live

Michael's Painting & Drywall

Open live site

Local service site shaped around trust, clear offerings, and a faster path to contact.

Local trustService clarityLead path

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.

First security spark Xbox hardware research JTAG-era console research, tooling, and exploitation concepts.
First coding class Web fundamentals High school HTML and JavaScript turned curiosity into code.
Completed B.S. Computer Science Montana State University Bozeman
In progress M.S. Cybersecurity Security direction layered onto the systems foundation.
CSCI 468

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
CSCI 455

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
CSCI 443 / 445

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
M.S. direction

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

Tell me what you're trying to build.

Static form for now. Submitting opens a prepared email draft.