I've done a few hackathons. Never placed. My contribution always stopped at the slide deck — I could define the problem, shape the pitch, make it look good. But I couldn't ship anything.
That used to be the ceiling.
Building with AI as a designer broke it. This was our first real deployment — and we got it live, got recognized, and landed 3rd place. Eight hours, two people, one shot.
Something I'm actually proud of.
Every company with remote employees in more than one state has a compliance problem. Most just don't know it yet. The laws change weekly. The handbook doesn't. The gap is where penalties come from.
Not a chatbot. Not a compliance checklist. A full workflow tool that handles the entire lifecycle of a policy update — from the moment a regulation changes to the moment employees are informed. Every change is version-logged with a full audit trail — who edited, who approved, when, and which regulation triggered it.
Section 4.1 — Employees are entitled to accrued paid sick leave beginning on the 30th day of employment, up to 24 hours per year. Sick leave may be used for personal illness, care of family, or safe leave purposes.
Section 4.2 — Notice of intended leave must be provided to a direct supervisor at least 14 days in advance where foreseeable, and as soon as practicable otherwise.
Section 4.3 — Retaliation of any kind is prohibited under federal and state law. Employees may file a complaint with HR or directly with their state Department of Labor.
The thing that makes Canon different isn't the workflow — it's what the AI actually knows. This is the part I'm most proud of.
I wanted Canon to feel like something you command, not something you file paperwork into. The brief I gave Claude: private jet UX. HR should feel like they're running compliance, not drowning in it.
This is what actually got done, hour by hour, between the coffee, snacks and the pitch.
Building something real in 8 hours forces every decision to be intentional. There's no time to second-guess the design system, or the name (still noy sure how we landed on CANON) no time to refactor the component architecture, no time to bikeshed the copy. You make a call and you ship it.
The regulatory monitoring space is genuinely broken for mid-market HR teams, and the technology to fix it — live APIs, capable language models, structured approval workflows — all exists right now. We built a proof of concept in 8 hours. A production version is a matter of scope, not possibility.
(Internal joke that keeps on giving, it was only two of us, but if definitely felt like 4)

Handled product vision, Problem Statement, UX architecture, the full frontend, the pitch deck, and the landing page.

Built the FastAPI backend, integrated the Federal Register API, and engineered the Claude AI pipeline powering Canon's gap analysis and policy generation.
Policy OS for HR teams. Monitor. Compare. Update. Communicate. Compliance in 30 seconds — not 14 hours.