I build AI-powered software — and run the projects that ship it.
11+ years of enterprise PM/BA experience, now building production AI products for regulated industries — insurance and public adjusting — using modern no-code and low-code tooling.
Production products, shipped end-to-end.
Click any project to expand the full case study — problem, build, stack, and current status.
Problem
Homeowners and small public adjusting firms routinely misread carrier policy language, leading to underpaid claims and missed coverages. Existing tools either require a specialist on staff or oversimplify to the point of being misleading in a regulated context.
What was built
- Mobile app with policy upload, parsing, and conversational AI advisory
- Role-based experiences for consumers vs. licensed public adjusters
- Subscription billing with Stripe and entitlement-gated AI features
- Five-layer compliance architecture covering consumer protection, privacy, financial services disclosures, AI transparency, and professional advisory disclaimers
- Identity and phone verification flow for adjuster accounts
Full stack
Status
iOS Build 15 submitted to TestFlight. Android live on Google Play internal testing. Compliance architecture reviewed against state-level public adjuster regulations.
Problem
Solo founders juggling 3-5 projects waste hours context-switching between generic PM tools that assume a team. They need a workspace that treats each venture as a first-class environment without forcing them into per-seat pricing or enterprise complexity.
What was built
- Multi-workspace data model with isolated project, task, and note scopes
- Single-operator UX optimized for fast capture and weekly review
- Stripe-powered subscription with self-service billing portal
- Authentication, RLS policies, and tenant isolation
Full stack
Status
Live in production with active paying subscribers.
Problem
Public adjusters reviewing carrier estimates line-by-line against a 60-page policy lose hours per claim and still miss coverages. The work is pattern-matching at scale — a task language models do well when constrained correctly.
What was built
- Document ingestion for carrier estimates and policy declarations
- Coverage-gap analysis using Claude with structured prompting
- Reviewable diff output with citations back to policy sections
- Disclaimer and audit-trail layer for professional use
Full stack
Status
Build complete. Held for strategic release timing alongside MPAI distribution.
Problem
Small service businesses lose leads in the first hour after inquiry. Off-the-shelf SMS tools either ignore A2P 10DLC carrier registration requirements or wrap it in agency pricing that doesn't fit a single operator.
What was built
- Embeddable lead capture form with webhook delivery
- Automated SMS follow-up sequences with opt-out handling
- A2P 10DLC brand and campaign registration workflow
- Carrier-compliant message templates and audit logging
Full stack
Status
In production. Currently refining carrier-level messaging compliance and deliverability.
A decade of regulated-enterprise delivery.
Wells Fargo
Project / Business Analysis — Financial Services
- Coordinated cross-functional delivery across operations, technology, risk, and compliance stakeholders in a regulated enterprise environment.
- Gathered and translated business requirements into actionable specifications for engineering and operations partners.
- Led process-improvement initiatives that reduced manual handoffs and tightened control evidence for audit.
- Drove project governance — status, risks, dependencies, and decision logs — across multi-quarter initiatives.
Certifications
Google Project Management Certificate
AWS Certified AI Practitioner
Amazon Web Services
Generative AI for Project Managers
IBM
Domain expertise from the inside out.
I'm a public adjuster in training, building software for the exact industry I'm training to work in. That gives my products a practitioner's understanding of claims handling, policy language, and carrier dynamics that most software builders don't have — and means my compliance decisions come from inside the regulated workflow, not from a research memo.
Practitioner perspective
Training as a public adjuster — not a software outsider guessing at the workflow.
Compliance-aware by default
Consumer protection, privacy, AI disclosure, and professional advisory disclaimers built in from day one.
Enterprise delivery rigor
A decade inside financial services — the muscle for shipping in regulated environments carries over.
Why I do this work.
I spent over a decade inside enterprise financial services running project and business analysis work — the kind where shipping anything means navigating risk, compliance, technology, and operations in the same week.
Over time it became clear that regulated industries were being poorly served by software: tools were either built for engineers who didn't understand the workflow, or for the workflow by people who couldn't ship. I started building directly to close that gap, using modern no-code and low-code tooling to move at the speed the problems actually demand.
I'm pursuing a public adjuster license now because I'd rather deepen the domain expertise from the inside than guess at it from outside. The products I'm building are for the industry I'm training to work in.
Let's talk.
Two paths below — pick whichever fits. Both reach me directly.
Employment opportunities
Hiring for a senior PM, BA, or technical PM role — especially in regulated industries or AI product teams? Let's see if it fits.
Business inquiries
Want a product built for a regulated workflow, or thinking about using one of the live products below? Start here.